...
The openEHR project(1) is well known as a development source for the ISO 13606 standards(2). These standards are considered the technology basis of clinical information models which enable the interoperability for electronic healthcare applications. A number of projects have been implementing the openEHR specifications with various approaches. Development projects related to the openEHR are spreading worldwide. The core reference implementation has been implemented using Eiffel and is recognized as a reference implementation of the openEHR specifications. Java and C# are also being used in a number of reference implementations. These core implementations are provided as open-source software. This momentum provided an evidence that the openEHR specification are being widely accepted and gaining worldwide interest. On this steady international growth, we are taking this opportunity to introduce these specifications to a wider audience and explain their features. Even though these projects are still ongoing and have not yet completed their missions, developers, whether they are involved in openEHR or not, will benefit from the sharing of experiences and discussions discussions about the implementation of the openEHR specifications.
2 The workshop structure and arguments
This workshop will be consisted with the following contents. At first, we introduce openEHR architectural overview and the second, each speaker make presentation of each projectInitially, we will provide an overview of the openEHR architecture. This is followed by a number of presentations introducing various - quite different - openEHR projects.
2.1 The openEHR architecture overview
...
To be able to exchange clinical information in a semantically safe way across different openEHR-based systems, it is important to agree on the clinical concepts . Ideallyused in these systems. In openEHR, such concepts (are formally expressed in openEHR archetypes ) are and developed in regional, national and international collaboration - regionally, nationally and internationally. It is crucial that clinicians - even without any knowledge of openEHR - are inherently involved in this process by being able to review and comment as required. Only this can ensure that the clinical content models are clinically valid and comprehensive. To enable this collaboration, the Clinical Knowledge Manager (CKM) has been developed as a web-based system for collaborative development, management, validation, review and publishing of openEHR archetypes and other clinical knowledge resources. CKM is used internationally by the openEHR foundation as well as in several regional and national programmes. CKM supports the 'federation' of archetypes, so that the various programmes can work independently and to their own timelines, while sharing arhcetypes archetypes with each other where possible.
...
- Shinji Kobayashi, MD, PhD - Kyoto University, Japan
- Pablo Pazos, Ingeniero en Computación, openEHR en español, CaboLabs, ACHISA
- Koray Atalag (Deactivated), MD, PhD, FACHI - University of Auckland, New Zealand
- Sebastian Garde, Dr. sc. hum., Dipl.-Inform. Med., FACHI - Ocean Informatics, Germany
- Ian McNicoll MBChB,MSc, HandiHealth CIC, UK
- Erik Sundvall, MSc, PhD - Linköping University and Region Östergötland, Sweden
...