The data deadlock: solving NHS demand, capacity and flow with orchestration

The NHS does not lack strategy, clinical expertise or effort. What is missing, as it continues to strain under sustained pressure, is a way to coordinate existing capacity fast enough.

The challenge is most visible in the elective care waiting list, which rose from 2.3 million in 2010 to a peak of 7.7 million in 2023, remaining elevated today – a structural sign that demand has been outpacing the NHS’s ability to convert capacity into flow for years.

A structural pressure

Demand on the NHS will continue to grow, thanks to population rise, increased clinical complexity, and greater expectations of care. Constrained bed numbers, workforce shortages and the slow translation of financial investment into capability will concentrate these challenges. Therefore, any strategy about how to increase capacity must focus on how those limited resources are synchronised.

Doing so will improve the quality of care in frontline settings, while also supporting better preventive care in community services.

Currently, problems that crop up in one part of the system cascade through others. For example, a delayed discharge will reduce a ward’s bed availability, which adds pressure on the accident and emergency department, which in turn impacts ambulance handovers, and so on. There are tens of such compounding “flow effects” in every healthcare environment, and they reveal how interdependent the NHS, social care and local authorities have become.

Perhaps more data is the answer? Yet NHS organisations already generate more data than ever. Electronic patient records record clinical events, patient administration systems and bed systems track movement, and theatre systems manage utilisation. However, these are systems of record, not systems of coordination.

Connectivity is valuable, but it’s not the same as coordination, so data exchanged through interfaces and APIs helps systems talk to each other, but doesn’t produce a single operational truth that everyone can act on. Each system still holds its own version of reality, so staff must continue to attend bed meetings, huddles, and escalation calls to manually reconcile information. It is necessary, but absorbs time, attention and energy that should be focused on care.

A related problem is decision latency. When information arrives late, the response lags too. A delayed discharge might be noticed hours after it should have been resolved, or a theatre cancellation only becomes visible once it is too late to replace. The system reacts after the impact, rather than intervening.

Why current fixes fall short

The NHS has, of course, invested in pathway redesign, command centres and digital infrastructure. Those investments have value. But reporting explains what has happened, process redesign improves pathways, and escalation frameworks respond to failure. None of them creates continuous cross-domain coordination.

The likes of the NHS Federated Data Platform (FDP) are useful, but not sufficient. Connecting data more effectively strengthens the foundations for analysis and common visibility. The FDP is undeniably a positive step, but connecting data is not the same as coordinating operational activity across the whole ecosystem – including wards, theatres, diagnostics and discharge pathways. The NHS, its partners and patients need both.

The missing capability

How? Like many of the sectors Netcompany works in, it is about orchestration. That does not mean another system of record or replacing the core platforms that trusts depend on. Instead, orchestration technology sits above these and helps these systems work together more intelligently.

Orchestration is not another reporting or analytics layer – it is a real-time coordination capability that continuously synchronises activity across systems and teams. This enables the detection of emerging constraints, the ability to apply prioritisation logic, and the capability to coordinate responses across teams in real time. Fragmented signals combine to become a live operational picture that prompts action.

In healthcare, operational data is temporal. Beds turn over, admissions progress, diagnostics are run, and staff shifts change. Trusts, therefore, need a coherent view of what is happening in every moment – and what should change as a result.

Why architecture matters

Some parts of the NHS need to be shaped locally, because every trust serves different communities, works with different partners and faces different pressures. Care pathways, service models and day-to-day processes should reflect that. Other parts should span the entire system. Shared mechanics – like an orchestration layer that oversees moving information between trusts and departments, keeping records aligned, and coordinating activity – need to be reliable, standardised, and easy to reuse.

That is why coordination should be platformed, not rebuilt inside every trust or core system. Overcustomising EPRs or PAS platforms creates fragility and risk. So does a patchwork of point solutions and duplicate dashboards. An orchestration layer offers a better path: preserving the systems of record, adding coordination, and keeping the trust in control of its logic.

The economic case is compelling. In a constrained system, small gains compound quickly. An early discharge releases a bed, which eases admissions, which reduces A&E pressure, which lowers cancellations, which improves elective throughput.

To kickstart such efforts, trusts should select use cases where value can be unlocked fastest: the most visible pressure points for flow. Discharge is one example, theatre-bed alignment and diagnostic bottlenecks are two more obvious choices. Starting with low-hanging fruit allows trusts to prove value quickly, before scaling coordination more broadly.

Responsible digitalisation, better coordination

The NHS has digitised hugely, yet it still lacks systematic coordination. That is why waiting lists remain high, bed occupancy stays tight, and emergency performance continues to feel fragile.

The next phase of NHS digital evolution must be the introduction of an orchestration capability that maintains a shared operational state across domains, enables the continuous real-time coordination of data, patients and staff, and embeds prioritisation and action into workflows. This would improve flow without requiring wholesale replatforming.

In a system where expansion is constrained and workforce growth is limited, coordination is the only pathway to unlock further capacity.