Skip to content

Product guide

Every screen in the product. All of them.

35 real captures of CareAssist, grouped by the work they support. No mockups, no renders — each one is labelled with the route it lives at and the behaviour behind it.

About these screenshots. They are captured from a running instance loaded with realistic demo data — a partially completed post-fall protocol, an active hospice enrolment, therapy sessions, stock with an expiring lot, an approved two-week menu cycle, an admissions pipeline with someone at every stage, and a daughter on the family portal — so you see a working facility rather than a set of empty states. The family portal is shown at phone size, the way relatives use it. The residents are invented. No real person's record appears anywhere on this site.

Group 1 of 15

Getting in

Every staff account carries two-factor authentication. There is no shared facility login, because a shared login makes an audit trail worthless.

/login
Sign in — The way into the facility. Accounts are individual — one person, one login, always attributable.

Sign in

The way into the facility. Accounts are individual — one person, one login, always attributable.

  • Individual accounts only; no shared facility password
  • Forced password reset on first sign-in
  • Sessions are scoped to the facility the user belongs to
/two-factor-challenge
Two-factor authentication — A TOTP code from an authenticator app, required on every staff account — not an upsell, not an optional hardening step.

Two-factor authentication

A TOTP code from an authenticator app, required on every staff account — not an upsell, not an optional hardening step.

  • Standard TOTP: Google Authenticator, Authy, 1Password
  • Recovery codes issued at enrolment
  • Enforced for every role including caregivers

Group 2 of 15

The facility today

One screen that answers "what needs me right now" before anyone opens a resident chart.

/dashboard
Dashboard — The shift opens here, exceptions first: what is overdue, what is due, and what changed.

Dashboard

The shift opens here, exceptions first: what is overdue, what is due, and what changed.

  • Overdue care tasks and open medication passes at the top of the page
  • Open tasks, active orders, recent incidents and census at a glance
  • Visit requests, tours and move-ins that need someone today
  • A connection indicator, because the product never pretends to work offline

Group 3 of 15

Admissions

Everyone on their way in, from the first phone call to move-in day — with the assessment, the paperwork and the numbers an owner asks about in one place.

/admissions
Admissions board — Every prospective resident by stage — inquiry, tour, assessment, approved — with the pipeline numbers across the top.

Admissions board

Every prospective resident by stage — inquiry, tour, assessment, approved — with the pipeline numbers across the top.

  • Days at the current stage on every card, so nobody goes quiet for a month
  • Open inquiries, tours this week, move-ins and the inquiry-to-move-in rate
  • Occupancy against your licensed places
  • Declined and withdrawn inquiries keep their reason
/admissions/create
New inquiry — One form to fill in while the family is still on the phone.

New inquiry

One form to fill in while the family is still on the phone.

  • Only a name, a contact and how they heard about you are required
  • Expected payment, where they live now and when they hope to move
  • The contact email is reused later for the family portal invitation
/admissions/{inquiry}
Pre-admission assessment — Daily living (Katz), fall risk (Morse), thinking and memory, medications and mobility — and a suggested level of care that adds itself up as the nurse answers.

Pre-admission assessment

Daily living (Katz), fall risk (Morse), thinking and memory, medications and mobility — and a suggested level of care that adds itself up as the nurse answers.

  • The suggested level is shown with every point behind it
  • The nurse approves the level; a different level needs a written reason — enforced
  • A signed assessment is never edited; reassessment adds a new one — enforced
  • Wandering with severe impairment is flagged as needing a secured setting
/admissions/{inquiry}
Paperwork and move-in — The documents a move-in needs, each ticked with who and when — then one step creates the resident.

Paperwork and move-in

The documents a move-in needs, each ticked with who and when — then one step creates the resident.

  • Move-in is refused until the physician's report, TB screening, medication list, agreement and emergency contacts are in — enforced
  • Creates the resident, their code status and the family emergency contact together
  • Can invite the family contact to the portal at the same moment

