EVV Dashboard

Visit Verification insights

The EVV (Electronic Visit Verification) Dashboard within the BI DASHBOARDSarrow-up-right section is a real-time compliance monitoring tool. It is designed to help agency administrators and dispatchers track field activity, ensure that visits are being logged accurately via GPS, and identify technical or procedural issues before they impact billing.

1. Date Range Filter

At the top of the EVV Dashboardarrow-up-right, you can define the reporting period. By default, this often shows the current quarter or month.

  • Function: Adjusting this filter refreshes all summary cards and tables to show activity within the selected window.

2. High-Level Summary Cards (Real-Time KPIs)

These cards provide an instant health check of your agency's field operations:

  • Visits Scheduled (40): The total number of tasks or visits assigned to fieldworkers for the selected period.

  • Visits Sent (0): The number of visits where data has been successfully transmitted to the state or clearinghouse aggregator (e.g., HHAeXchange or Sandata).

  • Visits Not Yet Checked In (10): A critical alert showing visits that have reached their start time but have no recorded "Check-in" from the mobile app.

  • Visits Checked-in but Not Checked-out (1): Highlights "active" visits where a worker has started the shift but has not yet concluded it.

Use Case: Late Arrival Monitoring. If the "Visits not yet checked in" count is high during morning hours, a dispatcher can quickly identify which fieldworkers may be running late or experiencing app connectivity issues.

The dashboard includes trend charts to track transmission success over time:

  • Visits Sent over 12 Months: A line or bar graph showing the monthly volume of successfully verified visits.

  • Visits Sent (Distribution): Helps visualize the ratio of visits that are ready for billing versus those that are still pending verification.

4. Actionable Data Tables

The bottom of the dashboardarrow-up-right provides granular, row-level data to resolve compliance gaps:

Visits Checked-in but Not Checked-out

This table identifies staff members currently in the field.

  • Key Fields: Task ID (tas_id), Title, Type (e.g., Visit), Start/End Date, and Start Time.

  • Example: 3,010,262 | final check 3.0 | Visit.

  • Use Case: Identifying "forgotten" check-outs. If a visit from the previous day is still appearing here, the admin can contact the worker to manually adjust the timesheet.

Visits Not Yet Checked In

This table acts as a "Missing in Action" log.

  • Key Fields: Task ID, Title (often includes Client & Worker names), and Scheduled Time.

  • Example: 3,010,265 | Simple Workflow_Alexa Bolanto_01/23/2026.

  • Use Case: Preventing service gaps. Admins can see exactly which specific workflows or home visits haven't started and reassign them if necessary.

Summary of Potential Use Cases

Category

Practical Application

Real-Time Dispatch

Monitoring the "Not Yet Checked In" table to proactively manage staff attendance.

Billing Accuracy

Ensuring "Visits Sent" matches your expected claim volume before submitting to Medicaid/Payers.

Compliance Audits

Using the "Visits Checked-in but Not Checked-out" list to clean up data errors that could lead to "overlapping shift" denials.

Fieldworker Support

Identifying workers who consistently appear in the "Checked-in but Not Checked-out" table to provide additional training on the mobile app.

Last updated