FHIR stands for Fast Healthcare Interoperability Resources (pronounced like fire) and is a standard for the secure exchange of electronic health care data. The standard was created by the Health Level Seven International (HL7) health-care standards organization.
A key reason for HL7 FHIR becoming a standard is its ability to facilitate the delivery of electronic product information (ePI/ePIL) as digital leaflets (e-leaflets) on mobile apps.
DCL plays a pivotal role in helping pharmaceutical companies adopt and implement FHIR standards effectively. DCL staff serve on the FHIR Working Group and support the development and maintenance of the FHIR specification.
As this standard gains momentum, we put together a list of FAQs to help you understand this specification better.
FHIR FAQs
What is FHIR?
FHIR (Fast Healthcare Interoperability Resources) is a standard developed by HL7 (Health Level Seven International) for exchanging healthcare information electronically. It enables the interoperability of healthcare systems using modern web technologies. A key reason for HL7 FHIR becoming a standard is its ability to facilitate the delivery of electronic product information (ePI/ePIL) as digital leaflets (e-leaflets) on mobile apps.
What makes FHIR different from other HL7 standards?
FHIR combines the best features of HL7's previous standards, such as HL7 v2, v3, and CDA, with the simplicity and flexibility of RESTful APIs and web technologies like JSON and XML.
Who created, develops, and maintains FHIR?
FHIR is developed and maintained by HL7 International, a global authority on standards for healthcare information technology. DCL staff serve on the working group that advises on the standard.
What is a FHIR "resource?"
A FHIR resource is a fundamental building block in FHIR. Each resource is a discrete piece of healthcare data, such as a patient, observation, or medication, and is defined with a standard structure and data elements.
What formats does FHIR support for data exchange?
FHIR supports data exchange in XML and JSON formats.
Is FHIR secure and safe for my pharma content?
Yes! FHIR relies on industry-standard security protocols, including OAuth2 for authentication and authorization and HTTPS for encrypted communication.
Why should my organization adopt FHIR?
FHIR is used for various purposes, including:
Exchanging electronic health records (EHRs)
Enabling mobile apps for healthcare by facilitating the delivery of electronic product information (ePI/ePIL) as digital leaflets (e-leaflets)
Supporting clinical decision support systems
Facilitating patient access to their data
Is FHIR mandatory for healthcare, pharma, life sciences organizations?
While not mandatory everywhere, many governments and organizations are adopting FHIR as a standard for healthcare data exchange. For example, in the U.S., the ONC’s 21st Century Cures Act mandates FHIR for certain interoperability requirements. Countries such as the US, Canada, and the UK have used FHIR extensively as a healthcare data standard framework.
How widely is FHIR used?
FHIR is widely adopted globally, with support from major healthcare organizations, technology vendors, and government initiatives.
Can FHIR integrate with legacy systems?
Yes, FHIR can act as a bridge to legacy systems by enabling data exchange through APIs while allowing the systems to remain operational during the transition.
Want to learn how your organization can take advantage of FHIR to enable the distribution of e-leaflets?