The Engine / forward-deployed clinical AI

Clinical AI your hospital can evaluate in week one,
and run inside its own walls.

CareCompile reads the HL7 and FHIR messages your hospital already produces, reasons over each patient like a team of specialists, and briefs the on-call clinician with the evidence attached. It runs in your cloud, on your servers, or fully offline.

Forward-deployed engineering we embed in the workflow/build against your real message formats we run where you run/cloud, on-premises, or fully air-gapped
Engine trace · one message ON YOUR HARDWARE
ElapsedWhat the engine doesState
0.00s
ORU^R01 arrives
MLLP over TCP · 14 OBX segments · ACK returned
Ingested
0.04s
Parsed and normalised
LOINC mapped · units reconciled · Z-segments kept
Parsed
0.11s
Chart assembled
priors, notes and imaging fused from FHIR R4
In context
0.3s
Model routed
your weights, your perimeter — nothing egresses
Routed
1.8s
Specialists reason in parallel
cardiology · renal · pharmacy · pulmonology
Reasoning
3.6s
Every claim checked
13 clinical claims verified against the record
Verified
4.2s
Written to the audit trail
tamper-evident · 7-year retention · including silence
Logged
4.2s
NORA decides whether to speak
escalate now, stage for rounds, or stay quiet
Judged
4.2s
Message to
narrative
13
Claims checked
vs the chart
100%
Decisions
audit-logged
6
Specialist
stacks
One ORU^R01 through the engine on synthetic data. Timings move with the model you run, the hardware you run it on, and how much chart there is to read.
01 — WEEK ONE

Most clinical AI can't start
until month six. We start in week one.

The hardest problem in clinical AI was never the model. It's getting access to patient data to prove anything at all. We solved that by manufacturing our own.

01
Proof before procurement
No BAA required to see it work

Every capability is built and validated against synthetic patients with known answers. So we can show you the engine running on your message formats before a BAA, an IRB, or a security review is signed. Evaluation starts in week one, not month six.

02
A pilot that risks nothing
Silent by default

Thirty days in shadow mode. No pages, no workflow change, and not one clinician gets another alert to ignore. You see what we would have caught before anyone has to trust it — which is the only order that has ever worked in this market.

03
No cloud-security veto
Runs inside your perimeter

On-premises or fully air-gapped. The most common reason clinical AI dies in security review simply doesn't apply — because the data never leaves the building. That is also what makes this deployable in the field, and outside the country the software was written in.

04
One miss pays for the year
The economics

Failure to rescue — a deterioration knowable from data already sitting in the chart — drives extended ICU stays, transfers, and litigation exposure. The software was never the expensive part. The miss is.

02 — MODELS

Your models.
Your infrastructure.

We don't sell you a model. We make the ones you already own work inside clinical care — and we train them until a clinician will act on the output.

01
Bring your own models
No vendor to adopt

If your health system already licenses models, or owns weights you've invested in, the engine routes to them. Nothing about the clinical logic changes. The reasoning, the verification and the audit trail are ours; the model underneath is yours.

02
We train and we tune
Fitted to your workflow

We train models against your terminology, your order sets, your escalation thresholds — and keep tuning until the output survives a clinician reading it at three in the morning. Generic models don't clear that bar. Trained ones do.

03
Runs where your data lives
Sovereignty by deployment

Your cloud, your servers, or a sealed appliance with no network connection at all. Data residency stops being a negotiation and becomes a deployment setting — which is what makes this workable outside the countries the software was written in.

04
No lock-in, ever
Models are swappable

Models are replaceable without re-engineering a single clinical rule. When something better ships — and it will, repeatedly — you move to it in a configuration change. The engine is built to outlive any one model generation.

Your data
stays yours

The clinical reasoning, the verification against the record and the audit trail stay constant whichever model runs underneath. Your patient data never trains anyone's model.

Shared
codes

Every result is resolved to a shared, verified code before any model reasons over it. How terminology works →

03 — THE BUILD LOOP

How it gets built.
And how it gets better.

