HL7 FHIR

HL7 FHIR
Name	HL7 FHIR
Caption	Fast Healthcare Interoperability Resources
Developer	HL7 International
Initial release	2014
Latest release	R5 (2023)

HL7 FHIR HL7 FHIR is a standard for exchanging healthcare information electronically, designed to enable interoperability among healthcare systems, vendors, and applications. It emphasizes modular "Resources", RESTful APIs, and modern web technologies to facilitate data sharing across clinical, public health, and research domains. FHIR aims to bridge legacy healthcare standards and contemporary software ecosystems used by stakeholders such as hospitals, laboratories, regulators, and health IT vendors.

Overview

FHIR defines a set of granular, interoperable building blocks called Resources that represent clinical, administrative, and infrastructural concepts used by organizations like World Health Organization, Centers for Medicare and Medicaid Services, United States Department of Veterans Affairs, National Health Service (England), and private vendors such as Epic Systems Corporation, Cerner Corporation, Allscripts, McKesson Corporation. The standard leverages specifications and technologies from groups including Internet Engineering Task Force, W3C, IHE (Integrating the Healthcare Enterprise), and OpenEHR to support use cases ranging from electronic health records to mobile health, clinical decision support, and population health management. Major stakeholders such as Philips, Siemens Healthineers, GE Healthcare, Google, Microsoft, and Apple Inc. have built implementations or tools that interoperate using the FHIR model.

History and Development

FHIR was initiated by HL7 International in response to limitations observed with previous standards like Health Level Seven V2, Clinical Document Architecture, and HL7 Version 3 during interoperability efforts with organizations such as Centers for Disease Control and Prevention, Office of the National Coordinator for Health Information Technology, European Commission, and national programs in Australia and Canada. Early development drew on web architecture principles promoted by Roy Fielding and standards from W3C including XML, JSON, and HTTP. Pilot projects and connectathons involving participants like Boston Children's Hospital, Mayo Clinic, Cleveland Clinic, Kaiser Permanente, Intermountain Healthcare, and vendors refined core concepts leading to normative releases and the R4 and R5 editions that influenced regulatory and procurement frameworks in jurisdictions like United Kingdom National Health Service, US Food and Drug Administration, and European Medicines Agency.

Architecture and Core Concepts

FHIR's architecture centers on Resources, RESTful APIs, and a layered approach combining base semantics with profiles and extensions. It adopts web standards such as RESTful API, JSON, XML, and OAuth 2.0 while aligning with vocabularies and terminologies from authorities like SNOMED International, LOINC, ICD-10, RxNorm, and HL7 Vocabulary. Core concepts include Resources, Bundles, Profiles, Extensions, Operations, and Terminology Services, enabling modularity for systems developed by organizations like Google Cloud, Amazon Web Services, Microsoft Azure, Oracle Corporation, and research groups at Stanford University and Massachusetts Institute of Technology.

Resources and Data Models

Resources represent clinical entities such as Patient, Observation, Condition, Medication, and Encounter, and administrative entities like Practitioner, Organization, and Appointment. The model supports linking to coding systems and value sets maintained by SNOMED International, Regenstrief Institute, World Health Organization, United States Pharmacopeia, and regional authorities. Complex constructs like CarePlan, DiagnosticReport, and FamilyMemberHistory allow integration with clinical registries used by institutions such as Johns Hopkins Hospital, Dana-Farber Cancer Institute, Mount Sinai Health System, and international research consortia including The Global Alliance for Genomics and Health.

Implementation and Profiles

Implementers create profiles and Implementation Guides to constrain core Resources for local or domain-specific needs, a practice adopted by national programs like US Core Implementation Guide, Argonaut Project, SMART on FHIR, Da Vinci Project, and regional efforts in Norway, Denmark, and Germany. Healthcare vendors and integrators such as Redox, InterSystems, Orion Health, and academic groups build middleware, SDKs, and SMART applications that use profiles to ensure semantic interoperability across electronic health record platforms from Epic Systems Corporation, Cerner Corporation, and cloud providers like Google Cloud Platform and Amazon Web Services.

Security, Privacy, and Compliance

FHIR implementations commonly use security mechanisms standardized by organizations like IETF and W3C, including OAuth 2.0, OpenID Connect, and TLS, to meet legal and regulatory requirements from bodies such as Health Insurance Portability and Accountability Act, General Data Protection Regulation, European Commission, Office for Civil Rights (HHS), and national health authorities. Threat modeling, consent management, and audit logging integrate with identity providers like Okta and Auth0 and access control frameworks used by providers such as Mayo Clinic and Cleveland Clinic to satisfy compliance regimes and accreditation standards from Joint Commission and regional oversight agencies.

Adoption and Use Cases

FHIR is used in EHR integration, patient-facing apps, clinical decision support, public health reporting, research data exchange, and device interoperability. Real-world deployments include national health information exchanges in United Kingdom, Estonia, Canada, and projects by Centers for Medicare and Medicaid Services for quality reporting, research collaborations at Broad Institute, and startup ecosystems involving Flatiron Health, 23andMe, Tempus Labs, and digital health companies such as Babylon Health and Teladoc Health. FHIR-enabled apps leverage app platforms like SMART on FHIR and clinical APIs in vendor marketplaces.

Governance and Standards Integration

HL7 International governs the development through committees, workgroups, and ballot processes, coordinated with standards bodies like ISO, IEC, IHE, W3C, and regulatory agencies including FDA and EMA. The governance model includes normative cycles, open-source reference implementations, and community events such as connectathons that bring together academic centers like University of Oxford, professional associations like American Medical Association, and industry consortia to align FHIR with existing standards such as DICOM, IHE Profiles, CEN standards, and national policy frameworks.

Category:Health informatics standards