Observance Solutions
Home Healthcare

How to Implement Electronic Visit Verification (EVV) for Home Healthcare and Personal Care Services

Observance Solutions Engineering7 min read

EVV compliance isn't really about the technology - GPS check-ins and time stamps are the easy part. The real complexity is in exception handling and state-specific aggregator submission requirements.

What EVV requires, at minimum

The 21st Century Cures Act mandates EVV for Medicaid-funded personal care services (and home health services) nationally, requiring six data points for each visit: type of service performed, individual receiving the service, individual providing the service, date of service, location of service, and time the service begins and ends. Beyond these federal minimums, each state's Medicaid program specifies its own EVV model (state-run system, state-designated vendor, or open vendor model where providers choose their own EVV-compliant system that submits to the state) - this state-specific variation is the first major implementation decision, especially for any platform operating across multiple states.

Verification methods and their tradeoffs

Common verification methods include a caregiver's mobile app with GPS check-in/check-out, a telephony-based system (calling from the patient's landline or a fixed device at the location), and fixed-location devices. GPS-based mobile verification is the most common for platforms building their own solution, but needs to handle real-world edge cases gracefully: poor GPS signal indoors, a caregiver's phone being offline at check-in time, or a patient's location legitimately varying (community-based services delivered somewhere other than the home).

Exception handling is where most of the real work is

A verified, on-time, correctly-located visit needs no special handling - the operational complexity lives entirely in the exceptions: a late check-in, a missing check-out, a location that doesn't match the expected address, a manually entered visit because the app failed. Every exception needs a defined resolution workflow (caregiver or supervisor explanation, required documentation, approval before the visit is considered verified for billing) and an audit trail showing how it was resolved - state auditors and payers specifically scrutinize exception rates and how they're handled, not just the compliant-visit numbers.

Submission to state aggregators

Depending on the state's EVV model, verified visit data needs to be submitted in a specific format to either the state's own system or a state-designated aggregator, on a defined schedule - and submission failures or format errors can hold up billing, since many states require EVV verification as a precondition for Medicaid payment on these services. Build submission as a tracked, retryable process with clear failure visibility, the same way you'd treat claims submission - a visit that's verified but never successfully submitted is operationally identical to one that was never verified at all.

FAQ

Quick answers

Type of service performed, the individual receiving the service, the individual providing the service, the date of service, the location of service, and the time the service begins and ends - required nationally for Medicaid-funded personal care and home health services under the 21st Century Cures Act.

Have a project like this in mind?

Tell us what you're building. A senior healthcare technologist — not a salesperson — will get back to you within one business day.