Health Level Seven
hl7Definition
ISO-11179 Definition
Health Level Seven International (HL7) is the global standards development organization responsible for the most widely used healthcare data exchange standards in the world. Founded in 1987, HL7 has produced multiple generations of healthcare interoperability standards: HL7 Version 2 (v2), the message-based standard still used in the vast majority of EHR-to-system interfaces; HL7 Version 3 and Clinical Document Architecture (CDA), the XML-based document exchange standards used for structured clinical documents like CCDs and discharge summaries; and FHIR (Fast Healthcare Interoperability Resources), the modern RESTful API-based standard now mandated by CMS and ONC regulations. HL7 v2 messaging remains the dominant clinical interface standard used in US hospitals despite being over 35 years old, primarily because the installed base of v2 interfaces across EHRs, lab systems, radiology systems, and clinical applications is enormous and the standard works reliably for event-driven point-to-point messaging.
An HL7 v2 message is a pipe-delimited text file structured as a series of segments: the MSH segment contains message metadata (sending system, receiving system, message type, timestamp, message control ID); ADT messages (A01-A60) carry patient admission, discharge, and transfer events; ORM messages carry laboratory and radiology orders; ORU messages carry result observations; and DFT messages carry detailed financial transactions. Healthcare data engineers encounter HL7 v2 messages when building integration pipelines between clinical systems and analytical platforms. The primary engineering challenge is that HL7 v2 is highly configurable — different EHR implementations use non-standard segment structures, custom Z-segments, and local code systems that deviate from the base standard, making generic parsers unreliable without site-specific configuration.
Engineers implement HL7 v2 parsers using libraries such as HAPI (Java), hl7apy (Python), or Mirth Connect integration engines, then transform parsed message data into structured staging tables. Key segments for analytical use include PID (patient demographics), PV1 (visit/encounter data), OBX (observation results with LOINC codes and values), DG1 (diagnosis codes), and IN1/IN2 (insurance information). HL7 FHIR represents the next-generation replacement for v2 in new implementations, though v2 will remain operational across legacy systems for decades.
Standard Abbreviation
hl7
Category
Production DDL — DIM_SYSTEM
CREATE OR REPLACE TABLE DIM_SYSTEM (
sys_key INTEGER NOT NULL -- surrogate key,
sys_id VARCHAR(50) NOT NULL -- system identifier,
sys_nm VARCHAR(200) NOT NULL -- system name,
sys_type_cd VARCHAR(50) -- system type code,
sys_vrsn VARCHAR(50) -- system version,
vndr_nm VARCHAR(200) -- vendor name,
intfc_type_cd VARCHAR(50) -- interface type code,
intfc_proto_cd VARCHAR(20) -- interface protocol,
env_cd VARCHAR(20) -- environment code,
host_nm VARCHAR(200) -- hostname,
ip_addr VARCHAR(45) -- IP address,
sts_cd VARCHAR(20) -- status code,
eff_dt DATE NOT NULL -- effective date,
exp_dt DATE -- expiration date,
rec_creat_dt TIMESTAMP NOT NULL -- record created date
);
Standard Snowflake DDL for the canonical technology table. Convert to BigQuery or Databricks →
Why This Term Matters
Healthcare data terminology is foundational for any data engineer working in this industry. Precise understanding of standard terms enables accurate schema design, reduces downstream data quality issues, and ensures pipelines meet the regulatory and interoperability requirements imposed by HIPAA, HL7 FHIR, and CMS reporting frameworks. Without this foundation, even technically well-built pipelines produce data that fails validation when it reaches payers or regulators.
Related Content
Looking for more healthcare terms?
Browse our complete library of 100,000+ standardized healthcare data terms
Browse All Terms