Summary
North Carolina flipped the switch on EVV hard edits for home health on October 1, 2025, and the state’s Medicaid program now runs one of the most layered EVV setups in the country — three aggregators (Sandata, HHAeXchange, CareBridge), each tied to a different payer type. This post walks through what actually happened when NC moved from “pay and warn” to automatic denial, what tripped agencies up (taxonomy code mismatches, the 15% manual-entry ceiling, multi-vendor confusion), and what agencies in states still on soft launch should do now so their claims don’t stall the day the grace period ends. It closes with practical prep steps and a compliance disclaimer, since this touches active Medicaid policy.
Picture a Tuesday morning biller in Greensboro, pulling up NCTracks to check on a batch of home health claims. Half of them are sitting in edit 02077. Not because the visits didn’t happen — the aide was there, the client was helped out of bed, breakfast got made. The claim is stuck because the visit record never landed cleanly in the state’s EVV system. That’s the reality of an EVV hard edit: the care can be perfect, and the claim still won’t move.
North Carolina spent years easing into this. Personal Care Services went live with EVV back in 2021. Home health followed a longer road — a soft launch, a delay, another soft launch — before the state finally threw the switch to a full EVV hard edit on October 1, 2025. Claims with dates of service on or after that day get validated against EVV data before anything else happens. No match, no payment. If your state hasn’t hit that point yet, North Carolina’s rollout is worth studying closely, because the mistakes agencies made there are avoidable.
What an EVV hard edit actually changes
A soft launch is forgiving. Claims go through even when the EVV data is thin, maybe with a warning attached, maybe with a note for the file. It’s a grace period, and agencies tend to treat it that way — fix it later, no rush.
A hard edit removes that cushion entirely. NC Medicaid runs two specific EOB codes tied to this: 02077 fires when there’s no matching verified visit, and 02079 fires when the units billed don’t line up with what the EVV system captured. Neither code cares about intent. The claim either matches or it doesn’t, and once the hard edit is live, a mismatch means denial, not delay.
For agencies that built billing habits during the soft launch — batch-submitting claims and reconciling EVV gaps afterward — this is the part that stings. The reconciliation window disappears. Every mismatch has to get caught before submission, not after.
Why North Carolina’s setup is unusually hard to manage
Most states run EVV through a single state-designated aggregator. North Carolina doesn’t. Depending on which payer an agency bills, the system runs through a different vendor entirely:
- Sandata — used for NC Medicaid Direct and fee-for-service billing
- HHAeXchange — used for most LME-MCOs and Standard Plans
- CareBridge — used specifically for Healthy Blue
An agency serving a mixed client base — some fee-for-service, some through an LME-MCO, a few on Healthy Blue — ends up juggling three separate portals, three exception queues, and three sets of rules about what counts as a verified visit. It’s easy to see how a taxonomy code that’s correct for one payer gets submitted for another and bounces right back. Providers have to bill under taxonomy code 251E00000X or the claim gets denied outright, and that single detail has tripped up more agencies than anything else in the transition.
There’s also a manual-entry allowance worth knowing about: providers can enter up to 15% of visits manually when EVV genuinely can’t capture them electronically, but the state monitors that percentage closely, and leaning on it too often invites a Program Integrity audit rather than a payment fix.
What tripped agencies up during the hard launch
A few patterns showed up again and again once the hard edit went live, and they’re the kind of thing a home care agency in any state can prepare for ahead of time.
Caregivers clocking in through the wrong app for their assigned payer was the most common one — an aide using the HHAeXchange app for a client actually billed through CareBridge, for example, meaning the visit exists somewhere, just not where the claim needs it. Schedule mismatches were another frequent culprit: the service plan says four hours, the EVV record shows three and a half, and the claim gets caught even though nothing about the care was actually wrong. And a smaller but costly issue involved agencies routing claims straight to a payer instead of through the assigned EVV aggregator first, which guarantees a denial no matter how accurate the visit data is.
None of these are complicated fixes on their own. The problem is volume — one office staffer trying to catch all of this by hand across three payer systems, while also handling intake, scheduling, and everything else on a Tuesday.
The real lesson for agencies in other states
North Carolina’s hard launch didn’t fail because the rule was unreasonable. It caught agencies off guard because the systems underneath it — three aggregators, three login portals, three sets of exception logic — made manual tracking nearly impossible at scale. States moving toward their own hard edit deadline are watching this exact story play out.
The agencies that came through the NC transition cleanest were the ones that treated the soft launch period as a dress rehearsal, not a grace period to ignore. They tested every payer pathway before the deadline, confirmed taxonomy codes against actual authorizations, and built a habit of checking EVV exception queues daily instead of weekly. That’s not a technology problem to solve after the fact — it’s an operational discipline to build before the deadline hits.
Before your state’s grace period ends
If EVV enforcement in your state is still in soft launch, the work to do now is straightforward, even if it takes real hours to complete:
- Confirm which EVV aggregator applies to each payer you bill, and don’t assume one system covers everything
- Verify every taxonomy code on file matches what’s authorized, before a hard edit makes the mismatch a denial
- Train every caregiver on the correct clock-in method for their assigned client, not just the method that’s easiest
- Set a daily habit of clearing EVV exceptions instead of letting them stack up toward month-end
- Track manual-entry usage now, so it never creeps toward a percentage that draws audit attention
Conclusion
A hard edit doesn’t punish bad care. It punishes bad documentation, and North Carolina’s experience shows how quickly documentation gaps turn into real cash flow problems once the grace period disappears. Agencies that get ahead of it — payer by payer, code by code — are the ones still billing smoothly when the deadline everyone else scrambled for finally arrives.
This post is intended for general informational purposes and reflects publicly available Medicaid and EVV guidance as of publication. It is not legal or billing advice. Requirements vary by state and payer and can change with little notice — agencies should verify current rules directly with their state Medicaid program and assigned EVV vendor before making billing decisions.
Ready to stop juggling EVV exception queues by hand? See how myEZcare keeps EVV data, scheduling, and billing aligned in one place — talk to our team about your state’s compliance timeline.
