Skip to main content

TPRM Consulting

Healthcare · part 5

Interoperability changes the supplier relationship

What the European Health Data Space, and England’s new information standards powers, mean for supplier risk.

Clive Besterwitch, Founder and Director · Part 5 of 5

Replacing an electronic health record is when a hospital group finds out what owning its data really means. The contract says the group owns its data. The supplier agrees and offers an export. What arrives is technically complete and practically unusable: codes mapped to the old system’s own terminology, years of corrections without their history, and audit logs in a format nothing else can read.

The data was owned. It just couldn’t move.

Interoperability becomes a product requirement

Healthcare technology contracts have often treated interoperability as a project deliverable: build the interface, test the messages, go live. The European Health Data Space makes it part of the product.

The EHDS Regulation came into force in March 2025 and sets a common EU framework for using and exchanging electronic health data. Its main requirements are phased: patient summaries and ePrescriptions from March 2029, and medical images, laboratory results and discharge reports from March 2031.

For electronic health record suppliers, it reaches into product design. Systems placed on the EU market will need harmonised interoperability and logging components, tested before they go to market. The interoperability component has to import and export in the European exchange format, and the logging component has to keep a traceable record of who accessed what.

The UK is moving the same way

England is taking a different legal route towards a similar place. Information standards for health and adult social care have existed for years under section 250 of the Health and Social Care Act 2012, but they applied to the organisations providing care. The companies selling them IT were outside their reach. The Data (Use and Access) Act 2025 changed that. Its provisions on information standards, in force since February 2026, allow those standards to apply to IT suppliers directly.

The details will depend on which standards are published and how they’re enforced. The direction is the same as in the EU: interoperability is becoming something the supplier has to build in and answer for. Each hospital will have less to negotiate on its own.

Why this is a third-party risk question

Interoperability shapes resilience, data rights, your ability to switch supplier, and how dependent you really are on one vendor. You can own your data and still be locked in if the mappings, interface specifications, history, metadata or migration tools sit with one supplier. More portability also means more interfaces, more processors and more data flows to assure.
 
So supplier assessments need to test more than whether an API exists:
  • Can data be exported completely, in the required structured format, with its clinical meaning, codes, corrections and history intact?
  • Is every access, including emergency access, logged in a way you can review?
  • Which subcontractors, platforms and integration services sit in the data flow?
  • Could you actually exercise your exit, transition and archiving rights within a clinically safe period?

Exit is where interoperability gets tested

Most organisations only find out how portable their data really is when they try to leave. By then the supplier has little reason to help, and the clinical service can’t stop while the migration is worked out.

A better approach is to test portability before you need it. Ask the supplier for a sample export of real records, in the format you’d need for a migration, and have someone who knows the clinical data check whether it’s usable. Check that corrections, audit history and attachments come with it. Agree in the contract what an exit will look like, how long the supplier will support it, and at what cost. Revisit it when the system or the standards change.

The same thinking applies to the integrations. Every new interface brings in another supplier, another platform or another processor. Each one needs to be on the supplier register, with an owner, and with a view of what happens to the data flow if it fails.

Timing

The change will be gradual. The main EU dates are years away, implementing acts will fill in the technical detail, and England’s standards will be published over time. But procurement decisions made now decide how hard those requirements will be to meet, and a record system chosen today may still be at the centre of things in 2029 and 2031.

Our view

The European Health Data Space and England’s new information standards powers will push healthcare third-party risk past protecting data held by one supplier, towards assuring data as it moves between suppliers, care settings and permitted uses. The supplier relationships that last will be the ones that let data move without losing its meaning, and that don’t put a fresh dependency behind every new interface.