Technology in healthcare is moving at pace - so how do we implement this technology safely and responsibly? This was something really important that we at Accurx recognised, and in addition appreciated the support that GP practices would require. For new technology to be adopted safely and responsibly, not only do practice staff need to feel supported, but they need to have confidence in the implementation. To bridge this gap we partnered with Assuric to train over 80 staff members as clinical safety officers (CSOs) and do a deep dive into the DCB0160 standards.
Why the CSO role is critical now
As software becomes a core clinical component—through Electronic Health Records and Ambient Voice Technologies like Scribe—the CSO role has evolved. It’s no longer a compliance exercise or a role “on the side” of someone’s day job. The CSO now sits at the intersection of technology, clinical reality, and patient safety. They are the translators between how software should work and how it actually behaves in the messy, high-pressure environment of real clinical care.
That reality shaped how we approached the training.
Designing the training: From theory to practice
One of our earliest decisions was that this training couldn’t be overly theoretical. Many attendees were already deeply experienced clinicians. What they needed wasn’t just the what of DCB0160—but the how of applying it meaningfully in their day-to-day work.
We focused the structure of the sessions to:
- Build a strong foundation in the standard and its intent
- Rapidly move into practical tools and lived scenarios
- Create space for discussion, challenge, and shared learning
Rather than presenting safety as a static set of documents, we framed it as an ongoing mindset—one that evolves alongside products, teams, and clinical contexts.
We build the training to be 2-part - a theoretical e-learning module to build foundations and a facilitated live group session really focused on building on the foundations with real life experiences and practical exercises mimicking how CSOs should support the process in practice.
What surprised us
One of the biggest surprises was how energised people felt once safety was demystified.
There’s a common assumption that clinical risk management is daunting or restrictive. But once participants engaged with techniques like SWIFT (Structured What If), many described it as empowering and a way to proactively surface risks they already intuitively worried about, but didn’t always have the language or structure to articulate.
Another unexpected insight was how much value came from cross-disciplinary discussion. Everyone who attended each spotted different risks in the same scenarios tabled. That diversity of perspective reinforced a key lesson: good safety work is rarely done in isolation.
Key insights from the sessions
Identifying the “what ifs”Using the SWIFT technique, participants practiced mapping clinical processes and deliberately asking, “What could go wrong here?” This helped surface subtle but critical risks—especially those that sit at the boundary between user behaviour and system design.
Making the 3-document standard practicalWe focused heavily on making the Clinical Risk Management File (CRMF) feel usable rather than burdensome. By breaking down the Safety Case Report, Hazard Log, and Risk Management Plan into practical templates and examples, attendees could see how these documents actively support safer decision-making—not just audits.
Grounding safety in real-world scenariosSome of the richest conversations came from exploring real-world issues that were supported by our clinical facilitators. Exploring case examples that were seen regularly created confidence in how tools could be used differently in clinical settings under pressure. These discussions reinforced that safety risks are rarely abstract — they emerge from everyday workflows.
What we heard from attendees
Feedback from participants highlighted a shift in confidence. Many shared that they now felt better equipped to:
- Challenge assumptions earlier in product development
- Ask clearer, more structured safety questions
- Engage more confidently with regulators and external partners
Perhaps most encouraging was hearing people describe safety as something they now felt ownership over, rather than something “owned” by a single role or team.
Supporting ongoing safety, not one-off training
We ended the training by providing practical ongoing CSO support. Our reflection was that for our family of CSOs, this was essential. Safety isn’t a one-time certification — it’s a continuous practice that evolves as products, users, and risks change.
We are passionate about supporting the future of clinical safety, so as well as looking at how we continue to support CSO training going forward, we are rolling out the following resources for all clinicians across the NHS:
- A CSO WhatsApp Group - to share best practices and ask questions amongst peers to provide support to our CSO family.
- Providing dedicated clinical governance drop in sessions with an Accurx clinician to discuss and answer any relevant questions.
- Exemplifying the Accurx Trust Centre as a central hub for DCB0129 documentation, Hazard Logs, DPIA templates, and more, ensuring that we provide simplicity and facilitation at every touchpoint.
Final reflection
Delivering this training reinforced something we strongly believe at Accurx: when people are given the right tools, structure, and support, safety becomes a shared ambition rather than a checkbox.
And ultimately, that’s how safer digital healthcare is built — not through standards alone, but through people who feel confident, curious, and committed to doing the right thing.