This is the home page for documenting how HL7 FHIR can be integrated with openEHR. 'FHIR' stands for Fast Health Interoperable Resources, and is a new HL7 specification, designed around the concept of web-available XML resources served through REST services. Resource definitions are customised for local use by 'profiles'.
One of the questions for openEHR is how to integrate the content and APIs we use with FHIR. There are various aspects to this. The dimensions of the question appear to be:
- what does a combined openEHR / FHIR architecture look like?
- can FHIR be archetyped (i.e. in principle)? If so, it can be model driven; if not, we are in for a models => formats mapping exercise.
- how to convert openEHR archetypes into FHIR resources (profiles)?
- how to serve openEHR data as FHIR resources?
- how to integrate a FHIR REST service with openEHR APIs?
Work on these questions is just starting. Below are links to the current state of activities on these topics.
An openEHR / FHIR Architecture
TBD
Can FHIR be Archetyped?
Some initial investigations into archetyping for FHIR have started, as follows:
- Using ADL/AOM 1.5 to implement flexible archetyping for FHIR
Converting openEHR Archetypes to FHIR Resource Definitions
Converting openEHR Data to FHIR Resources