The care plan drives the shift
Published care plans generate the tasks a caregiver sees. Refusals are recorded as refusals with a reason — not left as an empty box that reads like nobody showed up.
For assisted living communities
One record your whole community runs on.
Care plans, the medication pass, incidents, diets and the kitchen — on one resident record, with an append-only history behind every entry.
The reality
What you are up against.
- Care plans live in a binder, the MAR lives in another, and the kitchen works off a laminated list that is three diet changes out of date.
- A caregiver finishes a pass and then spends twenty minutes catching the paperwork up from memory.
- When a family asks what happened on Tuesday, the answer depends on who is working today.
- A state surveyor asks for the incident file and someone starts photocopying.
/residents/{resident} 
How CareIT AL fits
Capabilities, mapped to your work.
A medication pass with five rights enforced
The eMAR confirms resident, drug, dose, route and time at administration, and cross-checks the resident's structured allergy list against drug stems before the dose is given.
Diet orders reach the plate
IDDSI textures and drink thickness flow from the dietary profile into the menu cycle, and the kitchen board tallies portions by texture. A diet order beats a derived texture where they disagree.
The incident file assembles itself
Filing a fall opens the post-fall observation protocol automatically and starts the statutory reporting countdown recorded for your state. Nothing is retyped, and the original account is never edited.
One timeline answers the question
Every module writes to the same resident timeline. "What happened on Tuesday" is a scroll, not an investigation — and corrections attach as amendments showing both versions.
Also built for
Other kinds of community.
See a shift run on CareIT AL.
A live walkthrough on the real product — the morning pass, an incident, and what a surveyor would see.