30-second briefing
The central finding
- Detection, response and prevention are separate measures.
- Evaluate workload and unwanted effects alongside potential benefits.
- Changing staffing or visits requires evidence about the resulting service.
Monitoring and prevention describe different achievements. A device may detect movement accurately while leaving the person waiting for assistance. An alert can be timely and still reach someone unable to respond. For a care provider, the consequential unit is the complete pathway: detection, interpretation, action and the person’s outcome.
This revised July feature examines that distinction through official falls guidance and care-technology consent guidance. It makes no general claim that monitoring reduces falls, avoids hospital admissions or permits safe staffing reductions. Those conclusions need evidence about a specific intervention, setting and population.
What falls evidence supports—and leaves unresolved
NICE’s 2025 falls guideline supports assessment and interventions matched to individual risk factors. Its discussion identifies insufficient evidence to recommend some assistive technologies for falls prevention, with further research needed. The implication is narrow: evidence for a monitoring product should not be inferred from general endorsement of prevention.
A falls alert after an event is also different from an intervention that prevents the event. Both can be useful, but they answer different questions. Marketing and procurement documents should distinguish detection performance, response times and changes in falls or injuries. Combining them into a single benefit makes it harder to see what has actually been demonstrated.
An alert needs a destination with capacity
Consider an illustrative overnight service receiving a movement alert. The worker first needs to know which person and room it concerns, whether a response is urgent and whether someone is already attending. If the alert goes to a device carried by a worker assisting another resident, notification alone supplies no additional capacity. This is a hypothetical pathway, not an observed failure.
The test should follow the alert under ordinary pressure: competing calls, handover, an absent colleague and a connection interruption. It should identify who takes responsibility if the first recipient cannot act. A product demonstration in a quiet room may establish a technical function while telling the service little about this operating condition.
More information can create more work
A system that flags every deviation may increase investigation without improving outcomes. Workers can spend time distinguishing harmless variation from something requiring action. The relevant evidence includes alerts that were not useful, situations that were missed and the burden of reviewing them. An impressive count of generated alerts does not indicate successful prevention.
Before judging a trial, the provider should agree what a meaningful change looks like for the person: fewer disruptive checks, an earlier clinical conversation, better sleep or a faster response. Measures should include adverse effects and the reasons staff dismissed alerts. Otherwise the evaluation risks counting the activity the technology creates as the benefit it delivers.
Privacy is part of care quality
CQC’s technology guidance says consent to care generally remains necessary when technology is involved. Where someone cannot make a particular decision, capacity and best-interest processes matter. Agreement to receive care should not be treated as blanket permission for every form of observation. The applicable data-protection requirements are a separate consideration.
The conversation should explain what is sensed, what is retained, who sees it and what happens when someone refuses. A person may welcome an unobtrusive call mechanism and dislike continuous recording. The provider’s practical problem is to offer a workable support arrangement while respecting that distinction, rather than reduce a personal decision to a ticked form.
A changed care model needs a changed evidence standard
Adding a sensor to an existing response arrangement is different from redesigning staffing or withdrawing visits around that sensor. The latter decision changes the consequences of failure. A reliable device cannot establish that a new pattern of support is appropriate for everyone who might receive it.
Any proposed redesign should show its assumptions explicitly: which people it concerns, how they were involved, who responds, what happens during downtime and when the previous arrangement will be restored. A small favourable pilot may support further testing. It cannot establish that the same result will persist across different buildings, workforce arrangements or levels of need.
Follow the person, not just the dashboard
A strong reported follow-up would reconstruct the sequence from a detected change to an actual response, using appropriately handled records and the person’s perspective. It would examine cases where the pathway worked and where it did not. It should also report whether other changes occurred at the same time, such as staffing, medication review or environmental improvements.
That context matters because a before-and-after fall count cannot alone attribute a change to one device. Differences in who lives in the service or how events are recorded can alter the result. Care Circle has not undertaken that investigation here. The proposed evidence standard is intended to make future coverage more demanding than a summary of supplier claims.
Questions leaders should ask now
The Care Circle view
Care Circle assessment
Prevention is an outcome, not a property a service can assume from the presence of a sensor. The provider must connect technical performance with response capacity and individual choice.
The most valuable next evidence will explain the complete care pathway. That is where a useful technology becomes a useful service—and where the limitations of an apparently successful installation become visible.
Continuing coverage
Follow the question into the later editions.
Can your care records leave the system without losing their meaning? · 10 October 2026
The January telecare transition is a care-continuity test · 9 October 2026
A digital reset needs to prove that care can continue · 5 August 2026
Develop the analysis
Read the connected flagship reports.
Digital continuity: can the care service depend on its systems?
Operational assurance: suppliers, equipment and resident voice
Sources, method & limitations
How to read this analysis
Individual review and full rewrite of a genuine July article, completed 10 October 2026. Linked primary sources support attributed findings; operational interpretation is Care Circle analysis. No interviews, provider audit or unpublished records underpin this edition.
- No observed service case, product comparison or claimed reduction in falls.
- NICE discussion concerns its specified population and settings.
- Hypothetical examples are explicitly labelled.