Clinical Interface Engine
Your middleware says it delivered. Can it prove it?
Vorian Health Connect is a clinical interface engine built to replace legacy lab middleware — not bolt onto it. Every result it moves carries its own evidence: the acknowledgment, the delivery attempts, and the routing decision, ready for your team to inspect without opening a support ticket.
MSH|^~\&|ANALYZER|LAB|LIS|EHR ORU^R01 · MSG-88412 · Glucose 104 mg/dL MSA|AA|MSG-88412 Acknowledged in 0.84s · 1 attempt
- ACK traces
The actual acknowledgment from the receiving system — not a green checkmark that says “sent.”
- Delivery attempts
Every send, retry, and failure, timestamped. Sent is not delivered, and Vorian shows the difference.
- Routing decisions
Why each message went where it went, recorded at the moment it happened — not reconstructed later.
The Shadow Pilot
Proof before trust — on one instrument line
Don’t take our word for any of this. Run Vorian beside the middleware you already have, on a single line, and compare the two result-for-result. Your current setup keeps running your lab the whole time.
Bring one instrument line
Pick a single analyzer line — molecular is a strong place to start. One line is enough to prove delivery, matching, and routing.
Keep your current middleware running
Nothing is ripped out and nothing is re-pointed in production. Vorian runs in shadow mode alongside your existing engine.
Test data only
The pilot runs on test data against your environment. No live patient data is used at any point in the pilot.
What you get at the end is the evidence pack.
ACK traces, delivery attempts, and a result-for-result comparison your team can review line by line.
Sample Evidence Pack
This is what “delivered” looks like with proof
Every pilot ends with an evidence pack like this one: the messages, the acknowledgments that came back, and where the two systems agreed — or didn’t.
— ACK trace, message MSG-88412 — MSH|^~\&|TEST-ANALYZER|VORIAN-RIG|VORIAN|RIG|20261109141203||ORU^R01|MSG-88412|T|2.5 OBX|1|NM|GLU^Glucose||104|mg/dL|70-99|H|||F → forwarded to LIS endpoint, attempt 1 of 1 MSH|^~\&|LIS|RIG|VORIAN|RIG|20261109141204||ACK^R01|ACK-55107|T|2.5 MSA|AA|MSG-88412 → acknowledgment received in 0.84s — application accept (AA) → comparison vs. current middleware copy: MATCH — byte-for-byte, all segments
- ACK traces — the raw acknowledgment for every message, accept or reject.
- Delivery attempt log — sends, retries, timeouts, and final disposition.
- Result-for-result comparison — Vorian’s output against your current middleware’s, differences itemised.
- PHI-safe export — a validation export your team can share and review outside the system.
How It Works
Shadow first. Cut over only when the evidence says so.
Forward
Your instrument line’s traffic is mirrored to Vorian. Production keeps flowing through your current middleware, untouched.
Compare
Vorian processes the same messages in shadow mode and compares its output against your current system, result for result.
Review
Your team reviews the evidence pack: ACK traces, delivery attempts, and every difference, explained. No difference is silently passed.
Cut over
If the evidence holds up, one source moves to Vorian at a time — staged, reversible, and only on your schedule.
Pricing Model
Priced after proof, not before it
Interface middleware has historically meant a large upfront license and a long commitment before you’ve seen the software do anything. Vorian is structured the other way around.
One recurring monthly fee once you’re live on Vorian. No perpetual license to buy back, no surprise renewal cliff.
You don’t pay a license fee to find out whether it works. The pilot and its evidence come first.
Pricing is quoted after the shadow pilot, scoped to the sources and volume the evidence actually covered.
See the evidence first. Then we talk price — with the proof on the table.
The Builder
Built by someone who has run these interfaces
laboratory technologist
Built LISs · Designed &
configured interfaces
Clinical & anatomic labs
United States & Canada
Vorian was built by a clinical laboratory informatics specialist with 30 years of experience — trained as a laboratory technologist, and the person who has built LISs and designed and configured interfaces for laboratories across the United States and Canada, in both clinical and anatomic labs.
Vorian exists because of what those 30 years looked like from the bench side: middleware that reported “delivered” with nothing behind it, and labs left to reconstruct what happened from fragments. Vorian Health Connect was built to produce the evidence instead — ACK traces, delivery attempts, and routing decisions a lab can stand behind.
“Sent is not delivered. If the system can’t show you the acknowledgment, it hasn’t proved anything.”
Questions & Pilot Request
Before you ask for the pilot
No. The shadow pilot runs on test data only, against your environment. Live patient data is not used at any point in the pilot.
No. Your current middleware keeps running production throughout the pilot. Vorian runs beside it in shadow mode, and any cutover happens one source at a time, afterwards, only if the evidence supports it.
No. Vorian Health Connect is a clinical interface engine in its own right — a replacement for legacy middleware, not a bolt-on or a dashboard layered over it. The shadow pilot is simply how we prove that before you commit to anything.
Vorian includes configurable outbound profiles and validation fixtures for Epic Beaker- and Oracle Health Cerner PathNet-style HL7 interfaces, on a vendor-neutral HL7 v2 / MLLP core. Compatibility with another LIS is assessed and validated per interface — tell us yours in the pilot request and we’ll be straight with you about what it takes.
A monthly subscription with no upfront license fee — quoted after the pilot, scoped to what the evidence covered. You see the proof before you ever see a price.
The evidence pack: ACK traces, the delivery attempt log, and a result-for-result comparison against your current middleware, with every difference itemised. It’s yours to review whether or not you go further.
Request sent
We will reply from [email protected] within one business day.
The Middleware Evaluation Checklist for Beaker Teams
Questions to ask any middleware vendor before signing.