
What you need to know
- DCB0129 sets clinical risk management requirements for manufacturers of health IT systems, and DCB0160 sets them for the organisations that deploy and use them.
- Both are information standards under section 250 of the Health and Social Care Act 2012; the current versions took effect on 1 July 2018.
- Since 7 July 2025, section 250 says persons to whom a standard applies must comply, but NHS England says that, as the standards stand, bodies must continue to have regard to them.
- Manufacturers need a Clinical Safety Officer who is a registered clinician, a hazard log and a clinical safety case report shared with the deploying organisation.
- NHS England consulted on revising both standards from 29 June to 11 September 2026, and had set autumn 2026 as its target for publishing new versions.
DCB0129 is the NHS clinical risk management standard for manufacturers of health IT systems used in England, and DCB0160 is its counterpart for the hospitals, practices and care providers that deploy them. For suppliers, gaps in DCB0129 documentation can stop a sale at the assurance stage. For trusts, a weak DCB0160 process can leave a new electronic record, app or AI tool in clinical use without its hazards examined. This guide covers the legal basis, the Clinical Safety Officer role, the hazard log and safety case, the link to medical device regulation and NHS England’s review of both standards.
What DCB0129 and DCB0160 are
Both are information standards listed in the NHS Data Standards Directory. DCB0129, titled Clinical Risk Management: its Application in the Manufacture of Health IT Systems, carries the reference DCB0129 Amd 24/2018 and is described as designed to help manufacturers of health IT software evidence the clinical safety of their products. DCB0160, Clinical Risk Management: its Application in the Deployment and Use of Health IT Systems, carries the reference DCB0160 Amd 25/2018. Both are listed as active, with NHS England as publisher.
The directory says DCB0160 was prepared by the NHS Digital Clinical Safety team and forms part of the NHS Digital Clinical Safety Standards, accompanied by its manufacturing counterpart. Both entries list their scope as health services, NHS services and adult social care.
The standards are not new. NHS England says they were first introduced in 2009 and have been updated periodically, with the current versions, DCB0129 version 4.2 and DCB0160 version 3.2, published in 2018 to include medical devices. The directory gives the same dates for both 2018 amendments, set out below.
| Milestone | DCB0129 | DCB0160 |
|---|---|---|
| Approved | 29 May 2018 | 29 May 2018 |
| Published | 7 June 2018 | 7 June 2018 |
| Effective from | 1 July 2018 | 1 July 2018 |
| Post-implementation review date | 31 December 2018 | 31 December 2018 |
| Directory page last updated | 30 September 2026 | 30 September 2026 |
The reason for the 2018 change is recorded in the directory entry for DCB0160: following the publication of the EU Medical Devices Regulation (EU 2017/745) in May 2017, and evidence of the need for clinical risk assessment of medical devices using software, a decision was made to extend the scope of the standard to include medical devices. The information standards notice for DCB0160 records that the Data Coordination Board, acting under delegated authority from the Secretary of State for Health, approved the change for publication under section 250 of the Health and Social Care Act 2012.
The legal basis: section 250 and the duty to comply
Section 250 of the Health and Social Care Act 2012 lets the Secretary of State or NHS England prepare and publish information standards. According to section 250 as published on legislation.gov.uk, subsection (6A) now says any other person to whom an information standard applies must comply with it, except where the requirement is waived under subsection (6B). The site records that the subsections replacing the old subsection (6) took effect on 7 July 2025 under section 95 of the Health and Care Act 2022, and that further amendments took effect on 5 February 2026.
Those February 2026 amendments were made by paragraph 3 of Schedule 15 to the Data (Use and Access) Act 2025, which section 121 of that Act introduces under the heading information standards for health and adult social care in England, and were brought into force by S.I. 2026/82. Among them, paragraph 3(4) adds a relevant IT provider to the list in subsection (2B), and subsection (7) now defines a relevant IT provider as a person involved in marketing, supplying, providing or otherwise making available the technology and services the section describes.
NHS England’s supporting information for its national review sets out what this means. It says section 95 of the Health and Care Act 2022, in force from 7 July 2025, changed the duty from have regard to must comply and introduced the Health and Social Care Information Standards (Procedure) Regulations 2025. It says section 121 of the Data (Use and Access) Act 2025, in force from 5 February 2026, expanded the scope so that IT providers can be subject to a duty of compliance.
NHS England then adds a qualification. As the standards stand, it says, bodies exercising a health and care function must continue to have regard to them, while future revisions of the standards are likely to use the enhanced powers. The supporting paper gives no date for revised standards; NHS England’s 2024 response to HSSIB, described below, set autumn 2026 for publishing them.
NHS England already describes the standards as mandatory. Its response to a recommendation in the HSSIB safety recommendations log, received on 6 November 2024, described them as mandatory standards in place to ensure that healthcare IT suppliers and NHS organisations, including primary care providers, follow structured clinical risk management processes. A 7 April 2026 blog on the AI and Digital Regulations Service by an NHS England clinical lead describes DCB0129 as a mandatory NHS England requirement.

