Healthcare · BPO Services
Home health billing operations: ATRIO Home Health Care
A St Paul home care provider needed caregiver visit records turned into clean claims every cycle: EVV reconciled, hours checked against the authorisation, claims submitted, and denials coded by reason rather than re-keyed.
By the numbers
- 15 minutes Authorisation unit
- 6 Things built
The challenge
A home health agency employs the support workers but carries the financial risk when a claim fails. At ATRIO the failures were being found in the wrong place: EVV gaps, timesheet mismatches and authorisation ceiling overages were surfacing after payment, sometimes weeks later, by which point the caregiver could no longer explain the discrepancy and the money had already been counted.
Two things made that worse. Minnesota DHS conducts post-payment review and can recover funds for claims unsupported by EVV records, so a late discovery is not a tidy-up, it is an exposure. And the programme transition that replaced Personal Care Assistance with CFSS from 1 October 2024 added coding complexity on top of an already manual reconciliation that was consuming office hours better spent on recruitment and client care.
What we changed
We moved the reconciliation to the front of the process. The desk now runs four stages in order: EVV and visit data reconciled against timesheets, timesheets and authorisations checked against the client’s service units, claims prepared and submitted against the programme actually delivered, and denials followed up with a reason code attached.
The ordering is the whole intervention. Checking before submission catches a missing capture while the caregiver can still say what happened; checking after payment catches it when the only remaining option is a correction. The service-authorisation unit is 15 minutes, which is small enough that a rounding habit nobody had noticed becomes an overage at the end of a cycle.
What changed for the agency
Reconciliation now happens before submission rather than after payment, and the office team’s time moved from chasing paid claims to recruitment, compliance and client care. Denials carry a reason code, which means the recurring causes are visible as a list rather than as a feeling.
Until those are confirmed there are no performance figures on this page, which is deliberate.
The project in detail
The summary above is what changed. What follows is how: where a home health claim actually fails, the order the desk runs in and why the order is the whole intervention, and what another agency in the same position should take from it.
A claim does not fail at submission. It fails at the visit.
Almost every denial on a home care claim is decided hours before anybody opens the billing system. A caregiver arrives and the electronic visit verification capture does not complete. A timesheet says ninety minutes where the authorisation allows sixty. A programme code is applied that does not match the service actually delivered. None of that is visible from the claim — the claim looks clean.
So the failure surfaces at the far end, as a denial or, worse, as a post-payment recovery. By then the caregiver has worked twenty more visits and cannot reconstruct the one in question, and the money has already been counted as revenue. The agency is not disputing a claim at that point; it is trying to remember one.
The four stages, in the order that matters
The desk runs the same four stages every cycle, and the sequence is the intervention rather than any one stage in it.
- Reconcile EVV against the timesheet. Before anything is coded. A gap found here is a question a caregiver can still answer.
- Check the timesheet against the authorisation. Units delivered against units approved, per client, per period — not at the end of the month when the ceiling has already been passed.
- Prepare and submit against the programme actually delivered. The code follows the service, not the habit.
- Follow up denials with a reason code attached. So the cause is recorded at the moment somebody knows what it was.
Every one of those checks existed before. They ran after payment. Moving them in front of submission is the entire change, and it is why this is an operations project rather than a billing one.
What a fifteen-minute unit does to a rounding habit
The service authorisation unit here is fifteen minutes. That is small enough that a habit nobody has ever named — rounding a visit up to the next quarter hour, consistently, because it feels tidier — becomes an overage across a caseload by the end of a cycle. Nobody is doing anything wrong and the money is still recoverable by the payer.
A desk that only looks at claims never sees this, because each claim is individually plausible. A desk that reconciles units against authorisations sees it as a pattern in week two. That is the difference between a control and a report.
Reason codes turn a feeling into a list
Before, the office knew denials were “mostly EVV stuff”. Afterwards, denials carry a reason code, which means the recurring causes can be counted, ranked and fixed at source — a caregiver who needs retraining on the app, a client whose authorisation renewal is always late, a programme whose coding changed. Monthly reporting is by cause rather than by volume, because volume tells you how busy the desk was and cause tells you what to change.
How it ran
- Process capture. Sat with the existing process and wrote down what actually happens, including the parts nobody had written down.
- Procedure drafting and approval. One written procedure per stage, approved by the agency before go-live rather than described afterwards.
- Parallel running. The desk ran alongside the existing process until the reconciliation was catching what the old route caught, and more.
- Handover to steady state. Monthly exception reporting by cause, and a named owner on both sides.
The agency owns the clinical and contractual substance throughout. OveliTHub is responsible for the procedure being followed, recorded and reported, which is the part a BPO desk can be accountable for.
What another home health agency should take from this
Move the check in front of the money
Any check that currently runs after payment is a check that runs when it can no longer be answered. Moving it before submission usually costs nothing but sequence.
Write the procedure before you outsource the work
A desk without a written, approved procedure is a group of people guessing consistently. The procedure is the deliverable; the staffing is how it gets run.
Code the denial, not just the resubmission
Fixing a denial recovers one claim. Recording why it happened is what stops the next forty.
Home health billing questions
Is this billing, or is it operations?
Operations, with billing as the output. The submissions are the visible part, but the work that changes the result is the reconciliation that happens before them. An agency buying only claim submission usually still has the problem it was trying to solve.
Who is accountable for a claim that still fails?
The procedure names it, per stage, before go-live. Where a failure is upstream of the desk — a missing capture, a late authorisation renewal — it is reported as that rather than absorbed, because a desk that quietly absorbs upstream failures is a desk that hides them.
How long does a desk like this take to stand up?
The constraint is procedure approval, not staffing. Writing down what actually happens and getting it agreed is the slow part; once it is agreed the desk runs in parallel before it runs alone. Our medical billing support guide sets out the stages in general terms.
What about the data?
We act as a processor and the agency remains the controller. Access is role-based and logged, and the terms are signed before any record reaches us. Related reading: healthcare BPO services and insurance verification support.
The build
What was actually delivered
The scope as it shipped, not as it was proposed. Anything added or dropped along the way is described in the study above.
- EVV and visit data reconciled against caregiver timesheets before submission
- Timesheet and authorisation checks against the client service units
- Claim preparation and submission coded to the programme actually delivered
- Denial follow-up with reason coding, so patterns surface rather than repeat
- A written procedure for each of the four stages, approved before go-live
- Monthly reporting on exceptions by cause rather than by volume
What our clients say
What clients said about work like this
Published by the clients themselves on Instagram, Trustpilot, Google and Facebook, with their names against them. Nothing on this page was written on a client’s behalf.
Happy with their Pinterest and Instagram marketing and optimization. The results have been fantastic.
Dylan Hardcastle
Owner, Renuskinclinic UK
As a small business owner navigating the digital landscape, their expertise has been a game-changer.
Jeffery Dread
CEO, Deals Lova
They improved our on-page SEO, and now the website is getting stronger, more meaningful results.
Sonia Sunghea Park
Owner, TimelessSkinCare Clinic UK
Extremely satisfied with their Facebook and Instagram advertising and optimization. The results have been truly outstanding.
Anthony Piccirillo
CEO, A&L Agency
Amazing experience. OveliTHub improved the design and significantly improved my website performance.
Vida
Founder, Vida Hair & Beauty UKMore work
Other projects worth a look
Telehealth and concierge care website: WheelHouse Health
A Virginia telehealth and concierge primary care practice needed a site that explains two different care models, publishes membership pricing openly, and routes every…
WheelHouse Health Client
Google Ads and Shopping: ManCave
Shopping results are matched from product data, not from keywords, so the campaign work started in the feed rather than in the bidding.
ManCave Client
Salon website: Vida Hair & Beauty
A premium salon site built to present the treatment list clearly, earn trust on a phone screen, and route visitors to a booking enquiry.
Vida Hair & Beauty Client
