> hl7_version_2.x_series
HL7 Version 2.x Series
Health Level Seven (HL7) Version 2 Messaging Standard
HL7 Version 2 is the workhorse of hospital integration engines, supporting event-driven data exchange across electronic health records (EHR), laboratory systems (LIS), radiology information systems (RIS), and billing software. Using pipe-delimited segment structures (MSH, PID, PV1, OBX), it enables real-time clinical workflows including patient admission (ADT), order placement (ORM), and observation reporting (ORU).
Scope & Applicability
Standard communication protocol for acute care hospital integration engines, interface engines (e.g. Mirth Connect), and clinical software.
Non-Coverage Boundaries
Does not use modern REST/JSON architectures (which are addressed by HL7 FHIR) and relies primarily on MLLP over TCP sockets.
Key Clauses & Control Requirements
Message Header (MSH) & Event Triggers
Defines encoding characters, sending/receiving applications, message timestamp, and trigger events (e.g. ADT^A01, ORU^R01).
Required Regulatory & Audit Evidence Artifacts
- [✓]HL7 v2 Interface Specification & Profile Document
- [✓]Integration engine message routing and error-handling logs
- [✓]Message acknowledgment (ACK/NACK) verification audit records
“Despite being decades old, HL7 v2 powers the vast majority of hospital backends. Any enterprise healthcare product must master HL7 v2 interface engines to survive in real hospital deployments.”
Cross-Surface Ecosystem Relationships
- HL7 Version 2 Product Family ↗(Health Level Seven International)
Frequently Asked Questions
What transport protocol does HL7 v2 typically use?
HL7 v2 messages are commonly transmitted using the Minimum Lower Layer Protocol (MLLP) over raw TCP/IP sockets.