...
The openEHR project is well-known for publishing and updating a set of open specifications to build maintinable and semantically interoperable (and even intraoperable) electronic health record systems that stay agile in a changing clinical reality. It is closely related to the family of ISO 13606 standards and to CIMI (now an HL7 WG). The detailed openEHR clinical models (archetypes and templates) are authored by global and regional clinical communities in an online enviromnment environment where the authoring and review process gathers views and concensus from a breadth of clinical specialities. The openEHR archetypes are archetypes are often used as a source of clinical requirements gathering also in non-archetype-based systems and interoperability standards (e.g.HL7 FHIR).
This workshop will introduce and discuss openEHR based implementations and integrations primarily from developer and systems-engineering perspectives. In recent years several different technical openEHR persistence implementation approaches have been published, two recent approaches using graph-databases and combinations of relational+schemaless databases will also be described and discussed. Developers in an openEHR context nowadays thus have access to both a wealth of detailed clinical models and a wealth of published approaches to technical implementation using various persitence solutions, APIs and programming languages.
...
The core technology of openEHR specification features a multi-level modeling system, often referred to as ‘archetype-based systems’. In this archetype-based technology, technical implementation is separated from the continuously updated detailed clinical modeling concerns in a way that makes it easier for implementers to maintain semantic intra- or interoperability. In this workshop introductioniintroduction, we will overview this:
- The openEHR reference model (RM) and the Archetype Model (AM) and associated specification documentations etc.
- Standardized approaches to clinical querying (AQL), REST-interfaces and Clinical Decision Support rules (GDL)
- The mix of people, process and technology; how using archetypes, templates, AQL and GDL etc. a as a basis in EHR systems enables agility in adapting to changing clinical needs and reduces maintenance time.
- Options on the spectrum between semantic intraoperability and interoperability. (By intraoperability we here refer to the possibility to align internal clinical EHR datamodels across organizational boundaries and between insi systems from different vendors - and thus easily share both data and share the workload of model authoring and maintenance.)
A quick overview of different exisiting (previously published/available/discussed) approaches to implementing openEHR; persistence solutions, APIs, programming languages, open source core reference implementnations (in e.g. Java, C#, Ruby, Eiffel)
- Comparing steps needed to implement archetype-based systems from scratch versus using/integrating existing openEHR based components and APIs
- A quick overview of where in the world openEHR is used.
...