How Carrie Works

One Patient. One Carrie.
Every Chapter of Their Care.

Every patient gets a Carrie of their own — present for every diagnosis, every follow-up, year after year.

01The Open Loop Problem

Open loops are healthcare’s most common and least visible failure mode. Every referral, test, and follow-up carries an implicit promise that someone will confirm it was completed — a promise that depends entirely on memory, goodwill, and manual follow-through. That dependency breaks differently depending on scale, but it breaks everywhere: complexity overwhelms it in large systems, and absence of infrastructure prevents it in small ones.

02Carrie Closes the Care Loop

One conversation at a time.

Every Program Carrie runs on closes its own loops. A question isn’t just asked — it’s tracked until answered. An answer isn’t just logged — it triggers a defined action. And that action isn’t assumed to happen — it’s confirmed. Nothing depends on a person remembering to check back in.

Carrie’s Actions

03Programs

What is a Program?

  • A pre-built playbook for one condition/specialty-specific workflow
  • A ready-to-customize solution that can be easily adjusted to meet your needs

Can Programs run together?

Yes. Several Programs can all run at once for the same patient. They are mutually aware of each other. What one Program hears informs the others, and one conversation covers all of them. A symptom mentioned in passing lands wherever it matters.

Written by specialists, versioned like software.

Programs encodes the questions clinicians would ask, in the order they’d ask them, and the logic Carrie should follow for each possible answer. Changes can be made at any time, with each going through a review and release stage. Every released version is immutable and goes into record.

Why Carrie runs on Programs.

An improvising model gives you its best guess in the moment, and tomorrow’s best guess may differ. A Program can be printed, read, and signed off before a single patient is called. Afterward, every call can be replayed against the exact version and logic it ran.

Ask why Carrie said something and you get the Program version, the line of logic, and the recording. That’s what makes AI safe to run at this scale: providers stay in command of what it says, and audit is built into the system itself.

Security and governance

04The integration ecosystem.

These connections run on the SMART-on-FHIR Connect Engine. Upstream it reads provider intent and patient context out of the record. Downstream it turns decisions into actions and writes the evidence back. All exists as one cohesive.

New EHRs or data sources can serve as an extra connection at any time. Every Program has the ability to access this connection and use it immediately.

The EHR owns the record. Carrie supports the relationship.

Upstream · tells Carrie the patient’s whole story

Electronic health records the patient’s chart and history
Remote monitoring devices scales, blood pressure cuffs, glucose monitors at home
Labs & diagnostics test results, as they land
Social & demographic context language, transportation, coverage
Medical knowledge bases the clinical guidelines care Programs draw on

Downstream · lets her get things done

Practice workflows & clinical oversight the queue your team reviews and acts on
Pharmacy & prescriptions refills picked up, or flagged when they aren’t
Scheduling visits booked, moved, and recovered
Transportation to appointments rides arranged when getting there is the barrier
Home health & medical equipment services and supplies at home
Quality reporting the measures programs are graded on

Evaluating Carrie?

Book a Discovery Call →