Interface Templates
Vorian Connect provides a library of reusable interface templates that capture the field mappings, protocol dialects, and vendor-specific settings needed to connect lab analyzers. Instead of configuring every instrument from scratch, interface engineers start from a curated template, deploy it for their environment, and iterate — reducing per-instrument setup time from hours to minutes.
How It Works
- Templates capture the full interface configuration: vendor, instrument model, protocol (HL7 v2.x or ASTM), field mappings from analyzer codes to Vorian's internal representation, and Go dialect definitions for vendor-specific quirks
- The Interface Repository at
/templateslists all available templates, filterable by vendor, instrument name, or protocol. Templates are globally readable across tenants so the community can share common analyzer configurations - When a template is deployed, Vorian creates a new instrument source with the template's connection settings, dialect profile, and field mappings pre-loaded. The source starts disabled so the interface engineer can review and adjust before enabling live traffic
- Template deployment writes an
interface_deployaudit row and notifies the edge agent's configuration watcher so the new source is available immediately after review - Flatfile mapping templates extend the system to non-standard analyzer output — labs can define column-to-HL7 field mappings for custom flat-file formats like CSV exports or legacy LIS dumps
What's Included
- Interface Repository: A searchable library of templates organized by vendor (Roche, Beckman, Siemens, Abbott, Sysmex) and instrument model. The repository is globally readable — templates are shared as community resources
- Field mappings: Each template includes analyzer-code-to-standard-code mappings, LOINC proposals, unit conversions, and test display names. Field mappings flow through the mapping proposal system — they are surfaced as suggestions for human approval before becoming active test-code mappings
- Vendor dialects: Templates capture Go-level dialect definitions for vendor-specific field separator quirks, segment ordering, and non-standard encoding patterns that the generic HL7 or ASTM parser needs to handle correctly
- Protocol support: Templates specify the protocol (HL7 v2.x or ASTM E1381), connection mode (server or client), default port, and any vendor-specific handshake or initialization requirements
- Deploy workflow: One-click deployment from template to instrument source. The new source inherits all template settings and starts in a disabled state for review
- Flatfile templates: For labs with non-standard analyzer output, flatfile templates define column layouts, delimiter settings, header detection rules, and field-to-segment mappings that convert raw flat files into normalized Vorian messages
- Promotion pipeline: Templates and their associated sources, rules, code maps, delivery targets, and vendor profiles can be promoted from a test tenant to a production tenant with a single operation. The promotion system generates new UUIDs for every row and skips duplicates by name — each resource type is atomic so all rows of a given type succeed or fail together
Where It Fits
Interface templates live in the Configure section of the dashboard alongside Sources, Destinations, and Rules. They are designed as a force multiplier for interface engineering teams: build the template once on a known instrument, then deploy it across multiple sites or tenants. The promotion pipeline connects templates to the broader configuration lifecycle — validate settings in a test tenant, then promote the entire configuration bundle (templates, sources, rules, delivery targets) to production atomically.
Template creation must not create or enable clinical rules from extracted documentation. Deploying a template creates an instrument source from a curated configuration, validates mode, port, and client-host input before tenant mutations, and writes an audit trail for every deployment.
Technical Details (for evaluators)
Interface templates are stored in the interface_templates table with tenant-scoped creation (created_by_tenant_id) but globally readable access patterns. Flatfile templates live in flatfile_templates with full CRUD operations through a tenant-aware store backed by PostgreSQL transactions. The promotion system uses separate database pools for source and destination tenants, copies rows in per-resource-type transactions, and generates new UUIDs for every promoted row to avoid primary key collisions across environments. Each template deploy and promotion writes an audit event recording the actor, resources affected, and source/destination tenants.