Practical ways to balance verification, accessibility, and payment integrity for in-home services
Meeting Electronic Visit Verification (EVV) requirements sounds straightforward on paper: prove that a caregiver was where they said they were, at the right time, and for the required service. The reality for home-health operators and Medicaid programs is messier. Proposed measures that layer mandatory biometric checks onto EVV create immediate operational questions about worker access, error rates, appeal paths, and the downstream effect on payments and enrollment.
Recent reporting that Ohio lawmakers proposed a package requiring statewide EVV dashboards and, for some high-risk providers, fingerprint or facial recognition is a reminder that the debate is now about how verification gets done, not whether it should happen. The choices states and providers make will determine whether verification improves program integrity or instead creates new barriers to care and costly administrative churn.
Why verification choices matter beyond fraud prevention
Verification is meant to protect public funds and keep bad actors out of the system. What gets less attention is how verification requirements interact with everyday caregiving. Home-health aides often work multiple jobs, use shared phones, or serve clients in rural areas with poor connectivity. Biometric checks can introduce false positives or failures that stop the payroll pipeline until an appeal is resolved.
Those operational failures show up three ways. First, access. A verification method that assumes every caregiver has a smartphone, a stable connection, and willingness to submit biometric data will exclude some portion of the workforce. Second, friction. When a visit fails verification, agencies must investigate, re-verify, or suspend payment. That creates work for both providers and the agency, and it delays legitimate payments. Third, auditability. Regulators want a clear, auditable record that supports both enforcement and fair appeals, but more data is not the same as better evidence if the data is noisy or unverifiable.
What to watch for when designing EVV and biometric policies
- False-positive and false-negative rates, and how they will be handled operationally. A system that rejects a legitimate visit without a fast appeals path shifts the burden to providers and clients.
- Worker accessibility, including device availability, language preferences, and whether the verification method respects privacy concerns and consent.
- Payment-flow rules tied to verification results. If payment is conditioned on a biometric match, the agency needs clear temporary-payment policies so care providers do not face sudden cash-flow shocks.
These are not abstract technical problems. They are the day-to-day issues that determine whether EVV compliance actually improves program integrity, or whether it simply creates more exceptions and more paperwork.
Practical verification patterns that keep care moving
There is no single right answer. A measured approach treats verification as a set of complementary tools that map to real-world constraints. A few practical patterns tend to work better in operations.
Mix verification options by risk tier. For most providers, a phone call check-in or a secure personal identification number is fast, low-friction, and auditable. Reserve stronger methods, such as biometrics, for providers that meet an objective high-risk threshold and after the state has worked through accessibility and appeal procedures.
Build fast, human-led exception handling into the workflow. Whatever verification method is in place, visits will fail. The system should make it straightforward for a provider to submit supporting information, for a supervisor to review it, and for payment holds to be temporary rather than final. Operational policies that specify who reviews exceptions, what evidence is acceptable, and how long holds last reduce confusion and outside appeals.
Design dashboards for action, not just surveillance. A statewide EVV performance dashboard is only useful if the metrics it displays are tied to operational responses. Dashboards should surface unusual claim patterns, concentrated failure rates by provider, and recurring device problems so program integrity teams can prioritize investigations rather than chasing one-off data points.
Consider phone, SMS, and secure messaging as real alternatives to biometrics. These channels reach caregivers who lack smartphones or who decline biometric collection for privacy reasons. A telephone-based verification or a text-confirmed PIN, when combined with a clear audit trail and documented exceptions process, can meet both accessibility and auditability goals without adding the technical and legal complexity of mass biometric collection.
Integration and enrollment screening
Stronger verification rules tend to be paired with tougher enrollment screening, such as in-person inspections or address-matching checks. That makes sense, but it also increases the workload on enrollment teams. Automating repeatable intake steps and building alerting for suspicious patterns reduces manual triage. The screening logic should align with the verification policy so a provider does not clear enrollment only to be repeatedly flagged in operations.
A quieter issue is the appeal and audit trail. Audit-ready documentation matters more than the particular technology. When an auditor or a provider asks “did this visit happen,” the record should answer that question plainly. That requires consistent, attributable entries and a clearly documented appeals workflow tied to payment rules.
Tougher rules usually surface more exceptions. A policy that expects perfect data will generate perfect headaches. The better path is to make verification robust enough to deter fraud, flexible enough to include legitimate providers, and procedural enough to resolve disputes quickly.
For teams thinking through the build versus buy choice, focus first on the workflow: how visits are scheduled, how verification is attempted, who reviews exceptions, and how payments respond to outstanding issues. Those operational decisions matter more than the vendor logo on the contract.
Our notes on EVV workflows and phone-based verification options.
Related coverage: Rep. Mike Dovilla Announces Ohio Medicaid Program Integrity and Fraud Prevention Act — ohiohouse.gov