The openEHR Developers' workshop

Shinji Kobayashi^a, Ian McNicolMcNicoll^b,c, Xudong Lu^cd, Christian Chevalley^de

^_aThe EHR Research Unit, Kyoto University, Japan,

^bHandiHealth^copenEHR Foundation, ^c CHIME UCL

^d Biomedical Engineering Department of Zhejiang University

^deADOC Software

Abstract

The openEHR project is well-known for publishing and updating a set of open specifications to build maintainable 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 environment where the authoring and review process gathers views and concensus from a breadth of clinical specialities. The openEHR archetypes are often used as a source of clinical requirements gathering also in non-archetype-based systems and interoperability standards.

...

• 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 insi inside 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 existing (previously published/available/discussed) approaches to implementing openEHR; persistence solutions, APIs, programming languages, open source core reference implementnations implementations (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.

...

• Shinji Kobayashi, MD, PhD - Kyoto University, Japan
• McNicoll, Ian, MSc, MBChB - UCL CHIME, openEHR, London, openEHRUK
• Lu, Xudong,Professor of Medical Informatics in Biomedical Engineering Department of Zhejiang University, China.
• Chevalley, Christian, Founder and Technical Director, ADOC Software,Thailand

...