DI Migration Mode
Vorian Connect's Migration Mode lets labs validate cutover readiness by importing historical Data Innovations result data, running shadow-mode comparison against live analyzer traffic, and reviewing per-result discrepancies — so interface engineers can prove match rates before switching a single instrument to production.
How It Works
- Export historical result data from Data Innovations as CSV — a standard export from DI's reporting or data export tools
- Import the CSV into Vorian Connect through the Migration dashboard, mapping DI's column names (timestamp, instrument, analyte, value, units, flag, LOINC) to Vorian's internal fields
- Each imported DI result becomes a shadow-mode reference record — it doesn't affect live processing, it exists only for comparison
- Configure one DI outbound connection to forward a copy of all analyzer traffic to Vorian (the simplest path — one DI connection, no per-instrument reconfiguration)
- As live analyzer traffic flows through Vorian, each result is automatically compared against the corresponding DI shadow record by instrument, analyte, and timestamp window
- The migration dashboard shows a side-by-side comparison: Vorian processed count, DI processed count, matching results, and discrepancies broken down by type — value mismatch, mapping mismatch, flag mismatch, missing from DI, missing from Vorian, and timing delta
- A confidence score (0–100%) aggregates the match rate across all shadowed sources — updated every 15 seconds as new results flow in
- Interface engineers review discrepancies in the review panel, accepting or rejecting each mapping difference, and tracking resolution progress
- When the confidence score reaches 95%+ and holds for two weeks, the source is ready to switch from shadow mode to live — Vorian becomes the primary interface engine
What's Included
- CSV import with column mapping: Import DI result data by mapping seven columns (timestamp, instrument, analyte, value, units, flag, LOINC) — CSV headers are auto-detected and presented in a dropdown for each field
- DI forwarding guide: Step-by-step instructions for configuring one DI outbound connection to forward all analyzer traffic to Vorian — the simplest ingestion path
- Conversion SOP checklist: A structured checklist covering pre-flight checks, DI forwarding setup, shadow comparison, and go-live gates — each step trackable with a completion timestamp
- Migration confidence dashboard: Real-time confidence score with color-coded progress bar (green ≥95%, blue ≥80%, yellow <80%) and target guidance — 95%+ match rate for two weeks before production cutover
- Side-by-side metrics: Vorian and DI processed counts, matching results, and per-type discrepancy breakdowns displayed in paired metric panels
- Discrepancy classification: Six discrepancy types — value mismatch, mapping mismatch, flag mismatch, missing from DI, missing from Vorian, timing delta — each with human-readable labels
- Review panel: Accept or reject mapping discrepancies with per-source review progress tracking
- Per-source shadow status: Each instrument source shows whether it's in shadow mode (comparison active) or live mode (production) with started-at timestamps
Where It Fits
Migration Mode is the bridge between an existing Data Innovations environment and Vorian Connect production. It sits between the DI export workflow (where the lab extracts historical result data) and the live cutover decision (where the lab switches sources from shadow to production). The migration dashboard is a validation surface — it doesn't modify live traffic, it only compares. Once confidence is established, the lab team switches individual sources from shadow mode to live in the Sources page, and Vorian becomes the primary interface engine for those instruments. The migration data and discrepancy history remain available for audit and regulatory review after cutover.
Technical Details (for evaluators)
| Capability | Detail |
|---|---|
| Import format | CSV with configurable column mapping — seven fields: timestamp, instrument, analyte, value, units, flag, LOINC |
| Shadow comparison | Per-result matching by instrument, analyte, and timestamp window against imported DI reference data |
| Discrepancy types | Value mismatch, mapping mismatch, flag mismatch, missing from DI, missing from Vorian, timing delta |
| Confidence score | Aggregated match rate across all shadowed sources, refreshed every 15 seconds |
| Cutover threshold | 95%+ match rate sustained for two weeks — configurable in migration settings |
| Ingestion path | One DI outbound connection forwarding all analyzer traffic to Vorian — no per-instrument reconfiguration |
| Source modes | Shadow (comparison active, not live) and Live (production routing) — per-source toggle |
| Review tracking | Per-discrepancy accept/reject with per-source progress tracking |
| Data isolation | Migration data stored in tenant-scoped PostgreSQL tables — no cross-tenant visibility |
| API endpoints | GET /api/migration (summary), POST /api/migration/import-di-results (CSV import), GET /api/migration/review (review status) |
Migration Mode imports CSV result data only — it does not import DI configuration, connection settings, or mapping rules. Labs configure their Vorian sources, destinations, and rules independently. The shadow comparison validates that Vorian produces equivalent results from the same analyzer traffic — it is a validation tool, not a configuration migration utility.