Chapter 28: EVV Center

Chapter Overview

What You'll Learn:

When EVV Center appears
How to monitor Ohio Alt-EVV Call In/Out sync
How office staff edit call times with Sandata reason codes and resubmit
How EVV relates to claim submit (Betasky EVV)

Path: Sidebar → Billing & revenue → EVV Center → /dashboard/evv-center

Text-only. Sits between Claims and Payment Posting in the billing workflow.

28.1 When You See EVV Center

Requires:

Agency Alt-EVV enabled
Permission such as evv:exception-view

Visible for full EMR and billing-only when Alt-EVV is on (not sandbox-hidden by nav flag).

Subtitle on page: Ohio Alt-EVV visit sync (Call In/Out). Office can edit call times with reason codes and resubmit.

28.2 What Visits Need EVV

Hard Call In/Out capture and claim EVV checks apply when both are true:

Agency Alt-EVV is active (enabled + Ohio Medicaid Provider ID / link status as configured)
The visit’s service code is flagged requires EVV (Ohio Medicaid / many MCO service codes — not Medicare HIPPS service visits)

EVV is not “every Medicaid visit automatically.” It is service-code + Alt-EVV agency driven.

28.3 What You See

Title: EVV Center
Banner: Agency Alt-EVV · Medicaid Provider ID: · link-status chip
KPI chips: Attention N · Pending N · Error N · Incomplete N · Verified N

Filters:

Search patient…
EVV status — All EVV statuses / None / Pending / Incomplete / Verified / Error
Clinician — All clinicians
From / To
Switch: Missing Call Out

Columns: Patient · Service · Clinician · Calls (In / Out) · EVV status · Visit status · Last error · Updated · Actions (View details)

Empty: No EVV visit records yet. Complete an Alt-EVV visit on mobile…

28.4 Visit Detail Drawer

Title: EVV visit

Shows Sandata UUID:, Last synced:, sections:

Calls
Recent modifications
Recent sync logs
Actions

Office actions (by permission)

Action	Purpose
Add Call In / Add Call Out	Manual call entries
Edit Call In / Edit Call Out	Correct times
Resubmit sync	Force sync retry
Payload view	Inspect payload when permitted

Edit dialog titles: Add Manual Call In|Out / Edit Call In|Out
Office edits need a Sandata reason code (product currently offers the standard office code 99).
Fields: Reason code · Note (optional) → Save & resync

28.5 How This Relates to Claims

Billing-only / New Claim Billing Source may be Betasky EVV or External EVV — Sandata (Chapter 27).
For Betasky EVV visit-generated claims, electronic submit is blocked until Call In + Call Out exist and EVV status is Verified.
If Sandata is in dry-run / not live, visits can stay Pending and claims will not clear the EVV gate until sync reaches Verified.
EVV Center is the operational place to fix Call In/Out sync problems before or after billing.

External Sandata visits (not Alt-EVV)

If EVV was captured in Sandata (outside Betasky Call In/Out), do not expect those visits to appear in EVV Center. Import them with Sandata Migration (Chapter 35), match patients, then bill with New Claim → Billing Source External EVV — Sandata → Use Visit.

28.6 Common Mistakes

Expecting EVV Center without Alt-EVV enabled — it will not appear.
Assuming every Medicaid visit needs EVV — check the service code requires EVV flag.
Submitting a Betasky EVV claim while status is still Pending / Error / Incomplete — fix calls and wait for Verified (or use External EVV billing source when visits were captured outside Betasky).
Editing Call In/Out without a reason code — Save & resync requires one.
Looking in EVV Center for visits that only exist in a Sandata Visits Claims Verification Status export — use Sandata Migration instead (Chapter 35).

28.7 Quick Checklist

Alt-EVV enabled and Medicaid Provider ID shown
Attention / Error queues reviewed
Missing Call Out addressed
Edits include Sandata reason codes + resync
Betasky EVV claims only submitted when EVV is Verified

Previous: Chapter 27: Claims Center
Next: Chapter 29: Payment Posting

Claims Center

Payment Posting