Washington home-care margin recovery: when the visit cleared and the authorization edit did not.

Washington splits its home-care machinery across two state agencies, and that split is where a lot of margin quietly goes missing. The Health Care Authority (HCA) is the single state Medicaid agency. It runs Apple Health and the ProviderOne claims system. The Aging and Long-Term Support Administration (ALTSA), inside DSHS, runs the long-term-care service side: the assessments, the authorizations, the program rules. A personal-care visit in Washington has to satisfy both. It clears EVV, it reaches ProviderOne, and then the claim gets validated against an authorization that was built on the service side. When those two halves do not line up, the claim does not pay.

This page is about where that money leaks in Washington specifically, and why catching it means reading your visit data against the authorization rather than trusting that what was scheduled got collected.

Provider Choice EVV, with ProviderOne as the aggregator

Washington did not pick a single EVV vendor and force every agency onto it. It runs a Provider Choice model. Agency providers select their own EVV system and submit the captured visit data through ProviderOne, the state's claims system, which also serves as the EVV data aggregator. That gives agencies flexibility, but it also means the burden of getting the data right sits with each agency rather than with a state-run tool.

There is a second track that operates differently. As of June 1, 2022, Consumer Direct Care Network Washington (CDWA) became the Consumer Directed Employer for all Individual Providers of state-purchased in-home care, and those workers clock in and out through CDWA's CareAttend app. So an agency that also touches consumer-directed clients is dealing with more than one path to the same aggregator. Federal rules required personal-care EVV by 2021, and in Washington agencies were required to have EVV implemented as of January 1, 2023, with new EVV data elements made mandatory on Home Health Care Services claims for dates of service on or after January 1, 2024.

The authorization edit is where the money actually moves

Here is the Washington-specific mechanism. In ProviderOne, social-services claims are validated against the client's authorization. The authorization carries the approved units, the date span, and the provider, and those details are visible to billing providers in ProviderOne. A claim that does not match the authorization can be denied or suspended. Separately, a personal-care claim that arrives without valid EVV data can be denied for missing visit verification.

That is the trap, and it is structural. The authorization is created on the ALTSA service side. The claim is adjudicated on the HCA payment side. The caregiver who delivered the care never sees either system. So a unit count that drifts from the authorization, a service code that does not match the approved service, or an EVV record that never landed cleanly in ProviderOne produces a denial that nobody on the floor caused and nobody in scheduling can see. Note that Washington publishes the validation mechanism rather than a single numbered code for it, so the right way to find these is to reconcile the data, not to wait for a tidy denial reason.

Where the margin actually leaks in Washington

From the way Washington wires Provider Choice EVV, ProviderOne, and the ALTSA authorization together, the recoverable losses cluster in a few predictable places:

• Authorization mismatches. Claims that fall outside the ProviderOne authorization on units, dates, or service line. This is the core Washington edit, because the authorization lives on the service side and the claim adjudicates on the payment side.
• Missing or unmatched EVV. Personal-care claims with no valid EVV data in ProviderOne, or visit data that does not reconcile to the claim, denied for missing verification.
• CFC and MPC code drift. A client who qualifies under one program billed under the other, or a service code that does not match the program the authorization was built for.
• Consumer-directed and agency overlap. Where the same client touches both an agency provider and the CDWA Individual Provider path, visit data and authorizations have to be kept straight across two different capture routes.
• Silent underpayments. Claims that pay below the expected rate, never flagged as a denial, visible only when payment received is compared against payment expected, line by line.

None of these are visible from inside the scheduling view. The schedule says the visit happened. The EVV system says the caregiver clocked in. It is only when you reconcile the EVV data against the ProviderOne authorization and the actual remittance that the gap appears.

Why a read-only recovery layer is the right tool for this

Reeve sits read-only over whatever EMR and EVV export an agency already runs, whether that is WellSky, AxisCare, HHAeXchange, AlayaCare, or anything else, and compares what was delivered with what was authorized and what ProviderOne actually paid. For a Washington agency, that means lining up the EVV visit data, the claim lines, and the ProviderOne authorizations, then surfacing every place they fail to reconcile: the authorization mismatches, the missing EVV, the CFC and MPC code drift, and the silent underpayments.

Because Reeve is read-only and neutral across every EMR, it never writes to your billing workflow without your control, and it has no reason to look past a finding that implicates a billing module. It hands you a ranked list of recoverable dollars with the reason attached, the unmatched visit or the out-of-authorization line. The ones still inside the 365-day window are the ones you can rebill now.

This is the same engine described across the rest of the site. For the broader map of revenue loss in home care, see where home-care margin leaks. For the authorization side specifically, see home-care authorization tracking. For the full playbook on getting uncollected revenue back, see home care revenue recovery.

What the free Washington Margin Teardown does

The way to find out whether ProviderOne authorization edits and EVV gaps are draining your margin is to look at a real, de-identified slice of your own data, before you spend a dollar. The Margin Teardown is a one-time, read-only read of where margin is leaking in your book: the authorization mismatches, the missing EVV, the code drift, and the underpayments. It is free, and it is yours to keep whether or not you ever work with Reeve. It carries the same 3×-or-free guarantee the rest of the engine does. If Reeve does not surface at least three times its monthly fee in recoverable margin you agree is real, you do not pay.