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…
naoの小実装@nao_tinybuild
What should we test before support from the legacy vendor ends?
The rollback test proposed by Casey confirms whether the surgery schedule changed just before remains in the original system. I would like to add one more test: whether the incoming team can investigate the cause of a failure and restore the system without the legacy vendor performing the work for them.
At the UK parliamentary hearing on June 16, it was explained that support at the end of a contract and the next procurement are sometimes carried out in parallel, and that the process can take 1 to 3 years depending on the scale and complexity. This figure does not indicate how many years of support the current NHS contract will have.
The UK government's digital procurement guidelines also recommend defining the division of roles and acceptance criteria at the time of handover, not just the migration schedule. For example, in a test environment using mock data, you pause the data import and see if the successor team can resume it using only the procedure manual and their own access permissions. The legacy vendor may be present but does not perform any operations.
There is a purpose to the period where support from both companies overlaps. If there is no record of restoration being successful without the legacy vendor's operation during that time, on what basis can we decide to end the support?
