Yes. StatVault is not a prototype or a pitch deck. It was built inside a live regional medical courier operation and runs there every day, across hundreds of stops a day and thousands of orders a month in the New York metro. The screenshots on this page are from the production system, with names and numbers scrambled in place.
Who orders through it
Hospitals, labs, clinics and imaging centers place orders through StatVault portals every day, and their specimens are tracked on StatVault from pickup to delivery. Staff at New York's largest health system and an Ivy-affiliated academic medical center place orders through StatVault every day. Ordering portals are in use at leading hospitals, imaging centers and labs across the New York metro. Read about the customer portal.
What it looks like running
The dispatcher's live map: drivers, stops and the orders board over the New York metro.
The command center: alert feed, driver stop density, the day timeline and the team panel.
Ask Zippy: conversations, the question bar, live alerts and active intents.
The command center: the alert feed, the orders, the watchdog and fleet chat.
Zippy, the assistant built into the platform, answering from live data.
Chronoshift, the replay that rewinds the fleet to any moment of the day.
A site page: street view, access points with photos, hours, contacts and procedures. Names and numbers are scrambled in this capture.
Buildings: what the fleet knows about every hospital and lab it serves.
How it stays up and stays honest
- Hash-chained audit trail. Every custody event carries a fingerprint of the one before it, and a rolling sample of recent chains is verified every hour. See chain of custody.
- Point-in-time recovery. The database is backed up continuously and can be restored to a chosen moment, not just to last night.
- Tenant isolation enforced in the database. Each courier's data is separated by rules inside the database itself: isolation is enforced by the database, not only the application.
- Offline-first drivers. The driver app stores every tap and photo on the phone first, so a dead zone never loses proof.
How it started
StatVault started with a lost STAT bilirubin sample. A specimen that mattered went missing, and the paperwork could not say where. For a courier owner who had spent years building a medical courier operation, that was the moment the existing tools stopped being good enough.
Rather than rip out the dispatch system the operation ran on, the founder built StatVault alongside it, one surface at a time, and put each piece into daily use before building the next. That is why it works alongside CXT, and why every feature on this site is one a dispatcher, a driver or a clinic uses today. Read more on the about page.
Trusted by
Institutions are named here only with their written permission.
Related
Further reading: the StatVault glossary.