Skip to content

The platform

Twenty-two modules. One resident record.

CareAssist 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 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 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

Move-in and families

The admissions pipeline with its scored pre-admission assessment and move-in checklist, and the family portal with its own sign-in, shared updates and visit booking.

  • Admissions
  • Family

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.

Admissions & move-in

Inquiry, tour, a scored pre-admission assessment and a paperwork checklist — then the resident record in one step.

Family portal & visits

Families see the updates and photos staff choose to share, and request visits inside your visiting hours.

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.

See all of it, screen by screen

Admissions

From the first phone call to move-in day.

Inquiries are captured while the family is still on the phone and move across one board — tour, pre-admission assessment, approval, move-in. The assessment scores daily living and fall risk and suggests a level of care, showing every point it added up. The nurse makes the decision.

  • Katz daily-living index and Morse Fall Scale, scored as the nurse answers
  • A suggested level of care from 1 to 4 — a different approved level needs a written reason
  • Signed assessments are append-only; reassessment adds a new one
  • A move-in checklist: physician's report, TB screening, medication list, agreement, contacts
  • Move-in creates the resident, the family emergency contact and an optional portal invitation
  • Occupancy, inquiry-to-move-in rate and average days to move in
/admissions/{inquiry}
An approved inquiry: daily-living and fall-risk scores, the approved level of care, and why that level was suggested, point by point.
Pre-admission assessment

Family portal

Families close, and the chart still private.

Relatives get their own sign-in, invited from the resident's record. They see the moments, activities and wellbeing notes staff choose to share, and they request visits that the front desk confirms. The portal runs on a separate login entirely, so a family session can never reach a staff page or the clinical record.

  • Access per resident, with the legal basis recorded — consent, power of attorney, guardianship
  • Single-use invitation links that expire; access can be withdrawn at any time
  • Photos need a consent tick and have camera location data removed
  • Visit requests inside your visiting hours, confirmed or declined with an email to the family
  • Every family sign-in, view and request is written to the facility's audit trail
/family-access
The Family & visits page: visit requests waiting for a decision, confirmed visits this week, shared updates and family portal accounts.
Family & visits

For caregivers

The shift, on the phone already in your pocket.

CareAssist 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
A caregiver arriving at a residence, phone in hand, greeted at the door.

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
A nurse scanning a medication package at a resident's side, tablet in hand.

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
  • The move-in pipeline, from first call to move-in day, on one board
  • Visit requests from families confirmed or declined in one place
An administrator reviewing operational dashboards at her desk.

Engineering you can hold us to

Rules the software enforces, not suggests.

Each one exists because the alternative fails in a way somebody eventually has to explain to a family — or to a surveyor.

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.

Move-in waits for the paperwork

The resident record cannot be created until the assessment is signed and the required documents are ticked. A suggested care level is shown with every point behind it, and a nurse who approves a different level must write down why.

Family access needs a legal basis

Nobody sees a resident in the family portal until staff record why they may — the resident's consent, a power of attorney, a guardianship. Access is per resident and can be withdrawn, and the portal never shows the clinical chart.

/audit
The audit trail listing attributed, hash-chained entries across modules.
The audit trail — uneditable by any role, including administrators

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

  • 22 care and operations modules, all built and tested — including admissions and the family portal
  • 192 automated tests covering tenant isolation, ledger immutability, five-rights enforcement, two-factor, admissions and family access — run on MySQL as well as SQLite before every release
  • TOTP two-factor on every staff 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.
  • Family messaging, statements and family two-factor The family portal shows updates staff choose to share and books visits. Two-way messaging, billing statements and two-step sign-in for family accounts are 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. CareAssist 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

CareAssist 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.

See a shift run on CareAssist.

A live walkthrough on the real product — the morning medication pass, an incident filed at the scene, and what a surveyor would see afterwards.