Fast Healthcare Interoperability Resources
|Base standards||JSON, XML, RDF|
|Domain||Electronic health records|
The Fast Healthcare Interoperability Resources (FHIR, pronounced "fire") standard is a set of rules and specifications for exchanging electronic health care data. It is designed to be flexible and adaptable, so that it can be used in a wide range of settings and with different health care information systems. The goal of FHIR is to enable the seamless and secure exchange of health care information, so that patients can receive the best possible care. The standard describes data formats and elements (known as "resources") and an application programming interface (API) for exchanging electronic health records (EHR). The standard was created by the Health Level Seven International (HL7) health-care standards organization.
FHIR builds on previous data format standards from HL7, like HL7 version 2.x and HL7 version 3.x. But it is easier to implement because it uses a modern web-based suite of API technology, including a HTTP-based RESTful protocol, and a choice of JSON, XML or RDF for data representation. One of its goals is to facilitate interoperability between legacy health care systems, to make it easy to provide health care information to health care providers and individuals on a wide variety of devices from computers to tablets to cell phones, and to allow third-party application developers to provide medical applications which can be easily integrated into existing systems.
FHIR provides an alternative to document-centric approaches by directly exposing discrete data elements as services. For example, basic elements of healthcare like patients, admissions, diagnostic reports and medications can each be retrieved and manipulated via their own resource URLs.
|2011-08-18||-||The initial draft of FHIR, then known as Resources For Healthcare (RFH), was published on Grahame Grieve's blog in Australia|
|2011-09-11||-||The standard was adopted by Health Level Seven International (HL7) as a work item|
|2014-09-30||0.082||DSTU1 (First Draft Standard for Trial Use) official version published|
|2015-10-24||1.0.2||DSTU2 (Second Draft Standard for Trial Use) official version published|
|2019-10-24||3.0.1||STU3 (Third Standard for Trial Use) included coverage of a variety of clinical workflows, a Resource Description Framework format, and a variety of other updates|
|2019-10-30||4.0.1||Release 4 has the First Normative Content and Trial Use Developments|
|2023-03-26||5.0.0||Release 5 |
FHIR is organized by resources (e.g., patient, observation). Such resources can be specified further by defining FHIR profiles (for example, binding to a specific terminology). A collection of profiles can be published as an implementation guide (IG), such as The U.S. Core Data for Interoperability (USCDI). The ONC anticipates finalizing USCDI v4 in July 2023.
Because FHIR is implemented on top of the HTTPS (HTTP Secure) protocol, FHIR resources can be retrieved and parsed by analytics platforms for real-time data gathering. In this concept, healthcare organizations would be able to gather real-time data from specified resource models. FHIR resources can be streamed to a data store where they can be correlated with other informatics data. Potential use cases include epidemic tracking, prescription drug fraud, adverse drug interaction warnings, and the reduction of emergency room wait times.
Global (non country specific)
A number of high-profile players in the health care informatics field are showing interest in and experimenting with FHIR, including CommonWell Health Alliance and SMART (Substitutable Medical Applications, Reusable Technologies).
A variety of applications were demonstrated at the FHIR Applications Roundtable in July 2016. The Sync for Science (S4S) profile builds on FHIR to help medical research studies ask for (and if approved by the patient, receive) patient-level electronic health record data.
In January, 2018, Apple announced that its iPhone Health App would allow viewing a user's FHIR-compliant medical records when providers choose to make them available. Johns Hopkins Medicine, Cedars-Sinai, Penn Medicine, NYU-Langone Medical Center, Dignity Health and other large hospital systems participated at launch.
In 2014, the U.S. Health IT Policy and the Health IT Standards committees endorsed recommendations for more public (open) APIs. The U.S. JASON task force report on "A Robust Health Data Infrastructure" says that FHIR is currently the best candidate API approach, and that such APIs should be part of stage 3 of the "meaningful use" criteria of the U.S. Health Information Technology for Economic and Clinical Health Act. In December 2014, a broad cross-section of US stakeholders committed to the Argonaut Project which will provide acceleration funding and political will to publish FHIR implementation guides and profiles for query/response interoperability and document retrieval by May 2015. It would then be possible for medical records systems to migrate from the current practice of exchanging complex Clinical Document Architecture (CDA) documents, and instead exchange sets of simpler, more modular and interoperable FHIR JSON objects. The initial goal was to specify two FHIR profiles that are relevant to the Meaningful Use requirements, along with an implementation guide for using OAuth 2.0 for authentication. 
A collaboration agreement with Healthcare Services Platform Consortium (now called Logica) was announced in 2017. Experiences with developing medical applications using FHIR to link to existing electronic health record systems clarified some of the benefits and challenges of the approach, and with getting clinicians to use them.
In 2020, the U.S. Centers for Medicare & Medicaid Services (CMS) issued their Interoperability and Patient Access final rule, (CMS-9115-F), based on the 21st Century Cures Act. The rule requires the use of FHIR by a variety of CMS-regulated payers, including Medicare Advantage organizations, state Medicaid programs, and qualified health plans in the Federally Facilitated Marketplace by 2021. Specifically, the rule requires FHIR APIs for Patient Access, Provider Directory and Payer-to-Payer exchange.
Proposed rules from CMS, such as the patient burden and prior authorization proposed rule (CMS-9123-P), further specify FHIR adoption for payer-to-payer exchange. The CMS rules and Office of the National Coordinator for Health IT (ONC) Cures Act Final rule (HHS-ONC-0955-AA01) work in concert to drive FHIR adoption within their respective regulatory authorities.
Further, other agencies are using existing rule-making authority, not derived from the Cures Act, to harmonize the regulatory landscape and ease FHIR adoption. For example, the U.S. Department of Health and Human Services (HHS) Office of Civil Rights (OCR) has proposed to update the HIPAA privacy rule (HHS–OCR–0945–AA00) with an expanded right of access for personal health apps and disclosures between providers for care coordination. Unlike the CMS and ONC final rules, the OCR HIPAA privacy proposed rule is not specific to FHIR; however, OCR's emphasize on standards-based APIs clearly benefits FHIR adoption.
In 2020, Brazil's Ministry of Health, by the IT Department of the SUS, started one of the world's largest platforms for national health interoperability, called the National Health Data Network, which uses HL7 FHIR r4 as a standard in all its information exchanges.
In 2020, Israel's Ministry of Health began working towards the goal of promoting accessibility of information to patients and caregivers through the adoption of the FHIR standard in health organizations in Israel. Its first act was to create the IL-CORE work team in order to adapt the necessary components for localization and regulation in the health system in Israel. The ministry, in cooperation with the Nonprofit Organization 8400, created the FHIR IL community, whose purpose is to encourage the adoption of the standard in the Israeli healthcare system while cooperating with healthcare organizations and the industry. As part of a joint activity of the Ministry and 8400, a number of projects were launched for the implementation of FHIR in health management organizations (HMO) and hospitals, alongside other projects that are being independently promoted by healthcare organizations. In addition, the Ministry of Health allocated budgets to the HMOs and other organizations for the purpose of establishing organizational FHIR infrastructure. In the 2020 Eli Hurvitz Conference on Economy and Society, run by the Israel Democracy Institute it was estimated that the cost of implementing central FHIR modules of in the Israeli healthcare system is estimated at about 400 million NIS over 5 years. In 2023, the Israeli government began a legislative process to promote the sharing of information between organizations in the Israeli health ecosystem for the benefit of the patient, with an emphasis on patient empowerment and reduced information blocking. The proposed legislation also refers to the need to standardize the data by adopting the FHIR standard and utilizing standard terminologies, such as SNOMED-CT, both in source systems and in the data exchange process. The sharing of information will be with the patient's consent, and this consent will be given according to data buckets.
- "Welcome to FHIR". HL7.org. 1 November 2019. Retrieved 12 February 2021.
- Grahame Grieve (18 August 2011). "Resources For Health: A Fresh Look Proposal". Health Intersections. Retrieved 22 August 2019.
- René Spronk (11 August 2016). "Five years of FHIR". Ringholm. Retrieved 22 August 2019.
- "All Published Versions of FHIR". hl7.org. Retrieved 17 December 2022.
- "HL7 Fast Healthcare Interoperability Resources Specification 'FHIR™', Release 1". HL7 International. 2 February 2014. Archived from the original on 28 December 2014. Retrieved 26 December 2014.
- "HL7 publishes a new version of its FHIR specification". Healthcare IT News. 22 March 2017. Retrieved 30 March 2017.
- "History - FHIR v4.0.1". hl7.org. Retrieved 17 December 2022.
- "Directory of published versions". hl7.org. Retrieved 10 October 2023.
- "Fast Healthcare Interoperability Resources® (FHIR)". eCQI Resource Center.
- "Draft U.S. Core Data for Interoperability (USCDI) and Proposed Expansion Process" (PDF). USA HHS. Retrieved 27 November 2019.
- "USCDI ONDEC". www.healthit.gov. Retrieved 30 May 2023.
- "What is FHIR? And what does it mean for Healthcare IT Monitoring?". 28 August 2015. Retrieved 28 August 2015.
- Dan Munro (30 March 2014). "Setting Healthcare Interop On Fire". Forbes. Retrieved 22 November 2014.
- "Geisinger moves to mobilize its EHR platform". mHealthNews. 11 November 2014. Retrieved 6 December 2014.
- "Open Source FHIR implementations - HL7Wiki". Archived from the original on 20 December 2014. Retrieved 6 December 2014.
- "Mix of Applications at Showcase to Demonstrate FHIR's Potential | David Raths | Healthcare Blogs". www.healthcare-informatics.com. Retrieved 13 September 2016.
- "Precision medicine: Analytics, data science and EHRs in the new age". 15 August 2016. Retrieved 13 September 2016.
- "Apple announces solution bringing health records to iPhone". Apple Newsroom. Retrieved 9 August 2018.
- "EHR interoperability solution offered by key IT panels". Modern Healthcare. 16 October 2014. Retrieved 8 November 2014.
- "Proposed interoperability overhaul finds boosters, doubters". Modern Healthcare. 21 October 2014. Retrieved 8 November 2014.
- "Federal HIT Committees OK Public API Recommendations to ONC". Healthcare Informatics. 15 October 2014. Retrieved 8 November 2014.
- "Teams Make their Pitch for Defense EHR Contract". Health Data Management. 7 November 2014. Retrieved 8 November 2014.
- "HL7 Launches Joint Argonaut Project to Advance FHIR" (PDF). HL7 International. 4 December 2014. Archived from the original (PDF) on 28 December 2014. Retrieved 26 December 2014.
- "Kindling FHIR". Healthcare IT News. 4 December 2014. Retrieved 6 December 2014.
- "Can Argonaut Project Make Exchanging Health Data Easier?". InformationWeek. 26 January 2015. Retrieved 28 February 2015.
- "Halamka: Expect Argonaut Deliverables by May". healthcare-informatics.com. 19 February 2015. Retrieved 28 February 2015.
- "HL7 Teams with Healthcare Services Platform Consortium on FHIR Development | Healthcare Informatics Magazine | Health IT | Information Technology". www.healthcare-informatics.com. Retrieved 30 March 2017.
- "Top Ten Tech Trends 2017: Slow FHIR: Will a Much-Hyped Standard Turbo-Charge Interoperability—Or Maybe Not Quite? | Healthcare Informatics Magazine | Health IT | Information Technology". www.healthcare-informatics.com. Retrieved 30 March 2017.
- "CMS Interoperability and Patient Access final rule | CMS". www.cms.gov. Retrieved 22 September 2020.
- "CMS Proposes New Rules to Address Prior Authorization and Reduce Burden on Patients and Providers". www.cms.gov. Retrieved 21 May 2021.
- "ONC 21st Century Cures Act Final Rule". www.healthit.gov. Retrieved 21 May 2021.
- "HHS Proposes Modifications to the HIPAA Privacy Rule to Empower Patients, Improve Coordinated Care, and Reduce Regulatory Burdens". www.hhs.gov. 10 December 2020. Retrieved 21 May 2021.
- "RNDS – Ministério da Saúde" (in Brazilian Portuguese). Retrieved 10 November 2020.
- "Israel Core". fhir-il-community.org. 7 August 2022. Retrieved 7 August 2022.
- "FHIR In Israel – An Overview". outburn.co.il. 28 February 2022. Retrieved 7 August 2022.
- "מוכנות מערכת הבריאות למצבי משבר" (PDF). idi.org.il. 16 December 2020. Retrieved 7 August 2022.
- "תזכיר חוק ניוד מידע בריאות, התשפ"ג-2023". www.tazkirim.gov.il. 24 January 2023. Retrieved 14 February 2023.
- "Everything You Need To Know About The Health Data Mobility Law". outburn.co.il. 2 February 2023. Retrieved 14 February 2023.
- Braunstein, Mark L. (11 February 2022). Health Informatics on FHIR: How HL7's API is Transforming Healthcare. Health Informatics. Springer Cham. p. 470. doi:10.1007/978-3-030-91563-6. ISBN 978-3-030-91563-6. S2CID 246705195. Retrieved 8 August 2022. History of FHIR with many detailed examples of applications, including Apple Health, Apple Watch, and EHR integrations.
- FHIR Standard (latest release)
This article is a direct transclusion of the Wikipedia article and therefore may not meet the same editing standards as LIMSwiki.