Following a visit record from the caregiver’s phone call or app tap to a paid claim, and the integration questions that decide whether it gets there
Most EVV problems do not show up at the moment a caregiver clocks in. They show up days or weeks later, when a claim is denied or a visit sits in an exception queue because the data did not line up. That is an integration problem, and it is why EVV integration deserves as much attention as the app or the IVR call itself.
This article explains how EVV integration works, how the path differs by state model, and what to ask before connecting an IVR or install-free app component to your EVV platform.
Open model and closed model states
States generally take one of a few approaches to EVV.
In a closed model, the state selects a single EVV vendor, and agencies use that system. Options for bringing in other tools may be limited, and anything that touches visit data has to work within the state’s rules.
In an open model, the state provides an aggregator and allows agencies to use the EVV system of their choice, as long as that system sends visit data to the aggregator in the required format. Many states also offer a hybrid approach, providing a state-sponsored system for free while allowing agencies to use an alternate system.
The model your state uses shapes almost every integration decision. Before you evaluate any vendor, confirm your state’s model, the aggregator’s data specifications, and what is required for any alternate system.
What the aggregator does
The aggregator is the state’s collection point for EVV data. It receives visit records from approved EVV systems, checks them against the required data elements and the state’s validation rules, and makes that data available for claims matching. If a visit record is missing an element or fails a check, it may be rejected or flagged as an exception, and the related claim may not pay.
The data path, step by step
Here is the typical flow of a single visit:
- Capture. The caregiver clocks in and out using one of two methods: an IVR call from the client’s phone, or an install-free caregiver app opened from a home screen shortcut that captures GPS location. This is where the six Cures Act data elements are first collected.
- EVV platform or EHR. The captured visit lands in the agency’s EVV system or EHR, where it is matched to the schedule, the client, the authorization, and the caregiver.
- Review and exceptions. Visits with problems, such as a missing clock-out or a location mismatch, go to an exception queue where staff correct them with reason codes.
- Aggregator. The EVV system submits the verified visit to the state aggregator.
- Claims. The claim is matched against the verified visit. If they agree, the claim can move forward.
Every hop in that chain is a place where data can be lost, delayed, or mismatched. Good integration is the work of making each hop reliable and visible.
The hidden integration risk: app versions
Integration is not only about the connection between systems. It is also about the version of the capture tool sending the data. With a native app from an app store, every change to data fields, validation rules, or reason codes requires a new build, a store review, and an update on every caregiver’s phone. Until each caregiver updates, some visits arrive in the old format, and those are the visits that end up rejected or stuck in exceptions.
An install-free hybrid app removes that risk. Because it is a special link to a secure, mobile-only website that looks and behaves like an app, saved to the home screen as a shortcut, there is only one current version. When an integration change goes live on the secure site, every caregiver is using it the next time they open the shortcut. IVR call flows work the same way: the change is made once, centrally, and every caller gets it.
Why alternate system timelines matter
If you are considering an alternate EVV system in an open model state, plan for the certification process. For example, Wisconsin notes that alternate EVV certification can take up to three months. That is time where you may still be relying on your current system, so plan the transition carefully. Our article on making EVV deployments audit-defensible covers how to keep records clean during changes like this.
Questions to ask before you integrate
Whether you are adding an IVR option, an install-free caregiver app, or a full system, ask:
- Real-time or batch? Does visit data move to the EVV platform as each call or clock-out ends, or in scheduled batches? Real-time helps schedulers catch problems the same day. Batch can work, but you need to know the timing.
- How are rejections and exceptions handled? When the EVV platform or the aggregator rejects a record, where does the error go, who sees it, and how is it fixed and resent?
- How do capture changes roll out? If a field or rule changes, does every caregiver have to update an app, or does the change go live centrally?
- How is location captured and mapped? Ask how GPS coordinates from the app and caller ID or token data from IVR are passed to your EVV platform.
- Who owns testing? Integration testing across the capture tool, the EVV platform, and the aggregator needs a clear owner. Ask who writes the test cases, who runs them, and who signs off.
- How are reason codes mapped? States often have specific reason codes for manual edits. Make sure the codes your staff choose are the ones the aggregator expects.
- What is documented? Ask for integration documentation and API references before you commit. At IVR Lab, our APIs are documented and shared under a signed MSA.
Where IVR Lab fits
IVR Lab is a boutique firm that builds hyper-custom voice IVR, SMS, and secure messaging. For EVV, we provide two clock-in and clock-out components that integrate with your existing EVV platform: phone IVR, and an install-free hybrid caregiver app with mobile GPS capture. Our components are system agnostic, which means we design the integration around the platform you already use instead of asking you to change it.
We want to be straightforward about our role. We are not a state-certified alternate EVV system, and we do not submit data directly to state aggregators. Your EVV platform remains the system of record and handles certification and submission. We focus on capture: making sure the data arriving at your platform is complete, accurate, and on time, from every caregiver, on the current version.
Because every agency’s stack is different, our work starts with your workflow. Learn more about how we approach custom interactive voice response systems, or see our EVV IVR and mobile clock-in tools to understand how a targeted component can plug into the system you already trust. We are HIPAA compliant and SOC 2 audited, and happy to walk through the details with your team.

