Flat File Parser

Ingest CSV, TSV, and fixed-width flat files from laboratory instruments — including legacy analyzers and LIS exports that don't speak HL7 — through template-based column-to-HL7 mapping. Each row converts into a valid HL7 ORU^R01 result message ready for auto-verification, routing, and delivery.

How It Works

What's Included

Where It Fits

The Flat File Parser lives in the Interface Analyzer workflow alongside the HL7 parser and ASTM parser. It targets instruments and LIS exports that produce tabular data instead of standard HL7 — common with legacy hematology analyzers, flow cytometers, microbiology systems, and regional reference lab exports.

The Interface Analyzer auto-detects the format when you paste a sample: CSV flat file, TSV flat file, or Fixed-width flat file. Non-HL7 samples go through the same review posture as HL7 samples — staged as mapping proposals with test code, condition, and reference range candidates — before a reviewer approves them for production use.

After a template is created and validated, batch ingestion runs the full pipeline: template lookup → file parse → HL7 transform → database persist → downstream delivery. The same auto-verification rules, routing policies, and destination delivery that apply to native HL7 traffic also apply to flat-file-generated messages.

Supported Formats

Template Configuration

Each mapping template has three configuration layers:

Templates are reusable — once validated for an instrument model, the same template ingests any file from that vendor and instrument. Updates to a template take effect on the next ingestion without affecting previously stored messages.

Last updated: May 29, 2026