Docbuilder & Interface Extraction

Upload a vendor's PDF implementation guide and Vorian Connect extracts the structured interface metadata — field mappings, Z-segment definitions, and vendor-specific quirks. The docbuilder produces a ready-to-use Go dialect snippet and a full human-readable report in minutes, replacing hours of manual PDF annotation.

How It Works

What's Included

Where It Fits

The docbuilder is the first step in the Vorian interface engineering workflow. A lab with a new analyzer sends the vendor's HL7 implementation guide to Vorian — the docbuilder extracts the interface metadata, generates a dialect, and surfaces any discrepancies against real trace data. The generated dialect is deployed to the edge agent's dialect registry, and the instrument is ready for message ingestion. What previously took a week of manual PDF annotation and field mapping is completed in one session.

Technical Details (for evaluators)

The docbuilder is a Go CLI that runs as a child process spawned by the dashboard API. It accepts PDF files, plain text files, and optional HL7 trace files. Extraction uses LLM-based structured data extraction with strict JSON schema validation — the output is verified against the expected schema before being returned to the dashboard. Protocol detection uses keyword density analysis (MSH/OBX for HL7, H|\\^&| for ASTM, CSV/delimited patterns for flat-file).

The docbuilder is designed for lab environments: it runs on the same infrastructure as the edge agent and gateway, requires no external services beyond the configured LLM provider, and processes documents up to 80,000 characters per chunk. Extraction reports are written to a configurable output directory with timestamped filenames for audit trail purposes.

Last updated: May 14, 2026