A Clinical Safety Officer (CSO) needs more than a title on an organisation chart. The person must be able to oversee clinical risk management for the particular system and clinical context, challenge weak evidence and remain involved when that system changes. NHS England's developer guidance says software builders need to nominate or hire a CSO; its CSO training module addresses eligibility, responsibilities, oversight and independence.
Five checks when appointing a CSO
Clinical standing. Check the person's current professional registration and whether their clinical experience fits the patients and workflow affected by the product.
Risk-management competence. Ask how they identify hazards, judge controls and review evidence under the applicable standard. Training can support competence, but a course certificate alone cannot demonstrate experience with every product or deployment.
Defined scope and authority. Put the appointment in writing. State which product, release or deployment they oversee; what they review and approve; how concerns are escalated; and who makes organisational release or risk-acceptance decisions.
Time and independence. Allow enough time to join the work while design decisions can still change. A final signature on a document prepared without clinical challenge is a weak control.
Continuity. Plan who reviews significant releases, incidents and changes in clinical use, and how the hazard log and safety case are kept current if the CSO leaves.
Is a specific NHS course mandatory?
Do not rely on an old blanket statement about a particular course. NHS England's current DTAC assessment guidance says the previous DTAC form's requirement for the named CSO to undertake NHS England-provided training no longer stands. That change does not remove the need to demonstrate suitable competence for the role. NHS England continues to provide digital clinical safety training.
Can the role be external?
An organisation may appoint an appropriately suitable external CSO within a clear agreement. It still needs to provide access to the product, people and evidence needed for meaningful oversight. Outsourcing a role does not make the manufacturer's or deploying organisation's own responsibilities disappear. Confirm the individual's remit, availability, independence and appropriate cover before relying on the arrangement.
Our Clinical Safety Officer guide explains the role in more detail. Assurance AI's current service scope distinguishes documentation support from a formal CSO appointment. We work in support of your appointed CSO and do not act as your CSO unless formal competence, appointment and cover arrangements have been established and recorded in writing.
Primary sources
- Clinical safety — introduction to healthcare technology(opens in a new tab)
NHS England
- Clinical risk management training: curriculum level 3, module 3.1(opens in a new tab)
NHS England
- Conduct a DTAC assessment(opens in a new tab)
NHS England
- Clinical risk management training(opens in a new tab)
NHS England