HL7 FHIR Use Cases
FHIR stands for Fast Healthcare Interoperable Resource. This emerging standard combines the best features of HL7 V2, HL7 V3, and CDA, while leveraging the latest web service technologies. The design of FHIR is based on RESTful web services. With REST... More has the potential to make needed changes to the way data is communicated across the healthcare spectrum. A major difference between An HL7 standard that is short for Fast Healthcare Interoperability Resources and pronounced “Fire”. The standard defines a set of “Resources” that represent granular clinical concepts. The resources provide flexibility for a range of healthca... More and other versions of HL7 is a Standards Developing Organization accredited by the American National Standards Institute (ANSI) to author consensus-based standards representing a board view from healthcare system stakeholders. HL7 has compiled a collection of message form... More is that data exchange using FHIR maintains a single source of truth, rather than having multiple versions of the same record propagated through systems via HL7 v2. This leads to greater flexibility and more timely access to accurate data for clinicians and patients alike. The two workflows below help demonstrate these advantages.
In this workflow, an HL7 v2 order message is sent to the lab via Corepoint Integration Engine. The lab then returns the order result using HL7 v2. Corepoint Integration Engine then takes the HL7 v2 order result message and stores it into a FHIR repository in the Electronic Health Record (EHR), as defined in Defining Key Health Information Technology Terms (The National Alliance for Health Information Technology, April 28, 2008): An electronic record of health-related information on an individual that conform... More.
Once in the EHR, the result data is available to anyone with the proper credentials. Clinicians can view the data using with their favorite app that uses FHIR. This eliminates having to use the lab portal or another extra system to view the results. The patients can also use a FHIR app to view the results. Similarly, there is no requirement that a patient needs to log onto the lab portal and keep up with one more password.
In this workflow, immunization data is sent to the state and stored in a FHIR repository. As in the previous example, this allows flexibility for both clinicians and patients to access immunization data.
Instead of having to log into a state-provided portal, clinicians and patients can use their favorite FHIR-capable healthcare app to view immunization records. This allows for flexibility in using an application that is familiar to the user, and allows accurate patient data to be integrated and viewed through one application.
There are many potential workflows that FHIR enables. Read about more use cases in our FHIR Primer.
Learn more about FHIR
Dave Shaver, Co-Chair of the HL7 FHIR Governance Board, provides an in-depth look at how FHIR will impact the future of health data exchange, including:
- What differentiates FHIR from other Health Standards?
- Where might FHIR be used?
- Where does FHIR go from here?
Download our HL7 FHIR primer as you plan a modern, integrated healthcare IT environment.