For healthcare operations
One procedure on paper. As many versions as you have staff.
Eligibility and benefits, prior authorization, claim status, denials and appeals. At scale the question is not whether the work repeats, it is how far each desk has drifted from the documented procedure and what that drift is costing. Orchard records how the work is actually performed, desk by desk, and turns the repeatable stretch into a supervised Playbook you own.
The shape of the problem
Where the hours actually go
The documented procedure is not the performed one
Policy describes one path. A floor of specialists runs dozens, each defensible, none written down, and the variance stays invisible until it surfaces somewhere expensive.
Training never catches up with attrition
Each cohort learns from whoever has capacity that week. The distance between your best desk and your median desk is margin, and nobody can currently measure it.
The work lives between the systems
EHR, payer portal, clearinghouse, spreadsheet. The handoffs nobody owns are where accounts age, and no integration project reaches them because they are performed by hand at the interface.
What the record holds
Everything above is already happening. None of it is written down.
- Which payer portal, which work queue, and how many times the same authorization screen is re-opened
- Where one specialist’s route through a denial diverges from the person sitting beside them
- The exact fields carried out of the EHR into the payer portal and back into the account note
- How long an eligibility response stays on screen, and how often the account is returned to afterwards
- Which accounts are touched a second and third time, and the step the earlier pass stopped at
At a hundred desks, a month of this is more than ten million recorded observations. Scale is not the obstacle here, it is the instrument: divergence between desks only becomes legible once you have enough of them.
The work
Eligibility, authorization, and denials
The repeatable stretch of your own operation, learned from the desks that already run it best.
- Verifying eligibility and benefits ahead of the schedule
- Assembling authorization requests the way each payer expects them
- Working denial and rejection queues through to resolution
- Keeping referrals and appeals moving instead of aging
How it learns the work
Watched, learned, proposed, then armed by you
It starts by watching
Install quietly and keep working. Every five seconds Orchard records which application has focus and what was done inside it: the screen, the control, the value in the field, what was copied and where it landed. Never a screenshot, a printable keystroke, or a password.
Repeated work becomes evidence
One desk generates thousands of observations a day. Across weeks they resolve into the shape of the job: the steps, what varies each time, what never does, which exceptions are real rather than noise, and what the whole thing costs in hours. You do not have to know what to automate first.
It asks before it acts
When the evidence is strong enough, Orchard proposes the piece of the work it is ready to take on, with the receipts underneath it. Nothing runs until someone on your team arms it.
Supervised first. Autonomy earned.
Armed work runs supervised: outward writes wait for approval, every run keeps a step-by-step record, and your team decides when a proven Playbook has earned more room.
Where this work happens today
It records in the systems you already use
- Epic
- Oracle Health
- athenahealth
- Availity
- Waystar
- Excel
- Outlook
Orchard records at the interface, on the same screens your team already uses. No API, no integration project, and no system that has to expose its data before Orchard can see the work happening in it.
Control before autonomy
Your hand stays on the controls
- Not employee surveillance: Orchard keeps task structure, decisions, and outcomes — never screenshots, printable keystrokes, or passwords.
- Nothing acts unreviewed. Work begins supervised, and approvals sit in front of anything that leaves your systems.
- Autonomy is chosen, not assumed — and your team can pause everything at any time.
- Your business owns the result: the Playbook, its procedures, and the record of every run.