Who DCB0129 applies to and who DCB0160 covers
The split is between the organisation that makes a health IT system and the organisation that puts it into clinical use.
- DCB0129 is addressed to manufacturer personnel who are responsible for ensuring clinical safety, according to its directory entry. NHS England says it applies to manufacturers of health IT systems and requires them to appoint a clinical safety officer throughout the development lifecycle.
- DCB0160 applies to health organisations responsible for ensuring clinical safety in the deployment, use, maintenance or decommissioning of IT systems. NHS England lists NHS trusts, primary care organisations, social care providers and other care entities among the care organisations it covers.
Many organisations sit on both sides. A trust that builds its own software and offers it to other organisations is treated as a manufacturer under the NHS England Digital Technology Assessment Criteria (DTAC), and DTAC expects in-house products to meet the same standards. Where a supplier sells hardware and software together, NHS England says the DCB0129 documentation submitted in DTAC section C1 must cover the combined system.
NHS England’s review paper gives a sense of how far the standards reach. It says that over the past 15 years the standards have helped build a digital clinical safety ecosystem, with thousands of clinical safety officers trained and deployed across manufacturing and health and care organisations.
What DCB0129 requires of manufacturers
The requirements below are taken from NHS England pages that summarise or apply the standard, and each is attributed.
The Clinical Safety Officer
The core personnel requirement is a named Clinical Safety Officer (CSO). An NHS England clinical lead, writing on the AI and Digital Regulations Service in April 2026, said there is a requirement for a CSO to be appointed under DCB standards. The DTAC assessed-section guidance says the Clinical Safety Officer must be a clinician with a current registration with a professional body, and asks suppliers for the CSO’s details.
One training expectation has eased. NHS England’s DTAC page says the previous version of the DTAC form required the clinical safety officer named in its clinical safety section to undertake training provided by NHS Digital, and that this requirement no longer stands. The registration requirement and the duty to appoint a CSO are separate from that training point, and the assessed-section page still says the CSO must be trained in clinical risk management.
Hazard log, safety case and risk management plan
The same NHS England blog says DCB0129 requires a Hazard Log and Clinical Safety Case Report, and that the manufacturer must share the DCB0129 Clinical Safety Case Report with the deploying organisation. The DTAC assessed section asks manufacturers to upload their completed DCB0129 documents, listed as the risk plan, the clinical safety case report and the hazard log.
DTAC also requires manufacturers to keep an up-to-date DTAC form and the required supporting documents for each product version, and tells buying organisations to re-assess elements that have an expiry date or change due to upgrades. For a manufacturer, that ties the DCB0129 documents submitted in section C1 to each product version, not only to the first sale.
What DCB0160 requires of deploying organisations
DCB0160 places parallel duties on the buyer. The AI and Digital Regulations Service’s guidance for adopters on complying with the clinical risk management standards, last reviewed on 12 January 2023, says both developers and adopters must carry out a risk assessment on the digital technology. For adopters it says:
- create a clinical risk management system;
- be able to evidence clinical risk management governance arrangements, clinical risk management activities, and clinical safety competence and training;
- do a clinical risk assessment;
- not adopt a digital technology that does not meet these standards.
The guidance describes this work as legally required and essential. It also says staff must have the appropriate knowledge, experience and competencies for the risk management tasks assigned to them, without naming any specific course or certificate. Under its heading on how to meet DCB0160, it says the clinical risk management process must start at the earliest stage of the development lifecycle, notes that risk management includes maintenance and decommissioning, and says to plan how to monitor and manage risk after deployment.
For medical devices connected to hospital networks, the same guidance recommends a further standard, ISO/IEC 80001-1:2021, when integrating a medical device into IT infrastructure. The April 2026 NHS England blog says DCB0160 is a mandatory step for any new health IT deployment in NHS settings, and that deployers must assess local risks and document how they will manage them.

