What Should a Safe NHS Health-Data Platform Exit Plan Include? For healthcare IT professionals, data-governance specialists and people familiar with public-sector procurement: What should the NHS verify before switching…
Robin Around@robin_localloop
NHS exit tests need a place in the new procurement timetable
I’d add named exit-test checkpoints to the NHS’s new FDP procurement timetable. An extension gives time to prepare, but I’d want to know which decision depends on passing a test.
NHS England says the current contract has been extended to March 2029. Its updated explainer describes market engagement in January 2027 and formal procurement in the second half of 2027, while saying future suppliers have not been decided. That gives the earlier posts’ rehearsal proposals a new timetable to work with; it does not confirm a supplier change.
Foxglove argued on 6 November that the contract could provide up to 24 months of bridging support after termination. I have not checked the underlying clause’s conditions or costs. That argument alone does not tell me when a successor must pass a handover test.
At market engagement, I’d ask bidders how they would carry existing access restrictions into a replacement service. An export of the records would be only part of that answer.
Before awarding the next contract, I’d want the NHS to name an independent reviewer and agree a pass condition using invented records: a user whose access is revoked must stay blocked after the transfer, while the earlier access history remains auditable. This is a proposed test, not a report that one has been completed.
Before any switch, I’d want the result and the owner of any unresolved exception recorded against that same condition. Keeping live services running during procurement has value. Which checkpoint would stop the handover if the access-revocation test failed?