Summary
Electronic visit verification has moved from a compliance requirement agencies were implementing to one that states are actively enforcing through automatic claim rejections, corrective action plans, and payment holds — and the agencies managing it well are the ones whose EVV data flows directly into billing without a manual reconciliation step in between. The two things that protect your revenue cycle most effectively are a validated aggregator integration that matches your specific state’s implementation model and a caregiver mobile experience that makes real-time clock-in the default rather than the exception. If you’re looking for home care software with electronic visit verification built in as a core module — not an add-on — that handles aggregator integration, compliance monitoring, and billing synchronization in one platform, myEZcare is worth a serious look.
Introduction
A caregiver clocked out of a three-hour visit at 4:47 p.m. from a location two miles from the client’s home. Nobody caught it until a Medicaid auditor flagged the discrepancy six months later and requested full documentation for twenty-three claims.
That’s the problem electronic visit verification was designed to solve — and in most states, it’s now federal law that you use it.
If you’re running a Medicaid-funded home care or home health agency, electronic visit verification isn’t optional and it isn’t a future consideration. The 21st Century Cures Act mandated electronic visit verification for personal care services and home health services under Medicaid, and states have moved decisively from soft enforcement to hard edits that reject claims automatically when EVV data is missing or incomplete. Understanding what electronic visit verification requires, how it works, and where agencies most commonly get it wrong is the foundation of a billing process that doesn’t hemorrhage revenue on preventable rejections.
What Electronic Visit Verification Actually Requires
Electronic visit verification is a federally mandated system that electronically captures and verifies six specific data points for every covered Medicaid home care visit. Those six elements are: the type of service delivered, the individual receiving the service, the caregiver providing it, the date of the visit, the precise start and end times, and the location where the service was provided. Every covered visit must have all six captured electronically at the point of care — not reconstructed after the fact, not manually entered at the end of the day.
The six-element requirement is the federal floor. States can and do add requirements on top of it — specific aggregator connections, data format standards, transmission deadlines, and compliance thresholds that vary by state and sometimes by managed care plan. Electronic visit verification compliance in practice means satisfying both the federal data requirements and the specific technical and timing requirements of your state’s chosen implementation model. Agencies that understand the federal floor but haven’t tracked their state’s specific overlay are the ones discovering compliance gaps during a billing cycle, which is precisely the wrong moment.
What electronic visit verification doesn’t dictate is the specific technology your agency uses to capture that data — unless your state has chosen a state-mandated system. In open-model states, agencies can use any CMS-approved EVV vendor as long as that system integrates with the state’s designated aggregator and transmits data in the required format. That integration point — between your EVV software and your state’s aggregator — is where most technical compliance failures originate.
The Five EVV Implementation Models You Need to Know
CMS approved five implementation models for electronic visit verification, and which model your state has adopted determines how your agency’s system needs to be configured. Getting this wrong is an infrastructure error that shows up in every billing cycle until it’s corrected.
Here’s what each model means for your agency’s electronic visit verification setup:
- Provider choice model — The agency selects its own EVV vendor from a list of CMS-approved options and manages its own system. Most common in larger states. Your EVV vendor must integrate with the state aggregator.
- Managed care organization (MCO) choice model — Each managed care plan selects its own EVV system. Agencies serving clients across multiple MCOs may need to support multiple EVV systems simultaneously.
- State-mandated in-house model — The state operates its own electronic visit verification system and requires agencies to use it directly. No third-party EVV vendor choice.
- State-mandated external vendor model — The state contracts with a specific EVV vendor and requires all agencies to use that platform.
- Open model — Agencies may use any approved EVV system, with data flowing through a state-designated aggregator like Sandata, HHAeXchange, or AuthentiCare.
If you’ve been operating in a state that recently changed its EVV model — or if you serve clients across multiple states — your electronic visit verification configuration needs to reflect each state’s current model, not the model that was in place when you first set the system up. Model changes are announced through state Medicaid bulletins that don’t always reach agency owners directly.
What Happens When Electronic Visit Verification Data Is Incomplete
States have moved from soft-edit enforcement — where claims with minor EVV data issues were paid with a warning — to hard edits that trigger automatic rejections with no grace period. Missing or incomplete electronic visit verification data doesn’t generate a flag for human review in most states now. It generates a denial. The claim goes back without payment, and your billing team has to correct and resubmit while the visit record ages.
The two most expensive electronic visit verification failure modes are high manual entry rates and aggregator mismatches. Manual entries — retroactive edits made after a visit because a caregiver didn’t complete real-time clock-in and clock-out — are now treated as a primary audit indicator in multiple states. Pennsylvania has established a 15% threshold where exceeding that manual entry rate triggers a formal compliance review. Texas requires an 80% mobile app usage rate and issues corrective action plans when agencies fall below it. Electronic visit verification compliance isn’t just about having a system — it’s about your caregivers actually using it correctly, every visit, in real time.
Aggregator mismatches are the second major failure mode. In open-model states, your electronic visit verification data has to reach the state aggregator in the correct format through a validated integration pipeline. A configuration error in that pipeline generates rejection notices that are often indistinguishable from clinical documentation failures — which means billing teams spend time investigating technical problems they may not have the visibility to diagnose. Electronic visit verification software with a validated, maintained aggregator integration removes that failure point from your billing workflow.
How Electronic Visit Verification Connects to Your Billing and Compliance Systems
The agencies getting the most value from electronic visit verification aren’t just using it to satisfy a mandate. They’re using the visit data it captures as the foundation of their entire billing and compliance operation. When electronic visit verification data flows automatically into your billing platform, the visit record that satisfies your state’s EVV requirement is the same record your billing team submits for payment — no manual reconciliation, no cross-referencing two systems before each claim cycle, no re-entry errors between verification and submission.
That integration matters more in the current enforcement environment than it ever has. Electronic visit verification data that lives in a standalone app but doesn’t connect to your billing system means someone on your team is manually moving information between them before every billing run. That manual step is where data integrity breaks down, where errors enter claims, and where compliance exposure accumulates quietly. Electronic visit verification built into your scheduling and billing platform as a native module — not a third-party integration bolted on — eliminates that manual step entirely.
Electronic visit verification also generates operational data that most agencies aren’t using effectively. Visit completion rates by caregiver, geographic patterns in clock-in timing, routes that consistently show late arrivals — that information lives inside your EVV system and surfaces patterns that directly affect scheduling efficiency, caregiver retention, and billing accuracy when your platform makes it visible. Electronic visit verification compliance and operational intelligence aren’t separate outcomes. They’re both products of the same visit data when your system is configured to surface both.
See how myEZcare’s built-in electronic visit verification connects real-time visit capture, state aggregator integration, and billing in one platform built for Medicaid home care and home health agencies. Schedule a free demo today and find out exactly where your EVV compliance stands.
