The resident record
Identity, condition flags, structured code status, care plans and the append-only clinical timeline every other module writes into.
- Residents
- Conditions
- Clinical
- Care
The platform
Twenty modules. One resident record.
CareIT AL is not a chart with add-ons bolted around it. Every module writes into the same append-only resident timeline, which is why the incident, the medication refusal and the physician call all appear in one place, in order.
What is inside
Grouped the way a facility thinks, not the way code is filed.
The shift
Shifts, assignments and handoff; the dashboard that opens the shift; the eMAR that runs the medication pass with five rights enforced.
- Scheduling
- Dashboard
- Medication
When something happens
Incident capture and investigation with statutory countdowns, the emergency centre and printable cards, and the generated paper pack for outages.
- Incidents
- Emergency
- Downtime
The wider care team
Hospice co-management, outside physicians and agencies, and therapy programmes with session attendance — none of whom need a login.
- Hospice
- Providers
- Therapy
Food and supplies
Structured allergies and IDDSI diet orders, menu cycles with derived textures and dietitian approval, and stock derived from a movement ledger.
- Dietary
- Menus
- Inventory
The platform underneath
Accounts with TOTP two-factor, per-facility isolation, reporting and exports, and the shared services every module is built on.
- Identity
- Tenancy
- Reports
- Shared
Capabilities
What your team gets on day one.
Residents & condition flags
Structured flags and code status, visible on the roster before anyone clicks into a chart.
Care plans & tasks
Published plans generate the shift's tasks. Refusals are recorded as refusals, with a reason.
eMAR with five rights
Resident, drug, dose, route and time confirmed at administration — enforced in the application.
Incidents & post-fall protocol
Filing a fall opens the observation protocol and starts your state's reporting countdown.
Diets, allergies & IDDSI
Structured allergies and IDDSI textures that reach all the way to the kitchen board.
Shifts, assignments & handoff
Who is on, who they have, and an acknowledged handoff at the end of every shift.
Hospice, providers & therapy
Co-management notes, outside providers and therapy attendance — without giving anyone a login.
Inventory from a ledger
Stock derived from movements, par-level reordering, expiry sweeps, per-resident consumption.
Menus & the kitchen board
Author the cycle once; textures derive per resident and portions tally by texture.
Reports & CSV exports
The questions asked most often, answered from the live record rather than a cached copy.
Audit trail & amendments
Hash-chained, uneditable by any role, covering reads of sensitive records as well as writes.
Downtime Pack
Generated paper — MAR sheets, summaries, emergency cards — for when the network is not there.
For caregivers
The shift, on the phone already in your pocket.
CareIT AL runs in the browser on a phone or tablet — nothing to install, nothing to sync. Your assigned residents, the tasks due, and the flags that change how you approach someone are on the first screen.
- Your assigned residents and what is due, first thing
- Record care as you go — including refusals, with a reason
- File an incident in your own words, at the scene
- Condition flags and code status before you walk in the room
For nurses
The medication pass, with the checks underneath it.
Five rights confirmed at administration, an allergy cross-check on drug stems, and an administration record that cannot be quietly rewritten afterwards.
- Five-rights confirmation enforced, not suggested
- Allergy cross-check matches drug stems (sulfa → sulfamethoxazole)
- Holds and refusals recorded as outcomes, never as blanks
- Post-fall neuro checks scheduled and chased by the system
- Corrections attach as amendments — the original stays visible
For administrators
Survey-ready as a by-product of the work.
The incident file, the audit trail and the exports are assembled continuously by people doing their jobs — not reconstructed the week a surveyor books a visit.
- Statutory reporting windows recorded per facility, per state
- Hash-chained audit trail no role can edit or clear
- Resident, incident and medication exports on demand
- Roles and permissions down to the action
- A Downtime Pack drill you can actually run
Engineering you can hold us to
Rules the software enforces, not suggests.
These come straight from chapter 15 of the user guide. Each one exists because the alternative fails in a way somebody eventually has to explain to a family.
Clinical entries are append-only
Database triggers block UPDATE and DELETE. A correction is an amendment that shows both versions, so nobody can tidy the record after an event.
Five rights are confirmed, not reminded
The administration cannot be recorded without them. A prompt you can dismiss is not a control.
Warnings never block care
An allergy or interaction warning informs the person giving the dose; it does not lock them out. Software that stops a pass creates a workaround.
Free text is never auto-interpreted
Allergies and code status are structured records. The system will not parse a sentence and act on what it thinks it found.
Timestamps come from the server
Occurrence times are normalised from the facility timezone server-side. A device with the wrong clock cannot misdate a clinical record.
Reporting defaults fail early
With no state rules recorded, the countdown defaults to 24 hours for every severity — earlier than any realistic deadline. Conservative by design, and it says so on screen.
/audit 
What this is, and is not
We would rather lose the deal than oversell the software.
Assisted living software gets bought on promises and lived with for years. Here is the part most vendors leave for the implementation call.
Shipping today
- 20 care and operations modules, all built and tested
- 137 automated tests covering tenant isolation, ledger immutability, five-rights enforcement and two-factor
- TOTP two-factor on every account, including caregivers
- Append-only clinical record enforced by database triggers
- Per-facility timezone and per-facility state reporting windows
- Runs in the browser on phone, tablet and desktop
Not built, and not implied
- Offline charting The product tells you when the connection drops and gives you a Downtime Pack. It never pretends a note saved.
- A family portal Families are contacts on the record today. A portal is on the roadmap; it is not in this build.
- Billing, payroll and invoicing Not in scope for this product. We will not claim a billing module we have not written.
- GPS visit verification That is a home-care capability. CareIT AL is built for facilities.
- A native mobile app It is a responsive web application. It works well on a phone; it is not in an app store.
- Pharmacy interfaces and SSO Roadmap. Scoped when available, not sold now.
On compliance, plainly
CareIT AL is not certified, and we do not represent it as HIPAA-attested. It is built with the controls a regulated deployment needs — individual accounts, two-factor, role-based permissions, an append-only record and a hash-chained audit trail — and an external security assessment is a deferred gate we will complete with a design partner. Any vendor telling you their software makes you compliant is selling you something software cannot do.
The same list appears in the 38-page user guide, under "What this system is not" — download it and check us against it.
See a shift run on CareIT AL.
A live walkthrough on the real product — the morning medication pass, an incident filed at the scene, and what a surveyor would see afterwards.