NHS neighbourhood health needs a telecare feedback loop, not another proactive care campaign

NHS neighbourhood health is not just another policy slogan.

It is a signal that health, social care, housing, voluntary services and local communities need to work as one connected system — closer to home, earlier in the pathway, and with better use of data.

For telecare providers, this should be a major opportunity.

Telecare already sits inside people’s homes. It already receives signals from people who are frail, isolated, recently discharged, at risk of falling, or living with long-term conditions. It already connects people to alarm receiving centres, responders, social care teams, housing providers, next of kin and emergency services.

But the traditional telecare model has a problem.

It handles events, but rarely closes the loop.

Commissioners often know how many alarms were installed, how many calls were answered, and how quickly an alarm receiving centre responded. They do not always know whether the service reduced avoidable admissions, improved recovery after discharge, reduced carer strain, prevented repeat falls, supported urgent community response, or helped neighbourhood teams understand where risk was building.

That is the gap NHS neighbourhood health exposes.

The future of telecare is not another pendant alarm contract. It is not another marketing campaign about “proactive care” or “cognitive care”. It is a cohesive, measurable, commissioner-visible feedback loop between people, providers and local systems.

Short answer

NHS neighbourhood health needs telecare to become a source of real-time operational intelligence, not just a reactive alarm service.

Commissioners need to see:

who is being supported;
what risks are being detected;
what actions were taken;
what happened next;
whether the pathway worked;
where escalation was avoided;
where the system failed;
which cohorts need earlier support;
which providers are genuinely improving outcomes.

Without that feedback loop, proactive care remains a campaign phrase.

What is NHS neighbourhood health?

Neighbourhood health is the NHS and government direction of travel for delivering more care closer to home.

NHS England’s 2025/26 neighbourhood health guidance describes a shift toward integrated working between the NHS, local government, social care and partners. It says systems should focus first on people with complex health and social care needs, including adults with frailty, people with multiple long-term conditions, and people with high use of urgent and emergency care.

Source: NHS England: Neighbourhood health guidelines 2025/26

The neighbourhood health framework goes further. It says the NHS and local authorities must transform how they work together, aligning services, contracts and pathways at neighbourhood level.

Source: GOV.UK: Neighbourhood health framework

That matters for telecare because telecare is already positioned at the edge of the neighbourhood model.

It is in the home.

It is connected to risk.

It is used by people who often need multiple services.

It can support urgent response, falls pathways, discharge, reablement, independent living and long-term condition management.

But only if the service is integrated into the wider care pathway.

The commissioner-provider problem in telecare

In theory, telecare should give commissioners a powerful view of community risk.

In practice, many telecare contracts still operate like this:

A person presses a pendant or a sensor triggers.
The alarm receiving centre answers.
A script is followed.
A responder, carer, family member or emergency service is contacted.
The incident is closed in the telecare platform.
The commissioner receives activity reporting.

That model can be operationally useful. It can also be dangerously incomplete.

The missing question is:

What did the commissioner learn that changes tomorrow’s pathway?

For example:

Was this the third fall in six weeks?
Did the person recently leave hospital?
Was the call linked to loneliness, confusion, medication, mobility or housing?
Was urgent community response available?
Did the responder attend?
Was the person conveyed to hospital?
Did a care plan change?
Did the incident trigger a review?
Did the provider’s action prevent escalation?
Did the system learn anything?

If those answers remain trapped inside a supplier platform, a call note, a spreadsheet, or an alarm receiving centre workflow, the commissioner does not have a feedback loop.

They have a service report.

That is not enough for neighbourhood health.

Why feedback loops matter

A feedback loop is the difference between activity and learning.

For telecare, a useful feedback loop looks like this:

graph TD
    A[Alarm, sensor, call or scheduled check-in] --> B[Structured event and person context]
    B --> C[Workflow-driven response]
    C --> D[Outcome captured]
    D --> E[Shared with commissioner and relevant care teams]
    E --> F[Pathway reviewed and improved]
    F --> G[Earlier intervention next time]

This is how telecare becomes part of prevention.

It allows commissioners to ask:

