Search Clinical Safety Officers
Browse independent CSOs who offer DCB0129/DCB0160 support across primary care, acute medicine, mental health, care technology, pharmacy and more. Look for the registration-checked badge.
How Csoportal works
One connected journey from finding a CSO to a reviewed, evidence-backed clinical safety case.
Describe your product
Tell us what your software does, the clinical context it operates in, and whether you need DCB0129, DCB0160 or both.
Find a Clinical Safety Officer
Search the independent directory by specialty, technology and standards experience. Compare profiles and submit an enquiry.
Manage the work in one place
Your CSO runs the engagement in the Csoportal workspace: hazard log, risk matrix, evidence and actions — with AI assistance throughout.
Review and sign off
The CSO reviews every AI-generated draft, makes the professional judgement and approves the clinical safety case. AI assists; the CSO decides.
DCB0129 vs DCB0160
The two NHS England clinical risk management standards that apply to health software suppliers — and how they fit together.
DCB0129
The standard your organisation operates to. It requires a documented clinical risk management system: a named CSO, a clinical safety management plan, hazard log processes, training records and organisational oversight of clinical risk across everything you deliver.
- Appoints and empowers a Clinical Safety Officer
- Maintains a clinical risk management file per organisation
- Trains staff in clinical risk management
DCB0160
The standard applied to each product. It requires clinical hazard identification, risk assessment and mitigation for the specific health IT system, culminating in a clinical safety case signed off by the CSO before deployment and maintained through change.
- Hazard log for the product
- Risk assessment with severity × likelihood scoring
- Clinical safety case signed by the CSO
The Clinical Safety Workspace
Everything a CSO needs to run DCB0129/DCB0160 work properly — in one place, structured for audit.
Projects
One workspace per product or deployment, with status tracking from setup to sign-off.
Hazard log
Structured DCB0160-style hazard logging: causes, consequences, controls and residual risk.
Configurable risk matrix
A 5×5 matrix by default — with the methodology stored as data so it can match your organisation's approach.
Evidence library
Upload UAT results, workflows, training packs and testing records, linked directly to hazards.
Action tracking
Actions raised from hazards, with owners, priorities and overdue highlighting.
Safety case workspace
Draft and refine a structured clinical safety case, ready for CSO review and export.
The AI Clinical Safety Assistant
Describe your product — the assistant suggests clinically plausible hazards, possible causes, potential consequences and candidate controls. It spots gaps in your hazard log, flags missing evidence, and drafts safety case sections for the CSO to refine.
What it never does is make the decision. The AI does not approve hazards, accept residual risk, declare ALARP or sign off a safety case. Every suggestion carries the same label: “AI-generated suggestion. Clinical Safety Officer review required.”
- Suggest hazards from a product description
- Analyse workflows for failure points
- Propose causes, consequences and controls
- Identify missing evidence and log gaps
- Draft safety case sections for CSO review
CSO input
Our system allows care-home nurses to submit requests to GPs.
Potential hazard
Request submitted against the wrong resident.
Possible cause
Incorrect patient selection.
Potential clinical consequence
Incorrect treatment or medication change.
Suggested controls
Patient identity verification and confirmation before submission.
For digital health companies
Find the right CSO fast
Search an independent directory by clinical specialty, technology and standards experience — no more cold outreach.
Support your procurement documents
A structured DCB0129/DCB0160 evidence trail to draw on when NHS and ICB buyers ask for clinical safety documentation. Your Clinical Safety Officer remains responsible for the content.
See the work as it happens
When your CSO works in Csoportal, hazard logs, evidence and actions live in a structured workspace — not email threads.
Independent and credible
A directory that endorses no one, run by a platform that is not an NHS service.
For Clinical Safety Officers
Win enquiries
A free professional profile in a directory that health-tech companies actually search.
Run projects properly
Structured hazard logs, a configurable risk matrix, evidence library and action tracking — built for DCB0129/DCB0160 rather than generic project tools.
Work faster with AI
Draft hazard suggestions, gap analysis and safety-case sections that you review and approve on your terms.
Stay audit-ready
Every scoring decision captured, every AI draft labelled, every safety case versioned.
Featured Clinical Safety Officers
Independent clinicians available for DCB0129/DCB0160 work. Csoportal does not endorse individual CSOs — assess suitability yourself before engaging.
Awais Iqbal
Clinical Safety Officer
Founder and AI Developer . healt Tech Enthusiast
Are you a Clinical Safety Officer?
Create a free professional profile, receive enquiries from digital health companies, and upgrade to the full clinical safety workspace when you are ready.
Frequently asked questions
What is a Clinical Safety Officer (CSO)?
A CSO is a suitably experienced clinician responsible for clinical risk management when health software is developed or deployed. Under the NHS Digital standards DCB0129 (organisation level) and DCB0160 (product level), health IT suppliers are expected to have a CSO leading hazard logging, risk assessment and the clinical safety case.
Do I need DCB0129, DCB0160 or both?
DCB0129 applies at the organisation level — the clinical risk management system your company operates. DCB0160 applies at the product level — the clinical risk management of a specific health IT product. Most suppliers building clinical software need both. If you are unsure, submit an enquiry and a CSO will help you work it out.
Is Csoportal part of the NHS?
No. Csoportal is an independent platform. It is not an NHS service, it is not an NHS directory, and it does not claim NHS endorsement. The standards referenced (DCB0129/DCB0160) are published by NHS England and freely applicable to any organisation.
How does the AI assistant work?
The AI assistant suggests hazards, causes, consequences, controls and evidence gaps based on your project data. Every output is labelled as an AI-generated suggestion requiring CSO review. The AI never approves risk, declares ALARP, or signs a safety case — those judgements always rest with the CSO.
Does the AI replace my CSO?
No — deliberately. The platform's design principle is that AI assists the CSO; it does not act as the CSO. Clinical safety accountability under DCB0129/DCB0160 requires a named, qualified human being, and the workspace is built around that.
Is my data safe?
The platform uses role-based access control, project-level permissions, audit logging and private storage. It is designed so patient-identifiable information is not uploaded: the workspace displays a standing warning against uploading clinical records. GDPR compliance depends on deployment configuration, contracts and operational processes.