Summary
Is integrated patient experience intelligence finally possible in the NHS? Or will infrastructure without design leave us with expensive technology and limited value?
The jigsaw pieces needed for integrated patient experience intelligence are finally starting to come together across the NHS, but the question is whether anyone is going to bother assembling them. In this three-part series, Ben Kenyon has examined the fragmentation of the current system and explored how the infrastructure pieces are now forming. In the final blog of the series, Ben shows what becomes possible if the systems and infrastructure are designed properly.
Content
When the infrastructure connects properly, several capabilities become real rather than theoretical:
Pattern recognition across populations: Linking feedback to patient records could identify that seven patients in ward 4B this month all experienced poor discharge Family and Friends Test (FFT) scores, formal complaints and readmissions, surfacing a systemic ward-level failure invisible in aggregated data.
Pathway intelligence: Tracking experience across organisational boundaries. For example, Mr Patel's diabetes journey from GP through hospital to community could reveal communication breakdowns at specific transition points, showing exactly where coordinated intervention is needed rather than where we assume it might be.
Temporal layering: Using feedback sources that operate on different timescales as genuinely complementary intelligence rather than competing measurements. FFT flags issues within days. Complaints provide detail and context weeks later. National surveys validate patterns months on. Together they give you early warning, understanding and confirmation.
Experience-to-outcome causation: Linking Patient Reported Experience Measures (PREM) to Patient Reported Outcome Measures (PROMs) and clinical outcomes, potentially revealing which specific process failures correlate with worse patient health. This is the capability that makes the whole architecture matter clinically, not just operationally.
What actually needs to happen
None of these capabilities emerge automatically from Federal Data Platform (DDP) deployment or NHS App rollout. Here is what does need to happen.
Clear strategic intent
Before building anything, organisations need clarity on what capabilities they're actually trying to create. Pattern recognition, pathway intelligence and predictive analytics each require fundamentally different data structures and analytical approaches. "We want better patient experience data" is not specific enough to design for. "We want to identify when multiple patients on the same ward experience the same failure pattern within a 30-day window" is.
Purpose-built data architecture
FDP access does not mean your data is structured for integration. Patient-level linking requires designing how feedback records connect to patient identifiers with appropriate consent and anonymisation. Record-level linkage between feedback and clinical systems requires technical integration between databases that don't currently communicate. Cross-organisational pathway tracking requires data sharing agreements and common identifiers across providers. These are conscious design choices. They do not make themselves.
Governance that enables rather than blocks
The capabilities described here require uses of patient feedback data that current governance frameworks may not explicitly permit. Linking feedback to clinical records for pattern recognition raises information governance questions. Sharing data between organisations for pathway intelligence requires formal agreements. Using feedback to predict clinical outcomes needs specific governance approval.
Commercial platforms have customer consent built into their terms of service. NHS data operates under stricter legal requirements and requires governance specialists to work through what's appropriate, how to maintain privacy whilst enabling intelligence, and what frameworks teams can actually operate within. This is not a blocker. It's a design task that needs to be resourced.
Serious analytical capability
The vision requires specialist analytical work that goes well beyond deploying a large language model (LLM). Pattern recognition needs queries identifying specific combinations across sources. Predictive analytics needs models trained, validated and maintained as patterns evolve. Experience-outcome causation needs statistical methods that can distinguish correlation from causation. This means data scientists and health services researchers doing substantive work, not something technology deployment delivers on its own.
Organisational change
Complaints teams, patient experience teams and quality teams currently operate independently. Integration requires them to collaborate, share intelligence, coordinate responses and act on insights that cross traditional silos. That is cultural change. It requires leadership commitment and accountability for outcomes that nobody currently owns.
Technology cannot solve this. Leadership can.
Sustained investment
This is not a project. Data architecture needs maintaining. Analytical models need refining as patterns evolve. Governance needs updating. Teams need supporting. Permanent capability requires permanent resources. The organisations that will realise value from this infrastructure are the ones that treat it as ongoing capability investment, not a one-off implementation.
The risk worth naming
The NHS has a long history of deploying sophisticated infrastructure and then wondering why outcomes haven't changed. The risk here is specific: FDP operational, NHS App rolled out, PREMs collected, LLMs available, and none of the integrated intelligence these pieces could enable because the design work was never done.
Expensive technology generating limited additional value is not a hypothetical failure mode. It is a well-documented pattern.
The window to shape how integration works in practice is now, while the infrastructure is still forming, before architectural decisions get locked in by default rather than design. The organisations investing in strategic design work now will extract the intelligence this infrastructure can deliver. The ones that wait for the technology to do it for them will spend the next decade asking why they're still struggling.
Other blogs in the series:
About the author
Ben Kenyon has spent around 20 years working on healthcare's harder problems with data, analytics and, more recently, AI. He began on the NHS Graduate Informatics Training Scheme and went on to lead the Business Intelligence function at Manchester University NHS Foundation Trust, the UK's largest hospital trust, before moving into consultancy and health technology.
During his time at Quantium Health, he led the team responsible for taking Quail from concept through to commercialisation and deployment across the NHS. Quail became the first third-party product to go live on the NHS Federated Data Platform and one of the earliest production applications of large language models to unstructured NHS patient feedback—work cited in the NHS 10 Year Health Plan and recognised with an HSJ Award.
His interest lies in the design decisions that turn healthcare data into meaningful intelligence, and, ultimately, intelligence into better decisions and outcomes for patients.
Recommended Comments
Create an account or sign in to comment