ML & Mapping Intelligence

Vorian Connect runs machine learning models in shadow mode — they predict outcomes, suggest rules, and propose LOINC mappings without ever changing a live verification verdict or result. Interface engineers review every suggestion before it becomes operational, giving you AI-assisted speed with full human control.

ML Shadow Predictions

The ML Shadow Predictions dashboard shows what Vorian's XGBoost models would do if they were making verification decisions. Every analyte in every message gets a prediction: auto (the model would pass the result through) or held (the model would flag it for manual review). These predictions run silently alongside the auto-verification pipeline and never override the live verdict.

ML Rule Suggestions

Vorian Connect can analyse historical message patterns and suggest new auto-verification rules for lab review. These suggestions are generated by a Python pattern-extraction service and shown in the Rule Suggestions dashboard — they never become live rules until an interface engineer reviews and approves them.

Test Catalog Import

Instead of manually mapping every instrument code to LOINC, upload a vendor test catalog — CSV, TSV, Excel workbook, or PDF — and let Vorian Connect suggest LOINC mappings for every test. Azure OpenAI powers the mapping intelligence using semantic embeddings and large language model reasoning.

Unmapped Results Queue

When a new instrument code arrives without a configured LOINC mapping — either from a new instrument or a test that was missed during initial setup — it lands in the Unmapped Results Queue. The queue groups results by source, instrument code, analyte name, and unit so you can resolve entire families of unmapped results at once.

Where It Fits

The ML & Mapping Intelligence tools span two dashboard sections. ML Shadow Predictions, Rule Suggestions, and Catalog Import live under Migration & Intelligence alongside validation tools. The Unmapped Results Queue lives under Configure alongside sources and destinations, since resolving unmapped codes is part of ongoing interface configuration.

All ML features run on Azure OpenAI (not direct OpenAI API) using the following models:

ML model predictions are viewable by users with ml:manage permission. Mapping suggestions and unmapped result management require config:mappings. Viewing individual result values within unmapped groups also requires results:view.

Last updated: May 20, 2026