Written and maintained by CASRAI Editorial Board
Last updated
Short answer: Healthcare interoperability is the technical and governance capability of disparate Electronic Health Record (EHR) systems, laboratory information systems, medical devices, and clinical research platforms to securely exchange, parse, and computationally act upon electronic health information (EHI) with preserved clinical meaning. In the United States, EHR interoperability is mandated by the 21st Century Cures Act (42 U.S.C. § 300jj(10)) and structured around the four-tier Healthcare Information and Management Systems Society (HIMSS) model, the United States Core Data for Interoperability (USCDI), HL7 FHIR APIs, and the Trusted Exchange Framework and Common Agreement (TEFCA).
What Is Healthcare Interoperability? Statutory Definition Under the 21st Century Cures Act
To establish an enforceable regulatory baseline for certified health IT developers, healthcare providers, and health information networks, Section 4003 of the 21st Century Cures Act (codified at 42 U.S.C. § 300jj(10) and implemented by the Assistant Secretary for Technology Policy / Office of the National Coordinator for Health IT [ASTP/ONC] at 45 CFR Parts 170 and 171) defines interoperability through three statutory criteria:
- No Special Effort: Enables the secure exchange of electronic health information with, and use of electronic health information from, other health IT without special effort on the part of the user (such as manual re-keying, custom point-to-point interface fees, or proprietary format translation).
- Complete Access, Exchange, and Use: Allows for complete access, exchange, and use of all electronically accessible health information (EHI) for authorized use under applicable State or Federal law.
- Absence of Information Blocking: Does not constitute “information blocking” under Section 3022(a) of the Public Health Service Act (45 CFR Part 171), which prohibits practices likely to interfere with, prevent, or materially discourage the access, exchange, or use of EHI unless covered by one of the statutory ONC Information Blocking Exceptions.
What Is Interoperability in Healthcare? The 4 HIMSS Levels Explained
Because moving a PDF fax over an encrypted connection is fundamentally different from ingesting a coded laboratory observation into an automated clinical decision support (CDS) algorithm, HIMSS and the National Academies classify interoperability in healthcare into four progressive levels:
| HIMSS Tier | Technical Definition | Core Standards & Protocols | Clinical & Research Capability |
|---|---|---|---|
| Level 1: Foundational Interoperability | Establishes basic transport connectivity allowing one health IT system to send a payload to another system, without requiring the receiving system to interpret the internal data structure. | Direct Project (SMTP with S/MIME X.509 certificates), HTTPS/TLS transport, SFTP, secure fax-to-PDF. | A clinician can view an external discharge summary PDF in an EHR media tab, but cannot automatically chart or compute on the values inside it. |
| Level 2: Structural (Syntactic) Interoperability | Defines the uniform syntax, data format, and field-level packaging of health data exchange so the receiving system can parse individual data elements without corruption. | HL7 v2.x (pipe-delimited ADT, ORU, ORM), HL7 C-CDA R2.1 XML templates, HL7 FHIR R4 RESTful JSON/XML resources, DICOM, ASC X12N 5010. |
An EHR or Electronic Data Capture (EDC) system parses discrete fields (such as Observation.valueQuantity) directly into structured database tables. |
| Level 3: Semantic Interoperability | Ensures both sending and receiving systems share an unambiguous clinical interpretation of the exchanged data by binding structural fields to standardized controlled vocabularies and ontologies. | SNOMED CT (clinical findings/procedures), LOINC (lab and clinical observations), RxNorm (normalized medications), ICD-10-CM/PCS, CPT/HCPCS, UCUM (units of measure). | Enables automated cross-institutional clinical decision support, drug–allergy checking, and multi-site observational research queries (e.g., OMOP Common Data Model). |
| Level 4: Organizational Interoperability | Encompasses non-technical governance, multilateral legal trust agreements, patient consent policies, and cross-network operational workflows across institutional boundaries. | ONC TEFCA (Common Agreement & QHIN Technical Framework), Carequality, CommonWell Health Alliance, eHealth Exchange. | Allows a hospital or authorized researcher to query nationwide health information networks under a single legal Common Agreement rather than negotiating thousands of bilateral BAAs. |
How EHR Interoperability Works in Practice: USCDI, FHIR R4, and TEFCA
Modern U.S. health system and clinical research architectures combine three federal pillars to operationalize Levels 2, 3, and 4 interoperability simultaneously:
- United States Core Data for Interoperability (USCDI): Maintained by ASTP/ONC and updated annually, USCDI defines the mandatory minimum dataset of standardized Data Classes (such as Allergies, Clinical Notes, Immunizations, Laboratory, Medications, Patient Demographics, Problems, Procedures, and Vital Signs) and constituent Data Elements that certified EHR technology must expose via APIs.
- ONC 45 CFR § 170.315(g)(10) Standardized API for Patient and Population Services: Requires every certified EHR vendor to provide a production HL7 FHIR Release 4 (R4) API conforming to the HL7 FHIR US Core Implementation Guide, secured via SMART App Launch (OAuth 2.0 / OpenID Connect) for single-patient and clinician-facing apps, and supporting FHIR Bulk Data Access (
$export) in NDJSON format for population-level cohorts and research registries. - CMS-0057-F Payer-to-Provider and Prior Authorization APIs: Extends FHIR R4 interoperability to Medicare Advantage, Medicaid, CHIP, and Qualified Health Plan issuers by mandating Patient Access, Provider Access, Payer-to-Payer, and Prior Authorization (HL7 Da Vinci CRD, DTR, and PAS) FHIR APIs.
Where Healthcare Interoperability Matters for Clinical Trials and Research
In clinical research informatics, achieving semantic and structural EHR interoperability transforms trial execution through the HL7 Vulcan FHIR Accelerator patterns:
- Automated EHR-to-EDC Data Capture: Instead of research coordinators manually transcribing dozens of laboratory values, vital signs, and concomitant medications from the hospital EHR into an Electronic Data Capture (EDC) form, SMART on FHIR research applications pull USCDI-coded FHIR
Observation,MedicationStatement, andConditionresources directly into CDISC ODM/SDTM pipelines. - Computable Cohort Identification: Standardized SNOMED CT, LOINC, and RxNorm bindings allow investigators to execute federated inclusion/exclusion queries across multi-center academic health networks without moving raw identifiable patient charts.
Common Misunderstandings About Healthcare Interoperability
- “Using FHIR automatically guarantees semantic interoperability”: False. HL7 FHIR R4 provides the structural JSON/XML resource schema (Level 2), but if a hospital populates
Observation.code.textwith local unmapped free-text strings instead of standard LOINC or SNOMED CT codes, the exchange remains syntactically valid yet semantically un-computable (failing Level 3). - “HIPAA prohibits health systems from sharing EHR data across different vendors”: False. The HIPAA Privacy Rule (45 CFR § 164.506) explicitly permits covered entities to disclose ePHI for Treatment, Payment, and Health Care Operations (TPO) without individual authorization, and the ONC Information Blocking Rule actively penalizes unjustified technical or administrative barriers to authorized EHI exchange.
Frequently Asked Questions
What is healthcare interoperability?
Under Section 4003 of the 21st Century Cures Act (42 U.S.C. § 300jj(10)) and HIMSS standards, healthcare interoperability is the ability of different health information technology systems, EHRs, medical devices, and research registries to securely access, exchange, integrate, and cooperatively use electronic health information within and across organizational boundaries without special effort by the user and without information blocking.
What are the 4 levels of interoperability in healthcare?
HIMSS defines four progressive tiers of healthcare interoperability: (1) Foundational Interoperability (basic transport connectivity from System A to System B), (2) Structural Interoperability (standardized message syntax and format such as HL7 v2, C-CDA, and FHIR R4), (3) Semantic Interoperability (shared clinical meaning using coded vocabularies such as SNOMED CT, LOINC, RxNorm, and ICD-10), and (4) Organizational Interoperability (legal governance, trust frameworks, and policy alignment such as TEFCA and Carequality).
Sources
- Assistant Secretary for Technology Policy / Office of the National Coordinator for Health IT (ASTP/ONC) — 21st Century Cures Act Interoperability, USCDI, and 45 CFR Parts 170–171 Standards
- Healthcare Information and Management Systems Society (HIMSS) — Interoperability in Healthcare: The Four-Level Framework
- HL7 International — HL7 FHIR Release 4 & US Core Implementation Guide Specifications
