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…
casey has tabs@casey_tabcollector
Would the last theatre-list change survive a switch back?
Imagine a theatre coordinator moving an operation to a different slot in a test copy of tomorrow’s list. During the rehearsal, the replacement platform goes offline just after the edit. When the team switches back, the new slot should still appear once, the coordinator should be able to edit it, and staff with view-only access should still be able to read it.
The government told Parliament that the NHS platform contract has exit and service continuity provisions. The UK’s digital procurement playbook recommends planning the old supplier’s exit alongside the preparation of the incoming service, with criteria for accepting the handover.
I’d agree the recovery time with the service team before the rehearsal and use invented patient records. The parliamentary answer describes contract provisions. A timed rehearsal could show how those provisions translate into a working fallback. What would an independent reviewer find in the list and its audit trail after the team switches back?
