Technology AI

Do you need a Clinical Safety Officer?

When a GP surgery, dental practice or clinic needs a Clinical Safety Officer for DCB0160, who can do it, and how to share one across a PCN.

Ava research teamPublished 6 min read

On this page
  1. What a Clinical Safety Officer does
  2. When you need one
  3. Who can be a CSO
  4. Your options
  5. Sharing a CSO across a PCN
  6. Why AI makes the role more important
  7. What the work looks like over a year
  8. Signs your practice is missing clinical safety work
  9. Questions to ask an external CSO
  10. The standards are being reviewed
  11. Dental practices and private clinics
  12. Example: a PCN that shared the load
  13. Frequently asked questions
  14. References

Key takeaways

  • A Clinical Safety Officer reviews risks of digital systems, makes sure they are managed before deployment and gives clinical sign-off[1].
  • At present a CSO must be a registered health or care professional[1]; most small practices share one rather than train their own.
  • New clinical systems, AI scribes, triage tools and some telephony changes are typical triggers for DCB0160 work.
  • The standards are under national review, partly because of AI[1], so check current requirements before you plan.

What a Clinical Safety Officer does

NHS England describes clinical safety officers as responsible for making sure that digital systems used in health and care are safe for patients: they review potential risks, ensure these are managed before systems are deployed and provide clinical sign-off that the technology can be used safely in practice[1]. The role sits within two mandatory standards. DCB0129 sets requirements for technology manufacturers, and DCB0160 covers how health and social care organisations deploy and use these systems safely[1].

In a practice, that means the CSO leads the clinical risk work whenever a health IT system is introduced or changed in a way that could affect patient care. They chair the hazard workshop, own the hazard log and sign the safety case report. They do not need to be a technology expert, but they do need training in clinical risk management and enough time to do the work properly.

Registered

a CSO must currently be a registered health or care professional, such as a registered clinician[1]

When you need one

Typical triggers for DCB0160 clinical risk work in a practice; check with your ICB for local expectations
ChangeDCB0160 work likely?Typical CSO involvement
New or replacement clinical systemYesFull safety case, often coordinated with the ICB
Ambient AI scribe or AI note toolYesHazard workshop, safety case, pilot review
Online consultation or triage toolYesSafety case focused on routing and urgent symptoms
Telephony with patient record lookup or call routing rulesOftenProportionate assessment of routing and lookup hazards
Document management or workflow toolOftenAssessment of misfiling and missed-action hazards
Office software with no patient dataNoNone
Configuration change in an existing system, such as new templatesSometimesProportionate review if it affects clinical decisions

The principle is proportion: the more a system could contribute to a clinical decision or a missed action, the more thorough the safety work. A simple phone menu change needs little; an AI tool that drafts clinical notes needs a full safety case.

Who can be a CSO

At the moment a CSO must be a registered health or care professional, for example a registered clinician or social worker[1]. In general practice that is usually a GP, nurse, pharmacist or other registered clinician who has completed clinical safety training. Being registered is not enough on its own: the CSO needs to understand hazard identification, risk assessment and the documentation the standards require.

  • Training: a recognised clinical safety officer course, followed by supervised experience on a real deployment.
  • Time: protected sessions for each project, not work squeezed between clinics.
  • Independence: enough distance from the purchase decision to say no if risks are not controlled.
  • Support: access to an experienced CSO for advice, often at ICB level.

Your options

Ways for a practice to access Clinical Safety Officer support
OptionWorks well whenWatch out for
Train a clinician in the practiceLarger practices with frequent digital changesTime away from clinics; skills fade if rarely used
Share a CSO across the PCNPractices adopting the same tools at the same timeClear agreement on hours, priorities and sign-off
Use the ICB's clinical safety teamICB-procured systems and national programmesCapacity; local tools may not be covered
Commission an external CSOOne-off projects or private clinics without NHS supportCost; make sure they understand your setting
Rely on the supplier's CSONever on its ownThe supplier covers DCB0129; your deployment needs its own DCB0160 sign-off

Sharing a CSO across a PCN

  1. Agree the need

    List the digital changes planned across member practices for the next year. Shared tools are the strongest case for a shared CSO.

  2. Choose and train

    Identify a registered clinician willing to take the role, fund the training and agree protected time.

  3. Write a short agreement

    Cover hours, how requests are prioritised, who signs off for each practice and what happens if the CSO leaves.

  4. Standardise templates

    Use one clinical risk management plan template and one hazard log format across the PCN.

  5. Report regularly

    The CSO reports to the PCN board on projects completed, open risks and incidents.

A shared CSO does not remove each practice's responsibility. Each practice still needs to accept the safety case for its own deployment.

Why AI makes the role more important

The spread of AI tools has raised the stakes. In 2025, 28% of GPs said they currently use AI tools in clinical practice[2], and 11% of all GPs use tools they obtained independently[3]. Use is higher in England than in Scotland or Northern Ireland[4]. The 10 Year Health Plan commits to rolling out ambient voice technology and digital triage to cut clinical admin within two years[5], so most practices will face a safety case for an AI tool soon.

