The Compliance Layer in a Home Care Software Stack

Scheduling and agency management platforms are built around the visit. AxisCare, WellSky, AlayaCare, and eRSP schedule caregivers against clients, capture electronic visit verification, generate claims, and feed payroll. The visit is the record everything else hangs from, and these systems are very good at the job.

Onboarding and compliance are built around a different object. The unit is the caregiver and the requirement set attached to their role, and most of the work happens when no visit exists. Between an accepted offer and a first shift there is no schedule to attach anything to. Between one credential renewal and the next, nothing about the visit record changes even though the caregiver's compliance status has.

Neither layer is a substitute for the other, and the distinction is not about quality. A system organized around visits will store caregiver documents when asked, in the same way a filing cabinet stores them. Storing is not the same as enforcing.

Where the seam shows

A certifications tab inside a scheduling platform holds what someone typed into it. Nothing in that design enforces a concept of a complete caregiver file, because the complete file was never what the system was built to produce. If a requirement was never entered for a caregiver, no field sits empty and no alert fires, so that caregiver looks identical to one who is fully current. The gap has nowhere to appear.

Expiration alerts run into a related limit. A scheduling platform can fire a notification when a date approaches, but the caregiver usually cannot act on it. There is nowhere to upload from the alert, so the caregiver texts a manager or does nothing, and a person in the office still receives the document, checks it, records the new date, and files it. The alert moves the work to a predictable moment rather than removing it. Where two systems both hold expiration dates, caregivers receive duplicate notices and learn to disregard both.

The onboarding window sits outside the operational layer almost entirely. A caregiver typically enters a scheduling platform once they are ready to be scheduled, which is the end of the process rather than the beginning. Everything before that point, meaning the documents, the signatures, the screening results, the I-9, and the chasing, happens in email, in text messages, in a shared drive, and on paper. The consequence is that an agency has no view of how many accepted candidates are actually progressing until they arrive, or fail to.

What belongs in which layer

The operational layer holds the schedule, visit verification, client records and care plans, billing and claims, and payroll.

The compliance layer holds the requirement set for each caregiver role, the documents that satisfy it, the dates those documents were verified and when they expire, the onboarding sequence from accepted offer to first shift, and the evidence that all of it happened.

Some of those records also have to be held apart from the personnel file. Medical information is confidential and separate by requirement, and I-9s and screening reports are conventionally kept apart as well. An operational system has no reason to model that separation, because it was never built to be the place a file is assembled from.

The two layers overlap at exactly one point, which is whether a given caregiver is currently eligible to be scheduled. That single fact is what has to pass cleanly between them, and work authorization is the case that catches agencies out, since a document can expire or be revoked long after the caregiver was cleared to work.

What a connection between them should do

Integration counts say little. The useful questions are narrower.

• What flows, and in which direction. A caregiver record moving one way and a compliance status moving the other are different arrangements with different failure modes.
• Which system owns each date. When two systems both hold an expiration date, one of them has to be the source of truth, or they will disagree and someone will have to adjudicate by hand.
• What happens on disagreement. Whether a conflict surfaces to a person or resolves silently in favor of whichever system wrote last.
• Whether anything is entered twice. Duplicate entry is where the two layers stop being connected and start being two jobs.

Adding a layer without adding a system

The reasonable objection to any of this is that an agency does not want another platform to log into, another vendor to manage, or another place where work can pile up unattended. That objection is correct, and it is the constraint the compliance layer has to satisfy rather than argue with.

Homecare Pro connects to AxisCare, WellSky, AlayaCare, and eRSP and runs underneath them. Caregivers receive their tasks by SMS through links that need no app and no account, so the caregiver-facing side adds no software at all. Renewed expiration dates are written once and flow back to the connected platform, so the scheduling system stays current without anyone retyping anything. The office keeps working where it already works, and the requirement set, the documents, and the dates are held together with a real-time answer to which caregivers are complete and where the gaps are.

Agencies see compliance rates rise by around 35% within the first three months, and onboarding completion roughly double. Implementation takes about a week.

Seeing how the two layers fit together for a real roster is the next step.

‍