Home and senior care
Scheduling that checks compliance before it checks availability
A caregiver with a lapsed background check should never appear on tomorrow's schedule. Most home care software finds out after the visit is billed.
What home care software has to get right
4 things that decide this
- 01Section 12006 of the 21st Century Cures Act requires every state Medicaid program to run Electronic Visit Verification for personal care services, with home health services required from January 1, 2023.
- 02Visit data has to reach a state aggregator, commonly Sandata or HHAeXchange, in the exact format that state accepts, or the claim behind it gets rejected.
- 03States are open-choice or closed-model: open lets an agency pick its own EVV vendor and transmit to the aggregator, closed hands every provider one state-mandated platform.
- 04A caregiver's background check, license, or training certificate has an expiry date. Scheduling that ignores the date finds out from a denied claim.
The software problem is submission, not capture
Recording a visit is the easy half. A phone app can log GPS and a timestamp on day one. The hard half is shaping that record so a state aggregator will accept it, and keeping it that way as states change requirements.
An open-choice state lets an agency run its own EVV system and transmit visit data to Sandata or HHAeXchange in that state's required format. A closed-model state skips the choice and hands every provider one platform. Either way, a rejected transmission is a rejected claim, not a warning to fix later.
The second half is credentials. A background check, a CPR certificate, or a state aide registration expires on a date. That date should remove the caregiver from tomorrow's schedule automatically. Most agencies still catch this from a denied claim, weeks after the shift already happened.
The compliance surface
2023
year EVV became mandatory for Medicaid home health services nationwide
70%
less manual compliance checking for the staffing platform behind our proof point
What agencies and platforms actually ask for
EVV that submits clean the first time
Visit capture, GPS or phone check-in, and a file sent to the state's aggregator, whether that is Sandata, HHAeXchange, or a state-run system.
Scheduling gated on eligibility
A caregiver whose certification lapsed does not appear on the available list. The check runs before the shift is offered, not after it is worked.
Family and case manager visibility
Read-only views into visit history and care notes for the people who need to trust the record without being able to alter it.
Reconciliation across payers
Medicaid, Medicare Advantage, and private pay each carry different documentation rules. One visit record, mapped to each payer's format, instead of three parallel logs.
- Credential checkExpiry read at schedule time, not visit time.
- Offer shiftOnly eligible caregivers see it.
- Visit captureGPS or phone check-in, in and out.
- FormatMapped to the state's aggregator spec.
- SubmitSandata, HHAeXchange, or the state system.
- ReconcileRejections routed back before rebilling.
Move the credential check to step one and a lapsed certification never reaches a shift. Leave it at the end and it shows up as a denied claim.
Aggregators reject silently unless you watch for it
A visit transmits, the aggregator accepts the file, and the agency assumes the claim is fine. Weeks later a batch of visits comes back denied for a formatting mismatch nobody noticed at submission time.
The fix is treating the aggregator's reply as a required input, not an afterthought. Build the retry path when you design the visit, not after launch. In 2026, several states moved from soft warnings to hard denials for gaps that used to just get flagged.
- Read every aggregator reply, not just the submission receipt.
- Route rejections to a person who can fix the record same-day.
- Track which state's format changed, because each state maintains its own.
Eligibility-gated scheduling we have shipped
The stack this work runs on
Platform
Verification
Controls
What home and senior care operators ask us
01Does EVV mean we need Sandata or HHAeXchange specifically?
Your state's model decides that. Open-choice states let you run any EVV system, as long as it transmits to the state aggregator in the required format. Sandata and HHAeXchange are two of the most common aggregators. Closed-model states assign one platform to every provider. Either way, the software has to match your state's spec, not a generic standard.
02Can credential expiry really be automated?
The tracking can. An expiry date is a fact the system can store and check at schedule time. Shift Link, our staffing platform, runs this same pattern against Right-to-Work status. The edge case still needs a person: a renewal filed but not yet processed, or a state extension during a backlog.
03What happens when an aggregator rejects a visit?
A rejection should come back as a clear, fixable error, not a mystery denial weeks later. The build has to read the aggregator's reply at submission time. Then it routes the rejection to someone who can fix the record before the billing cycle closes.
04Do we need separate systems for Medicaid and private-pay clients?
No. One visit and credential record, mapped to whatever each payer requires, works better than parallel systems that drift apart. Medicaid needs EVV submission; private pay usually just needs the same record shown to the family.
05Can this replace our existing scheduling software?
Not always, and it does not need to. If your scheduling tool already works for staff and shifts, the gap is usually the compliance layer on top. That means reading credential status before a shift is offered, then closing the loop with the aggregator after a visit. We scope which is true for your system before recommending either.
Go deeper
- Healthcare software development →The regulation map, the buyers, and the security review.
- Shift Link →Onboarding, validation, scheduling and payroll in one build.
- Workforce compliance systems →Eligibility gates and attributed overrides, argued in general.
- HIPAA compliant development →What the Security Rule requires of the record behind every visit.