Which cohorts are generating repeat alarms?
Which falls pathways are working?
Which providers respond quickly but fail to reduce repeat incidents?
Which neighbourhoods have rising risk?
Which housing schemes need targeted support?
Which people need proactive contact before crisis?
Which call types are being sent to 999 unnecessarily?
Which urgent community response pathways are rejecting referrals?
Which interventions actually reduce long-term care demand?

Without this loop, the commissioner is buying activity.

With it, the commissioner is commissioning intelligence, prevention and measurable improvement.

NHS England already points in this direction

NHS England’s technology enabled care referral guidance is important because it moves telecare beyond isolated alarm handling.

The guidance says there are over 200 TEC providers nationally, many commissioned by local authorities. It also says the top 10 national TEC providers account for around 1 million alarm connections — about 50% of all alarm connections — and deal with over 93% of alarm calls without further referral to ambulance or emergency services.

Source: NHS England: Technology enabled care referral guidance

That is a huge operational footprint.

The same guidance asks local systems to connect TEC providers with urgent community response services, establish referral pathways, identify data that can show the size of the opportunity, and use at least quarterly plan-do-study-act cycles to understand and reduce rejected referrals.

That is the beginning of the feedback-loop model.

It means telecare should not be commissioned as a disconnected response line. It should be part of a neighbourhood pathway that can learn.

The failure of incumbent telecare thinking

For years, the market has promised a shift from reactive alarms to proactive care.

The language has changed:

proactive care;
predictive care;
cognitive care;
intelligent care;
preventative support;
data-led wellbeing;
AI-enabled independent living.

But the tangible commissioner-facing change has often been weak.

Many incumbent market leaders have been very good at selling a future state. They have been less convincing at proving that future state in a repeatable, transparent, commissioner-visible way.

The issue is not whether sensors, analytics or AI can help. They can.

The issue is whether the provider can show:

the baseline;
the intervention;
the outcome;
the counterfactual;
the pathway change;
the cashable or non-cashable benefit;
the data-sharing model;
the governance model;
the evidence that a commissioner can trust.

Too often, the market has sold the story before building the system of evidence.

Cognitive care is the warning sign

Cognitive care should have been the point where telecare moved from reactive alarm handling into measurable prevention.

The promise was attractive:

identify changes in behaviour earlier;
detect rising risk before crisis;
reduce avoidable escalations;
support people to live independently for longer;
give commissioners better insight into population need.

That is exactly the direction neighbourhood health now requires.

The problem is that incumbent market leaders have often promoted cognitive care faster than they have delivered commissioner-visible evidence.

For commissioners, the test is not whether a supplier can describe a proactive care model. The test is whether they can prove it works across real pathways, real cohorts and real service contracts.

If a market leader says cognitive care reduces GP visits, ambulance callouts, hospital admissions or residential care demand, commissioners should ask:

Supplier claim	Commissioner question
“We detect deterioration earlier”	Which deterioration patterns, validated against what outcomes?
“We reduce ambulance callouts”	Compared with what baseline, over what cohort, and with what confidence?
“We reduce admissions”	Which admissions, in which pathway, and how was attribution measured?
“We support proactive care”	What operational workflow is triggered, who owns the action, and what is reported back?
“We use AI or analytics”	Can the commissioner inspect the logic, governance, false positives and false negatives?
“We improve independence”	How is independence measured beyond user stories?

The issue is not that cognitive care is the wrong idea.

The issue is that cognitive care without transparent workflows, structured outcomes and commissioner feedback loops becomes another campaign slogan.

Neighbourhood health needs more than a prediction. It needs an accountable pathway.

A risk signal should trigger a defined workflow. That workflow should assign responsibility. The outcome should be captured. The commissioner should be able to see whether the intervention worked.

Without that, the market is not delivering cognitive care.

It is delivering cognitive branding.

The evidence base is mixed

Telecare has value. But the evidence does not support blind faith in technology.

The Whole Systems Demonstrator telecare trial recruited 2,600 people with social care needs across three areas in England. The Nuffield Trust summary says telecare as implemented did not lead to significant reductions in service use over 12 months.

Source: Nuffield Trust: Effect of telecare on use of health and social care services

This does not mean telecare does not work.

It means technology alone is not the intervention.

