Short answer: openEHR is an open specification for building the clinical record itself: a stable reference model, plus clinical models called archetypes and templates that clinicians can design without changing the software, and a query language (AQL). HL7 FHIR is a standard for exchanging data between systems through resources and REST APIs. Many organisations use openEHR to store and FHIR to share.
How openEHR works
The reference model defines generic structures (compositions, entries, data types). Archetypes define a clinical concept once, for example a blood pressure measurement with its position and cuff size; templates combine archetypes for a specific use, such as a diabetes review form. Data is queried with AQL across the whole record. Several European national and regional programmes use openEHR for clinical data repositories.
How FHIR differs
FHIR resources cover the 80 % of data most systems share, and profiles narrow them for a use case. FHIR is optimised for APIs and integration, with a large developer ecosystem. It can be used as a storage model too (a FHIR server), which is the approach of many apps and of FHIR backends.
In practice: openEHR when the main job is a rich, long-lived clinical record designed by clinicians; FHIR when the main job is to connect systems and apps. Mappings between openEHR templates and FHIR resources let both coexist.
In Anpheros
Anpheros stores the patient's record as HL7 FHIR R4, because its main job is to be read by other systems and apps with the patient's consent. Developers: FHIR vs a custom database and interoperability.
Related pages
Sources
Frequently asked questions
Is openEHR an alternative to FHIR?
Partly. openEHR focuses on modelling and storing the record; FHIR on exchanging it. They are often used together.
What is an archetype in openEHR?
A reusable clinical model of one concept, such as a blood pressure measurement, defined by clinicians.
Can I store data in FHIR?
Yes, many systems use a FHIR server as their database; others store in openEHR or their own model and expose FHIR.
Which one should a new app use?
If the main job is integration with other systems and apps, FHIR is usually the shorter path.
Try it free in the sandbox
Your first FHIR call in 5 minutes. An HL7 FHIR R4 API with the patient's consent built in: try it in the sandbox, then connect your own app or clinic system.
Free · 30 synthetic patients · no card
Anpheros builds a medical record that the patient controls and can share with any clinic, on an HL7 FHIR R4 platform, based in the EU. These guides help you understand and organise your health; they do not replace your doctor.
About Anpheros →
AnpherosThe more you log, the clearer your record
Your health history in one place, under your control.
Free · Works in your browser · No card
