EVV Compliance for Home Care Agencies Is a Data Problem

EVV compliance means that every Medicaid-funded personal care or home health visit is verified electronically at the point of service, capturing six data points: the type of service, the individual receiving it, the individual providing it, the date, the location, and the time the service begins and ends. It is a federal requirement under the 21st Century Cures Act, and every state has an implementation with its own aggregator, formats and deadlines on top of it.

That is the definition. The reason EVV keeps hurting agencies long after they bought an EVV system is not the definition, and it is not the capture. It is what happens to the record after it is captured.

I build operations systems for home care agencies, and I do not sell an EVV system, which is exactly why agencies bring me the part the EVV vendors’ guides stop at.

What does EVV actually require?

Two layers, and agencies get in trouble by treating them as one.

The federal layer is the six data points, mandated for personal care services and home health services delivered in the home. Your EVV system captures these at the visit, by mobile app, telephony, or fixed device.

The state layer is everything about what happens next: which aggregator receives your records, in what format, on what schedule, and what match rate your claims must hit. Two agencies capturing identical visits can have completely different compliance obligations depending on the state, and multi-state agencies carry one pipeline per state.

Your EVV vendor handles capture and, usually, transmission. Neither layer is where most compliance findings actually come from.

Why do agencies fail EVV compliance with an EVV system in place?

Because the failure lives between systems, not inside one.

A visit record says a caregiver was there from 9:04 to 11:58. The authorization says this client has 40 approved hours this month from this payer. The claim says the agency billed 3 hours. EVV compliance, in practice, is these three records agreeing, and in most agencies they live in three places: the EVV or scheduling system, the payer’s authorization letters (often a PDF in someone’s inbox), and the billing system.

When they disagree, and they disagree constantly, a visit ran long, a caregiver clocked into the wrong client, an authorization lapsed mid-month, someone finds out at claim submission, or worse, at an audit. The home care CRM post names billing-to-authorization reconciliation as one of the six things a home care operations system must track, and EVV is the sharpest version of it: the reconciliation is mandatory, and the records are machine-readable, which means the matching is automatable and is still, in most agencies, a person with two screens open at month-end.

What does closing the gap look like?

Not another capture app. A connected layer over the three records:

Authorizations as data, not documents. Approved hours per client per payer per period, in a structured record, with burn-down: how much of the authorization has been used, live, not at month-end. Alerts fire as an authorization approaches its limit, before the visits that will not be paid.

Visits matched as they land. EVV records reconciled against scheduled visits and authorizations continuously, so an exception, a mismatch of person, place, time or remaining hours, is a same-day flag with an owner, not a month-end discovery.

Claims that inherit clean data. Billing built from visits that already passed the match, so the claim rate problem shrinks at the source.

For Affinity Care, a Minnesota home care agency, consolidating operational records into one connected system took caregiver onboarding from 21 days to 8 and made the operation audit-ready every day instead of the week before an audit. The same architecture, one source of truth with automated checks against it, is what turns EVV from a monthly scramble into a background process.

Which layer needs HIPAA coverage?

All of it: visit records tied to identifiable clients are PHI. The EVV vendor is a business associate, and so is every tool your reconciliation pipeline runs through. If schedules or visit data flow through a general automation platform, that platform is part of the chain, and the popular ones do not sign BAAs. This is one of the reasons we build this layer on covered infrastructure rather than consumer automation tools.

Frequently asked questions

What are the six EVV data points?

Type of service performed, individual receiving the service, individual providing the service, date of service, location of service delivery, and time the service begins and ends. Captured at the point of care, attached to the claim.

Does EVV apply to private-pay clients?

The federal mandate covers Medicaid personal care and home health services. Private-pay visits are outside it, though agencies often verify them the same way for operational consistency, one process is easier to run than two.

Is an EVV system enough for compliance?

It is necessary and not sufficient. Capture and transmission are the vendor’s job; the match between visits, authorized hours and claims is yours, and it is where audits look.

Can EVV reconciliation be automated?

Yes, and it is a natural fit: the records are structured and the matching rules are explicit. The blocker is rarely technology, it is that the three records live in disconnected systems, which is an operations problem before it is a software purchase.

If your agency’s month-end involves a spreadsheet, an inbox of authorization PDFs and a prayer, that is the exact situation our home care operations work exists for. Book a call and we will look at your reconciliation flow together.