Home Use Cases Work Insights About Contact
Back to Our Work

How a Growth-Stage Healthcare Provider Built Visit Billing That Codes Only What the Signed Note Supports

Operations1
Open the walkthrough

Seven-Step AI Workflow with Human Oversight

Each step shows the workspace, what the AI completed, and what still needs human review.

Steps 3, 5 and 7 need a person. Step 5 is waiting for approval right now. Click it to open the full walkthrough.

Estimates are directional and based on stated assumptions. All names, organizations, and identifying details have been anonymized in accordance with our confidentiality agreements.

The Transformation

How a Growth-Stage Healthcare Provider Built Visit Billing That Codes Only What the Signed Note Supports

Before
✗The front desk used to phone tomorrow's patients one by one and check each policy on the payer's line between calls.
✗The provider used to type each note from memory after the last patient left.
✗A coder used to read each signed note and pick the codes from memory against last year's rule book.
✗The front desk used to print the summaries and phone each patient to book their follow-up.
→
After
✓tomorrow's visits confirmed, charts ready, one coverage flag
✓every visit drafted into its note, blanks left honest
✓the notes wait on the hand that saw the patient
✓codes drafted off the signed words, nothing invented
✓clean claims out, held claims named, denials traced
Executive Summary

Everything around one patient visit, from the reminder that fills the slot to the payer's answer on the claim. The agents prep the chart, draft the note off the provider's own dictation, code only what the signed note supports, send the clean claims and hold the doubtful ones, and stop for a person exactly where the law or the money says a person signs. Seven stations, run as a loop: what the week's denials teach at station 7 changes how station 4 codes and how station 1 preps next week.

What Was Broken

The front desk used to phone tomorrow's patients one by one and check each policy on the payer's line between calls
The provider used to type each note from memory after the last patient left
A coder used to read each signed note and pick the codes from memory against last year's rule book
The real cost
The front desk used to print the summaries and phone each patient to book their follow-up.

What We Built

Seven stations and 14 subagents. Each subagent carries its own tasks and its own refusal.

A4
Reminder Desk
Send each reminder through the channel the patient chose, portal first
A3
Coverage Check
Verify each patient's coverage against the payer the chart names
A1
Dictation Scribe
Transcribe the provider's dictation with drug names spelled as the formulary spells them
A2
Chart Check
Compare the draft against the chart's problem list, allergy list and medication list
A3
Signing Queue
Route each drafted note to the provider who saw the patient
A1
Amendment Scribe
Apply the provider's spoken corrections to the draft, line by line
A1
Code Draft
Draft the diagnosis codes from the signed note's own sentences
A3
Compliance Check
Check each code pair against the payer's pairing rules before it reaches a claim
A3
Claim Builder
Assemble each claim from the signed note, the codes and the coverage record
A3
Denial Desk
Match each payer answer back to the claim and the visit it belongs to
A4
Summary Sender
Send each after-visit summary through the portal once its note is signed
A4
Recall Keeper
Book the follow-up interval the signed plan names, in the patient's chosen slot
A4
Week Close
Check every visit this week against where it ended: signed, coded, billed, followed
A2
Pattern Desk
Propose the coding or booking rule that would have stopped each repeated denial

How It Runs

1

Visit Confirmation

Nobody is asked anything here

Agents send the reminders, record the confirmations, verify each patient's coverage, and put a prepped chart behind every slot on tomorrow's book. Nothing waits on a person here. A coverage that does not verify is flagged on the schedule, never guessed at.

2

Visit Documentation

Nobody is asked anything here

Agents transcribe the provider's dictation, draft each note into its SOAP sections, check the draft against the chart, and leave blank what the audio does not settle. Nothing waits on a person here. A word the audio does not settle stays blank, because a guessed drug name is worse than a gap.

3

Note Signing

A person answers here

Agents queue each drafted note to the provider who saw the patient, put the flags and the blanks on top, and apply the spoken corrections line by line. This is where a person works. The signature is the fact the whole record hangs on, and no agent carries it.

4

Visit Coding

