Ohio System Requirements

Overview

While there is a default vendor for EVV management in Ohio, the state allows for approved alternate EVV vendors such as Ankota. To ensure consistency in procedures across the state, Ankota has several additional requirements and procedures outlined below for all Ohio vendors.

Sandata Transmission

All EVV data must be sent to Sandata every 24 hours, even for visits placed on hold. This is done as part of our normal procedures. Once a client is live in Ankota, that data is sent. Please note that all appropriate data must be included for seamless transmission, including IDs, caregiver codes (both caregiver ID and caregiver code must be entered for each caregiver), payer, etc. 

Ohio Unique Requirements in Ankota

There are many unique Ohio requirements for EVV management, most of which are naturally part of the Ankota system. There are a few which differ slightly from Ankota's normal operations, and are outlined below for your reference.

• EVV Data must be sent daily to Sandata, as described above
• A unique email must be used for log-in ID
• Each exception to a visit must have an exception code applied to it
• There are several potential Ohio IDs; this critical process of ID management is outlined here
• Confirming service is a three-part process where the visit type/service, times, and receipt of service are all confirmed separately
  • If visit data is changed after the visit is closed, the three-part confirmation can be affected
  • For example, if times are changed after the visit is closed by an admin, the confirmation of times by the client is null and void