The intervention is the whole operating model:

assessment;
installation;
monitoring;
workflow;
response;
escalation;
data-sharing;
review;
care planning;
commissioner learning;
continuous improvement.

When those parts are disconnected, telecare becomes a reactive service.

When they are joined, telecare can become a neighbourhood intelligence layer.

What incumbents have failed to give commissioners

The biggest failing of incumbent telecare platforms is not that they lack devices.

It is that they rarely give commissioners a live, useful model of what is happening across the population.

Commissioners need more than alarm counts and response times.

They need to know:

which cohorts are deteriorating;
where repeat incidents are clustering;
where pathways are failing;
which provider actions are creating value;
which risks are being hidden by operational closure;
which interventions should be scaled;
which services need redesign.

A call being “closed” does not mean the risk has been resolved.

A pendant alarm being “answered” does not mean the neighbourhood system has learned.

A dashboard being “available” does not mean the commissioner has actionable insight.

A cognitive care campaign does not equal cognitive commissioning.

What a cohesive solution should look like

Neighbourhood health needs a more cohesive model.

That model should connect telecare providers, commissioners, service providers, social care teams, housing providers, urgent community response, responders and family networks around shared workflows.

A modern telecare platform should support:

1. Shared commissioner-provider visibility

Commissioners should be able to see not just activity, but outcome.

That includes:

alarm type;
response route;
time to contact;
escalation;
responder attendance;
urgent community response referral;
outcome;
repeat risk;
follow-up requirement;
unresolved risk;
provider performance;
pathway bottleneck.

2. Workflow-driven care, not isolated call handling

A fall alarm should not simply generate a call.

It should trigger a pathway.

For example:

graph TD
    A[Fall detected] --> B[Check person is safe]
    B --> C[Assess injury and immediate risk]
    C --> D[Contact next of kin or responder]
    D --> E[Refer to urgent community response where appropriate]
    E --> F[Schedule follow-up check]
    F --> G[Update outcome]
    G --> H[Flag repeat fall risk to commissioner and care team]

This is different from a call script.

It is an auditable workflow.

3. Proactive contact with a defined purpose

Proactive care should not mean random check-in calls.

It should mean targeted, policy-controlled, measurable interventions.

Examples:

post-fall check-ins;
discharge follow-up;
medication adherence prompts;
loneliness and welfare calls;
heatwave and cold-weather checks;
power outage support;
missed activity pattern follow-up;
next-of-kin confirmation calls;
responder attendance confirmation.

Each proactive workflow should have a clear owner, escalation route and outcome measure.

4. Human-led AI with guardrails

AI can support telecare, but it should not replace accountability.

AI-assisted calls, summaries and triage should sit inside customer-defined workflows. Commissioners and providers should define:

what the AI is allowed to ask;
when it must stop;
when it must escalate;
what outcomes it can record;
what it cannot decide;
what requires human review;
what must be audited.

The system should be deterministic around safety and governance, even where AI supports conversation.

5. Feedback into commissioning

The commissioner should not receive a PDF report three months later and call that evaluation.

They should have structured insight into:

demand;
risk;
outcomes;
cost avoidance;
failed pathways;
provider performance;
inequality;
digital exclusion;
service resilience;
repeat incidents;
unmet need.

That is how commissioning becomes active rather than retrospective.

What commissioners should ask telecare providers now

Commissioners should ask direct questions.

Area	Question
Data access	Can we export structured event, workflow and outcome data without supplier lock-in?
Pathway integration	Can your platform support urgent community response, falls, discharge and neighbourhood MDT workflows?
Outcomes	What outcomes do you measure beyond call handling and installation volume?
Evidence	Which claims are independently evaluated and which are supplier-authored case studies?
AI governance	Where AI is used, what are the human oversight, audit and escalation controls?
Feedback loops	How does the service help us redesign commissioning decisions?
Data protection	What is the controllership model, DPIA position and information-sharing approach?
Interoperability	How do you integrate with digital social care records, shared care records and local data platforms?
Resilience	How do you handle digital switchover, connectivity loss and monitoring-centre failure?
Exit	Can we leave with our data, workflows and audit history intact?

If a provider cannot answer these questions, they are not ready for neighbourhood health.

