What EVV actually requires: a plain-English guide
If you run a home care or community-based care agency that bills Medicaid, you’ve almost certainly been told you need EVV — Electronic Visit Verification. What’s often left unexplained is what EVV actually requires, and why most agencies end up resenting the system they bought to do it. Here’s the plain version.
What EVV is, and where it comes from
EVV is a federal requirement under the 21st Century Cures Act. It applies to Medicaid-funded personal care services and home health services — care delivered to someone in their home or community rather than in a facility. The goal is simple: electronically confirm that a visit actually happened, the way it was billed.
To do that, every visit has to capture six data points:
- The type of service performed
- The individual receiving the service
- The individual providing the service
- The date of the service
- The location where the service was delivered
- The time the service begins and ends
That’s the whole core of it. Six facts, captured electronically, for every visit. Implementation details — which model your state uses, what aggregator it requires — vary, but those six points are the constant.
Why it’s a headache in practice
The requirement is reasonable. The pain comes from how agencies bolt it on.
- It’s usually a separate system. Most agencies buy EVV from a dedicated vendor (the big aggregators) and run it alongside whatever they already use for scheduling and care documentation. So the caregiver clocks the visit in one app and documents the care in another.
- The same information gets entered twice. The visit time, the client, the caregiver — EVV needs all of it, and so does your care record. Two systems, one set of facts, entered by hand in both.
- Mismatches cause claim denials. When the EVV record and the billing record disagree — a time that’s off by a few minutes, a location that didn’t register — the claim bounces. Reconciling those is its own job.
None of that is required by the law. It’s a consequence of treating EVV as a standalone compliance box rather than part of how a visit is already recorded.
What to look for in an EVV approach
Whether you evaluate us or anyone else, the questions that matter:
- Is EVV captured as part of the visit record, or a separate clock-in app? If the caregiver documents care and the visit is verified in the same step, you’ve eliminated the double entry and the mismatch risk at the source.
- Does it capture all six required data points automatically? Location and time should come from the device, not from a caregiver typing them later.
- How does it handle your state’s model and aggregator? EVV requirements are federal, but the plumbing is state-specific. Ask directly whether your state is supported, and what happens at onboarding if it needs to be built out.
- What does a denied or mismatched visit look like, and how do you fix it? A good system makes the exception visible and correctable; a bad one buries it until the claim is rejected.
How we think about it
We built EVV-ready visit verification into the same record where care is logged — so the six data points are captured once, as part of documenting the visit, instead of in a separate compliance app. The caregiver does one thing; the EVV trail and the care record come from the same source of truth. EVV plumbing is state-specific, so the honest answer on “does it work in my state” is a conversation, not a checkbox — book a short demo and we’ll tell you exactly where things stand for your state.
The bottom line
EVV is six data points, captured electronically, for Medicaid home and community-based visits. The requirement isn’t the problem — running it as a second system is. The less your EVV looks like a separate app and the more it looks like a byproduct of documenting the visit you’re already doing, the less it’ll cost you in double entry and denied claims.
— Del Peck Founder, TinyGuard
TinyGuard puts cameras, care logging, billing, and compliance on one on-site box. Book a 15-minute demo or see the pricing.