The following areas have been identified as priorities for the openEHR Clinical Program. The order of importance determined later by CPB, to create the roadmap.

Archetype Development

• accelerate rate of review of existing v0 international archetypes

• democratise & scale modelling effort, and organise, probably via Work Groups;

  • reduce editorial and other bottle-necks slowing down archetype production

  • better outreach:

    • Calling for more clinical modellers and health professionals to join the community during the discussions, trying to cover most of the specialties

    • try to reduce archetype silos forming in vendors - try to facilitate re-use as much as possible

  • strategies to obtain funding and resource-in-kind

  • use Affiliates to help scale clinical requirements gathering, modelling and dissemination

• investigate other CKMs / vendor archetype silos for merge, reuse etc

  • see e.g. discussions on Discourse

  • particularly Cambio GDL-related archetypes - consider how to re-engineer these GDLs; project page for a start to bring these archetypes into CKM

  • Nedap local archetypes repo

Governance

• review intellectual property (IP) safety/risk of archetypes, particularly scores, scales, terminology bindings

• good integration with other openEHR Programs (Specification, Software, and Education) to work together and discuss issues in periodic meetings.

• Priority integration with Educational program to capacitate more people to work with openEHR standards, help create modelling training materials etc

• Creation of working groups (WGs) based on individual's expertise and projects e.g. cardiology, pediatrics, PROMS, scores, ...

• more transparent project definition and management

• Establishment of a governance team to maintain CKM quality

Technology

• migrate CKM to ADL2

• migrate modelling eco-system - human and tools - to ADL2, to enable use of proper specialisation, ADL2 templates with overlays, translations, and many other ADL2 improvements.

  • For some time, ADL1.4 OPTs will need to be supported for runtime systems;

  • Migration can be done progressively, with support for ADL2 <=> ADL1.4 inter-conversion, already supported by many tools.

• better support for (partly) generating 'implementation guides', including dependency maps or similar (see Infrastructure & Tooling)

Methodology

• review current archetype modelling style guideline (current version)

• review all Clinical content on the openEHR wiki, particularly to do with archetype lifecycle, using CKM, etc.