Healthcare · Retirement living Representative scenario

Resident safety across a village and its frail care unit

Cottages, a clubhouse and a frail care wing on one site — three different safety problems, one system, and a record that can answer a family's question.

By Frank Guo · Technology & Product Leadership, addanode

At a glance

The deployment in one view.

Operation

A South African private retirement village — independent-living cottages, assisted living and an on-site frail care unit

Drivers

Call responses that could not be evidenced; a resident who left unnoticed; carers alone on night shift; an annual compliance report built from recollection

What we brought together

Existing call points retained, boundary reference points, staff and resident wearables, escalation rules, on-premises event server

Conditions designed for

Occupied cottages that cannot be rewired, outdoor gates and garden paths, disinfectant cleaning, load shedding

Compliance frame

Older Persons Act registration and the section 23(1) annual report; POPIA, including the resident's statutory right to privacy

The shift

From "we answer calls promptly" as an assertion to a record that shows it

The challenge

A village of this shape has three safety problems that look like one and are not. The call problem: residents press, staff go, and nothing in the system records who went or how long it took — so when a family asks, the answer is a duty roster and somebody's memory. The egress problem: a resident in frail care with dementia who walks out through a door a contractor propped open, where nothing is pressed and nothing alarms. And the staff problem: one or two carers covering a large site between 22:00 and 05:00, with the only panic button on a wall in a building they are not in.

Underneath all three sits a fourth: the operator of a registered residential facility must report annually to the Minister on compliance with prescribed service standards and measures to prevent and combat the abuse of older persons. That report was being assembled from rosters, incident files and recollection — defensible in a good year, fragile in a bad one.

The constraint that shaped everything: the site is occupied cottages, a converted main house and a frail care wing added decades later, spread across a landscaped property. Trenching between cottages and opening ceilings in occupied units was not a cost the village was going to carry.

Our approach

Keep the call system, add what it cannot do. Existing call points, pull cords and bathroom cords stayed in service. What was added was routing to the nearest available carer, arrival recorded by presence in the room rather than by someone cancelling a light at the wall, an escalation ladder on timers, and a call-to-arrival time written for every event.

Monitor the boundary, not the person. Reference points went on external doors, the frail care wing's exits, the lift lobby, the main gate and the garden paths that are the site's real perimeter. Inside residents' own cottages and the communal areas, the system deliberately does not watch. Boundary rules applied only to residents whose care assessment called for them, with accompanied exits silent so a resident leaving for an appointment with a carer is not an incident, and night-time profiles so a garden door unremarkable at 14:00 raises an alarm at 02:40.

No cabling where cabling was the problem. Battery-powered reference points with multi-year sealed cells mounted on cottage walls and gateposts and reported over a long-range radio link to a single gateway. Outdoor positions were specified for weather. The frail care wing, being refurbished anyway, took cabled Power-over-Ethernet units where the ceiling was already open — a mixed design rather than one answer for the whole site.

Privacy designed in, not bolted on. Resolution was set to room and boundary level rather than centimetres, raw position history given a short retention with the aggregate response measures kept longer, reporting limited to the named purposes, and processing kept on a server in the village's own office. Residents and families were told what was collected and why before go-live, and staff received a written notice covering the right to object — because under POPIA an employee may object to processing based on legitimate interests, and a purpose narrowly directed at safety is what makes that objection answerable.

Proven in one wing first. The frail care unit went live against acceptance criteria written before installation, in the operator's words. Only then did the cottages follow.

What changed

From assertion to record.

The annual report has evidence behind it

Response times, checks completed and who attended exist as data rather than recollection — so the section 23(1) report is assembled from records instead of reconstructed from files.

An exit raises an alarm on its own

Nobody has to press anything. A resident crossing a monitored boundary unaccompanied is known about while they are still metres from the door, not at the next headcount.

Night staff are not alone

A wearable button carries the carer's location with the alarm, and escalates to a named second responder if the first does not acknowledge.

Alarms stayed worth answering

Accompanied-exit rules, per-resident scope and time-of-day profiles keep the volume low, which is what stops staff learning to dismiss them.

Privacy held its line

No record is created of a resident's movements inside their own home — the system knows boundaries, not days. That is both the legal position and the reason families accepted it.

Nothing was trenched

Battery reference points meant no conduit across a landscaped site and no ceiling opened in an occupied cottage, which is what made the project affordable at all.

The change described above, stated as a before and after. The village could already say that calls were answered promptly; what it could not do was show it — and the right-hand column was achieved without recording anything about a resident inside their own home.

Why this shape of project works

Designed for the site you have, not the one on the plan.

Three decisions carried this deployment, and they are the ones we would make again. Keeping the existing call system, because replacing what works spends budget that the location layer needs. Monitoring boundaries rather than people, because it is simultaneously the cheaper design, the one families accept, and the one that sits properly against a resident's statutory right to privacy. And proving one wing before the rest, because a system that produces an untrustworthy record in a single unit will not become trustworthy across a village.

The approach is set out in full on our nurse call and staff safety page, the design reasoning in wander management without surveillance, and the compliance design in our POPIA guide.

This case study illustrates addanode's approach through a representative retirement-living scenario; client details and figures are omitted by policy. Obligations under the Older Persons Act, POPIA and the norms and standards regulations should be confirmed against the current legislation and your appointed advisers.

Tell us the site, and who answers at 02:40.

We walk the village, mark the real boundaries, and design to the smallest system that answers the question you could not answer last time it was asked.

Book a Site Survey Healthcare & retirement living →