Nobody is asked anything here

Agents draft the diagnosis and procedure codes off the signed note's own sentences, check every pair against the payer's rules, and hold any code they cannot trace to a sentence. Nothing waits on a person here. A held code stops the claim it was bound for, and the claim carries the reason to station 5.

5

Claim Submission

A person answers here

Agents assemble each claim, scrub it against the payer's format, submit the clean ones, and hold the rest with the reason written on each. Denials come back traced to the line the payer names. This is where a person works. A held claim leaves fixed or not at all, and the fix is a decision.

6

Recall Booking

Nobody is asked anything here

Agents send each after-visit summary through the portal, confirm the prescriptions reached the pharmacy, book the follow-up the signed plan names, and route every clinical question to the provider who signed. Nothing waits on a person here. A clinical question is never answered in a provider's name, only routed to one.

7

Practice Review

A person answers here

Agents check every visit against where it ended, count what settled without a person, propose the rules that would have stopped the repeated denial, and draft the compliance report off the visit trail. A person accepts or rejects each rule. How a note is coded and what a claim carries are practice rules, and an agent never changes them quietly.

Where a Person Decides

•Step 3, Note Signing. Sign the 5 notes, the flags are already on top. Give Lila Okafor's blank its number, the scribe would not guess it. no signature, no note, no claim.
•Step 5, Claim Submission. Clear the 2 held claims, each carries its reason and its fix. Send the resubmission, the empty field is filled. a held claim never leaves unfixed.
•Step 7, Practice Review. Accept or reject the two proposed rules. Chase the Tuesday note, nothing behind it moves until it is signed. the rules are yours to accept.

Operating Model

This changes how work flows through the team.

Role
Responsibility
Note Signing owner
Sign the 5 notes, the flags are already on top. Give Lila Okafor's blank its number, the scribe would not guess it. no signature, no note, no claim.
Claim Submission owner
Clear the 2 held claims, each carries its reason and its fix. Send the resubmission, the empty field is filled. a held claim never leaves unfixed.
Practice Review owner
Accept or reject the two proposed rules. Chase the Tuesday note, nothing behind it moves until it is signed. the rules are yours to accept.
Visit Confirmation, when it goes wrong
Look here only if a patient says they never got a reminder.
Visit Documentation, when it goes wrong
Look here only if a note reads unlike the visit you remember.
Visit Coding, when it goes wrong
Look here only if a code reads unlike the visit.
Recall Booking, when it goes wrong
Look here only if a patient says they never got their summary.

What Transfers, What Must Be True

What transfers
•A person is in the loop wherever a signature carries legal weight, a claim leaves with the practice's name on it, or the rules the agents work by change. Three stations refuse to proceed on their own, Note Signing, Claim Submission and Practice Review, and those are the three a person carries. Everywhere else the agents prep, draft, code, send and follow, and reach a person only with the flags already on top.
•Note Signing stops for a person, and no signature, no note, no claim.
•Claim Submission stops for a person, and a held claim never leaves unfixed.
•Practice Review stops for a person, and the rules are yours to accept.
•Every subagent says what it will not do. 14 of them do.
What must be true in your environment
•The agent can read the systems your records already live in. This one reads 24.
•Somebody owns Note Signing and has time for it.
•Somebody owns Claim Submission and has time for it.
•Somebody owns Practice Review and has time for it.

Failure Modes

What breaks this pattern:

✗ A Guessed Drug Name

The scribe hears an unclear word and writes its best guess instead of a blank. The provider signs the note without catching it, and a wrong drug or dose is now the record of care.

✗ A Code With No Sentence

A code the note does not support goes onto the claim anyway. An auditor traces it back months later, and one untraceable code puts every similar claim under review.

✗ A Known-Bad Claim Goes Out

The builder sends a claim that carries a held code or coverage nobody verified. The denial arrives weeks later, and staff spend that week's margin unwinding it.

✗ Clinical Detail In Plain Text

The sender puts a diagnosis or a result into an ordinary text message. That is a reportable privacy breach, and the practice owns it, not the agent.

