Ohio Reference

Ohio EVV (Sandata): 2026 compliance + denial prevention

The 2026 Ohio EVV (Sandata) compliance guide. Ohio aggressively denies claims when EVV does not match scheduled visits — here is how to prevent denials.

By Calvin Nesvig, Founding Partner·Updated May 3, 2026·8 min read
Quick answer
  • Ohio is closed-model: Sandata is the state-mandated EVV vendor.
  • Ohio aggressively denies claims when EVV does not match scheduled visits.
  • Schedule-EVV-claim reconciliation before submission is required to prevent denials.
  • AveeCare flags mismatches in visit-maintenance before the claim is built.
  • AveeCare exports to Ohio Sandata at $6 / active client / mo.
Quick answer Ohio EVV + Sandata EVV-driven denials Requirements AveeCare fit FAQ

Ohio EVV + Sandata overview

The Ohio Department of Medicaid (ODM) administers Medicaid EVV through Sandata in a closed-model implementation. All Ohio Medicaid PCS / HHCS providers submit EVV data to Sandata; ODM cross-checks EVV records against Medicaid claims at adjudication.

Ohio's aggressive EVV-driven denials

Ohio is one of the strictest enforcement states. ODM's claims engine checks: (1) every billed visit has a matching EVV record in Sandata, (2) the EVV start/end times match the billed duration within tolerance, (3) the caregiver and client identifiers match, (4) the service code matches the EVV-recorded service type. Mismatches trigger automatic denial or claim hold-back.

Agencies that do not reconcile schedule-vs-EVV-vs-claim before submission see denial rates climb to 15-25% of Medicaid claims. With clean reconciliation, denial rates drop below 5%.

6 Ohio denial-prevention practices

GPS-verified clock-in/out

Every visit, no exceptions.

Visit-maintenance within 7-14 days

Correct mismatches before they age out.

Pre-claim reconciliation

Cross-check schedule vs EVV vs claim before submitting.

Caregiver training

Clock in at arrival, clock out at departure — exact times.

Weekly EVV usage monitoring

Per caregiver, per client, per service code.

Justification narratives

Document any visit-maintenance correction with reason code.

AveeCare in Ohio

AveeCare exports EVV data to Ohio Sandata at $6 / active client / month. Our visit-maintenance workflow flags mismatches before claim build, and our pre-claim reconciliation cross-checks schedule-EVV-claim alignment to reduce ODM denials.

Try free demo EVV by state

Frequently asked questions

The Ohio Department of Medicaid (ODM) contracts with Sandata as the closed-model state-mandated EVV vendor for Medicaid PCS and HHCS visits, including ODM Next Generation managed care plans.
Ohio aggressively cross-checks Sandata EVV records against the visits submitted on Medicaid claims (837P). When the schedule, EVV, and claim do not match (e.g. visit billed but no EVV record, or duration mismatch beyond tolerance), the claim is denied or held back. This is a known Ohio enforcement pattern as of 2024-2026.
Best practices: (1) require GPS-verified mobile clock-in for every visit, (2) enforce visit-maintenance corrections within 7-14 days of the visit, (3) reconcile schedule-vs-EVV-vs-claim before submission, (4) train caregivers to clock in/out exactly at start and end of service, (5) monitor EVV usage rate weekly per caregiver and per client.
AveeCare exports EVV data to Ohio Sandata at $6 per active client per month. Our visit-maintenance workflow flags schedule-vs-EVV mismatches before submission, and our claim build cross-checks EVV records before generating the 837P. Your team still uses the Sandata portal for the EVV submission step.

Sources

Accessed May 3, 2026.

CN
Calvin Nesvig
Founding Partner, AveeCare

Builds home care software full-time and works with home care agencies on workflow and software fit every week.

Continue Reading

Browse all guides

Need EVV that prevents Ohio denials?

$6 / active client / month. Free demo, no card.

Try free self-serve demo View pricing