GPs using AI tools in clinical practice, by UK nationNuffield Trust and RCGP survey, 2025
GPs using AI tools in clinical practice, by UK nationColumn chart. England: 31%; Scotland: 20%; Northern Ireland: 9%.0%10%20%30%40%England: 31%31%EnglandScotland: 20%20%ScotlandNorthern Ireland: 9%9%Northern IrelandGPs using AI tools in clinical practice, by UK nationColumn chart. England: 31%; Scotland: 20%; Northern Ireland: 9%.0%10%20%30%40%England: 31%31%EnglandScotland: 20%20%ScotlandNorthern Ireland: 9%9%NorthernIreland

Source: Nuffield Trust, 2025[4]

Show the data
ItemValue
England31%
Scotland20%
Northern Ireland9%

Regulation adds another reason. The MHRA says many software and AI products used in health and social care are regulated as medical devices[6], and its July 2026 guidance on ambient voice technology asks organisations to identify and review any change in a product's functionality that may alter its regulatory status[7]. Someone needs to watch for that, and the CSO is well placed to do it.

What the work looks like over a year

For a typical practice the CSO role is not full time. It comes in bursts around projects, with a steady background of reviews. A realistic year might include:

  • One or two full safety cases for significant new systems, each needing a hazard workshop, drafting, review and sign-off.
  • Several smaller assessments for configuration changes, new integrations or supplier updates.
  • Quarterly review of open hazard logs, adding incidents and near misses found in audits.
  • Input to significant event reviews where a digital system played a part.
  • Keeping training current and attending ICB or PCN clinical safety meetings.

Agree time in advance for each project. Safety work that is squeezed into the week before go-live tends to become a paperwork exercise rather than a genuine look at risk.

Signs your practice is missing clinical safety work

  • Nobody can name who signed off the last new system the practice introduced.
  • Clinicians use tools that the practice manager did not know about, including free AI apps on personal phones.
  • Supplier updates are accepted automatically with no one checking what changed.
  • Incidents involving digital systems are logged as "IT problems" and never reach a clinical lead.
  • Safety documents exist but have not been opened since the system went live.

If two or more of these sound familiar, start with a simple register of every clinical system and digital tool in use, who owns it and whether a safety case exists. That register is the CSO's starting point.

Questions to ask an external CSO

  1. Which professional register are you on, and what clinical safety training have you completed?
  2. How many DCB0160 deployments have you led in general practice, dental or similar settings?
  3. Will you run the hazard workshop with our team, or work only from documents?
  4. What will we receive at the end: plan, hazard log, safety case report, and in what format?
  5. How do you handle reviews after go-live and changes to the product?
  6. Do you have any commercial relationship with the supplier whose product we are assessing?

The standards are being reviewed

NHS England is running a national review of DCB0129 and DCB0160, saying the revised standards must reflect advances such as AI supporting clinical decisions, interconnected systems and voice recognition[1]. The consultation asks whether the CSO requirement should remain, whether the role needs further definition and whether experienced non-registered professionals should have alternative routes to become CSOs[1]. Until any changes are published, plan on the current requirements.

Dental practices and private clinics

Practices delivering NHS services should assume DCB0160 applies to the systems they deploy. Private-only clinics should check their position with their adviser; many follow the same approach anyway, because a structured clinical risk assessment is good evidence of safe practice for regulators, insurers and patients. For a small clinic, an external CSO for a short project is often enough. Dental practices adopting AI charting, imaging analysis or new practice management systems should pay particular attention to tools that suggest findings, because those are the features most likely to be regulated as medical devices.

Example: a PCN that shared the load

Example: a fictional PCN of five practices planned to adopt an online triage tool and an AI scribe in the same year. Instead of each practice finding its own CSO, the PCN funded training for a pharmacist and a GP, gave them two sessions a month each, and used one set of templates. The hazard log for the triage tool was written once and adapted for each practice, and the AI scribe pilot was run in two practices before the others joined.

Frequently asked questions

Does every practice need its own Clinical Safety Officer?

Not necessarily. Many share a CSO through the PCN or use ICB support. Each practice still needs a signed-off safety case for its own deployment.

Can a practice manager be the CSO?

Only if they are a registered health or care professional. At present a CSO must be registered[1], although the national review is asking whether that should change.

Is the supplier's safety case enough?

No. The supplier covers DCB0129 for the product. DCB0160 covers how your organisation deploys and uses it[1].

Do we need a CSO for a new phone system?

Often a proportionate assessment is enough, focused on routing, patient lookup and urgent-call handling. Ask your ICB what it expects.

References

  1. NHS England (2026). National review of clinical risk management standards DCB0129 and DCB0160: consultation questions (opens in a new tab) ↑

  2. Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑

  3. Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑

  4. Nuffield Trust (2025). How are GPs using AI? Insights from the front line (opens in a new tab) ↑

  5. GOV.UK (Department of Health and Social Care) (2025). Fit for the future: 10 Year Health Plan for England (opens in a new tab) ↑

  6. GOV.UK (Medicines and Healthcare products Regulatory Agency) (2025). Software and artificial intelligence (AI) as a medical device (opens in a new tab) ↑

  7. GOV.UK (Medicines and Healthcare products Regulatory Agency) (2026). MHRA clarifies regulatory status of ambient voice technologies used in the NHS (opens in a new tab) ↑

Book a demo

See Ava handle your calls.

Book a short demo. We’ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo