Electronic visit verification: what EVV records and what it does not

Electronic visit verification — EVV — is the electronic capture of six facts about a home care visit: who received the service, who provided it, what service was delivered, where it took place, and the date and times the visit began and ended. In the United States it is a Medicaid requirement for personal care and home health services, implemented state by state, and the details of how a state accepts the data differ enough that the state’s own guidance is the only reliable source.

The reason it exists is billing integrity: it makes a claim for a visit that did not happen much harder to submit. That framing matters, because it explains both what the system is good at and why it produces so much friction for the people delivering the care.

What electronic visit verification captures

• The individual receiving the service, and the individual providing it.
• The type of service performed.
• The location of service delivery.
• The date, and the time the visit began and ended.
• And, in practice, an exception record explaining every visit that did not match its schedule.

Exceptions are the actual workload

The captured visit is the easy case. The work is in what the system flags: a caregiver who clocked in three streets away because the client’s address geocodes badly, a visit that ran forty minutes long because the client had a fall, a phone with no battery, a client who moved a visit by an hour. Every one of those becomes an exception that somebody has to review, code and either correct or justify, and the volume of them — not the visits — determines how much administrative time EVV costs an agency. Agencies that build a clear exception process in the first month cope; agencies that treat exceptions as an occasional nuisance find a backlog of unbillable visits by the third.

Verification is not documentation of care. EVV records that a visit occurred; the care notes record what was done and what changed. Agencies that let the EVV record stand in for the visit note end up unable to answer a clinical or safeguarding question, because nothing in the six data elements describes the person.

Choosing an approach

States generally offer a choice between a state-provided system and an approved alternate vendor, and the trade-off is real: the state system costs nothing and constrains everything; an alternate integrates with your scheduling and billing but must be accepted by the state and aggregator. Whichever route, the questions worth asking are the same — what happens with no signal, how the caregiver verifies without a smartphone, how an exception is corrected and by whom, how quickly data reaches the aggregator, and what the audit trail shows when a time is edited.

Rostering the visit is only half of it. Patient scheduling decides slot lengths, how much urgent capacity is held back, and what happens to a slot when someone cancels.

The records around the visit

The verification data belongs in the approved system. What sits around it is ordinary record work and is where audits actually find gaps: care plans, visit notes, caregiver training and competence, background check dates, client consent, the exception log and the reasons attached to it — the same discipline that a medication administration record demands of the medicines file. Ettex Records keeps that file per client and per caregiver with review dates visible, Ettex Forms collects the visit notes and competency checks, and Ettex Docs holds the policies with version history.

To be explicit, and this is a hard boundary: we are not an EVV system and cannot be used as one. EVV data must be captured and transmitted through a system your state accepts. Everything described here is the paperwork around it, and none of it is regulatory advice — your state Medicaid agency is the authority on what it requires.