All resources
Standards 12 May 2026 7 min read

DCB0129: Clinical Risk Management for Health IT Manufacturers, explained

What DCB0129 actually requires, why NHS buyers ask for it, and how to build a Safety Case that holds up to scrutiny.

DCB0129 is the NHS Digital information standard that places legal obligations on manufacturers of Health IT systems to apply clinical risk management to the design, development and modification of their products. If you sell software into the NHS, sooner or later you will be asked to evidence it.

It is not a tick-box exercise. The standard exists because software can, and does, harm patients when hazards aren't identified, mitigated or monitored. A good DCB0129 process makes your product safer; a bad one creates paperwork no one reads.

What DCB0129 actually requires

The standard expects you to operate a Clinical Risk Management System (CRMS), your governing process, and to produce, for each release, a Clinical Risk Management Plan, a Hazard Log and a Clinical Safety Case Report, all signed off by a suitably qualified Clinical Safety Officer (CSO).

  • Clinical Risk Management System (CRMS), your repeatable process
  • Clinical Risk Management Plan (CRMP), scoped to the release
  • Hazard Log, live, version-controlled, traceable to controls
  • Clinical Safety Case Report (CSCR), the narrative argument that the product is acceptably safe
  • Named Clinical Safety Officer, clinically qualified, independent enough to push back

Where teams go wrong

The most common failure is treating DCB0129 as documentation you write at the end. By then the design decisions are baked in and the hazard log is a back-fit. Done well, hazard identification happens at design time, controls are implemented in the product (not the manual), and the Safety Case writes itself.

The second failure is a CSO who only signs things off. A good CSO is in your sprint reviews, your incident calls, your roadmap conversations.

How DigiSafe helps

We build CRMS from scratch or upgrade what you have, run hazard workshops with your engineers and clinicians, and provide a Named CSO on retainer so your safety case is always release-ready, not scrambled together for a procurement deadline.

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.