Why Your Medical Records Don’t Follow You From One Doctor to the Next
You turn up at an urgent care clinic with a flare-up your GP has already treated twice this year. The nurse asks what medication you’re on, whether you’ve had this before, and what worked last time. You do your best from memory, because the clinic in front of you has no idea what the surgery across town already knows. Multiply that scene by every referral, every switched provider, and every weekend trip to A&E, and you start to see the actual cost of systems that don’t talk to one another.
Key Takeaways
- Interoperability in healthcare is the ability of separate systems to exchange information in a form the receiving clinician can read and act on immediately.
- A GP practice, a hospital trust, a pharmacy and a private specialist often run different software from different vendors, so records frequently move by fax, scanned PDF, or a patient carrying paperwork between appointments.
- The consequences are sharpest in emergency care, where allergies, current medication and existing conditions are needed within minutes and a missing record gets replaced by guesswork or delay.
- Researchers argue that interoperability is a prerequisite for digital medicine, because artificial intelligence and mobile health tools cannot work on data trapped in isolated databases and proprietary formats.
- Shared standards such as HL7 FHIR and the record structures published by the Professional Record Standards Body exist to let one system read another’s data without a phone call or a translation step.
That’s the problem interoperability in healthcare is meant to solve. Not as an abstract IT concept, but as the practical difference between a clinician who already has your history in front of them and one who’s starting from a blank page because your last three appointments live in a system they can’t reach.
The gap between your GP, your pharmacist and your specialist
Most people assume their health information moves with them automatically. It rarely does. A GP practice, a hospital trust, a community pharmacy and a private specialist often run on entirely different software, built by different vendors, on different timelines, for different purposes. Getting a referral letter, a set of scan results or a medication list from one to another can still depend on a fax machine, a scanned PDF, or a patient physically carrying paperwork between appointments.
This isn’t a failure of any single organisation. It’s what happens when systems are procured separately, over years, without a shared plan for how the data inside them should move. Each system might do its own job well. The problem sits in the connective tissue between them, which is exactly where interoperability is supposed to operate.
The stakes are highest in emergency care, where there’s no time to chase down a paper file or wait for a callback from another surgery. A clinician treating someone unconscious or confused needs to know about allergies, current medication and existing conditions within minutes, not hours. When interoperability is missing, that information gap gets filled with guesswork, caution that slows treatment down, or sometimes both at once.
A paramedic in a blue jacket and face mask holding the hand of a patient lying on a stretcher inside an ambulance
What interoperability actually solves for patients
Interoperability is not a filing problem. It is the difference between a clinician who knows about your allergy and one who has to ask.
Strip away the technical language and interoperability is about one thing: making sure the right information reaches the right person at the right moment, regardless of which system created it. In the NHS, that has meant efforts to standardise how records are formatted and shared, so a hospital in one region can read a summary written by a GP in another without translation, delay, or a phone call to check. The Summary Care Record is the most widely used example, giving staff outside a patient’s own surgery access to a core set of details such as medication and allergies.
Underneath that sit the shared formats that make any of it possible. Standards like HL7 FHIR, now on its fifth release published in 2023, define how a medication list or a test result should be structured so that a system which has never encountered its sender can still parse it correctly, while the Professional Record Standards Body publishes the clinical record structures those exchanges are expected to follow.
When it works, the benefit is almost invisible. A specialist already knows about your allergy before they prescribe anything. A pharmacist can see a recent dosage change instead of relying on you to remember it accurately. None of that requires you to do anything differently. It just means the systems have already done the work of finding each other.
It also matters for the questions patients rarely think to ask, like who else can see a record once it’s shared, and how easily it gets corrected if something in it is wrong. UK data protection law treats health information as a special category and gives patients the right to have inaccurate records rectified, though exercising that right across four organisations running four systems is harder than exercising it against one. The stakes of getting the security around that sharing wrong are not abstract: in March 2025 the ICO fined an NHS software processor over a 2022 ransomware attack that disrupted NHS 111 and left staff unable to access patient records, putting the data of nearly 80,000 people at risk. Interoperability that moves data without also giving patients some visibility into where it’s gone tends to feel invasive rather than reassuring, even when the underlying intention is good. The technical plumbing and the trust patients place in it need to be designed together, not treated as separate problems solved by separate teams.
A doctor in a white coat with a stethoscope turning the pages of a printed lab results report on a clipboard
Where the friction still shows up
For most people, the gaps in interoperability show up as small but familiar irritations rather than dramatic failures. You’re asked the same questions at every appointment. A referral seems to vanish for weeks. A specialist orders a test your GP already ran last month, because there was no easy way to check first. None of these are catastrophic on their own, but they add up to care that feels disjointed, and they occasionally let something more serious slip through the cracks, like a medication interaction nobody had visibility to catch.
When your fitness tracker and your doctor don’t speak the same language
There’s a newer version of this problem too. Millions of people now track sleep, heart rate, activity and blood glucose through wearables and health apps, generating more personal health data than most GP records have ever held. Very little of it reaches a clinician in a usable form. Your watch might flag an irregular heart rhythm for weeks before you mention it, and even then, your doctor usually can’t pull that history directly into your notes. The data exists. The interoperability to make it clinically useful, usually, does not.
This is the wider point made by Lehne and colleagues in a 2019 npj Digital Medicine paper, who argue that interoperability is a prerequisite for digital medicine rather than an optional refinement of it. Data hidden in isolated databases, incompatible systems and proprietary software cannot be exchanged or analysed properly, which means the artificial intelligence and mobile tools everyone expects to transform care are left working with a fraction of what has already been recorded.
A person outdoors tapping the screen of a black fitness tracker on their wrist
Why policy alone won’t fix this
National standards and data-sharing agreements matter, but they only get you so far. Interoperability ultimately gets built, or doesn’t, inside the software that clinicians and patients use every day, and that’s where good design decisions carry as much weight as good policy. A system can be technically compliant with every data standard going and still fail in practice if it’s slow, confusing, or built around how an administrator thinks rather than how a nurse works during a busy shift.
This is where specialist health-tech development earns its place alongside policy work. The platforms built by this healthcare software partner, a UK app and web development company, are designed around how clinical teams actually need information to move, rather than treating data-sharing as a box-ticking exercise. Its work on Radarr Medical, an NHS radiology communications platform built to get time-sensitive results to the right clinician quickly, sits squarely in this space: the same underlying challenge as interoperability more broadly, applied to one specific, high-pressure part of a patient’s care.
What better interoperability could mean for your next appointment
Imagine a version of the system where your allergy history, current medications and recent test results are simply there, wherever you happen to end up needing care. Where a locum GP or an out-of-hours clinician isn’t working from nothing. Where a hospital discharge summary reaches your regular GP the same week, not the same month. None of this requires patients to become more organised or more vigilant about carrying their own records around. It requires the systems behind the scenes to be built so that information follows the person, not the building they happen to be standing in.
That’s still a work in progress across most healthcare systems, the NHS included, and it will stay that way for some time yet. But the direction is clear enough, and every provider that gets interoperability right, whether through better standards, better procurement, or better software, makes the next appointment a little less like starting from scratch.
Frequently Asked Questions
What does interoperability in healthcare actually mean?
It means separate health IT systems can exchange information in a form the receiving system and clinician can read and act on straight away. The test is not whether data can be sent at all, but whether it arrives structured well enough to be used without someone retyping or interpreting it first.
Why can’t my GP and the hospital just see the same record?
Because they usually run different software, bought separately, at different times, from different vendors. Each system may work well on its own terms, and the difficulty lies in the connections between them, which were rarely part of the original purchase.
Does the NHS have any shared record at all?
Yes. The Summary Care Record gives staff outside your own GP surgery access to core details such as your medication and allergies, and it is the most widely deployed example of record sharing in England. It is a summary rather than your full history, so it does not remove the need for broader interoperability.
Can my doctor see data from my smartwatch or health app?
Usually not in any direct or automatic way. A small number of trusts and GP systems can accept structured exports from consumer health apps, but for most patients the data stays on the phone and only reaches a clinician if it is described out loud in an appointment.
What are HL7 FHIR and the PRSB?
They are the two things that make record sharing technically possible in the UK. HL7 FHIR is an international standard defining how clinical data should be structured for exchange, and the Professional Record Standards Body publishes the record structures that UK health and care services are expected to follow.