The clinical risk management process step by step
Putting the manufacturer and deployer duties together, a typical procurement of a new clinical system runs as follows. Each step is grounded in the NHS England and AI and Digital Regulations Service sources cited above.
- Manufacturer appoints a CSO who is a registered clinician, for the whole development lifecycle.
- Manufacturer builds the DCB0129 file: risk management plan, hazard log and clinical safety case report for the product version.
- Manufacturer checks medical device status with the MHRA rules and, where relevant, prepares the NHS England Pre-Acquisition Questionnaire as well as DTAC.
- Manufacturer submits DTAC section C1 with the DCB0129 documents and shares the safety case report with the deploying organisation.
- Deployer runs its own DCB0160 process through its clinical risk management system: a local clinical risk assessment covering the risks of implementing and using the system in its own environment.
- Deployer decides whether the system meets the standards. If it does not, the guidance says the organisation should not adopt it.
- Risk is managed after go-live. The deployer plans how to monitor and manage risk after deployment, including maintenance and decommissioning, and the manufacturer keeps its documentation current for each product version.
| Document or role | Produced by | Standard | Shared with |
|---|---|---|---|
| Clinical Safety Officer | Manufacturer (and deployer for its own process) | DCB0129 and DCB0160 | Named in DTAC section C1 |
| Clinical risk management plan | Manufacturer | DCB0129 | Uploaded to DTAC section C1 |
| Hazard log | Manufacturer | DCB0129 | Uploaded to DTAC section C1 |
| Clinical safety case report | Manufacturer | DCB0129 | Deploying organisation |
| Local clinical risk assessment | Deploying organisation | DCB0160 | Internal governance |
Neither directory entry lists a fee. Compliance is shown through the documents themselves, reviewed by deploying organisations and, for suppliers, through DTAC section C1. No official timescale for producing or reviewing them is published.
How DCB0129 relates to UK medical device regulation
Software can be both a health IT system under DCB0129 and a medical device regulated by the MHRA. The two regimes overlap but do not replace each other.
The MHRA guidance on software and AI as a medical device says many software products are regulated as medical devices and points developers to separate guidance on defining a product’s intended purpose. DTAC asks whether the MHRA classifies a product as a medical device and, if so, for the certificate and class. NHS England says DTAC is not intended to replace or be an alternative to medical device regulations, and its DTAC page says NHS England identified and removed elements in DTAC where there is overlap with the Medical Device Regulations.
On the risk management method itself, the April 2026 NHS England blog compares DCB standards with ISO 14971, which it says is globally recognised and referenced in European and UK regulations for medical devices. It says some activities, such as hazard identification, risk evaluation and documentation, can be used for both, but that DCB0129 introduces NHS-specific obligations such as the appointment of a CSO, and that completing both is not duplication.
The device rules are also changing. The MHRA’s implementation page for the future regulation of medical devices, updated on 12 March 2026, says new post-market surveillance requirements came into force on 16 June 2025, and that a further statutory instrument will follow in 2026 to introduce new pre-market requirements. It also says a consultation on indefinite recognition of CE-marked devices was open from 16 February to 10 April 2026. Suppliers of software devices should also note the MHRA’s annual registration fee deadline of 6 November, which The Healthcare Daily has reported.
The national review of DCB0129 and DCB0160
NHS England has been reviewing the standards since 2024. In its response to HSSIB, received on 6 November 2024, it said it had recently commenced work to review and modernise the Digital Clinical Safety Standards, DCB0129 and DCB0160, and listed the publication of the new DCB standards by autumn 2026 as an action, with NHS England’s chief clinical information officer as lead.
NHS England says it hosted 11 focus groups between January and July 2025 with manufacturers, health and care providers, clinical safety officers and industry experts. Its supporting paper gives the reasons for the review: accelerated digital transformation, newer technologies such as artificial intelligence, machine learning, ambient voice technologies and complex algorithmic systems that present novel risk profiles, a shift away from the traditional waterfall lifecycle model, care that relies on interconnected systems and cross-organisational data sharing, and new medical device regulations, cyber security requirements and data protection legislation.
According to the paper, all focus groups supported maintaining mandatory clinical risk management requirements, and a tiered model similar to medical device classification was widely supported. Participants supported updating terminology and reducing duplication between the standards, opposed removing existing themes, and concluded that no alternative existing standard could adequately replace the NHS-specific approach. They also called for stronger compliance tracking and clearer consequences for non-compliance.
The formal consultation on NHS England Engage opened on 29 June 2026 and closed on 11 September 2026. The page describes it as primarily a technical consultation for people with current experience or knowledge of the standards and lists suppliers as its audience. NHS England says it will analyse the survey responses and focus group insights and then publish a consultation response report setting out the proposed approach to revising the standards. It says some updates, such as revised guidance or templates, may come quickly, while others need longer-term work. As of 1 November 2026, the consultation page did not show a published response.