Forward-deployed means we work inside your environment, against your real data formats — not over the wall with a spec and a hand-off.

01
Plan

Map the workflow before writing anything — where the data originates, who acts on it, and what a miss actually costs the patient.

02
Prototype & test

A working slice against your real message formats in weeks. Every change is scored against synthetic patients with known answers, and a held-out harness scores each release against ground truth the engine never saw while it was being tuned.

03
Deploy & improve

Cloud, on-premises, or air-gapped: same engine, same verification, same audit trail. Changes ship because they measured better, not because they sounded better.

// Nothing ships that the validation suite hasn't seen. The full engagement process is on Professional services.

04 — NORA

NORA. The night shift
that doesn't get tired.

Nocturnal On-call Reasoning Agent — always on, and deliberately quiet. It runs two loops, because patients deteriorate in two different ways.

Loop 01 — when data arrives

Something happened

The moment a result, note, or admission lands, specialist reasoning runs on that patient — labs, imaging, notes and prior history fused and read in parallel. Findings are queued the second they exist, and NORA works that queue continuously, through the night, without being asked.

Loop 02 — when nothing arrives

Something didn't happen

Every five minutes, a sweep checks every admitted patient for what hasn't occurred — the results that stop coming, the monitoring that goes quiet, the admission nobody closed. Absence is a signal too, and it is the one that conventional alerting misses entirely.

The hard part is restraint

Flagging is easy. Any system can flag everything — that is precisely how clinical alerting earned the reputation it has, and why the last generation of early-warning tools got silenced within months of go-live. The engineering is in what NORA decides not to say. What earns a clinician's attention at three in the morning, and what waits until rounds. Every decision is written to a tamper-evident audit trail — including the decision to stay quiet.

Clinical & diagnostics
Live · command center, lab, imaging, EKG
Force-health & the field
Deployed offline · maritime, military, forward ops
Public-health surveillance
Live · cultures, resistance, reportable conditions
05 — THE STACK

Six stacks.
One shared record underneath.

Every stack reads the same patient record and the same knowledge base as NORA. Nothing here works in isolation.

01

The command center

Whole-chart synthesis

Reads the full chart and briefs your hospitalist the way a subspecialist would, with every critical flag ranked in one view. Includes: Physician.AI.

02

The continuous watch

Always-on monitoring

Specialist reasoning the moment new data lands, and a sweep across every admitted patient for what has not happened. Includes: NORA, covered above.

03

The lab's second reader

Result safety net

Cross-checks results across hematology, microbiology and transfusion medicine before an error reaches the chart. Includes: Laboratory.AI.

04

Imaging follow-through

Follow-up discipline

RADS-structured reporting and incidental-finding follow-through, plus a single-lead EKG read in minutes. Includes: Radiology.AI, EKG.

05

Infection surveillance

Facility-wide watch

Cultures, resistance patterns, cluster detection and reportable-condition readiness across the facility. Includes: Sentinel.AI.

06

Force-health & the field

De-identified · offline

The same engine, fully offline on local hardware, for spine and musculoskeletal screening, field reference and de-identified force-health briefs. Includes: SpineReady, Military.AI, Intrepid, MEDINT.AI.

NORA, the always-on agent that watches every stack overnight, is covered in 04 — NORA above.

One record.
One knowledge base.

Every stack reads and writes the same patient record and draws on the same clinical knowledge base. Add a stack and it inherits everything the others already know. Nothing here is a silo.

Start a silent pilot.

Thirty days running alongside your live stream. We page no one. Nothing reaches a clinician and nothing changes a workflow. At the end we show you what we would have caught, how early, and everything we stayed quiet about.

Clinical Decision Support Notice — CareCompile is a non-diagnostic clinical decision support tool intended to augment, not replace, physician judgment. All AI-generated analyses are advisory only; clinical decisions remain the sole responsibility of the licensed treating clinician. CareCompile is not FDA-cleared or FDA-approved as a medical device and is not intended to diagnose, treat, cure, or prevent any disease. For investigational and decision-support use only. Validation with practicing physicians is ongoing.