Fast Healthcare Interoperability Resources

Fast Healthcare Interoperability Resources (FHIR, pronounced "fire") is a standard describing 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.

Fast Healthcare Interoperability Resources (FHIR)
OrganizationHL7
Base standardsJSON, XML, RDF
DomainElectronic health records
LicenseCC0
AbbreviationFHIR
Websitehl7.org/fhir/

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, HTML and Cascading Style Sheets for user interface integration, a choice of JSON, XML or RDF for data representation, and Atom for results.[1] One of its goals is to facilitate interoperation 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. FHIR was supported at an American Medical Informatics Association meeting by many EHR vendors which value its open and extensible nature.[2]

Standardization

The initial draft of FHIR, then known as Resources For Healthcare (RFH), was published on Grahame Grieve's blog[3] in August 2011.[4]

In February 2014, Health Level Seven International published FHIR as a "Draft Standard for Trial Use" (DSTU), Release 1, version DSTU 1 (v0.0.82).[5]

In December 2014, a broad cross-section of stakeholders committed to the Argonaut Project[6] 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.[7] 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.[8] The initial goal, to be completed in time for the May 2015 HL7 FHIR Draft Standard for Trial Use revision 2 ballot, is 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. [9]

The CEO of HL7 argued in August 2016 that it already provided valuable features, was ready to use, and was being adopted.[10]

FHIR Release 3 was published in March 2017, as the first STU (Standards for Trial Use) release. It included coverage of a variety of clinical workflows, a Resource Description Framework format, and a variety of other updates.[11][12]

FHIR Release 4.0.1 was published on October 30, 2019.[12]

Architecture

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).[13]

Implementations

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).[14] In 2014, the U.S. Health IT Policy and the Health IT Standards committees endorsed recommendations for more public (open) APIs. The 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.[15][16][17][18]

Open source implementations of FHIR data structures, servers, clients and tools include reference implementations from HL7 in a variety of languages, SMART on FHIR[19] and HAPI-FHIR in Java.[20]

A variety of applications were demonstrated at the FHIR Applications Roundtable in July 2016.[21] 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.[22]

A collaboration agreement with Healthcare Services Platform Consortium (now called Logica) was announced in 2017.[23] 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.[24]

In January, 2018, Apple announced that its iPhone Health (Apple) 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.[25]

FHIR servers

A software package that implements a large number of FHIR features can be referenced as FHIR server.[26]

Implications for Health Informatics

Because FHIR is implemented on top of HL7 and the HTTPS (HTTP Secure) protocol, messages can be parsed by wire data analytics platforms for real-time data gathering. In this concept, healthcare organizations would be able to gather real-time data from specified segments in FHIR messages as those messages pass over the network. That data can be streamed to a data store where it can be correlated with other informatics data. Potential use cases include epidemic tracking, prescription drug fraud, adverse drug interaction warnings, and emergency room wait times.[27]

gollark: webm is just a subset of mkv.
gollark: mkv seems to be the nicest container format, but firefox is annoying and lacks support.
gollark: Also its file handling generally, I guess.
gollark: Discord's file extension handling is very annoying.
gollark: And encoding complexity.

References
  1. "Welcome to FHIR". HL7.org. 2016-05-15. Retrieved 2016-11-27.
  2. "SMART on FHIR a Smoking Hot Topic at AMIA Meeting". Healthcare Informatics. 2014-11-17. Retrieved 2014-11-22.
  3. Grahame Grieve (2011-08-18). "Resources For Health: A Fresh Look Proposal". Health Intersections. Retrieved 2019-08-22.
  4. René Spronk (2016-08-11). "Five years of FHIR". Ringholm. Retrieved 2019-08-22.
  5. "HL7 Fast Healthcare Interoperability Resources Specification 'FHIR™', Release 1". HL7 International. 2014-02-02. Archived from the original on 2014-12-28. Retrieved 2014-12-26.
  6. "HL7 Launches Joint Argonaut Project to Advance FHIR" (PDF). HL7 International. 2014-12-04. Archived from the original (PDF) on 2014-12-28. Retrieved 2014-12-26.
  7. "Kindling FHIR". Healthcare IT News. 2014-12-04. Retrieved 2014-12-06.
  8. "Can Argonaut Project Make Exchanging Health Data Easier?". InformationWeek. 2015-01-26. Retrieved 2015-02-28.
  9. "Halamka: Expect Argonaut Deliverables by May". healthcare-informatics.com. 2015-02-19. Retrieved 2015-02-28.
  10. HealthITInteroperability. "Health IT Standard FHIR Ready to Advance Interoperability". Retrieved 2016-09-13.
  11. "HL7 publishes a new version of its FHIR specification". Healthcare IT News. 2017-03-22. Retrieved 2017-03-30.
  12. http://hl7.org/fhir. "All Published Versions of FHIR". hl7.org. Retrieved 2017-03-30.
  13. "Draft U.S. Core Data for Interoperability (USCDI) and Proposed Expansion Process" (PDF). USA HHS. Retrieved 27 November 2019.
  14. Dan Munro (2014-03-30). "Setting Healthcare Interop On Fire". Forbes. Retrieved 2014-11-22.
  15. "EHR interoperability solution offered by key IT panels". Modern Healthcare. 2014-10-16. Retrieved 2014-11-08.
  16. "Proposed interoperability overhaul finds boosters, doubters". Modern Healthcare. 2014-10-21. Retrieved 2014-11-08.
  17. "Federal HIT Committees OK Public API Recommendations to ONC". Healthcare Informatics. 2014-10-15. Retrieved 2014-11-08.
  18. "Teams Make their Pitch for Defense EHR Contract". Health Data Management. 2014-11-07. Retrieved 2014-11-08.
  19. "Geisinger moves to mobilize its EHR platform". mHealthNews. 2014-11-11. Retrieved 2014-12-06.
  20. "Open Source FHIR implementations - HL7Wiki". Archived from the original on 2014-12-20. Retrieved 2014-12-06.
  21. "Mix of Applications at Showcase to Demonstrate FHIR's Potential | David Raths | Healthcare Blogs". www.healthcare-informatics.com. Retrieved 2016-09-13.
  22. "Precision medicine: Analytics, data science and EHRs in the new age". 2016-08-15. Retrieved 2016-09-13.
  23. "HL7 Teams with Healthcare Services Platform Consortium on FHIR Development | Healthcare Informatics Magazine | Health IT | Information Technology". www.healthcare-informatics.com. Retrieved 2017-03-30.
  24. "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 2017-03-30.
  25. "Apple announces solution bringing health records to iPhone". Apple Newsroom. Retrieved 2018-08-09.
  26. https://hapifhir.io/
  27. "What is FHIR? And what does it mean for Healthcare IT Monitoring?". 2015-08-28. Retrieved 2015-08-28.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.