Group 4 of 15

Residents

The resident record is the spine of the system. Everything else — medications, incidents, diets, therapy — hangs off it and writes back to one timeline.

/residents
Resident roster — Everyone in the community, with the flags that change how you approach them visible before you click.

Resident roster

Everyone in the community, with the flags that change how you approach them visible before you click.

  • Condition flags and code status shown on the roster row
  • Filter by unit, status and flag
  • Opens straight into the chart a caregiver actually needs
/residents/{resident}
Resident profile — The chart. Identity, room, contacts, care team and every module tab for this person in one place.

Resident profile

The chart. Identity, room, contacts, care team and every module tab for this person in one place.

  • Photo, room, admission date and responsible parties
  • Tabs for care, medications, diet, incidents, hospice, therapy
  • No free-text field is ever silently interpreted by the system
/residents/{resident}/condition-tags
Condition flags — Structured flags — falls risk, elopement risk, dementia, diabetes — assigned with a tier that decides how loudly they show.

Condition flags

Structured flags — falls risk, elopement risk, dementia, diabetes — assigned with a tier that decides how loudly they show.

  • Tier decides prominence; a per-tag semantic decides colour
  • Red is reserved for genuine urgency, so red still means something
  • Assignment and removal are both recorded, with who and when
/residents/{resident}
Clinical timeline — Every entry about this resident, in order, from every module — and nothing in it can be quietly rewritten.

Clinical timeline

Every entry about this resident, in order, from every module — and nothing in it can be quietly rewritten.

  • Append-only: originals are never overwritten
  • Corrections attach as amendments and show both versions
  • Database triggers block UPDATE and DELETE, not just the UI
/residents/{resident}
Care team — Who is responsible for this resident — internally and outside the building.

Care team

Who is responsible for this resident — internally and outside the building.

  • Assigned staff by role and shift
  • Family and responsible parties with contact order
  • External providers and agencies linked to their own records

Group 5 of 15

In an emergency

The screens designed to be used while something is going wrong — big targets, no scrolling for the answer, printable when the network is not there.

/residents/{resident}/emergency
Emergency card — One page a paramedic can read: code status, allergies, conditions, medications, contacts.

Emergency card

One page a paramedic can read: code status, allergies, conditions, medications, contacts.

  • Structured code status — never free text
  • Allergies and current medications on the same page
  • Prints to paper for the ride to hospital
/emergency
Emergency centre — The whole facility at a glance during an evacuation, lockdown or drill.

Emergency centre

The whole facility at a glance during an evacuation, lockdown or drill.

  • Every resident with code status and mobility needs
  • Emergency service number resolved from the facility country
  • Built to be usable one-handed, on a phone, in a hallway

Group 6 of 15

Daily care

The part of the product a caregiver touches thirty times a shift. If this is slow, nothing else matters.

/residents/{resident}/care-plans
Record care — Logging what was actually done — assistance given, refusals, vitals, observations.

Record care

Logging what was actually done — assistance given, refusals, vitals, observations.

  • Tasks come from the published care plan, not a blank page
  • Refusals are first-class, with a reason, not a missing tick
  • Every entry is attributed and timestamped in the facility timezone
/shifts
Shifts and assignments — Who is on, when, and which residents each person is responsible for.

Shifts and assignments

Who is on, when, and which residents each person is responsible for.

  • Shift windows follow the facility timezone
  • Assignments drive what each caregiver sees on their dashboard
  • Coverage gaps are visible before the shift starts, not after
/handoff
Shift handoff — The shift briefing: what happened since you last looked, acknowledged by the person taking over.

Shift handoff

The shift briefing: what happened since you last looked, acknowledged by the person taking over.

  • Assembled from the shift, not retyped from memory
  • Incoming staff acknowledge — and that acknowledgement is recorded
  • Open tasks and new incidents carried across explicitly

Group 7 of 15

Medications

An eMAR with five-rights confirmation enforced in the application, and the allergy cross-check running underneath it.

