The NHS has agreed on the model. Now comes the hard part

Neighbourhood health has become the NHS's dominant organising idea, with integrated care systems having broadly signed up to the model: care closer to home, multidisciplinary teams, prevention over reaction, and all of it digitalised. Let's make the plumbing work.

The co-ordination problem

The central difficulty is co-ordination and this depends on information moving freely across organisations that were never designed to share it; between systems that don't allow for it. Primary care, community services, mental health, social care and the voluntary sector each run their own systems, their own data models and their own workflows.

Structural integration has proceeded at the level of governance; at the level of the home visit or the ward round, little has changed. A care co-ordinator wanting a complete picture of a patient still navigates four or five separate platforms. Information arrives late, or not at all. Decisions get made on partial evidence, or held up waiting for the rest.

The cost of fragmentation upstream

This fragmentation becomes more damaging as care moves upstream. Early intervention requires a longitudinal view of individuals and populations — data that is stitched together for individuals across settings and time. Without it, risk stratification is guesswork and the patients who most need proactive attention remain invisible until they arrive in crisis.

A neighbourhood team cannot manage what it cannot see, and right now, most teams cannot see very much. So the window for early action closes quietly, without anyone noticing it has gone.

A root cause that's architectural, not organisational

The root cause is architectural. Core systems in primary care were built around the practice, not the network. Community and social care platforms vary widely in capability and in what they are willing or able to share. Data-sharing solutions have been bolted on top of existing infrastructure rather than designed into it, which multiplies complexity without resolving it.

The result is interoperability that is narrow, read-only, and unreliable — which is fine for ticking a box, not so fine for redesigning a workflow. Even where data connections exist, clinicians must still piece together a patient's history from multiple systems, a task that adds friction to services already stretched well beyond comfort.

Digitising old ways of working

The deeper consequence is the system ends up digitising existing ways of working rather than enabling new ones. Neighbourhood health, as a model, demands teams think and act across organisational boundaries. The digital environment, almost everywhere, pushes in the opposite direction. Workflows are constrained by what legacy systems will permit. Workarounds accumulate. The gap between the model on the whiteboard and the reality on the ground widens.

What genuine progress requires

Genuine progress requires treating data as a system-wide asset rather than the property of individual organisations. That means open standards, consistent data models and APIs built for real-time access rather than periodic exports. It also means taking identity and access management seriously.

In the case of neighbourhood teams, they are inherently cross-organisational, and clinicians, pharmacists and social workers all need role-appropriate access with proper auditability. These are unglamorous requirements, rarely featuring in ministerial announcements, but without them the model does not function.

Workflow design matters too. Many current processes are shaped less by clinical logic than by the limitations of the systems that support them. Moving to neighbourhood-based care offers a chance to redesign around patient journeys rather than organisational steps, but only if the underlying platforms are flexible enough to accommodate that redesign and stable enough to be trusted. Too often, they are neither.

The procurement trap

The harder constraint sits in procurement. Commissioning processes favour incremental solutions that fit existing configurations. Suppliers optimise for the world as it is. Programmes intended to transform care find themselves shaped, and ultimately limited, by the very environment they were meant to change. Technology ends up reinforcing existing silos rather than dissolving them. This dynamic is well understood and widely lamented. It is less well addressed.

Signs of a more serious reckoning

There are signs of a more serious reckoning. Some systems are moving beyond point solutions toward coherent, long-term architectural strategies including stronger interoperability requirements, clearer expectations around data standards and earlier engagement between clinical leadership and digital teams. The shift in emphasis is real, even if the results are still uneven.

What has changed is the recognition, in at least some quarters, that transformation cannot be procured incrementally. At some point, the foundations have to be rebuilt.

The verdict Is already being written

For those running ICBs and trusts, the implication is uncomfortable. Neighbourhood health cannot be delivered by layering ambition onto outdated foundations. The investment required is less in new services than in the slow, expensive, politically unrewarding work of fixing data infrastructure, governance and architecture — in other words, the kind of work that rarely generates headlines but determines whether everything else functions.

When it gets done, the returns are tangible: teams are able to co-ordinate without friction, earlier intervention, fewer crises and patients who experience care as joined-up rather than accidental.

 The risk of continuing to defer it is equally tangible. Neighbourhood health has been a policy commitment for long enough that its continued absence as an operational reality has become its own kind of verdict. The next phase of NHS reform will be judged less by the strategies it produces than by whether the systems underlying those strategies can finally deliver.