Working with FHIR and OpenEHR

OpenEHR is emerging as a vendor-neutral standard for persistent healthcare data. It is increasingly adopted  for many applications in many jurisdictions, and has significant benefits – avoidance of proprietary lock-in, a growing selection of healthcare data models and archetypes, with easily shareable and long-lasting applications built around them, and a growing skillbase of vendors and developers.

At the same time, FHIR is now the leading standard for healthcare data exchange, and there is widespread agreement that FHIR and OpenEHR need to work together, rather than compete. Any OpenEHR application needs to live in a FHIR world, exchanging data with a host of other applications – which increasingly do so using FHIR.

The FHIR Transform Engine (FTE) has been built from the ground up to transform FHIR to and from any other healthcare data formats, and has specialised support for OpenEHR.  If you need to transform data between OpenEHR and FHIR (in either direction), then FTE, with its specialised support for both, is the most cost-effective way to do it. You can define, test and maintain high-quality transforms using the graphical FTE editor and fast testing tools – and deploy them in many ways, such as fast and flexible Java code, on FHIR servers, OpenEHR servers, or integration engines.

If you adopt both OpenEHR and FHIR, then FTE is the best way to bring them together. Most important, you will not be on your own. Starting with the commonest use cases, and moving on to others, transforms between FHIR and OpenEHR will be developed, easily maintainable, shareable  and adaptable – sharing the work to build long-lasting assets in a changing world.

‍