MI7 FHIR (Fast Healthcare Interoperability Resources)

you don't have to worry about FHIR - we do.

FHIR (Fast Healthcare Interoperability Resources) is the latest iteration of the HL7 standard. HL7 has been providing data exchange protocols for healthcare data since 1988. FHIR is the latest of these protocols. FHIR was introduced in 2012, and as of 2019 version 4 is available with version 5 in the works.

Q is compatible with all current versions of FHIR and HL7. Simply implement our standardized JSON structure and you will be ready for FHIR.

Secret Agent Summary:

Like HL7 there will be multiple versions and multiple implementation methodologies.

Q is compatible with all current versions of FHIR.

FHIR Deeper dive

FHIR is healthcare's latest shiny coin. But what is it? FHIR brings the use of API's to clinical data exchange. More importantly, it defines standards for those API's. FHIR also brings JSON to the table by providing the data objects in JSON. These are important because they begin to bring healthcare IT departments into the 21st century, a decade late, but that is an improvement for the entire industry.

So FHIR solves all my integration to clinical data needs, right? No. What FHIR does is creates the basis for a more modern integration conversation. Now facilities with IT teams will converse about API's and JSON and hopefully more modern communication methodologies.

Like it's HL7 predecessors, FHIR only suggests standard ways of providing data. It is still modifiable by each implementor. This means that one EHR vendor or healthcare organization may only implement some of the FHIR API's or that they may not implement the entire API stack, or they may add their own extensions. All of these scenarios are happening today. The technical result of this is that organizations needing to integrate to a FHIR implementation will need to have knowledge of each implementation, and further will need staff resources to understand both the existing implementation and be prepared for changes.

FHIR, like HL7 and most industry driven de jur standards, is directed towards organizations who have large IT departments and budgets. In these past some of these implementations will trickle to the broader market but for the foreseeable future FHIR will be Healthcare IT's shiny coin.

Secret Agent Summary:

FHIR is still in infancy
FHIR does not address existing integrations or proprietary API's
FHIR is a set of standards but individual organizations may modify, limit, or exclude any parts
The industry is still challenged by multiple standards and data sharing methodologies

Where does this leave you?

The real question is, does FHIR solve your organizations need to exchange data with an EHR? The reality is, FHIR is simply another method of exchanging data. In the world of Healthcare IT there are nearly as many ways of exchanging data as there are EHR brands (over 900 by our count). While today FHIR has limited use in the field, over time it will most likely be used by more providers and software vendors. Like HL7 there will be multiple versions and multiple implementation methodologies. Further EHR vendors will continue to offer other data exchange methodologies such as, existing HL7 versions, DICOM (for imaging), folder based options, proprietary API’s, etc.

If you are focused on solving healthcare business problems and need access to clinical data, MI7 can help.

Q is FHIR ready

you don't have to worry about FHIR - we do.

FHIR Deeper dive

Where does this leave you?