Directional Outcomes

What the agent counts, and the station that counts it.

These counts are the tallies from one monitored run of the agents. They are not monthly or annual totals.

visits confirmed against the appointment book
Counted at Visit Confirmation
23
reminders sent carrying clinical detail
Counted at Visit Confirmation
0
coverage flags left on the schedule
Counted at Visit Confirmation
1
notes drafted into their SOAP sections
Counted at Visit Documentation
24
doses guessed where the audio was unclear
Counted at Visit Documentation
0
blanks and flags handed to the provider
Counted at Visit Documentation
2
codes drafted off the signed notes
Counted at Visit Coding
58
codes written without a sentence behind them
Counted at Visit Coding
0
held codes carried to a person on their claim
Counted at Visit Coding
1
summaries sent through the portal
Counted at Recall Booking
19
clinical questions answered in a provider's name
Counted at Recall Booking
0
plans flagged back to their provider
Counted at Recall Booking
1
Our measurement policy: We do not publish precise ROI without baseline methodology. Every figure above carries its basis.

What Runs Where

Every step names the subagent that does the work, the record it writes, the thing that raises a question for a person, and what it is allowed to touch. This is drawn from the source, not from a diagram somebody kept in sync by hand.

1Visit Confirmation
subagentvisit-prep
writesvisits/<visit-id>/prep.json
raiseshold-clinical-text
may touchvisits/**, the schedule read-only, the portal send-only
2Visit Documentation
subagentnote-draft
writesvisits/<visit-id>/note-draft.md
raisesunsettled-term
may touchvisits/<visit-id>/**, the chart read-only
3Note Signing
GATE
subagentnote-sign
writesvisits/<visit-id>/note-signed.md
raisesawait-signature
may touchvisits/<visit-id>/**, everything else read-only
4Visit Coding
subagentvisit-code
writesvisits/<visit-id>/codes.json
raiseshold-unsupported-code
may touchvisits/<visit-id>/**, the signed note read-only, the payer rules read-only
5Claim Submission
GATE
subagentclaim-out
writesclaims/<claim-id>.json
raisesawait-held-claim-decision
may touchclaims/**, visits/** read-only
6Recall Booking
subagentfollow-through
writesvisits/<visit-id>/follow.json
raisesroute-clinical-reply
may touchvisits/**, the portal send-only, the schedule
7Practice Review
GATE
subagentweek-close
writesrules/proposed/<rule-id>.json, reports/week-<date>.json
raisesaccept-rule-change
may touchrules/proposed/**, reports/**, the history read-only

Stack

Every system this agent reads or writes.

System
Read at
Stations
the EHR signing queue
Note Signing
1 of 7
the EHR synced both ways over FHIR
Visit Documentation
1 of 7
the allergy and medication lists
Visit Documentation
1 of 7
the chart record
Visit Confirmation
1 of 7
the claim record
Visit Coding
2 of 7
the clearinghouse
Claim Submission
1 of 7
the code sets
Visit Coding
1 of 7
the compliance report
Practice Review
1 of 7
the correction record
Note Signing
1 of 7
the correction record from station 3
Practice Review
1 of 7
the coverage flags from station 1
Claim Submission
1 of 7
the denial record
Practice Review
1 of 7
the dictation capture
Visit Documentation
1 of 7
the draft notes
Note Signing
1 of 7
the formulary
Visit Documentation
1 of 7
the patient portal
Visit Confirmation
2 of 7
the payer eligibility lines
Visit Confirmation
1 of 7
the payer portals
Claim Submission
1 of 7
the payer rule files
Visit Coding
1 of 7
the pharmacy lines
Recall Booking
1 of 7
the referral record
Recall Booking
1 of 7
the schedule
Visit Confirmation
2 of 7
the signed notes
Visit Coding
1 of 7
the week's visit trail
Practice Review
1 of 7
Next Step

Want to see if this pattern fits your healthcare?

Start a ConversationSee More Work
No build commitment·Real samples, not a demo·Estimate in writing