ASTM E1381 / LIS2-A2 Parser
Vorian Connect ingests ASTM E1381 and CLSI LIS2-A2 messages from clinical analyzers and point-of-care devices. The parser handles frame-level transport, typed record extraction, and vendor-specific field remapping — all at the edge, before PHI leaves the lab network.
How It Works
- The edge agent listens for ASTM frames using the standard ENQ/ACK handshake with ASTM E1381 modulo-256 checksum validation
- Multi-frame messages are reassembled automatically — instruments that split long transmissions across multiple frames are handled without configuration
- Six record types are parsed into typed structures: H (header), P (patient), O (order), R (result), C (comment), L (terminator)
- A vendor dialect registry maps non-standard field positions to canonical names — the same result value that appears in field R.4 for one instrument and R.5 for another is normalized to
result_value - Unknown record types are silently skipped rather than rejected, keeping the pipeline resilient to vendor extensions
What's Included
- Frame transport layer: ENQ/ACK handshake, STX/ETX/ETB framing, ASTM E1381 modulo-256 checksum validation
- Typed record parser: H, P, O, R, C, and L records with named field accessors
- Dialect registry: Vendor-specific field remapping — map any
RECORDTYPE.Nposition to a canonical field name - Built-in dialects: Abbott AxSYM and a generic ASTM template with standard field mappings
- Dialect generation: The docbuilder can generate new Go dialect snippets from vendor implementation guides
- Escaped delimiter handling: ASTM escape sequences (
&F&for pipe within a field) are decoded automatically
Where It Fits
The ASTM parser runs inside the Vorian edge agent alongside the HL7 v2.x pipeline. Both protocols share the same store-and-forward buffer, gRPC tunnel, and heartbeat infrastructure. A lab running a mix of HL7 and ASTM instruments uses one agent, one install, one dashboard. The parser feeds into the auto-verification engine and continuous stats module just like HL7 messages do — the protocol is normalized before it reaches the rules evaluator.
Technical Details (for evaluators)
Supported standards: ASTM E1381-97, E1394-97, and CLSI LIS2-A2. The parser uses the standard delimiter set (pipe field separator, caret component separator, backslash repeat separator, ampersand escape character). Frame integrity is verified with the ASTM E1381 modulo-256 checksum (rendered as two hexadecimal characters) on every frame before message assembly begins. Outbound messages are segmented into conformant frames of up to 240 bytes of message text, with intermediate frames ending in ETB and the final frame in ETX. Inbound checksum characters are accepted case-insensitively, while Vorian always emits uppercase checksum characters. The dialect layer supports any vendor-specific field layout through a simple RECORD.N → canonical_name mapping — no code changes needed to support a new instrument.
The parser is written in Go and runs on the edge agent (Linux, macOS, or Windows). It does not require Python, Java, or any runtime beyond the agent binary. ASTM messages are buffered to the same SQLite store as HL7 messages, providing identical durability guarantees regardless of transport protocol.