HL7 v2 Message Parser & Viewer
Paste or load a pipe-delimited HL7 v2.x message to read every segment, field, component, and subcomponent with human-readable labels. PHI never leaves your browser — all parsing is client-side.
HL7 v2 anatomy: each line is a segment (MSH, PID, PV1, OBR, OBX…). Fields are separated by |, components by ^, repetitions by ~, and subcomponents by & — all declared in MSH-1/MSH-2.
This parser shows structure and common field labels; it is not a conformance validator against a specific HL7 version or implementation guide. For FHIR resources, use the FHIR Resource Viewer.
Frequently asked questions
Is my patient data (PHI) uploaded or stored?
No. Parsing runs entirely in your browser — the message never touches a server, so real PHI can be inspected without leaving the machine. You can verify this in the browser's network tab or use the tool offline.
Which HL7 versions are supported?
All pipe-delimited HL7 v2.x messages (2.1 through 2.9) — the parser reads the version from MSH-12 and the delimiters from MSH-1/MSH-2 automatically. FHIR resources (JSON) are a different standard — use the FHIR Resource Viewer for those.
Can I open .hl7 or .er7 files?
Yes — use the file loader to open .hl7, .er7, or .txt exports directly from an interface engine or hospital system. The file is read locally and never uploaded.
Is this an HL7 validator?
It performs structural checks — delimiter consistency, required MSH fields, segment ordering — and decodes every field with labels. It is not a conformance validator against a specific implementation guide or message profile.
What is the difference between HL7 v2 and FHIR?
v2 is the legacy pipe-delimited format that still runs most intra-hospital messaging (ADT, ORU, ORM); FHIR is the modern resource-based standard for APIs, usually JSON over REST. Our HL7 v2 vs FHIR comparison covers when to use each, and the v2 message anatomy guide explains segments and delimiters in depth.