Designing for the resident who cannot press the call button.
The call button assumes four things in a row, and a meaningful slice of residents cannot complete the chain. Companion is built to notice first.
The nurse call button is the oldest UI in the building, and it has a hidden specification. To press it, a resident has to know something is wrong, name it well enough to act on it, remember where the button is, and have the hand strength to push. That is four assumptions in a row. For a meaningful slice of skilled nursing residents — arthritis, post-stroke motor loss, aphasia, advanced dementia — at least one of those links is broken on a given day.
A reactive UI fails quietly in that gap. Nothing is logged, because nothing was pressed. The shift report shows a calm night. The resident, meanwhile, was in pain, or confused, or trying to get out of bed alone.
Proactive instead of reactive
Companion inverts the default. It is hands-free, and it assumes the resident cannot initiate. It greets them by name, checks in at the cadence the care plan asks for, listens during the long quiet stretches, and asks open-ended questions a person can answer with a sound, a word, or a sentence. The resident is never the one expected to start the conversation.
What changes at the bedside
For a resident with aphasia, a yes/no prompt offered out loud is reachable in a way a wall button never was. For a resident with dementia, a familiar voice gently checking in is a form of orientation, not a test. And for the room as a whole, signs of distress — a wince, a long silence after a question, a request repeated three times in an hour — get surfaced to staff as they happen, instead of waiting on a press that was never going to come.
The product impact is the part we care about most. Someone who could not have asked for help still gets noticed. Concretely, that becomes a check-in event on the timeline, a draft note in the chart, and, when the pattern warrants it, a nudge to the nurse before the next round.