NHS customers ask for your safety case and hazard log before they use your product. Naq sets up the work for you and keeps your hazard log under review.
DCB0129 with Naq, a three-minute walkthrough of the product · Narrated, with captions
DCB0129 is the NHS clinical safety standard for companies that make health software. There is no certificate: you show your safety case and hazard log.
For every company whose health software is used in the NHS in England.
Your Clinical Safety Officer must be a registered clinician, and approves your safety case and hazard log.
You keep monitoring safety once your product is in use, not only before it.
This is everything DCB0129 asks of you. For each step, here is what you do and what Naq does.
Create a DCB0129 instance on your product's scope.
Maps it for you: 24 requirements, linked to 11 ready-made controls.
In People, give the Clinical Safety Officer role to a registered clinician.
Links the role to the controls that ask for it.
Fill in your details, then approve the plan.
Gives you 13 ready-written templates, such as your Clinical Risk Management Plan and Clinical Safety Case Report.
Log each hazard to patients, such as a booking made for the wrong patient, and link the controls that reduce it.
Keeps the risk rating before and after your controls, for every hazard, in one hazard log.
Your Clinical Safety Officer approves each version of the hazard log.
Checks it every night, and flags it for review if a hazard changes after approval.
Log each clinical safety incident, resolve it, and write down what you learned.
Keeps the type, severity and owner of every incident, with the lessons learned.
Naq links your hazard log to the right controls and checks it every night. A hazard that changes after approval is flagged for your Clinical Safety Officer.
Register · linked by Naq
Real checks from a DCB0129 control in Naq. The results shown are illustrative.
Publish your clinical safety controls and documents on your own Trust Centre. NHS customers answer their own questions before they ask you.
They see your clinical safety controls.
For example your Clinical Safety Case Report, with their name and the reason they need it.
Naq emails them a link straight away.
Mapped to DCB0129, version 5.0.
And 2 more.
And 4 more.
Every document you link as evidence is also checked automatically: its current version must be approved, staff acknowledgements must be complete, and its review date must not have passed.
Built from the Naq control library for DCB0129.
See the six steps in your own workspace, with your own product.
