FAQ: What is DCB0129?

In an era of rapid digital transformation, healthcare technology plays a crucial role in improving patient outcomes and streamlining clinical operations. However, ensuring that health IT systems are safe for clinical use is vital. That’s where DCB0129 comes into play – a clinical safety standard created to help healthcare technology manufacturers effectively manage clinical risks. This blog will explore what DCB0129 entails, its importance for healthcare technology manufacturers and healthcare organisations as well as practical steps for manufacturers to achieve compliance.  

What is DCB0129?

DCB0129 is a clinical risk management standard issued by NHS England and the UK Department of Health & Social Care that requires all Health IT system manufacturers to assess and manage clinical risks throughout the lifecycle of their product(s). It mandates the implementation of a Clinical Risk Management System, including thorough documentation and evidence of risk management activities through a Clinical Safety Case Report (CSCR) and an up to date Hazard Log. This mandate also includes the appointment of a Clinical Safety Officer or CSO to be actively involved in risk management activities and approve the documentation, alongside “Top Management”  

Why is DCB0129 important?

DCB0129 is crucial because it ensures the safe implementation of digital health technologies within healthcare organisations. It provides a systematic approach to managing clinical safety risks, ensuring that digital systems, such as electronic patient records, comply with UK healthcare regulations. By adhering to DCB0129, healthcare organisations can proactively address potential risks, reduce patient harm, and improve clinical outcomes. This standard reinforces the importance of having a CSO involved in the development, deployment, and monitoring of healthcare IT systems.  

What are the benefits of DCB0129?

Organisations that embed and appoint a Clinical Safety Officer (CSO) often experience substantial benefits. By ensuring compliance with standards like DCB0129, CSOs help align operations with UK regulations, upcoming regulations such as the EU AI Act and compliance with NHS standards. This compliance mitigates legal risks while establishing a strong foundation of trust and accountability within healthcare software development. CSO’s help to implement proactive risk management processes throughout the software development lifecycle, ensuring that clinical risks are reduced to as low as reasonably practicable. Their ability to document and assess risks systematically allows organisations to reduce potential threats early on, contributing to safer clinical environments and improved patient safety. In addition to their risk management expertise, CSOs encourage collaboration and best practices across development teams. They help create a safety-first culture where all members work together efficiently and responsibly which is not dis-similar from establishing multi-disciplinary teams in clinical settings. By aligning risk management processes with the software development lifecycle, this has the double benefit of not only strengthening the overall development process but also leads to enhanced clinical outcomes within the organisation the technology is being deployed into.  By engaging CSOs and adhering to DCB0129 standards, organisations benefit from safer clinical practices, improved patient outcomes, and a culture of excellence in healthcare software development.  

Is DCB0129 needed for Medical Devices?

The DCB0129 standard initially focused on clinical risk management for health IT systems, and did not specifically include medical devices in its first version. The standard was first published in 2013 by NHS Digital, aiming to ensure patient safety by guiding the clinical risk management of health IT, including software used in healthcare. The scope of DCB0129 was later expanded with updates to incorporate a broader range of health technologies, including medical devices that incorporate software or are connected to health IT systems. These updates came with revisions to align the standard with evolving regulatory requirements and industry practices. The incorporation of medical devices became more explicit in later revisions, such as the 2018 update, which reflected changes in regulatory expectations around Software as a Medical Device (SaMD) and interoperability. DCB0129 compliance for medical devices shares many similarities with ISO 14971, as both standards place responsibility for risk management on senior management and require staff competence in the processes involved. Both also mandate the creation of a risk management plan, a risk assessment, and a report, following a similar approach to identifying, assessing, and controlling risks. If you’ve already developed a Risk Management File under ISO 14971, you’re likely close to meeting the DCB0129 requirements. However, it’s important to be aware of the key differences between the two standards, as failing to address these could result in issues during reviews by customers or regulators. For further information read our blog Expert Insights: How ISO 14971 helps to meet DCB0129 (and vice versa)  

How is DCB0129 assessed by the NHS?

For each individual implementation of healthcare IT, a Clinical Safety Officer in the NHS, must evaluate the DCB0129 documentation of the supplier. This is done in order to assess the latest version of the documentation and ensure that the supplier is acting in accordance with the standard. Once the NHS CSO has reviewed the DCB0129, they can begin developing their own DCB0160, the parallel standard required for organisations deploying technology. For more information on DCB0160, read our blog here.  

How to implement DCB0129 for Digital Health Manufacturers

For health IT manufacturers aiming to comply with DCB0129 standards, establishing a robust clinical risk management process is essential. Here are key considerations to ensure a successful implementation: Establish a Clinical Risk Management Group: Start by forming a clinical safety team that includes key stakeholders from various departments, such as clinical, technical, and regulatory. Secure Top Management Buy In: Engaging senior leadership early on is crucial. Ensuring top management understands the importance of clinical risk management and is committed to providing the necessary resources, including time and budget, to support the process is essential. Their buy-in will facilitate a smoother implementation and create the environment to support ongoing compliance. Conduct Training and Awareness Sessions: The CSO will often train the clinical safety team and relevant staff on the DCB0129 requirements and processes. This will help ensure the team is aware of the time, resources, and commitment needed to complete assessments, and understands their roles and responsibilities within the clinical risk management framework. Ensure Core Documents Are in Place: Before proceeding, verify that the technical team has the essential documentation ready, such as product specifications, user requirements, and any existing risk assessments. This documentation will form the basis for identifying, analysing, and mitigating potential hazards.  

The future of DCB0129

The Department of Health and Social Care (DHSC) has announced a review of clinical risk standards for digital health technologies, including DCB0129 and DCB0160, set to take place in 2024/25. This review will involve public consultation and engagement with stakeholders across the healthcare sector. The aim is to ensure that the standards evolve to meet the challenges posed by emerging technologies and continue to safeguard patient safety. Here at 8Fold,  we hope a key area of focus for the review is the inclusion of standards and frameworks for artificial intelligence in digital health. As AI driven solutions become more integrated into healthcare delivery, there is a growing need for specific guidance on managing the unique risks associated with these technologies. Additionally, we hope to see more of a flexible and scalable approach to clinical risk management, allowing the standards to be more easily applied across a broader range of digital health products, from software applications to complex, data driven algorithms. This could involve clearer guidelines for smaller manufacturers or low risk digital health solutions, ensuring that safety standards are both accessible and proportionate. The upcoming review represents an important opportunity to modernise the clinical risk management framework and align it with current technological trends, ensuring that standards like DCB0129 continue to protect patient safety as healthcare systems become increasingly digital. At 8fold, we’ll be staying close to these developments and reporting on them as we learn more.