📖 The F.H.I.R. Acronym
FHIR stands for Fast Healthcare Interoperability Resources. From this acronym we get several more hints about its nature than just it being a standard, with all implications that come with that.
FHIR claims to be FAST
The meaning of FAST in this context is that FHIR is fast to implement.
To implement something refers to the process of putting a plan into effect. It involves taking the steps that are necessary to carry out the project in a practical, real-world setting.
FHIR is fast to implement because it uses modern web standards like Restful APIs, JSON and XML. Developers are already familiar with them because of they are widespread used all industries. Also, the docs are user friendly and focus on helping with implementation.
FHIR being fast can also apply to performance. The architecture of FHIR is built to handle high volumes of data and transactions, enabling swift access and retrieval of healthcare information.
FHIR is Healthcare-specific
FHIR is tailored for the healthcare industry.
Interoperability
The term interoperability appears to have originated within the context of the military and defense industry in the mid 20th century. It was used to describe the ability of different weapons systems, units or forces to work together effectively.
By the 1970s and 1980s, interoperability had become a common term in IT and telecommunications.
In healthcare, it means that doctors, nurses, hospitals, apps, pharmacies all can exchange and understand each other's medical records even if they use different types of computer systems. This helps everyone work together to improve healthcare for their patients.
In the introduction for non-developers we already mentioned some every-day examples for (missing) interoperability like different units for temperature and distance, or incompatibility of a Microsoft Office Presentation in Libre Office impress.
These everyday examples illustrate how lack of interoperability can lead to confusion and errors. But when it comes to more critical fields like aerospace, healthcare, or defense, the consequences of poor interoperability can be far more severe.
Resources
The central role of FHIR is played by resources. They are predefined data structures that represent different healthcare entities.
Examples are:
Patient (https://hl7.org/fhir/patient.html )
Condition (https://hl7.org/fhir/condition.html )
Medication (https://hl7.org/fhir/medication.html )
Practitioner (https://hl7.org/fhir/practitioner.html )
For each resource, specific properties are defined. For example, a patient has a name, an address, an identifier, a birthdate, a gender and other characteristics.
These properties are like fields in a form that can be filled with the patient’s data. But unlike a paper form, a patient resource provides more flexibility and mechanisms to check if the data is correct or missing. Moreover, it is readable and understandable by a computer.
All information that is exchanged is packaged in a FHIR resource.
Patient data, medication data, terminologies, even technical info like the capability statement of a server that says what it can offer, are resources.
You can imagine as separate paper forms for different aspects of health care.
You will learn more about Resources in this learning unit.