Ayub Bhayat (Chief Data & Analytics Officer) & Rebecca Llewellyn (Director of Data Management and Transformation)

The NHS Federated Data Platform has attracted intense scrutiny. What matters now is whether it is helping hospitals run better. The evidence is becoming harder to ignore: the programme is moving from technology infrastructure into the daily mechanics of waiting lists, theatres, discharge, cancer pathways and executive decision-making.

For much of its life, the NHS Federated Data Platform has been talked about as a technology contract. That was always too narrow. The argument around procurement, privacy and supplier choice mattered, and it still matters, but it was never the only test. The more important question was whether the programme would make the health service better at seeing what is happening, deciding what matters and acting quickly enough to change the outcome.

That question is becoming more relevant because the programme is no longer sitting at the edge of NHS operations. It is moving closer to the centre. NHS England says 139 trusts live on the platform and 137 are reporting benefits, while 170 trusts have signed up. Thirty-five integrated care boards are also live. The programme now touches a sufficiently large part of the service that it has to be judged as operating infrastructure, not merely as a national digital experiment.

At the centre of the national leadership are Ayub Bhayat and Rebecca Llewellyn. NHS England’s published governance documents identify Bhayat as the senior responsible owner for the data services transformation portfolio and Llewellyn as Director of Data Management and Transformation. Programme-board papers also show both roles embedded in the governance of the Federated Data Platform itself. That matters because the work is no longer about building a platform and handing it over. The task is to turn the platform into something trusts use repeatedly, safely and at scale.

The NHS has never lacked data. What it has lacked is a consistent operating picture. A chief operating officer can receive dozens of reports and still struggle to answer the questions that matter most: which patients are at risk of waiting too long, where is theatre capacity going unused, which discharges are stuck, which pathway errors need intervention today and where demand is beginning to outstrip capacity. The ambition behind the programme is to make those questions easier to answer from a common data layer rather than from disconnected spreadsheets and local workarounds.

The published benefits help explain why the programme has survived the controversy around it. NHS England says 4.69 million referral-to-treatment records have been reviewed using the RTT validation product and 993,477 people have been removed from waiting lists after pathway review for a range of reasons. The Inpatient Care Coordination Solution is associated with 111,589 additional patients undergoing procedures in theatres compared with the previous period without FDP use. NHS England also reports 87,842 patients safely requested for removal from inpatient waitlists and more than 218,000 outpatient entries requested for removal after validation.

The real value is not another dashboard. It is a common operating picture that helps the NHS identify risk and act sooner.

There is an important caveat. NHS England is explicit that some reported benefits are observational before-and-after comparisons and do not prove that the platform alone caused the improvement. Local case mix, adoption maturity and other operational changes can influence the numbers. That qualification should stay in the story. It does not, however, erase the scale of activity or the fact that the platform is now being used to change real workflows.

One of the clearest examples is referral-to-treatment validation. NHS England describes the RTT product as a near-real-time list that clinical teams can access together, allowing them to identify delays, complete required checks and better prioritise patients. Twenty-seven trusts were reporting benefits from the product by the end of March 2026. The value here is less glamorous than artificial intelligence and more important: reducing the risk that a patient is hidden inside bad data.

A trust-level case study from North West Anglia NHS Foundation Trust illustrates the point. The trust used FDP to strengthen RTT assurance while operating with legacy systems and preparing for a future electronic patient record. More than 11,000 pathways were validated, more than 3,000 were removed from the patient tracking list and 27.5% of reviewed pathways were cleared or corrected. The case study describes a move away from fragmented spreadsheets toward a live operational view, allowing teams to direct attention to the pathways most in need of action.

That is where the programme becomes a patient story rather than an IT story. A wrong specialty, an incomplete pathway or an outdated list entry is not simply a data-quality problem. It can translate into a patient waiting longer than necessary or a clinician working from the wrong assumption. Validation, when it is designed properly, is therefore part operational productivity, part clinical assurance and part access improvement.

The same logic is visible in discharge. NHS England says OPTICA, its patient-tracking application for people medically ready to leave hospital, has been associated with reductions of 13.58% in average delay days for patients staying more than seven days and 13.82% for those staying more than 14 days. Those figures are again observational, but they point toward the type of problem the programme is trying to solve: not producing another report on delayed discharge, but helping teams see the delay sooner and act on it.

Ayub Bhayat: holding the strategic line‍

Bhayat’s role sits across the wider data and analytics transformation agenda. The challenge is not only architecture. It is maintaining a coherent national direction while the programme is tested publicly on adoption, governance and measurable benefit.

The national leadership challenge is therefore a dual one. Bhayat has to maintain the strategic case for a national data and analytics architecture, particularly when the programme is under scrutiny. Llewellyn has to help make that architecture operational: translating policy, governance and platform capability into products that trusts adopt and keep using. NHS England’s June 2026 programme-board minutes show the Director of Data Management and Transformation chairing the board, while the wider governance structure continues to include Data and Analytics, clinical leadership, digital operations, transformation, governance and delivery.

The next phase matters because the programme is moving toward a broader operating model. NHS England’s own material emphasises near-real-time information for waiting lists, operations scheduling and care planning, and it is supporting trusts through a Centre of Excellence with training, business change and transformation support. In other words, the national team is no longer simply installing software. It is trying to change how organisations use data to run services.

That timing is important. The NHS is moving into the hardest stretch of the year, when winter preparation, elective recovery, financial planning and emergency pressure collide. The service does not need more dashboards in that period. It needs better intelligence: a clearer picture of risk, demand, capacity and action. The stronger the common operating layer becomes, the more useful it should be to the executives and clinical teams managing that pressure.

The platform will continue to attract scrutiny, and it should. A programme this large needs transparent benefit measurement, credible governance and public confidence. But the debate has moved on. It is no longer enough to ask whether the NHS should have built a national data platform. The more useful question is whether the one it has built is beginning to improve the way care is managed. On the published evidence so far, there is a credible case that it is.

‍