Interface Templates — Vorian Health Docs

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

What's Included

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.

Last updated: May 21, 2026