About us
Clinicians
Providers
Research
Developers
Newsfeed

Oslo Nov 2018 SEC meeting report

Community News | Nov. 17, 2018, 3:05 p.m.

The recent Specifications Editorial Committee (SEC) meeting in Oslo (meeting page), generously hosted and provided for at the offices of DIPS, made great progress, including:

  • The REST APIs were finalised, and will be published as Release-1.0.0 in the next 10 days.
    • these interfaces make it easy to create HL7 FHIR interfaces above openEHR systems.
  • The Implementation Technology Specifications (ITS) component was re-organised into separate sub-repositories, now published and undergoing final adjustments:
    • REST - the REST APIs (apiary files and generated documents) (Github repo)
    • XML - the openEHR XML schemas (Github repo)
    • JSON - an initial JSON-schema for openEHR Reference Model (Github repo)
    • BMM - the openEHR BMMs for RM and Task Planning (Github repo)
  • RM Release-1.0.4 was agreed and is nearly complete; we expect the final release in the next 10 days. See here for change list (23 CRs).
    • this release fixes a number of minor annoyances and improves documentation, all changes based on production system feedback.
  • RM Release-1.1.0 was agreed and will follow quickly. See here for change list (8 CRs).
    • this release extends the FOLDER model to support episode modelling, and also extends the demographic model.
  • The BMM (Basic Meta-Model), ODIN (Object Data Instance Notation) and EL (Expression Language) specifications were moved form BASE to a new component, LANG.
    • this reduces the BASE component to basic specifications that underpin the rest of the openEHR model eco-system.
  • Global UML site updated to reflect these changes.

Detailed discussions were held on AQL, and we expect to upgrade it soon to handle server-side functions, some form of joins, and logical reference-following.

The next SEC meeting is expected in February or March 2019, for which Cambio has offered to host in Stockholm. The main topics of this meeting are likely to be:

Implementation work based on the openEHR specifications is now rapidly increasing, and development of automated conformance testing is underway. Improvements to reducing the work for developers using archetypes, templates and terminology is also ongoing.

We hope these activities will benefit the openEHR community and the wider healthcare sector.






>> Back to Community News