DataTerminology.comNEW
Also known as: Health Level 7 Version 2
A widely adopted healthcare messaging standard enabling the exchange of clinical and administrative data between systems.
DESCRIPTION
HL7 v2 is a delimited messaging standard used extensively in hospitals and labs for events like admissions, orders, and results. Messages comprise segments (e.g., MSH, PID, OBX) and are commonly transported via MLLP. Despite its age, HL7 v2 remains pervasive due to installed base and flexibility. Modern efforts often bridge v2 to FHIR for APIs while maintaining legacy interfaces.
ALTERNATIVE DEFINITIONS
HL7
HL7 Version 2 (V2) is a messaging standard used to exchange clinical data between healthcare systems.
Official product brief underscoring v2’s role in clinical data exchange.
CDC
HL7 V2 is a widely used standard for the exchange of health care data among information systems.
Public health authority stressing ubiquity and interoperability.
Wikipedia
HL7 Version 2.x is a messaging standard for clinical and administrative data.
Contextualizes HL7 v2 within the HL7 family of standards.
RELATED TERMS
Confirmatory Data Analysis Electronic Health Record ADT Message OBX Segment Object-Relational Mapping MLLP Interoperability IHE Profiles
COMPETING TERMS
HL7 FHIR HL7 v3
KNOWLEDGE AREAS
Data Integration & Interoperability Data Privacy & Compliance Domain & Business Context Data Management
TARGET AUDIENCE
Data Engineer Data Architect Solution Architect Software Developer Data Privacy Officer
EXTERNAL SOURCES
- Wikipedia - HL7
- HL7 - Official HL7 v2 product brief
- HL7 - HL7 v2 Implementation Guide example
- IHE - Profiles building on HL7 v2
TOP QUESTIONS
Why is HL7 v2 still widely used?
Its massive installed base and flexible event-driven design make it reliable for hospital workflows despite newer standards.
Category: Relevancy
How do HL7 v2 messages work?
They are delimited text segments like MSH, PID, and OBX, typically transported via MLLP over TCP.
Category: Definition
What are common mistakes with HL7 v2 integrations?
Assuming consistent profiles across vendors. Always validate segment usage and local Z-segments.
Category: Mistakes
How does HL7 v2 compare to FHIR?
v2 uses delimited messages; FHIR uses RESTful resources and JSON/XML. Bridges often map v2 events to FHIR resources.
Category: Alternatives
What security considerations apply to HL7 v2?
Use secure transport (TLS), access controls, and auditing; messages may contain sensitive PHI requiring strict handling.
Category: Risk
What is an ADT message in HL7 v2?
Admission, Discharge, and Transfer events; core to patient movement and demographic updates.
Category: Example
How do you test HL7 v2 interfaces?
Use test harnesses, validate against implementation guides, and simulate real workflows and edge cases.
Category: Requirements
Is HL7 v2 outdated?
While mature, it remains relevant. Many organizations modernize via FHIR while maintaining v2-based integrations.
Category: Opinion
What transport protocol is typical for HL7 v2?
MLLP is most common, providing simple envelope and acknowledgments over TCP.
Category: Definition