Idaho looks easier to bill in than it is. The provider-choice EVV model feels flexible, you run the software you like, and on paper the rules are not exotic. But the flexibility hides a trap. The visit you captured in your own system is invisible to the state until it reaches the Sandata aggregator, and the hours you delivered only pay if they line up with an authorization the Bureau of Long Term Care issued months ago against one specific NPI. On a personal-care book billed in weekly hour blocks, the gap between those two facts is where the money goes.
This page is about where margin actually leaks in Idaho, and why catching it means reading your own data against the state's rules instead of trusting that a scheduled visit turned into a paid claim.
Idaho Medicaid home-care, at a glance
- Personal-care programs
- State Plan Personal Care Services (PCS); the Aged & Disabled (A&D) 1915(c) Waiver, a statewide nursing-home diversion program administered by the Bureau of Long Term Care
- EVV model
- Provider choice. Agencies pick any compliant EVV system that meets Idaho DHW requirements and feeds the state aggregator
- EVV aggregator
- Sandata, under contract to Idaho Medicaid, as the state's central visit-data store
- EVV dates
- PCS implementation January 1, 2021; compliance enforcement from July 1, 2021
Provider choice sounds free. The aggregator is not optional.
Idaho built its EVV program on a provider-choice model. You are free to run the EVV system that fits your agency, as long as it clears the Department of Health and Welfare's minimum requirements. That is genuinely useful, and it is why Idaho feels lighter than a single-vendor state.
The part agencies underweight is the destination. Whatever system captures the clock-in, the visit data has to reach the Sandata aggregator, the central store Idaho Medicaid contracts to hold every verified visit. Your own EVV database is not the source of truth the state checks against. Sandata is. A visit can be perfectly logged in your software and still be missing, or mismatched, at the aggregator, and the state has no way to see it.
The authorization is tied to an NPI, and it runs all year
Idaho's other quiet margin drain lives in the authorization. For A&D Waiver services, the Bureau of Long Term Care must authorize the service before it is delivered, and the authorization spells out the approved hours of service per week. Those authorizations generally run a full year from the date BLTC approves them.
Here is the detail that costs agencies money: authorizations are issued per billing provider NPI. Providers billing independently need their own. When staffing shifts, when a billing entity changes, or when a member moves between agencies, the claim can go out under an NPI that does not match the one on the authorization. The care happened. The hours were real. But the claim does not reconcile to the authorization on file, and it denies.
Because the authorization sits in place for a year and is bound to one NPI, a single structural mismatch does not cost you one claim. It repeats, quietly, across every claim that carries the same error, for as long as it takes someone to notice.
Where the margin actually leaks in Idaho
From the way Idaho wires provider choice, the Sandata aggregator, and year-long BLTC authorizations together, the recoverable losses cluster in a few predictable places:
- Aggregator gaps. A visit captured in your own EVV system that never reached Sandata in a clean, matched state, or reached it with a data element that does not match the claim.
- NPI mismatches. A claim billed under a provider NPI that does not match the NPI on the BLTC authorization. The most Idaho-specific denial, because authorizations are issued per billing NPI.
- Authorization drift. Claims that fall outside the approved weekly hours or the one-year authorization window. Common when a member's plan is renewed or revised mid-year.
- State-plan vs waiver confusion. A member moving between State Plan PCS and the A&D Waiver carries different rules, and claims billed under the wrong track reconcile against the wrong authorization.
- Silent underpayments. Claims that pay, but at less than the authorized amount. These never show up as a denial. They surface only when payment received is compared against payment expected, line by line.
None of these are visible from the scheduling view. The schedule says the visit happened. Your EVV app says the caregiver clocked in. The gap appears only when you reconcile the aggregator record, the BLTC authorization, and the actual remittance against the claim line.
Why a read-only recovery layer is the right tool for this
Reeve is built for exactly this reconciliation. It 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 against what was authorized against what was actually paid. For an Idaho agency, that means lining up the visit data sent to Sandata, the claim lines, and the BLTC authorizations, then surfacing every place they fail to reconcile: the aggregator gaps, the NPI mismatches, the authorization drift, and the silent underpayments.
Reeve is read-only and neutral across every EMR, so it has no stake in which system you run, and it never writes to your billing workflow without your control. It does not sell scheduling or EVV, so it has no reason to look past a finding that points at a billing module. You get a ranked list of recoverable dollars with the reason attached: the visit that never synced, the NPI that did not match, the authorization that lapsed. The ones still inside the filing window are the ones you can rebill now.
This is the same engine described across the rest of the site. For the mechanics of how EVV gaps become denials, see EVV billing for home care. For the authorization side specifically, see home-care authorization tracking. And for the broader map of revenue loss, see where home-care margin leaks.
What the free Idaho Margin Teardown does
The way to find out whether aggregator gaps and NPI-bound authorizations 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 visits that never reached Sandata, the NPI and hours mismatches, the authorization gaps, 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.
A free, de-identified Margin Teardown reconciles your EVV, authorizations, and claims and shows you exactly what slipped. Read-only. Yours to keep.