The blocks are already written
Hundreds of clinical and administrative skills, and connectors for the systems a practice already runs. Drop one on the canvas and it arrives wired, typed and logged. There is no integration sprint hiding behind it.
Flow Builder
Build the workflow, not the integration.
The hard parts are already built — reading the chart, placing the call, writing the note back. Flow Builder is where you put them in the order your clinic actually works in. There is nothing to migrate and no engineering quarter to book.
The builder, mid-run
Pre-visit prep
Last run finished
- folder_open
Step 01 — Opening the chart
Open the chart
Patient, coverage, last encounter.
- dataset
Step 02 — Calling the patient
Read the record
Encounters, notes, labs, meds.
- call
Branch — Calling the patient
Call the patient
Picks up what the chart does not have.
- edit_note
Step 03 — Sorting what matters
Draft the note
A pre-chart note off the findings.
- verified
Step 04 — Drafting and checking
Verify
AHR checks every claim against the chart.
- how_to_reg
Branch — Drafting and checking
Clinician sign-off
Anything uncertain waits for a person.
- sync_alt
Step 05 — Back into the record
Write it back
As a shadow user. No new tab to learn.
How it goes
An afternoon, not a roadmap slot
The person who knows the workflow is the one who builds it, and that is usually somebody in operations. What used to make this an engineering job — the connections, the retries, the audit trail — is already handled underneath.
Assemble
Drag the blocks the flow needs onto the canvas and wire them in the order the work happens. Skills, connectors, branches and human checkpoints all come from the same library.
Rehearse
Run it against real historical encounters before it touches a patient. Every step shows what it read, what it decided and what it would have written.
Release
Publish to a single clinic, a service line or the whole estate. Versioned, reversible, and reporting from the first run.
Building it
Nothing on this canvas needs an engineer
Blocks snap together, connectors carry their own types so two that should not join will not, and every edit is versioned. Work that used to sit behind a ticket now sits behind a meeting.
Start from one that works
Take a flow that already handles the ordinary case and change the parts that are yours: the intake questions, the acuity thresholds, who gets called at six, what happens on a Friday.
Keep a person in the loop
Send the risky and the uncertain to a named reviewer, and let the agents have the rest. The queue, the deadline and the audit trail come attached to the block.
Every block reports
Volume, latency, how much got deflected, how often a human was pulled in, what a completed task costs. Live, and you can open any single run and read the transcript behind it.
Reaching your systems
Your stack stays exactly where it is
Flow Builder sits on OIL, the same layer everything else here runs on. A new flow inherits every connection that layer already holds, so the second one costs nothing the first did not already pay for.
Everything OIL already reaches
EHRs, payer portals, data warehouses, claims platforms and HIEs are on the layer today. A flow built this morning can reach them this afternoon, under the same tenancy and the same audit.
Epic and Cerner, both ways
Read the chart, reason over it, write the result back. Over HL7 and FHIR where they exist, and by driving the session as a shadow user where they do not.
And everything either side of it
HIEs, CRMs, telephony, scheduling, data lakes. If the work crosses a system boundary then so does the flow, and nobody re-keys anything on the far side.
In production
Every practice builds a different one
These are the flows teams reach for first. None of them took a roadmap slot, and none of them needed a system replaced.
- Pre-visit intake48h ahead
- After-hours triage24/7
- Referral chaseDaily
- Medication refillOn request
- Recall campaignsScheduled
- Insurance verificationPer booking
- No-show recoverySame day
- Results follow-upOn result
Bring us the workflow you dread
Tell us the one that eats your team's week. We will build it on the canvas while you watch, against your EHR and your rules, and you can decide afterwards whether it is worth running.