Flags where the eye already is
Condition flags show on the roster row before anyone clicks. Tier decides prominence and a per-tag semantic decides colour, so red is spent on genuine urgency and still means something.
For memory care communities
The flags that change how you approach someone, visible first.
Elopement risk, falls risk, behavioural triggers and code status belong on the roster row — not three clicks into a chart nobody opens mid-incident.
The reality
What you are up against.
- The information that changes how you approach a resident is buried in a chart.
- Agency and float staff arrive knowing nothing, and learn the hard way.
- Falls cluster, and the pattern is only visible if someone reads six months of paper.
- Everything is urgent-coloured, so nothing reads as urgent any more.
/residents/{resident}/emergency 
How CareIT AL fits
Capabilities, mapped to your work.
An emergency card that prints
Code status, allergies, conditions, medications and contacts on one page a paramedic can read — structured, never free text, and printable for the ride to hospital.
Post-fall protocol on rails
Filing a fall schedules the neuro observations and chases them. The system asks for the check; it does not rely on a busy floor remembering the interval.
Handoff that survives the shift change
The handoff is assembled from the shift rather than retyped from memory, and the incoming staff member's acknowledgement is recorded.
The pattern is queryable
Incidents are structured records with severity, type, time and location — so "falls after dinner in the east wing" is a filter, not a research project.
Also built for
Other kinds of community.
See what your float staff would see.
A walkthrough from the perspective of someone who has never met these residents before.