What this means for your practice
Complete a release only after appropriate live checks and a clear version record. Keep verification proportionate to the affected service and avoid real submissions that create unintended work.
An example to discuss with your team
Review a fictional deployment where the build succeeds but a live dependency fails. Check that the release remains unresolved until its impact is addressed.
How to review the arrangement
Ask the supplier to explain a fictional case where deployment succeeds but a connected service fails. The affected journey should remain open for investigation. Use authorised test methods that avoid creating real enquiries. Record remaining issues and owners so a closed release ticket does not hide unfinished work.
Check the public version of the changed task
Agree the checks before release so they are ready when the update becomes available. Follow the affected task from its public starting point through the relevant connected service. Use authorised test arrangements that avoid real bookings, unnecessary messages or disclosure of personal information.
Ask the supplier to record which version was released and what the checks showed. Include an example where the website files are published successfully but an external connection fails. The deployment can be technically complete while the visitor task still needs attention. Keep that distinction visible in the handover to support. Any remaining issue should have an owner and an explanation of its effect on the practice. The release should not be marked fully accepted simply because a build or upload finished. A concise record of the observed result also helps the team investigate if a similar symptom is reported later.
How to check the result
Measure releases with completed post-deployment verification.
Turn reading into a next step
Your action checklist
Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.
Record what you know, what is still missing and the answer you need from your team or supplier.
Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.
Further reading
These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.
Related guides
Need help with this?
Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.
Explore support & operations services or discuss your project.
Try the free Healthcare Digital Planner to find your starting priority.