Public Service ITSM Reference

Playbooks

Change enablement with clinical safety

Building clinical risk management into change and release for health systems.

Most relevant to NHS England NHS Wales NHS Scotland HSCNI

The aim

Every change to a clinical system should be safe and fast enough. Clinical risk management under DCB0160 (mandatory in England, good practice elsewhere) and change enablement can work as one process rather than two queues.

Build it into the change model

Change model Clinical safety approach
Standard change (pre-approved, low risk, repeatable) The Clinical Safety Officer (CSO) assesses the change type once and records it in the safety case. Each instance follows the approved procedure.
Normal change A clinical safety screening question on every change form: "Could this affect patient care, clinical data or clinical decisions?" If yes, the CSO assesses the hazards before approval.
Emergency change The CSO, or a delegated clinician, is reachable out of hours and gives a rapid assessment. Full review afterwards.

What a clinical safety assessment covers

  • What clinical functions, data or workflows the change touches.
  • New or changed hazards (for example wrong patient, missing data, delayed information, misleading display).
  • Controls: testing, training, communications, configuration, and workarounds if it goes wrong.
  • Residual risk and whether it's acceptable.
  • Updates to the hazard log and, for significant changes, the clinical safety case report.

Release and testing

  • Test with realistic clinical scenarios, including the edge cases that cause harm.
  • Involve clinical users in acceptance for changes that alter how they work.
  • Plan rollback and the clinical impact of rolling back (for example, data entered in the new version).
  • Tell clinical staff what's changing and when, in plain language.

Supplier releases

When a supplier issues a new release of a clinical system:

  1. Ask for the release notes and the supplier's DCB0129 safety documentation.
  2. Assess the local impact: configuration, integrations and workflows unique to you.
  3. Update your own hazard log and safety case.
  4. Approve through your change process like any other change.

Make it workable

  • Train change managers to spot clinical relevance; not every change needs the CSO.
  • Give the CSO a seat (or a delegate) at the change advisory board for clinical systems.
  • Track clinical safety review time as part of change lead time, and improve it.
  • Feed incidents with patient-safety impact back into hazard identification.