Ohio DODD EVV, in plain English.
EVV is one of the most-asked, least-explained parts of running an Ohio IDD or home-care agency. Here's what the rules actually require, how Sandata and alternate EVV vendors fit together, and where Enmantle fits — as a DODD-approved alternate EVV vendor submitting directly to Sandata.
See EVV in the platform →What EVV is, and why it exists
Electronic visit verification records six things about a service visit: who received it, who provided it, what service was delivered, where it happened, and the times it began and ended. The federal 21st Century Cures Act requires states to use EVV for Medicaid-funded personal care and home health services — which is why every Ohio provider delivering applicable waiver services has to capture it.
The goal is simple even if the implementation isn't: confirm that the visit billed to Medicaid is the visit that actually happened. Done well, EVV protects the provider as much as the payer — a clean, GPS-stamped record is the best answer to any question an auditor can ask.
Sandata, or an alternate EVV vendor
In Ohio, providers capture EVV one of two ways:
- The state-provided system (Sandata). Ohio's EVV data is collected through Sandata, the state's EVV aggregator. Providers can use the Sandata system directly to record and submit visits.
- An alternate EVV vendor. Ohio also allows providers to use a third-party "alternate" EVV system that captures visits in its own software and sends the required data to Sandata. The state still receives every visit through the aggregator — the provider just gets to use software they actually like.
Most agencies that pick an alternate vendor do it for one reason: they don't want EVV to be a separate chore. If clock-ins, documentation, scheduling, and billing already live in one platform, bolting a standalone EVV tool onto the side just creates another login and another place for data to fall out of sync.
Rules change — confirm the current ones. EVV requirements, covered services, and approved-vendor processes are set by Ohio DODD and the Ohio Department of Medicaid and are updated periodically. Treat this page as an orientation, not legal guidance, and confirm specifics with DODD for your services.
A DODD-approved alternate EVV vendor — native, not bolted on
Enmantle is a DODD-approved alternate EVV vendor and submits directly to Sandata. But the real difference is that EVV isn't a feature off to the side — it's part of the same platform a DSP already uses for the shift:
- GPS-stamped clock-ins from the mobile app, captured the moment the visit starts and ends.
- Service-code mapping handled for you, with every Ohio county board's rates already loaded.
- Submission errors surfaced and handled — flagged with a reason, not left for someone to discover at billing.
- Offline-tolerant capture — clock in, document, and log services without signal; it syncs when the device reconnects.
- Straight line to billing — the visit a DSP verifies in the morning is the line your billing director closes on Friday. Same record, no reconciliation.
That's the whole argument for an operating platform over a standalone EVV tool: the verified visit and the billable visit are the same object, so EVV stops being a second system to maintain and becomes a byproduct of doing the work.
Switching EVV systems mid-stream? Onboarding runs two to four weeks with a parallel-run period, so you keep submitting cleanly while you move. Migration support is included.
Ohio DODD EVV questions.
What is EVV for Ohio DODD providers?
What is an alternate EVV vendor in Ohio?
Is Enmantle a DODD-approved alternate EVV vendor?
Does EVV work offline in the field?
How does Enmantle's EVV connect to billing?
— See EVV on your workflow —
EVV that disappears into the work.
See how Enmantle captures, submits, and bills a visit as one record — in a 30-minute demo mapped to your agency.