openEHR is a virtual community working on means of turning health data from the physical form into electronic form and ensuring universal interoperability among all forms of electronic data. The primary focus of its endeavour is on electronic health records (EHR) and related systems.
The term 'eHealth', which encompasses the use of information and communication technologies in health care, has become inseparable from the vision of modern health care in future. In the last 15 years, many approaches towards 'making eHealth happen' have been developed and many eHealth projects of various scale and success have been implemented. The experience with eHealth projects concerning EHR systems showed that there are a number of major recurring challenges.
The first problem usually occurs during the course of the project and involves lack of the clinical input from the health practitioners who are the end users of the system. This may be for different reasons, such as a lack of health professional consultants in the company implementing the project, inability to communicate properly in the mixed teams of IT and health professional or simply the scale of health knowledge required for a given project unforeseen during the project planning and budgeting. The result is very often the production of EHR system that causes difficulties to health professionals in their daily work and sometimes even coupled documentation.
The second problem arises shortly after the deployment of the system, even in cases when the first problem is completely avoided. Because of health procedures and health data being not static but developing with the progress in medicine, sooner or later a content change in EHR system would be required. EHR systems whose software design was inspired by software design practices in other areas, usually suffer from inseparability of structure and content, which requires major input from project implementer every time a change need to be realised.
The third problem concerns long time horizon, when limits of system scalability and interoperability are exposed only when systems need to be deployed in the large scale and in conjunction with other systems.
All these problems are addressed and reflected in the approach proposed by openEHR community. The endeavour of this community is coordinated and promoted by openEHR Foundation.
The openEHR approach is multi-level, single source modelling within a service-oriented software architecture, in which models built by domain experts are in their own layer. It is delineated by a set of specifications published by the openEHR Foundation.
The foundational artefact of the openEHR approach is its reference model - a very stable information model that defines the logical structures of EHR and demographic data. All EHR data in any openEHR system obey this reference model. The openEHR Foundation provides the reference model specification, which is a formal, logical definition of the information, not the concrete physical data schema.
The next level consists of a library of data points/data groups that are independent of particular use – these are called archetypes. The creation of a library of use-independent data points removes the need for modelling the same data point more than once. The international library of openEHR archetypes (CKM) currently contains about 500 archetypes, or 6,500 data points. Another advantage is that these archetypes can be modelled by clinical professionals or health informatics experts without any technological knowledge of the final EHR systems. The openEHR approach also allows to make use of external health terminologies, such as SNOMED CT, LOINC and ICDx in the modelling process. The openEHR Foundation provides the archetype model specification and also tools for their authoring and editing.
At the next level, the data-points and data-groups are assembled into context-specific data sets – it could be the data for a form, a particular message, or a document. In openEHR, these are called templates. All openEHR systems are built with templates, which contain the relevant bits of various archetypes. Templates preserve the paths of archetype elements they use, even within variable depth structures. Templates are usually developed by implementers local to the solution being built, but it is also possible to build a standard template for a country, e.g. a discharge summary. The tools for template design and editing are provided by the openEHR Fondation.
The last level, closest to the user are template-generated artefacts, such as application program interfaces, XSDs, UI forms. These artefacts are used by application developers. The openEHR Foundation provides the operational template specification.
The essential outcome of the openEHR approach is systems and tools for computing with health information at a semantic level, thus enabling true analytic functions like decision support, and research querying.
There are some key benefits to openEHR's approach. Firstly, it is now possible to build an EHR repository independently of content specifications. In other words, your EHR system doesn't need to know a priori about any of the clinical data it will process, such as vital signs, diagnoses or orders. Models for those things are developed separately. Models for data sets and forms are also developed separately, and UI form components are generated from these definitions. This enables a new generation of EHR systems that routinely adapts to new requirements - because that's how the architecture is designed in the first place.
Secondly, building software is now very different. Significant parts of the software are now generated by tools from the templates, reducing the amount of work to do, and greatly improving semantic traceability. Model-generated code and UI (user interface) is an area of continual innovation in openEHR, and promises to revolutionise health computing.
Components and systems conforming to openEHR are 'open' in terms of data, models and APIs. They share the key openEHR innovation of adaptability, due to the archetypes being external to the software, and significant parts of the software being machine-derived from the archetypes. The archetype specification is now an ISO standard (ISO 13606-2). These are now being used by several national governments to specify national e-health information standards.
Strategically, the openEHR approach enables a platform-based e-health software market, in which vendors and developers of back-end and front-end solutions interface via standardised information models, content models, terminologies and service interfaces. This gives procurement stakeholders new choices, enabling them to:
It also allows application developers to concentrate on their applications, and simply plug in to a reliable back-end.
The openEHR White Paper provides a more detailed discussion of the advantages of an open, extensible health computing platform.
This website will give you information on how it all works, and how to become a member of openEHR. The openEHR approach offers opportunities and value to many different stakeholders, including clinicians, health care providers, governments, software developers and research institutions.
Are you a clinician or health care provider? You can help creating and reviewing the archetypes. Are you a message designer? You may want to get involved in building template-based message specifications, based on the archetypes. Are you a software vendor or developer? You can help build the new generation of EHR tools. If you are a researcher, you can get involved in specifying how openEHR querying, published terminologies and standards like CDISC can be used to improve how longitudinal data-based studies are done. Maybe you want to obtain tools and solutions? You will find vendor solutions, as well as open source components. If you are from the government institution, the openEHR approach can provide a platform to integrate your local eHealth systems.