What it means for suppliers, trusts and investors
For suppliers, the immediate cost of DCB0129 compliance is people and paperwork: a registered clinician acting as CSO and a maintained hazard log and safety case for each product. The focus groups supported a tiered model similar to medical device classification and stronger compliance tracking; whether the revised standards adopt either is not yet known. AI and ambient voice technologies are among the categories the review paper names as presenting novel risk profiles. The Healthcare Daily has reported NHS buying in this area, including the Surrey and Borders NHS trust ambient voice AI contract with Accurx.
For trusts and integrated care boards, DCB0160 is the buyer’s own safety case. Large deployments such as electronic patient records and shared records, like the shared cardiology record launched by a Bristol NHS trust, depend on deployer-side hazard analysis of local configuration and workflow, which a supplier’s own safety file cannot provide. NHS England says future revisions of the standards are likely to use the must comply duty now in section 250.
For investors, the addition of relevant IT providers to section 250 by the Data (Use and Access) Act 2025 matters for diligence on UK health software businesses. A target’s clinical safety file, CSO arrangements and history of safety incidents are part of its regulatory exposure. The Healthcare Daily’s Suppliers Guide and digital health section cover the vendors affected.
What to watch next
As of November 2026, these are the points to track.
- The consultation response. NHS England has said it will publish a report on the summer 2026 consultation. Its HSSIB action plan set autumn 2026 for publishing the new standards.
- Use of the new powers. NHS England says future revisions are likely to use the enhanced powers, including the must comply duty and the extension to IT providers. Watch whether revised standards are issued under the Health and Social Care Information Standards (Procedure) Regulations 2025.
- A tiered model. Focus groups supported risk-based tiers similar to device classes. Whether the revised standards adopt this will decide how much documentation lower-risk tools need.
- DTAC changes. NHS England says it will update DTAC when the two standards change.
- Medical device reforms. The MHRA’s implementation page says a further statutory instrument introducing new pre-market requirements will follow in 2026.
Regulatory changes affecting health IT suppliers can also be followed in The Healthcare Daily’s Tracker.
Questions readers ask
What is DCB0129?
DCB0129 is the NHS information standard Clinical Risk Management: its Application in the Manufacture of Health IT Systems. Published under section 250 of the Health and Social Care Act 2012, it is designed to help manufacturers of health IT software evidence the clinical safety of their products. The current amendment, DCB0129 Amd 24/2018, took effect on 1 July 2018.
What is the difference between DCB0129 and DCB0160?
DCB0129 applies to manufacturers of health IT systems and covers how they manage clinical risk in building a product. DCB0160 applies to health and care organisations that deploy, use, maintain or decommission those systems. A manufacturer shares its DCB0129 clinical safety case report with the deploying organisation, which carries out its own DCB0160 risk assessment.
Is DCB0129 a legal requirement?
It is an information standard under section 250 of the Health and Social Care Act 2012. Since 7 July 2025, section 250 says persons to whom a standard applies must comply. NHS England says that, as the current standards stand, bodies must continue to have regard to them, with future revisions likely to use the enhanced powers. NHS England describes the standards as mandatory.
Who can be a Clinical Safety Officer?
NHS England's DTAC guidance says the Clinical Safety Officer must be a clinician with a current registration with a professional body. DCB standards require a CSO to be appointed. NHS England's DTAC page says the earlier requirement for the CSO to undertake NHS Digital training no longer stands under the form introduced in February 2026.
What documents does DCB0129 require?
According to NHS England sources, DCB0129 requires a hazard log and a clinical safety case report, and DTAC asks manufacturers to upload a risk management plan, the safety case report and the hazard log. The manufacturer must share the clinical safety case report with the deploying organisation.
Are DCB0129 and DCB0160 being replaced?
They are being reviewed rather than abolished. NHS England held 11 focus groups in 2025 and consulted from 29 June to 11 September 2026. Focus groups backed keeping mandatory requirements and modernising the standards. NHS England has said it will publish a consultation response report; as of 1 November 2026, none was shown on the consultation page.
Sources
Announced plans, figures and dates are as stated in the sources below at the time of publication and can change. Conclusions drawn from them are our reading.
- NHS Data Standards Directory: DCB0129 Clinical Risk Management, its Application in the Manufacture of Health IT Systems (Reference, dates, scope)
- NHS Data Standards Directory: DCB0160 Clinical Risk Management, its Application in the Deployment and Use of Health IT Systems (Reference, dates, scope, 2018 medical device extension)
- NHS Data Standards Directory: Information standards notice, DCB0160
- legislation.gov.uk: Health and Social Care Act 2012, section 250 (Revised text and amendment notes)
- legislation.gov.uk: Data (Use and Access) Act 2025, section 121 (In force 5 February 2026, S.I. 2026/82)
- legislation.gov.uk: Data (Use and Access) Act 2025, Schedule 15 (Paragraph 3 amends section 250)
- NHS England: National review of clinical risk management standards DCB0129 and DCB0160, supporting information (Legal context, history, focus groups, next steps)
- NHS England Engage: National review of clinical risk management standards DCB0129 and DCB0160 (Consultation dates)
- HSSIB: Safety recommendations log, workforce and patient safety (NHS England response) (Response received 6 November 2024)
- AI and Digital Regulations Service: DCB standards vs ISO 14971, what healthcare IT deployers in England need to know (NHS England blog, 7 April 2026)
- AI and Digital Regulations Service: Complying with NHS Digital clinical risk management standards (Reviewed 12 January 2023)
- NHS England Transformation Directorate: Digital Technology Assessment Criteria (DTAC)
- NHS England Transformation Directorate: DTAC assessed section (Clinical safety questions)
- GOV.UK (MHRA): Implementation of the future regulation of medical devices (Updated 12 March 2026)
- GOV.UK (MHRA): Software and artificial intelligence (AI) as a medical device
Follow The Healthcare Daily on Google News
New stories appear where you already read the news.
The Healthcare Daily. We report from primary sources and list them on every story.


