As the interoperability standard HL7 format has evolved over the years, its use has opened up to current web practices such as HTML, XML and JSON.
This has led to the FHIR (Fast Healthcare Interoperability Resources) standard which broadens the field of possibilities with its library of open source resources.
FHIR is seen to be one way to help boost interoperability in healthcare and is defined as a standard describing data formats and elements (known as “resources”) and an application programming interface (API) for exchanging electronic health records (EHR).
Benefits can include making data sharing easier, it can be fast to implement and it is vendor-neutral.
To understand how and why the FHIR standard came into being, Frédéric Laurent, project manager at Enovacom, reflects on the origins of this interoperability standard.
This white paper outlines everything you need to know about HL7 FHIR.
Find out more below.
Read the full case study
Copyright: © Enovacom
The Porter Building, 4th Floor
Enovacom Contact: email@example.com
22 July 2021 @ 12:36
Fihr sounds to me, an aged patient who has been waiting for twenty tears for the hospitals which treat me, to transfer data seamlessly between each other and my GP, to be a comprehensive set of standards t achieve just that.
I also note that it and its predecessor, HL7, have been around a long time, and have the added bonus of being internationally accepted, and being accepted by NHS Digital.
As far as I know, FiHR is not being implemented by any of the four august London hospitals which have been treating me in the last year, endangering my safety and creating cost and inconvenience for the hospitals that treat me. I am curious to learn how widely Fihr has been implemented across the NHS.
My guess is :not widely. If so, why not, When something like Fihr has clearly been needed to drag us out of the fragmented “bottom-up” morass currently in place.