JA Technology Solutions
HL7 Message Explorer
Parse HL7 v2.x healthcare messages with segment descriptions, field labels, and message type identification.
HL7 Message Explorer
Parse HL7 v2.x healthcare messages into a structured view with segment descriptions and field labels. Supports ADT, ORU, ORM, and other common message types — navigate segments (MSH, PID, OBX, etc.) in a structured list with field counts and message hierarchy, then click any segment to inspect individual fields, components, and sub-components with HL7 data types and table references. The MSH header breakout shows sending and receiving applications, message type, trigger event, version, and encoding characters at a glance. View patient demographics, lab results, orders, and more with human-readable field names; export all segments and fields to CSV or Excel for interface mapping. Everything runs in your browser — no PHI is uploaded to any server.
Learn more ↓
Loading interactive explorer...
What Is HL7 v2.x?
HL7 (Health Level Seven) version 2.x is the most widely deployed healthcare data exchange standard in the world. It uses a pipe-delimited message format where each line is a segment identified by a three-character code: MSH (Message Header), PID (Patient Identification), OBR (Observation Request), OBX (Observation Result), and dozens more. The MSH segment defines the encoding characters, sending and receiving systems, message type, and version. Fields within segments are separated by |, components by ^, and sub-components by &. Despite being decades old, HL7 v2.x remains the backbone of most hospital system integrations.
Common HL7 Message Types
The most common message types include ADT (Admit/Discharge/Transfer) messages like ADT^A01 (admit) and ADT^A08 (update patient information), ORU (Observation Result) messages carrying lab results, ORM (Order) messages for placing lab or radiology orders, SIU (Scheduling) messages for appointment management, and MDM (Medical Document) messages. Each message type has a defined set of required and optional segments. Real-world implementations often include custom Z-segments for institution-specific data that does not fit the standard segment definitions.
Healthcare Integration Services
Healthcare IT environments typically involve dozens of systems — EHRs, lab information systems, radiology, pharmacy, billing — all exchanging HL7 messages through an integration engine. I build HL7 interfaces that parse, transform, route, and acknowledge messages between clinical systems, handling the real-world complexities of varying HL7 versions, custom segments, and site-specific field mappings. For the modern JSON-based standard, see the FHIR Resource Explorer. Learn about integration services or get in touch to discuss your healthcare integration needs.
All tools run entirely in your browser. Your data never leaves your machine. Need help? Ask James.