The NHS App opened the front door. Prevention asks a harder question of the data

Date posted
15 June 2026
Reading time
7 minutes

The NHS App serves as a digital front door connecting patients to their healthcare, but prevention efforts require more integrated and actionable data beyond this, says Product Lead Stephen Arthur.

 

What people think the NHS knows about them 

Ask people what the NHS knows about them, and most assume the answer is "everything" – one joined-up record holding every appointment, test result and prescription under their name. It's a reasonable assumption; it's how the NHS feels when it works well. But that isn't how it's built – there's no single record. What looks like one is a network of separate systems, each holding part of the story: your GP record, the details of your hospital visits, the screening and vaccination reminders that reach you as messages. The NHS App pulled much of that together behind one front door – a real achievement, and one that works largely by hiding the complexity underneath. But it's also where the 10 Year Health Plan's biggest ambition meets its hardest constraint: prevention can't work by hiding the seams; it must reach across them. 

 

The NHS App waits to be asked 

The NHS App answers when it's asked. Open it to order a repeat prescription, book an appointment or look at your GP record, and it fetches what you need from the GP, hospital and national systems that hold it. Pulling those services together so it feels like one place is what made the App a front door millions of people use. But a front door waits to be knocked on. It doesn't speak first. 

Those services are transactional, built so you can get something done. Take your GP record; the App can show it to you, but it doesn't act on what's there, because that data isn't in a form prevention could use. Even the moments that feel proactive – an appointment reminder, say – are a provider pushing a message through the App, not the App noticing something about you.

Prevention works the other way round. It depends on the system noticing something and reaching out before anyone thinks to open the App. Access waits to be asked. Prevention can't. 

 

Prevention asks more of the data 

A system that acts only when asked reaches the people who already ask: the engaged, the confident, the worried-well. The ones who'd gain most are the least likely to knock first. Which is why prevention starts with the data underneath and needs more than the current foundation can reliably give. 

First, it needs a joined-up view over time. Risk rarely shows itself in a single record on a single day; it emerges from the pattern across your GP, your hospital visits and the care you've had in the community. No one system holds that whole picture today. 

Second, it needs data that means the same thing wherever it came from, structured and coded consistently. When the same clinical fact is recorded three different ways in three different systems, you can't reason across it. Prevention depends on being able to interpret data reliably, not just retrieve it. 

Third, it needs to know when something changes. Acting early means responding to a new result or a new diagnosis as it happens – a flow of changes, not a snapshot fetched when someone opens the App. 

And finally, reaching someone who hasn't asked is a different relationship from answering one who has. That needs shared rules for how data can be used and acted on across organisations, and consent built for being contacted, not just looking something up. 

People must trust why the NHS is getting in touch. 

 

Same App, different experience 

Here's where it gets trickier than it looks. Even something as ordinary as getting your GP record meant connecting to several different GP systems. When the App first integrated with general practice, the same feature could behave differently for patients at neighbouring surgeries – not by design, but because each supplier exposed its data in its own way, with its own limits. The patient never saw that, but it made a consistent experience hard to build. 

That picture is improving. Newer national interfaces are standardising how patient-facing services connect to GP systems, so new providers follow one route rather than each being a special case, and more hospital services are being joined up nationally too. The direction of travel is towards consistency. 

But prevention raises the bar again. The NHS already does proactive prevention at scale – vaccination, screening, the NHS Health Check – each working out who's eligible and reaching out in its own way, some nationally, some locally. That's manageable for a handful of programmes; it won't stretch to the broader, more personalised prevention the 10 Year Health Plan wants. The inconsistency that made one App feature awkward is what would keep every new service solving the same problem from scratch – and care from reaching people when it should. 

 

The platform's ready. Is the data? 

The important question in the 10 Year Health Plan isn't about the App at all. The front door is built. The data sitting behind it is the harder, slower problem prevention depends on most. 

The encouraging part is that the centre is acting on this. The move towards a Single Patient Record is, at its heart, an attempt to give every service a more joined-up, more consistent view to build on – the NHS App among them. How that's delivered is still being worked out, and it won't fix everything on its own. But the intent is right: to make the data something services can rely on, rather than something each must stitch together for itself. 

The platform has shown what's possible. The real test of the next decade is whether the data can catch up. 

 

About the author: Stephen Arthur is a Product Lead in Kainos's Healthcare sector, with almost ten years on large-scale, patient-facing NHS services. He led product on the NHS App for five years – from its early days through to live service – and more recently on the digital NHS Health Check, giving him a foot in both the "front door" the App built and the prevention services that now depend on the data behind it.