A stable resident generates no alerts.
Alert fatigue kills monitoring products before they earn trust. Companion is built on the opposite premise — silence is the default state.
Every monitoring product fails the same way. It launches loud, surfaces everything it sees, and within a month the badges are on silent and the dashboard is a wallpaper. The floor has decided, correctly, that nothing on the screen is worth interrupting a med pass for.
We built Companion with the opposite premise. A stable resident generates no alerts. Vitals nominal, intake nominal, behavior nominal — auto-logged into the chart, no notification, no buzz, no banner. The system's job is to keep watch quietly, not to perform watching.
Exception-based alerting is a discipline.
It is not a feature you toggle on. It's a posture the whole product has to hold. Every time we consider raising a signal, the question is: does this change what someone does in the next ten minutes? If the answer is no, it belongs in the shift summary, not on a badge.
And when something does cross the threshold, it gets scoped to who can actually act on it. A blood pressure trend goes to the nurse. A toileting request goes to the CNA on that hall. An after-hours clinical question routes to on-call. The wrong person never hears about it, which is what keeps the right person reading.
What this earns us.
Credibility, mostly. When a Companion alert lands on a nurse's phone, she reads it — because the last twelve didn't go off, and this one did. That is the entire product. Next up: per-role quiet hours, so the night charge nurse stops seeing daytime CNA pings.