EVV aggregator

An aggregator exists because states let providers record visits in more than one system. CMS’s 2018 informational bulletin on EVV sets out the problem: when providers choose their own EVV vendors, the state has little say over the data and may need an aggregation solution that collects and consolidates visits from the different systems. The state needs that single feed to meet the federal EVV requirement and to link visits to claims, care plan authorizations and its Medicaid Management Information System, and CMS notes such systems may qualify for enhanced federal funding¹.

In Indiana and Wisconsin the aggregator belongs to the state’s own EVV vendor. Indiana uses Sandata as its state-sponsored system, lets providers pick a different EVV system, and requires those providers to export their visit data to the Sandata aggregator, which takes in visits from both groups; Indiana’s claims system is configured to work with Sandata². Wisconsin provides Sandata to agencies, requires every alternate system to integrate with the Sandata aggregator, and leaves implementation and interface costs with the agency that chooses its own system³.

For billing, the aggregator is the record that counts. A visit captured in a third-party app but missing from the aggregator does not exist for the state’s claim check. Wisconsin also has agencies on an alternate system complete Sandata’s aggregator portal training and can ask them to recertify their system³. The habit that protects claims is a daily comparison of the visits in your own system against what the aggregator shows, with rejected or missing records fixed before the billing run.