What Should an Agency Do While WellSky EVV Transactions Are Failing and Medicaid Claims Go Unpaid?
How to Protect Medicaid Cash While the EVV Feed Is Down
The goal is simple: no visit delivered during the outage goes unbillable, and compliance for the whole window can be proven on paper. Here is what does that, move by move.
1. Run a Parallel Verification Log the Day the Feed Breaks
The moment the EVV transactions start failing, do not wait for the vendor to fix it before documenting visits. Stand up an independent, time-stamped log of every visit as it happens: date, caregiver, patient, start and end time, and service delivered. This is your billable proof and your compliance evidence, captured while it is fresh and accurate. Reconstructing it weeks later from memory and fragments is the disaster; capturing it in real time is the insurance policy.
2. Reconcile the Log Against the Aggregator When the Feed Recovers
When the EVV feed comes back, the vendor system and your parallel log will not automatically agree. Match every visit in your log against what actually landed in the state aggregator, find the gaps where the feed dropped or duplicated transactions, and correct the linkage. This reconciliation is what converts your outage-period care into visits the state can see as verified, which is the precondition for getting paid at all.
3. Resubmit Affected Claims With Corrected EVV Linkage
Claims denied or held for missing EVV during the outage do not fix themselves when the feed returns. Each one has to be resubmitted with the corrected verified-visit linkage, in the order and format the payer expects, and tracked until it actually pays. Working the resubmission queue deliberately, oldest and largest first, is how the unpaid pile that built during the outage actually turns back into cash instead of aging out past timely filing.
4. Manage the Payer Appeal Trail for the Whole Outage Window
An EVV outage is a compliance event, not just a billing hiccup, and the payer will want to see that the visits were real and the failure was vendor-side. Keep the appeal trail for the entire window: the outage dates, the parallel log, the reconciliation, and the resubmissions, all documented as one defensible package. That trail is what protects the agency if visits are questioned, and it is what turns a stretch of EVV non-compliance into a documented, recoverable event instead of a financial hole nobody can explain.
5. Hand EVV Reconciliation and Recovery to a Dedicated Team
Agencies that survive an EVV outage without a cash crisis do it by handing the reconciliation and recovery to a dedicated team: remote specialists who run the parallel log, reconcile against the aggregator, resubmit the claims, and hold the appeal trail, live in 1 to 2 weeks. The agency keeps delivering care, the biller stops drowning in denied Medicaid claims, and the outage stops being a financial disaster. Below is what it sounds like when nobody owns it yet, in providers’ own words.
Key Pain Points and Discussions by Providers
real reports from practice staff, lightly edited
“We were EVV non-compliant for over a month because the transactions kept failing and there was no fix from the vendor side. The Medicaid claims went unpaid the whole time. I can only describe it as a financial disaster we did not cause.” – administrator, home health agency
“The visits were real, every one of them. But when the EVV feed breaks, Medicaid does not care that care happened; it cares whether it can see a verified visit, and we had no independent trail to prove it.” – billing manager, home health agency
“Reconstructing weeks of compliance evidence after the outage took longer than the outage itself. If we had kept a parallel log from day one, we would have had our proof ready instead of piecing it together backward.” – revenue cycle lead, home health agency
“Nobody owned the reconciliation when the feed came back. The transactions had dropped and duplicated in ways nothing flagged, and until someone matched every visit against the aggregator, the claims just sat unpaid.” – office manager, home health agency
“The appeal trail is what saved us in the end, but we built it late and under pressure. Documenting the outage window, the visits, and the vendor failure as one package is the thing I wish we had started on day one.” – practice administrator, home health agency
Our Answer
Here is what we actually do. The day the EVV transactions start failing, a dedicated remote specialist stands up a parallel, time-stamped verification log so every visit is documented as it happens, independent of the broken feed. When the feed recovers, they reconcile that log against the state aggregator, find the dropped and duplicated transactions, correct the linkage, and resubmit every affected Medicaid claim in the format the payer expects, tracking each until it pays. Throughout, they hold the appeal trail for the whole outage window as one defensible package. Our specialists are credentialed professionals, overseas-trained physicians and US-licensed nurses and pharmacists, working inside the WellSky environment and your state EVV portal, with AI drafting the first-pass reconciliation and a human verifying every visit and claim. This is our revenue cycle management paired with an AI-first workflow, in one paragraph.
Why This Keeps Happening
If the visits are real, why does Medicaid refuse to pay? Because electronic visit verification is a federal mandate, not an optional feature. Section 12006 of the 21st Century Cures Act requires states to implement EVV for Medicaid personal care and home health services that involve an in-home visit, with the home health deadline set for January 1, 2023. EVV electronically confirms that a visit occurred, when it started, and when it ended, and Medicaid pays against that verification. When the vendor-side transaction feed breaks, the care still happens, but the verification that Medicaid pays on does not exist, so the claim has nothing to bill against.
The exposure is bigger than a batch of held claims. States face incremental federal funding reductions of up to one percent for failing to comply with the EVV mandate, so the pressure to keep verification intact runs all the way up the chain, and agencies that go non-compliant during an outage are caught in the middle of it. A stretch of failed transactions is not a quiet billing lag; it is a compliance gap that has to be documented and defended, and the longer it runs without an independent record, the harder it is to prove the visits were real. That is why a disciplined denial management and appeals workflow matters most exactly when the feed is down.
And the reason it becomes a disaster rather than an inconvenience is timing. The reconstruction is always harder after the fact than the capture would have been in the moment, because memory fades, staff turn over, and the aggregator data is incomplete. An agency that starts a parallel log on day one has its proof ready; an agency that waits until the feed returns is reconstructing weeks of compliance evidence backward, under timely-filing pressure, while new visits keep piling on. The outage is survivable. What turns it into a financial hole is having no independent trail while it runs.
Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:
| What you tried | What actually happened | Who ended up doing the work |
|---|---|---|
| Waited for the vendor to fix the EVV feed before acting | Weeks of visits went undocumented independently, and some claims aged toward timely-filing while the agency waited | A vendor that could not restore the feed |
| Tried to reconstruct compliance evidence after the outage | Rebuilding weeks of visit proof from memory took longer than the outage and left gaps | Whoever was left piecing it together |
| Assumed the feed would reconcile itself on recovery | Transactions had dropped and duplicated; claims sat unpaid until someone matched every visit by hand | A recovery that never happened automatically |
| Gave EVV reconciliation and recovery to a dedicated remote specialist | Parallel log from day one, aggregator reconciled, claims resubmitted, appeal trail held as one package | Someone whose whole job it is |
The Solution
So what does “someone whose whole job it is” look like during an EVV outage? The specialist starts on day one, not after recovery: a parallel, time-stamped verification log capturing every visit as it happens, independent of the broken feed. That log is the billable proof and the compliance evidence, built while it is fresh and accurate instead of reconstructed backward under pressure. Protecting cash during a feed failure is a documentation-and-timing problem, and that is exactly what dedicated revenue cycle management is built to handle before the outage becomes a hole.
When the feed recovers, the specialist runs the reconciliation the agency rarely has bandwidth for: matching every visit in the log against what actually landed in the state aggregator, finding the dropped and duplicated transactions, correcting the linkage, and resubmitting each affected Medicaid claim in the payer’s expected format, tracking it until it pays. Oldest and largest first, so nothing ages out while lower-value claims get worked. The unpaid pile that built during the outage becomes a worked queue instead of a growing loss.
Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow reconciles the log against the aggregator, flags the gaps, and assembles the resubmission and appeal packages; a person confirms every visit is real and owns the payer trail. Every security control that protects the visit and patient data moving through that process is documented and auditable, and the whole approach is described on our HIPAA and security page, because handling Medicaid visit and compliance data during an outage is only safe when the controls are real.
Who Actually Does This Work
Fair question: why would an outsourced team handle your EVV outage better than your own staff? Because reconciling visit verification and recovering Medicaid claims is their entire day, not the thing they scramble to cover while still delivering care. The people running your recovery are credentialed medical professionals: overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US home health revenue cycle and EVV compliance. They know what the state aggregator expects, how EVV transactions drop and duplicate during a feed failure, and how to assemble an appeal trail a payer will accept. That is not a task handed to whoever is free during a crisis; it is a specialty.
We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical agency is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so the reconciliation and recovery never stall because the one person who handles EVV is unavailable.
And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for HITRUST, ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.
Put the routine and the people together, and a specific list of things simply stops happening.
Ready to Protect Your Medicaid Cash Through an EVV Outage?
How We Permanently Fix the Process
A person alone is not the fix, and neither is a bot alone. The fix is a documented EVV-outage workflow: the parallel verification log that starts on day one, the reconciliation against the aggregator when the feed recovers, the resubmission queue worked by filing deadline, and the appeal trail assembled for the whole window. Before an outage ever hits, we build that playbook for a new agency so the response is a procedure, not a scramble, and the log is running the moment transactions start failing rather than days later when the damage is done.
From there the workflow becomes a living playbook rather than a panic in one biller’s head. It records how the parallel log is captured, how visits are matched against the state aggregator, how affected Medicaid claims are resubmitted and tracked, and how the appeal trail is assembled and kept. It is written down, kept current as EVV rules and aggregators change, and owned by the team. When your specialist is out, a trained backup runs the same playbook the same way, so an outage never catches the agency with no one who knows the recovery steps.
That is the difference between surviving this outage and being ready for the next one, and it is what a dedicated revenue cycle management partner actually buys you. A biller leaving used to mean the EVV recovery knowledge left with them. Under this model the workflow keeps running, the playbook stays, the backup steps in, and an EVV feed failure stops being the thing that quietly turns weeks of real care into unpaid claims.
The Whole Thing in Four Sentences
An agency loses Medicaid cash during a WellSky EVV failure because care keeps being delivered while the verified-visit trail Medicaid pays on does not exist, and EVV is a federal mandate under the 21st Century Cures Act, not an optional feature. Waiting for the vendor to fix the feed, reconstructing evidence after the fact, or assuming the feed self-reconciles all fail the same way, and claims age toward timely filing while everyone waits. The fix is a parallel verification log from day one, a reconciliation against the state aggregator on recovery, resubmission of affected claims by deadline, and an appeal trail for the whole outage window. A multi-branch home health agency runs exactly this model with us today, names withheld, no patient data shown.
If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.
Ready to protect your Medicaid cash through an EVV outage? Try us risk free: two weeks, your real EVV reconciliation and recovery queue, dedicated specialists holding the log and working the appeals, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.
One Flat Weekly Rate. 45 Hours of Coverage.
No hourly meters, no setup fees, no long-term contracts. Your dedicated team member covers your desk 45 hours every week, and a trained backup steps in at no charge whenever they are out.
One dedicated remote specialist running your parallel EVV verification log and Medicaid claim recovery, single-site home health agency on WellSky
5+ remote specialists covering EVV reconciliation, resubmission, and payer appeals across a multi-branch home health agency
10+ remote specialists, multi-location home health network, MSO, or PE-backed platform managing EVV compliance and Medicaid recovery across many branches
45 hours of coverage for less than others charge for 40.
Standard US full-time year: 40 hrs x 52 weeks = 2,080 hours, the federal basis for computing hourly pay per the U.S. Office of Personnel Management. A Staffingly plan: 45 hrs x 52 weeks = 2,340 hours a year, that is 260 additional hours included in your flat rate. $399/week x 52 = $20,748 a year / 2,340 hours = $8.87 per hour. Typical US market rates for healthcare virtual assistants run $9.50 to $13.00 per hour for 40 hours of coverage.
Recover Your Unpaid Medicaid Claims This Month
You have seen the whole method. The pilot proves it on your own EVV recovery queue, with a trail your team can defend every cycle.
Book a 2-Week Risk-Free PilotRequest Information
Single specialty or multi-site? One payer or many? Tell us your situation and we will map the right coverage within 24 hours.
Frequently Asked Questions
Where the Claims on This Page Come From
Sources & References
- Medicaid.gov Electronic Visit Verification. Federal guidance on the EVV mandate under Section 12006 of the 21st Century Cures Act, including the home health services implementation deadline. medicaid.gov
- HHS Guidance Portal, Cures Act Electronic Visit Verification. Federal guidance on EVV requirements, covered services, and incremental FMAP reductions for non-compliance. hhs.gov
- CMS Home Health Prospective Payment System and Billing Resources. Guidance on home health claims, timely filing, and Medicaid interaction for post-acute providers. cms.gov
- MGMA Practice Operations and Revenue Cycle Resources. Benchmarks and guidance on claim recovery, appeals, and cash flow for medical group and post-acute practices. mgma.com
- HFMA Revenue Cycle and Denials Management Resources. Guidance on payer appeals, resubmission workflow, and the revenue impact of held or aged claims. hfma.org