/residents/{resident}/medication-orders
eMAR and medication orders — Active orders, the pass windows they generate, and the administration record itself.

eMAR and medication orders

Active orders, the pass windows they generate, and the administration record itself.

  • Five rights confirmed at administration — enforced, not a reminder
  • Allergy cross-check on drug stems (sulfa → sulfamethoxazole)
  • Refusals and holds recorded as outcomes, never as blanks
  • Administrations are append-only; corrections are amendments

Group 8 of 15

Incidents

The module a state surveyor reads first. Two layers: what you saw, and what the facility concluded — kept apart on purpose.

/incidents
Incident register — Every incident, its severity, its reporting clock and whether the investigation is closed.

Incident register

Every incident, its severity, its reporting clock and whether the investigation is closed.

  • Statutory reporting countdown per incident
  • Filter by severity, type, resident and status
  • Nothing disappears from this list — closed is a state, not a delete
/incidents/create
Report an incident — Written at the scene, in the caregiver's words, without a conclusion being demanded up front.

Report an incident

Written at the scene, in the caregiver's words, without a conclusion being demanded up front.

  • Observation is captured separately from cause
  • Occurrence time is normalised from the facility timezone server-side
  • Filing a fall opens the post-fall observation protocol automatically
/incidents/{incident}
Incident detail and investigation — The full record: the original account, the post-fall checks, the investigation, and the reporting deadline.

Incident detail and investigation

The full record: the original account, the post-fall checks, the investigation, and the reporting deadline.

  • Post-fall neuro checks scheduled and chased by the system
  • Reporting window comes from the facility's recorded state rules
  • The screen states which source set the deadline
  • The original account is never edited — findings attach to it

Group 9 of 15

Diet and allergies

Structured allergies and IDDSI-coded diet orders that reach all the way through to what the kitchen plates up.

/residents/{resident}/dietary-profile
Dietary profile — Diet order, texture, drink thickness, preferences and structured allergies in one place.

Dietary profile

Diet order, texture, drink thickness, preferences and structured allergies in one place.

  • IDDSI food textures and drink thickness levels
  • Allergies are structured records, never parsed from free text
  • Allergy matching uses shared singularised words — shellfish never matches fish
  • A diet order beats a derived texture where the two disagree

Group 10 of 15

The wider care team

Hospice, outside providers and therapy — the people involved in a resident's care who do not work for you.

/residents/{resident}/hospice
Hospice co-management — An active hospice enrolment, the agency, and the notes that pass between both teams.

Hospice co-management

An active hospice enrolment, the agency, and the notes that pass between both teams.

  • Hospice status is derived from the enrolment, never typed by hand
  • Co-management notes recorded against the enrolment
  • Revocation is a recorded event with its own date
/providers
External providers and therapy — Physicians, podiatrists, therapists and agencies — tracked without giving any of them a login.

External providers and therapy

Physicians, podiatrists, therapists and agencies — tracked without giving any of them a login.

  • Provider visits recorded against the resident timeline
  • Therapy programmes with session-by-session attendance
  • Consecutive missed sessions are flagged, not silently tolerated

Group 11 of 15

Families

Families see what the care team chooses to share and book their own visits — on a separate sign-in that can never reach the clinical record.

/residents/{resident}#tab-family
The Family tab — Who in the family has access, what they have been shown, and their next visits — on the resident's own record.

The Family tab

Who in the family has access, what they have been shown, and their next visits — on the resident's own record.

  • Invite a relative and record the legal basis for their access — enforced
  • Share a moment, an activity or a wellbeing note, with an optional photo
  • A photo needs a consent tick, and camera location data is removed before families see it
  • Shared updates are never edited — they are withdrawn with a reason
/family-access
Family & visits — The front desk for families: visit requests to answer, confirmed visits this week, and every portal account.

Family & visits

