Worked example · Meridale Health · Example company
One health system, five people, one year.
Meridale Health is a regional health system. Its board has goals, its revenue cycle team runs a process spread across policies, procedures, years of records and the experience of its people, and the pieces do not always agree. This is how Inovagio learns that business and puts it to work.
Every health system has these five roles.
The board
Sets the plan
Three-year goals, and the budget that funds them.
Elena Brooks
CEO
Needs every team pulling toward the same goals.
James Whitfield
Director of Revenue Cycle
Runs a process spread across policy, records and experience.
Aisha Rahman
Senior Denials Specialist
Handles the payer exceptions the procedures leave unclear.
Tom Becker
Payment Posting Specialist
Keeps every remittance posted and every account balanced.
The board sets the goals; the team shows how the work is really done.
Week 1
The board’s plan goes in first
The strategy, the budget and the regulatory commitments become the top of Meridale’s rulebook: every denial worked before its appeal deadline, every payment checked against the contract, grow without adding to the backlog. Each goal carries its owner and its target.
Week 2
The CEO’s interview becomes a draft
Elena answers one question: what must be true in twelve months? Her answers become a draft the executive team accepts, edits or rejects in one meeting.
Weeks 3 to 6
The Director of Revenue Cycle describes the process
“Every payer has its own rules, every contract has its own rates, and our procedures, our systems and our people don’t always agree.” His interview, the payer contracts and the denial history become a first draft, with its open questions listed, that his team corrects.
Weeks 4 to 8
It learns from the procedures, the records and the specialists
Aisha and two other specialists walk through how the work is really done: where it follows the procedures, where it differs, and where the procedures are unclear.
Week 8
Every task traces to a goal
Each rule links up to the goal it serves and down to the Virtual Employees that follow it, with its reason one click away. The same pattern serves payment posting: when a remittance pays a line below the contract rate, the AI holds Tom’s posting and asks.
Where policy and practice part.
In his interview, James says every denied claim is appealed. Aisha says: “Not when the payer missed an authorization we had. Then we send a corrected claim with the number. An appeal is for when the payer disputes the facts.” Two other specialists agree. Inovagio flags the gap instead of guessing, and James decides, with the Compliance Officer as second approver: when the authorization was on file, send a corrected claim with its number; otherwise draft the appeal with the record pages it cites, for a person to sign. That approved rule is now followed on every denial.
- The gap between policy and practice is where AI that only reads documents goes wrong.
- Every rule links back to the interviews and documents it came from.
- Nothing is used until an expert approves it.
Rule review · Authorization denials
Meridale Health · Patient financial services
Stated rule
Every denied claim is appealed.
Director of Revenue Cycle · interview
Actual practice
When the authorization was on file, a corrected claim with its number goes back instead of an appeal.
Three specialists · interviews
Approved rule
Authorization on file: send a corrected claim with its number. Otherwise: appeal with the cited pages, signed by a person.
Approved by the Director of Revenue Cycle and the Compliance Officer
In force on every denial. The Virtual Employees follow version 2, and each corrected claim links back to the rule and the interviews it came from.
What Meridale sees.
Every name and record here is an example.
- The card app its people use to decide and correct.
- A map of how its records connect.
- Search that finds the rule in other words.
- The workflow its Virtual Employees follow.
The AI drafts. Aisha decides every one.
Nothing goes out without a person. Every correction teaches the Virtual Employees, and they take on routine work one payer at a time, after go-live and as accuracy holds.
A draft for every denial.
Each denial arrives matched to the payer’s reason, the claim and the record, with a corrected claim or an appeal drafted, for Aisha to mark right or wrong.
Every correction teaches it.
When a draft is wrong, Aisha says why: a payer’s new rule, a missing page. “The drafts improved every week, because my corrections became approved rules.”
Meridale stays in control.
It runs in Meridale’s own data center, and Meridale owns the data and the models. Patient records stay there.
Aisha’s new job.
The target: Aisha spends her day on the denials that need a phone call. The “with Virtual Employees” column is what shadow mode measures before anything goes live: a target, never a result.
| Aisha’s work | Today | With Virtual Employees |
|---|---|---|
| Her day | Matching each denial to its claim and record by hand | The denials that need a call or a clinical conversation |
| Routine denials | Every one by hand | Reviews only the ones the Virtual Employees flag, and rates each result: right, wrong, and why |
| When a payer changes its rules | Finds out from the next denial | Approves the rule changes her feedback raises |
Denials worked on time, with a record of every appeal.
- Routine denials worked inside rules Meridale’s own experts approved, with only the exceptions sent to a person.
- Each remittance line checked against the contract, with every underpayment raised for a person to dispute.
- The cost of every denial worked, shown beside what the same work costs today.
- Every decision shows the rule, the record and the person who approved it.
- The knowledge, the models trained on it and the record belong to Meridale.
Start with one workflow and the people who know it.
A 30-minute briefing on how Inovagio would learn one of your workflows, where your people approve, and the record it leaves.