Every clinical incident in one place
Keep a complete log of clinical incidents, with each one’s status, severity, investigation and outcome visible at a glance, from first report through to closure.

One place to log, investigate and resolve clinical incidents, linked to the relevant hazards, controls and releases.

Trusted byclinical safety teams
Features
Keep a complete log of clinical incidents, with each one’s status, severity, investigation and outcome visible at a glance, from first report through to closure.

Staff can report incidents through the Staff Portal, external stakeholders through your Trust Centre, and AI assistants such as Claude or ChatGPT through the Assuric MCP. New reports trigger notifications by email, in-app and in Slack, so the right people can act straight away.

Investigate each incident to the right standard, record root cause analysis, and assess whether it meets any relevant reporting threshold (such as MHRA).

Link an incident to the hazards it affects in your hazard log, or add a new hazard straight from the incident, so every investigation feeds back into your clinical risk and keeps it current.

Incidents sync automatically from tools such as incident.io and our other integrations, logged against the relevant hazards and controls rather than sitting in a separate system.

Generate incident reports in a few clicks, and let automation pull incident data into your audits and reviews, so trends and actions are ready when you need them.

Benefits
Any event involving your product that affected, or could have affected, patient care, whether or not harm actually occurred. That includes software faults, but also misuse, human error, and workflow or configuration issues. If you are unsure, log it and triage it alongside your clinical safety officer.
An incident is an event that affected, or could have affected, patient safety. A complaint is someone’s expression of dissatisfaction. One event can be both, and Assuric lets you manage incidents and complaints in the same place.
Yes. DCB0129 and DCB0160 both expect you to monitor your product once it’s deployed (post-deployment monitoring) and feed safety incidents back into your clinical risk management.
Only if the incident meets the MHRA reporting threshold, which depends on severity and on whether your product is a registered medical device. Incidents that fall below it still belong in your record for post-market surveillance, and Assuric records each decision and its reasoning so it can be reviewed when needed.
Staff can report through the Staff Portal, external stakeholders through your Trust Centre, and AI assistants through the Assuric MCP. Incidents can also be imported automatically from tools such as incident.io through our integrations. New reports trigger notifications by email, in-app and in Slack, so the right people can act straight away.
Your internal team, alongside your clinical safety officer. They look at the impact of the incident, record the root cause and agree corrective actions or controls to prevent it happening again, with any affected hazards updated in your hazard log.
No. The main purpose of the incident log is to show that every incident is logged, investigated and acted on in line with the DCB standards. An empty log is more likely to raise questions than a full one.
See how Assuric can help you manage your incidents, investigations, hazards and more, all in one place.