What service providers need

Service providers also need a better model.

A provider delivering telecare, response, care calls or ARC operations should not be trapped between separate commissioner requirements, supplier systems and manual workarounds.

They need:

clear workflows;
shared case context;
auditable handovers;
structured outcomes;
escalation rules;
next-of-kin pathways;
AI guardrails;
live operational dashboards;
commissioner reporting;
integration with real-world events;
evidence that the service is working.

This is especially important where providers work across multiple commissioners.

One local authority may want next-of-kin first. Another may want AI triage before human handover. Another may want technical alarms handled differently from personal alarms. Another may want 30-minute attendance confirmation after escalation.

A cohesive platform should support those different commissioning models without turning every new contract into custom operational chaos.

The real shift: from telecare as a service to telecare as infrastructure

The old model was:

graph LR
    A[Device] --> B[Alarm]
    B --> C[Call centre]
    C --> D[Closure]

The neighbourhood health model needs:

graph LR
    A[Signal] --> B[Workflow]
    B --> C[Response]
    C --> D[Outcome]
    D --> E[Learning]
    E --> F[Commissioning action]

That is a different category of platform.

It is not just telecare.

It is neighbourhood care infrastructure.

It connects people, devices, calls, AI support, operators, responders, family contacts, social care, housing and NHS pathways into a shared operating model.

This is where the market needs to move.

Where Care3 Labs and Intoku fit

At Care3 Labs, our view is simple:

Neighbourhood health will not be delivered by more disconnected dashboards, more vague AI claims, or more proprietary alarm workflows.

It needs a control plane for community care.

That means:

deterministic workflows defined by commissioners and providers;
safe AI-assisted communication inside clear guardrails;
proactive calls triggered by care events, schedules or external risks;
auditable alarm handling;
structured outcomes;
human escalation;
provider performance visibility;
commissioner feedback loops;
integration with telecare, ARC and wider care operations.

This is the shift from reactive monitoring to measurable neighbourhood support.

Technology should not replace human care.

It should make human-led care more coordinated, more visible and more accountable.

Conclusion

NHS neighbourhood health creates a clear challenge for telecare.

The sector can either keep selling the same promise — proactive care, predictive care, cognitive care — without giving commissioners tangible feedback loops.

Or it can become a real part of neighbourhood infrastructure.

That means moving beyond alarm handling and into shared workflows, structured outcomes, transparent evidence and commissioner-visible learning.

The winners in this market will not be the suppliers with the loudest campaign.

They will be the ones that help commissioners answer the question that really matters:

Did this service help people live safely and independently at home — and can we prove it?

FAQ

What is the link between NHS neighbourhood health and telecare?

NHS neighbourhood health aims to bring care closer to home and connect NHS, local authority, social care and community services. Telecare is relevant because it already operates in people’s homes and can support falls, urgent response, discharge, independent living and proactive wellbeing pathways.

Why do commissioners need telecare feedback loops?

Commissioners need to understand whether telecare is improving outcomes, not just answering calls. A feedback loop connects alarm events, provider actions, outcomes and pathway learning so commissioners can redesign services and target prevention.

What is wrong with traditional telecare reporting?

Traditional reporting often focuses on installations, alarm volumes and response times. Those metrics are useful, but they do not show whether risk reduced, admissions were avoided, repeat falls changed, urgent community response worked, or care plans improved.

Has cognitive care delivered on its promise?

Not consistently enough.

Cognitive care is the right ambition, but incumbent market leaders have often failed to turn the concept into transparent, repeatable and commissioner-visible evidence. Commissioners should challenge any proactive or cognitive care claim by asking for pathway-level outcomes, baseline comparisons, governance controls and evidence that the service changed decisions in the real world.

What should modern telecare providers offer?

Modern telecare providers should offer interoperable data, workflow-driven response, structured outcomes, audit trails, AI guardrails, proactive contact, human escalation, commissioner dashboards and evidence that pathways are improving.

Is AI safe in telecare?

AI can support telecare when it is constrained by clear workflows, human oversight, escalation rules, audit trails and data governance. It should not make autonomous care, clinical or eligibility decisions without appropriate governance and accountability.