The agent orchestration layer for diagnostics.
An agent that can act on clinical data needs to be told what it may touch, under whose authority, and where a human takes over. CareOS is that layer, and it owns the PACS and the LIS underneath it, so the agents see the real record.
Three commitments
The routine runs; the judgement escalates
Agents absorb the booking, drafting, checking, coding and reconciliation around a decision, so a qualified person spends the day on the decision itself.
Grounded, or it abstains
Every factual answer carries a citation. When your record does not support one, CareOS says so rather than guessing. Enforced in code, not in a prompt.
Nothing clinical is released unattended
Drafts wait for a signature; flagged results wait for a pathologist. Every release carries an audit row naming who made it.
Organised the way your centre already is
Each room automates the work that repeats and escalates the work that doesn't, all on one patient identity, one order spine and one audit trail.
Front Desk
Answers the phone in the caller's language, finds the patient across every centre, holds the slots a multi-station booking needs, and sends the confirmation. The transcript files itself against the patient.
- Voice calls answered and booked end to end
- Multi-station appointments across CT, ultrasound and pathology
- Package pricing with discount split by MRP share
- WhatsApp confirmations, prep and reminders
Protocols
Every centre works differently, and on most systems that difference becomes a fork: a release, a consultant, a version only you run. On CareOS it is a Protocol you change on a Tuesday afternoon.
- Typed workflow stages with conditional gates and parallel branches
- Rules matched by priority, falling back to client and tenant defaults
- SLA timers, escalation and critical-finding clocks in the workflow
- One codebase for every customer: your configuration, not your version
What it is built on
The parts an operator never sees, and would notice immediately if they were missing.
Isolation the database enforces
Row-level security on every table, under an independent policy engine. Two failure domains, not one convention.
Events, not overwrites
State is a projection of an immutable ledger. What happened is recoverable; nothing is silently rewritten.
Durable workflows
Long-running clinical workflows survive restarts and partial failures because they execute durably, not in a job queue.
Standards at the boundary
DICOM and DICOMweb for imaging, HL7 v2 and FHIR for orders and results. Unmapped sources are rejected, not absorbed.
Independently audited
CareOS runs on certified quality and information security management systems, so hospital procurement and IT security reviews have something to check against rather than a promise.
ISO 13485
Medical device quality management
ISO 27001:2022
Information security management
Questions we get asked
No. Most centres start with whichever side hurts more, usually the lab, and add the other later. The modules share an identity and an order spine, so the second costs far less than the first.
It comes with you. Prior studies and results are migrated so trends and priors work from day one; a platform that starts empty is one nobody trusts.
It can release results your rules classify as routine. You write that rule and can change it. It cannot sign a report, and it cannot release anything flagged.
No server, no appliance. Modalities reach a central router fleet over a VPN, which is why adding a centre is configuration rather than a site visit.
See it run on your own workflow
Bring your test catalogue, your modality list and your busiest morning.