The front desk for families: visit requests to answer, confirmed visits this week, and every portal account.

  • Confirm or decline a request — the family is emailed either way
  • Declining needs a message, so the family hears why and when instead
  • Staff book a confirmed visit for a family who phoned
  • Invitations that were never opened can be resent
/family
The family portal — What a daughter sees on her phone: the latest from the care team, and a visit requested in a few taps.

The family portal

What a daughter sees on her phone: the latest from the care team, and a visit requested in a few taps.

  • A separate sign-in from staff — a family session cannot open a staff page
  • Only the residents they have been given access to, and never the clinical chart
  • Visits requested inside your visiting hours, in the residence's local time
  • Single-use invitation links that expire after seven days

Group 12 of 15

Inventory

Self-contained supply tracking — incontinence supplies, gloves, nutrition, wound care — with stock derived from a movement ledger rather than typed into a box.

/inventory
Stock on hand — What you have, what is below par, and what is about to expire.

Stock on hand

What you have, what is below par, and what is about to expire.

  • Stock is derived from the movement ledger, so it reconciles by construction
  • Par-level reordering excludes family-supplied items
  • Expiry sweep surfaces lots before they turn into waste
/inventory/{item}
Item and movements — Every receipt, issue, adjustment and wastage for one item, including who it went to.

Item and movements

Every receipt, issue, adjustment and wastage for one item, including who it went to.

  • Per-resident consumption where an item is charged to a person
  • Adjustments require a reason and are attributed
  • The ledger is append-only, like the clinical record

Group 13 of 15

Menus and the kitchen

Author the cycle once; the kitchen board works out who gets what texture, which substitution applies, and how many portions to cook.

/menus
Menu cycles — A multi-week menu authored once, with variants derived per resident from their diet order.

Menu cycles

A multi-week menu authored once, with variants derived per resident from their diet order.

  • Textures derived from each resident's dietary profile
  • Dietitian approval is a gate on the cycle, recorded with a date
  • Substitutions are append-only — you can see what changed and why
/menus/kitchen
Kitchen board — Today's service: the production tally to cook from, and dining cards for the floor.

Kitchen board

Today's service: the production tally to cook from, and dining cards for the floor.

  • Portion counts tallied by texture and thickness
  • Dining cards list allergies and preferences per seat
  • Service date follows the facility timezone, not the server's

Group 14 of 15

Reports, audit and downtime

What you hand a surveyor, an owner or a family — and what you fall back to when the internet is not there.

/reports
Reports and exports — The questions asked most often, answered without anyone building a spreadsheet.

Reports and exports

The questions asked most often, answered without anyone building a spreadsheet.

  • Resident CSV export, plus incident and medication reporting
  • Exports are generated from the live record, not a cached copy
  • Your data is exportable at any time, not only when leaving
/audit
Audit trail — Who did what, when, from where — across every module, in one searchable place.

Audit trail

Who did what, when, from where — across every module, in one searchable place.

  • Hash-chained entries; tampering breaks the chain visibly
  • Covers reads of sensitive records, not just writes
  • Cannot be edited or cleared by any role, including administrators
/downtime
Downtime Pack — A generated paper pack — MAR sheets, resident summaries, emergency cards — for when the network is down.

Downtime Pack

A generated paper pack — MAR sheets, resident summaries, emergency cards — for when the network is down.

  • Generated from live data, so the paper is current
  • Covers the medication pass, not just contact details
  • The product never claims offline charting — this is the honest alternative

Group 15 of 15

Administration

Accounts, roles and the facility settings that quietly decide whether the clinical record is correct.

/staff
Staff and access — Accounts, roles, facility assignment and two-factor status for the whole team.

Staff and access

Accounts, roles, facility assignment and two-factor status for the whole team.

  • Role-based permissions down to the action
  • Facility assignment controls what a user can see at all
  • Deactivation preserves everything the person recorded
  • Unlimited staff accounts on every plan

Want to drive it yourself?

We will walk you through these screens on a live instance, with your own scenarios — a resident like one of yours, an incident like one you have had.