Skip to main content

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.

SAMPLE · Vorian test rigACK RECEIVED
MSH|^~\&|ANALYZER|LAB|LIS|EHR
ORU^R01 · MSG-88412 · Glucose 104 mg/dL
MSA|AA|MSG-88412
Acknowledged in 0.84s · 1 attempt
0.84sACK turnaround
1Delivery attempt
AAApplication accept
  • 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.

01

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.

02

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.

03

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.

See a sample

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.

SAMPLE

Test data from Vorian’s own test rig. Everything below was generated on our internal test system — synthetic messages, no patient data, no customer site. It shows the format of a real pilot evidence pack, not a customer’s results.

Evidence pack — test rig runSOURCE: VORIAN TEST RIG · SYNTHETIC ORU^R01 FEED
— 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
MSG-88412 · ORU^R01 · Glucose panelMatchACK AA received · 1 attempt · result identical to current middleware output
MSG-88413 · ORU^R01 · CBCMatchACK AA received · 1 attempt · result identical to current middleware output
MSG-88414 · ORU^R01 · TroponinDifference flaggedACK AA received · 2 attempts (first endpoint timeout, retried) · flag formatting differed — held for review, shown in pack
MSG-88415 · ORU^R01 · LactateMatchACK AA received · 1 attempt · result identical to current middleware output
1,248Synthetic test messages in this rig run
1,241Matched the reference output exactly
7Differences flagged and held for review — each one listed, none hidden
  • 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.

01

Forward

Your instrument line’s traffic is mirrored to Vorian. Production keeps flowing through your current middleware, untouched.

02

Compare

Vorian processes the same messages in shadow mode and compares its output against your current system, result for result.

03

Review

Your team reviews the evidence pack: ACK traces, delivery attempts, and every difference, explained. No difference is silently passed.

04

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.

Monthly subscription

One recurring monthly fee once you’re live on Vorian. No perpetual license to buy back, no surprise renewal cliff.

No upfront license fee

You don’t pay a license fee to find out whether it works. The pilot and its evidence come first.

Your number, after the pilot

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

30 yearsClinical laboratory informatics
Trained as a
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

Request a shadow pilot

One instrument line. Your current middleware stays up. Test data only.

No PHI in this request. Sent directly to [email protected].

The Middleware Evaluation Checklist for Beaker Teams

Questions to ask any middleware vendor before signing.