All resources
Standards 19 May 2026 6 min read

DCB0160: Clinical Risk Management for NHS Deployers, explained

DCB0160 is the deployer's responsibility, and it doesn't disappear just because your supplier has DCB0129. Here's what NHS organisations actually need to do.

DCB0160 is the companion standard to DCB0129. Where DCB0129 governs the manufacturer, DCB0160 governs the NHS organisation deploying, configuring and using a Health IT system. It is a legal obligation on the deploying organisation, not the supplier.

We see trusts and ICBs assume that buying a 'DCB0129-certified' product means their job is done. It doesn't. Local configuration, integration, training and workflow choices all introduce new hazards that only the deployer can assess.

What DCB0160 covers

  • Local clinical risk assessment of the deployment
  • Local hazard log, the hazards introduced by how you use the system
  • Clinical Safety Case Report owned by the deploying organisation
  • Named Clinical Safety Officer accountable for the deployment
  • Ongoing assurance, incident monitoring, change control, retirement

Where deployers go wrong

Two patterns: passing supplier documentation off as your own (it isn't, it doesn't cover your context), and writing the deployment safety case only at go-live (too late to influence configuration).

DCB0160 done well sits inside your change-control and clinical-governance routines, not as a separate consultancy artefact.

How DigiSafe helps

We support ICBs, trusts and health boards with deployment risk assessments, hazard workshops with clinical and operational staff, and named CSO cover for the deployment, including ongoing assurance once you're live.

Want this applied to your product?

We turn standards like this into evidence packs, safety cases and embedded CSO support, so you can focus on building.