How Alt-EVV Sync Into HHAeXchange Actually Works

The single biggest objection agencies raise when evaluating a new EVV app is some version of: “We’re not switching our EHR.” Fair enough, and you don’t have to. Here’s what an Alt-EVV integration actually does, and doesn’t, touch.

What HHAeXchange Actually Is

HHAeXchange is Minnesota’s designated EVV aggregator, the system DHS uses to receive and validate visit verification data before it flows into Medicaid claims processing. Every agency billing PCA, CFSS, CADI, BI, or EW services needs their visit data to land there, one way or another. DHS doesn’t process visit-level compliance itself; it delegates that job to HHAeXchange, which validates each visit against the six required EVV data points (service type, client, date, location, individual providing the service, and time the service begins and ends) before the visit is considered exception-free and claim-ready.

Agencies that don’t use a third-party app default to entering visits directly into HHAeXchange’s own portal: either caregivers logging in themselves, or office staff transcribing paper timesheets after the fact. Both work, technically. Neither is what most agencies would design if they were starting from scratch.

What “Alt-EVV” Means

An Alternate EVV provider is a certified third-party vendor whose software can submit visit data into HHAeXchange on an agency’s behalf, instead of caregivers using HHAeXchange’s own portal directly. The certification process confirms the vendor’s data format and transmission method meet the state’s spec. It’s not a marketing designation, it’s a technical one, and DHS maintains the list of who currently holds it.

Practically, this means:

• Caregivers clock in and out on the Alt-EVV vendor’s app, a two-tap mobile experience in Zayd’s case.
• The vendor’s backend formats that visit (service code, caregiver ID, client ID, timestamps, GPS) into the structure HHAeXchange expects.
• The visit is transmitted via API, typically shortly after clock-out.
• Your office staff and billers keep using HHAeXchange exactly as they do today. The sync is invisible to them except that visits show up automatically.

The Data Flow, Step by Step

It helps to walk through what actually happens between a caregiver tapping “clock in” and a biller seeing a completed visit in HHAeXchange.

1. Clock-in. The caregiver opens the app, selects the client from their assigned schedule, and taps clock in. The app captures a GPS coordinate at that moment and timestamps the event.
2. Service delivery. The app doesn’t track location continuously during the visit, only at the two verification points. This matters both for battery life and for the caregiver trust question addressed below.
3. Clock-out. Same pattern in reverse: a tap, a timestamp, a GPS coordinate.
4. Validation. Before the visit is ever transmitted, the app checks it against the required data points locally. Missing GPS, an implausible visit duration, or a location well outside the client’s known address gets flagged as an exception right there, before it ever reaches HHAeXchange’s queue.
5. Transmission. Clean visits are sent to HHAeXchange via API, usually within minutes of clock-out. Exceptions are held for the agency to resolve first.
6. Reconciliation. Your billing staff see the visit land in HHAeXchange exactly as if it had been entered through the state’s own portal, because as far as HHAeXchange is concerned, it was.

None of this requires a caregiver to ever open HHAeXchange directly, and none of it requires your billing team to learn a second system.

Certification Isn’t a One-Time Event

Alt-EVV certification isn’t something a vendor earns once and keeps forever without oversight. DHS periodically reviews the data format and transmission methods of certified providers to confirm they still meet spec, particularly after the state makes changes to its own requirements. A vendor that treats certification as a badge earned years ago, rather than an ongoing relationship with the state, is one worth asking pointed questions about: specifically, when their integration was last reviewed and whether anything changed as a result.

This matters more than it might seem, because a certification that quietly lapses doesn’t announce itself. Visits keep transmitting, dashboards keep looking normal, and the first sign of a problem might be a claim getting flagged months later for a data format issue nobody caught in the meantime.

What Doesn’t Change

• Your system of record stays HHAeXchange. No data migration, no new database of client records to maintain in parallel.
• Your billing workflow stays the same. Claims still get generated and submitted the way they always have.
• Your existing HHAeXchange account stays active. You’re adding a better front door for caregivers, not standing up a second system to maintain.
• Your relationship with DHS is unchanged. The state still sees HHAeXchange as the source of truth; the Alt-EVV provider is invisible to that relationship except as the method of data entry.

What Does Change

• Caregivers get a simpler clock-in experience. Select client, tap clock in, instead of navigating HHAeXchange’s own mobile interface, which was built for compliance, not for someone standing in a doorway juggling a bag and a phone.
• Exceptions get caught earlier. A missed clock-out or missing GPS shows up in the Alt-EVV vendor’s exception manager before the visit is ever exported. That’s weeks earlier than when a denied claim would otherwise catch it.
• Your office gets a second set of eyes. A dedicated exception dashboard, separate from HHAeXchange’s own reporting, gives your scheduler or office manager one place to check for problems daily instead of waiting for a billing rejection to surface them.

Where This Goes Wrong

Not every product marketed as “EVV software” is actually certified Alt-EVV. Some are scheduling or care-plan tools that happen to log a timestamp, with no real transmission pathway into HHAeXchange at all, which means an agency using one is still, functionally, manually re-entering every visit into the state portal to stay compliant. Others hold certification but route data through a batch upload process instead of a real-time API, which delays exception visibility and can leave a backlog of unresolved visits right before a billing cycle closes.

The failure mode to watch for during a demo has nothing to do with the sales pitch: it’s what happens to a visit between clock-out and the moment it’s usable for billing. If that gap is measured in days instead of minutes, or if resolving an exception requires a phone call to the vendor’s support line instead of a few taps in the app, the integration is thinner than it’s being presented as.

What Your Billing Staff Actually Notice

The people who never touch the caregiver app at all, your billers and schedulers, notice a different kind of change. Before an Alt-EVV integration, they’re either manually keying visits into HHAeXchange from paper timesheets, or reconciling caregiver-entered visits against a separate schedule to catch discrepancies. After, they open HHAeXchange to a queue of visits that are already there, already matched to the schedule, and already exception-free, because anything that wasn’t got caught upstream, before it reached their desk.

The change billers usually mention first is a task they stopped having to do, not a new skill they had to learn. That’s a reasonable way to evaluate whether an integration is real: ask your billing lead, a few weeks after go-live, what changed about their day. “Nothing, it just shows up” is the answer you want. “I have a new dashboard to check” means you’ve added a step, not removed one.

A Note on Timing and Claim Cycles

Because visits transmit shortly after clock-out rather than in a nightly or weekly batch, your billing team gets a much shorter feedback loop on problems. An exception caught the same day a visit happens can usually be resolved with a quick call to the caregiver, who still remembers the details. An exception discovered during a batch reconciliation two weeks later, right before a claims deadline, usually can’t: the caregiver has moved on to dozens of other visits, and the details are gone.

This is less about any single feature and more about where the checkpoint sits in your workflow. Real-time transmission puts the checkpoint close to the visit, where it’s cheap to fix. Batch processing puts it close to the claims deadline, where it’s expensive.

The Practical Test

Before switching anyone onto a new EVV app, ask the vendor one direct question: “Does this require us to change how we bill in HHAeXchange?” If the honest answer is anything other than “no,” you’re looking at a system replacement wearing an EVV badge, not an Alt-EVV integration. Ask a second, more specific follow-up while you’re at it: “Can I watch a test visit go from clock-out to appearing in our HHAeXchange account, right now?” A vendor with a real integration can show you that in minutes. One that can’t is asking you to take the sync on faith.