Health and care
Clinical safety and health IT
DCB0129, DCB0160 and medical device rules, and how they plug into change and release.
Most relevant to NHS England Suppliers
Why IT can harm patients
Health IT can contribute to harm: a wrong result shown against the wrong patient, a missing allergy, a delayed referral, an outage at the wrong moment. Clinical risk management is the discipline of identifying and controlling those hazards across a system's life.
The two standards (England)
Both are mandatory information standards under section 250 of the Health and Social Care Act 2012:
| DCB0129 | DCB0160 | |
|---|---|---|
| Who | Manufacturers of health IT | Health organisations that deploy and use health IT |
| Requires | Clinical risk management system, Clinical Safety Officer, hazard log, clinical safety case and report | The same, for deployment, configuration, use, change and decommissioning |
| ITSM touchpoints | Product releases, defects, problem management | Change enablement, release, incident, problem, configuration, decommissioning |
The Clinical Safety Officer (CSO) must be a suitably trained, registered clinician. The hazard log records each identified hazard, its causes, controls and residual risk. The clinical safety case report argues that the system is acceptably safe for its use.
In Wales, Scotland and Northern Ireland the standards aren't mandatory, but they're widely used as good practice.
Where it plugs into ITSM
- Change enablement: every change to a clinical system gets a clinical safety assessment proportionate to risk. Standard changes can carry a pre-assessed safety case. See change enablement with clinical safety.
- Incident management: flag incidents with potential patient harm and involve the CSO. Patient safety incidents may also need reporting through clinical incident systems.
- Problem management: link known errors to hazard log entries; a workaround can be a new hazard.
- Configuration management: clinical configuration (templates, order sets, decision support rules) needs the same control as code.
- Supplier management: get the manufacturer's DCB0129 safety case and hazard log, and keep them current.
Software as a medical device
Some software is a medical device, for example software that diagnoses, calculates doses or gives treatment recommendations. It must meet the medical device regulations and be registered with the MHRA in Great Britain; in Northern Ireland, EU rules apply under the Windsor Framework. Check the status of software before you deploy it, and treat changes to it with particular care.
Don't let clinical safety become a sign-off at the end. Involve the CSO in design and testing, so that safety work changes the system rather than just documenting it.