HL7 v2.x Parser

Vorian Connect parses HL7 v2.x messages from clinical analyzers with full support for multi-occurrence segments, vendor-specific dialect remapping, and automatic LOINC code enrichment. Every message gets a standards-compliant ACK or NACK — the instrument never waits on cloud delivery.

How It Works

What's Included

Where It Fits

The HL7 parser runs inside the Vorian edge agent, processing messages immediately after they arrive over MLLP. The parser feeds into the auto-verification engine (rules, ranges, delta checking) and the downstream delivery subsystem (webhook, MLLP forwarding, FHIR R4). It shares the same agent infrastructure as the ASTM E1381 parser — labs running a mix of HL7 and ASTM instruments use one agent, one install, one dashboard.

Parsed messages are available in the Trace Inspector as a double-pane view: raw HL7 text on one side, structured JSON on the other. Every field, segment, and LOINC enrichment is visible and searchable.

Technical Details (for evaluators)

The parser is written in Go and handles the full HL7 v2.x message structure — MSH through any terminal segment — with support for non-standard line endings (CR, LF, CRLF). Multi-occurrence segments (OBX, NTE, etc.) are preserved as ordered arrays in the parsed output. The parser rejects messages that do not begin with an MSH segment as required by the HL7 standard.

The dialect system maps instrument-specific field positions to a canonical namespace. For example, a Beckman Coulter AU analyzer might place the test code in a different OBX field than a Sysmex XN — the dialect layer normalizes both to OBX.<code>.value before the message reaches the rules engine. Adding support for a new instrument model requires only a dialect definition; no parser changes are needed.

The LOINC map covers 35 common chemistry, hematology, and immunoassay analytes. Each mapping includes the LOINC code, preferred display name, canonical UCUM unit, and flag label interpretation for abnormal result flags.

Last updated: May 15, 2026