Health Information Exchange (HIE) Overview
Health Information Exchange (HIE) refers to the electronic sharing of health-related information among organizations according to nationally recognized standards. HIE enables clinicians, patients, and other authorized users to access and share patient information across different healthcare settings, improving care coordination and reducing duplicative testing.
HIE Models
| Model | Description | How It Works |
|---|---|---|
| Directed Exchange | Point-to-point secure messaging between known, trusted providers | A provider sends patient information directly to another provider using secure, encrypted messaging (similar to secure email). Used for referrals, care transitions, and lab result delivery. Relies on the Direct Standard protocol. |
| Query-Based Exchange | On-demand access to patient information from other organizations | A provider searches for and retrieves patient data from other sources when needed, typically during unplanned care events (e.g., emergency department visits). Requires a centralized or federated record locator service. |
| Consumer-Mediated Exchange | Patient-controlled access to health information | Patients manage and control their own health data, aggregating information from multiple providers. Supports patient engagement through personal health records (PHRs) and patient portals. |
Interoperability Levels
The Healthcare Information and Management Systems Society (HIMSS) defines four levels of interoperability:
| Level | Definition | Example |
|---|---|---|
| Foundational | Ability to send and receive data between systems without requiring the receiving system to interpret the data | Sending a PDF document from one system to another; the document can be received but cannot be parsed by the receiving system |
| Structural | Defines the format, syntax, and organization of data exchange so that data fields can be interpreted at the field level | HL7 v2 messages with defined segments and fields; the receiving system can parse individual data elements (patient name, date of birth) |
| Semantic | Provides shared meaning of data through common vocabularies and coding systems, enabling clinical interpretation | Using SNOMED CT and LOINC codes so that both sending and receiving systems understand the clinical meaning of data elements |
| Organizational | Includes governance, policy, social, legal, and organizational considerations that enable secure and timely communication | Data use agreements, trust frameworks, consent management policies, and business associate agreements that support exchange |
Health Data Standards
| Standard | Type | Purpose |
|---|---|---|
| HL7 Version 2 (v2) | Messaging | Most widely implemented healthcare messaging standard; uses pipe-delimited segments (e.g., ADT, ORM, ORU messages) for real-time data exchange between systems (admissions, orders, results) |
| HL7 FHIR (Fast Healthcare Interoperability Resources) | API-based exchange | Modern, RESTful API-based standard using resources (Patient, Observation, Condition, etc.); supports web and mobile applications; uses JSON and XML formats; designed for ease of implementation |
| HL7 CDA (Clinical Document Architecture) | Document | XML-based standard for clinical documents; defines structure and semantics of clinical documents for exchange |
| C-CDA (Consolidated CDA) | Document | Standardized set of CDA templates including Continuity of Care Document (CCD), discharge summaries, progress notes, and care plans; required for Promoting Interoperability |
| ASC X12 (HIPAA transactions) | Administrative/Financial | Standards for electronic administrative transactions: 837 (claims), 835 (remittance), 270/271 (eligibility), 276/277 (claim status), 278 (authorization) |
| NCPDP | Pharmacy | National Council for Prescription Drug Programs; standards for pharmacy claims, eligibility, and e-prescribing (SCRIPT standard) |
| DICOM | Imaging | Digital Imaging and Communications in Medicine; standard for medical imaging data exchange, storage, and display (radiology, cardiology, pathology imaging) |
Clinical Terminology Standards
| Standard | Purpose |
|---|---|
| ICD-10-CM/PCS | Diagnosis and inpatient procedure classification |
| CPT/HCPCS | Outpatient and physician procedure/service coding |
| SNOMED CT | Comprehensive clinical terminology for EHR documentation; covers diseases, findings, procedures, body structures |
| LOINC | Logical Observation Identifiers Names and Codes; standard for laboratory tests and clinical observations |
| RxNorm | Standard nomenclature for clinical drugs and drug delivery devices |
| NDC | National Drug Code; identifies drugs in commercial distribution (manufacturer, product, package) |
ONC and Federal Health IT Initiatives
- Office of the National Coordinator for Health IT (ONC): Federal entity responsible for coordinating nationwide health IT efforts, developing standards, and promoting interoperability
- 21st Century Cures Act: Addresses information blocking; requires healthcare providers, health IT developers, and health information networks to share patient data without unreasonable barriers
- Information Blocking: Practice that interferes with the access, exchange, or use of electronic health information; subject to penalties and enforcement by ONC and OIG
- USCDI (United States Core Data for Interoperability): Standardized set of health data classes and elements required for nationwide interoperability; replaces the Common Clinical Data Set
TEFCA (Trusted Exchange Framework and Common Agreement)
TEFCA is a framework established by ONC to create a universal governance and technical floor for nationwide health information exchange.
- Establishes a common set of principles, terms, and conditions for HIE
- Enables exchange through Qualified Health Information Networks (QHINs) that agree to the Common Agreement
- Supports multiple exchange purposes including treatment, payment, operations, public health, individual access, and government benefits determination
- Aims to simplify connectivity by reducing the need for individual point-to-point agreements
- The Recognized Coordinating Entity (RCE) administers the Common Agreement on behalf of ONC
Direct Messaging
- Secure, encrypted, point-to-point messaging protocol based on SMTP (email) standards
- Uses digital certificates to authenticate senders and receivers
- Supports exchange of C-CDA documents, lab results, referral communications, and care summaries
- Managed through Health Information Service Providers (HISPs) that issue Direct addresses and manage security certificates
- Does not require a centralized data repository - information flows directly between participants