> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assuric.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Clinical Safety FAQ

> Quick answers to the things customers ask us most.

## Hazard log

<AccordionGroup>
  <Accordion title="How should I split hazard logs across products, variants, versions and shared features?">
    Keep one central set of hazards and link each to every product it applies to.

    * A shared hazard is one record, so editing it updates every linked product.
    * Each product's log is still versioned, exported and published on its own.
    * Add a variant or older release as a separate product, link the shared hazards, and add the extra hazards only there.

    See [Create a hazard](/clinical-safety/hazard-log).
  </Accordion>

  <Accordion title="Can I import our existing hazard log?">
    Yes, through Claude, ChatGPT or another AI assistant connected with the Assuric MCP Server with *Editor* access.

    1. Give it your Excel or CSV hazard log.
    2. Approve each change before it's written.
    3. Check the entries, including the risk scores, since a spreadsheet's scale may not match yours.

    See [Connect an AI assistant with the Assuric MCP Server](/integrations/mcp-server#work-in-your-hazard-log) and [Risk scales and thresholds](/clinical-safety/risk-scales-and-thresholds).
  </Accordion>

  <Accordion title="Can I click through an existing hazard just to look, without changing anything?">
    Be careful: clicking through an existing hazard can save changes to it. Open a record only when you intend to work on it. See [Create a hazard](/clinical-safety/hazard-log).
  </Accordion>

  <Accordion title="When and how are hazards risk-scored?">
    After you've identified the hazard and its causes. Score **Initial Risk** with its existing controls, then **Residual Risk** after any additional controls. From an *Undesirable* residual rating (3 on the default matrix), you also need to justify the risk. See [Create a hazard](/clinical-safety/hazard-log) and [Risk scales and thresholds](/clinical-safety/risk-scales-and-thresholds).
  </Accordion>

  <Accordion title="Can I use a different risk matrix, and should operational risks go in the hazard log or the risk register?">
    No: the hazard log uses one rating method across your workspace.

    * It's the DCB0129 matrix by default.
    * Only Assuric can switch your workspace to multiply likelihood by severity, or to one of a few organisation-specific scales.
    * Put operational and information security risks in the risk register, which has its own scoring.

    See [Risk scales and thresholds](/clinical-safety/risk-scales-and-thresholds) and [Risk register](/privacy-security/risk-register).
  </Accordion>

  <Accordion title="Does a high residual risk score need extra sign-off?">
    It needs a written justification. From an *Undesirable* residual rating (3 on the default matrix), *Residual Risk Justification* is required and Assuric asks you to confirm the risk is as low as reasonably practicable (ALARP). The hazard won't save without it. See [Risk scales and thresholds](/clinical-safety/risk-scales-and-thresholds#what-happens-at-3-and-above).
  </Accordion>

  <Accordion title="How do I attach and manage evidence on controls?">
    Evidence attaches to controls, not hazards, and can be a file, link, note or a document already in Assuric. Each item is stored once and can be linked to several controls, so replacing it updates them all. See [Causes, controls and evidence](/clinical-safety/causes-and-controls#evidence).
  </Accordion>

  <Accordion title="If I copy a cause instead of linking it, does editing it later affect the original?">
    No. Copy takes the text only, giving you an independent cause or control. Link connects to the original, so editing it anywhere changes it everywhere. See [Causes, controls and evidence](/clinical-safety/causes-and-controls#copy-or-link).
  </Accordion>

  <Accordion title="What happens if I delete a linked cause or control?">
    It's deleted everywhere it's used, with its evidence. Check its **References** first, or archive it to keep it for audit. See [Manage hazards](/clinical-safety/managing-hazards#deleting-a-linked-cause-or-control).
  </Accordion>

  <Accordion title="Can I recover a deleted hazard or hazard log version?">
    No. Archive a hazard, cause or control you no longer need instead of deleting it. Archived items stay available for audit, and the *Archived* filter brings them back into view. See [Manage hazards](/clinical-safety/managing-hazards) and [Approve and version your hazard log](/clinical-safety/hazard-log-approvals).
  </Accordion>

  <Accordion title="How does Assuric help me decide what is a hazard, cause or effect, and can the AI suggest hazards?">
    That's your clinical judgement. The **New Hazard** form can suggest hazards and harms from your product description. The Hazard Log Assistant in Ask Assuric drafts a hazard, cause and control from a plain-English description. See [Manage your hazard log with AI](/clinical-safety/hazard-log-with-ai).
  </Accordion>

  <Accordion title="Can AI just write my hazard log for me?">
    No. Neither the suggestions nor the assistant's drafts can tell you which hazards apply in your product's clinical context. Treat every suggestion as a draft for your clinical safety team to review. See [Manage your hazard log with AI](/clinical-safety/hazard-log-with-ai).
  </Accordion>

  <Accordion title="How does hazard log versioning and approval work?">
    A version is a named snapshot you approve, with a version number, title and summary of changes. The live log keeps changing as you edit, so a change after approval needs a new approved version. See [Approve and version your hazard log](/clinical-safety/hazard-log-approvals).
  </Accordion>

  <Accordion title="What does the hazard log export look like, and does it follow the NHS template?">
    Yes. An approved version downloads as an Excel workbook that has the hazard log in the NHS hazard log template layout, as well as in Assuric's own layout. Send an approved version rather than the working log, or publish it and share the link. See [Export a hazard log](/clinical-safety/exporting-a-hazard-log).
  </Accordion>

  <Accordion title="How do I share a hazard log with customers, deployers or meeting attendees?">
    Approve a version of the product's hazard log, then publish it.

    * You get one link for the bundle, with a Trust Centre view and spreadsheet download for each product.
    * Republishing keeps the same link and shows the latest version.
    * For a review meeting, publish the version you'll discuss and share the link in advance.

    See [Share and publish your hazard log](/clinical-safety/sharing-and-publishing).
  </Accordion>

  <Accordion title="Are customers notified when a published document is updated?">
    Only when you send a notification, using **Send Notification** on a published Trust Centre resource. You need a privacy notice URL on your Trust Page first. Approving a new version with the resource ticked under *Republish options* moves the published copy to it automatically. See [Notify stakeholders of updates](/trust-centre/updates-and-notifications).
  </Accordion>
</AccordionGroup>

## Incidents

<AccordionGroup>
  <Accordion title="How do incidents work, and how do they get reported?">
    Clinical and security incidents share one incident log. You add them in Assuric or [import them from incident.io](/clinical-safety/importing-incidents). Staff report through the staff portal, anonymously if you allow it. Anyone can report through your Trust Centre if you switch it on. See [Set up incident reporting](/clinical-safety/reporting-an-incident) and [Manage your incident log](/clinical-safety/managing-incidents).
  </Accordion>

  <Accordion title="How do incidents link back to the hazard log?">
    A clinical incident links to the hazard it relates to, and a security incident to a risk in the Privacy & Security risk register. See [Link the incident](/clinical-safety/incidents#link-the-incident).
  </Accordion>

  <Accordion title="Does Assuric integrate with incident systems such as incident.io or PSIRF?">
    Assuric imports incidents from incident.io into your incident log. There's no PSIRF integration. See [Import incidents from incident.io](/clinical-safety/importing-incidents).
  </Accordion>

  <Accordion title="Are incident statuses customisable, like hazard and control statuses are?">
    Yes. You define your own statuses for hazards and controls, and you can create and reorder incident statuses too. See [Set up hazard IDs and statuses](/clinical-safety/hazard-ids-and-statuses#statuses) and [Manage your incident log](/clinical-safety/managing-incidents#statuses).
  </Accordion>
</AccordionGroup>

## Clinical documentation

<AccordionGroup>
  <Accordion title="How do hazard log tables and scores get into the safety case report?">
    Through live tables. In a clinical document, insert a **Hazard Log Summary** or a **Hazard Risk Summary Table** and filter it by product, status or undesirable risk.

    * It keeps up with the hazard log, and each approved version keeps the rows it had at sign-off.
    * Set *Filter by Products* on the table so it shows only the hazards for the product you choose.

    See [The live hazard log table](/clinical-safety/clinical-documentation#the-live-hazard-log-table) and [Configure a live table](/documents/placeholders#configure-a-live-table).
  </Accordion>
</AccordionGroup>

## Related articles

<Columns cols={2}>
  <Card title="Clinical Safety: Overview" icon="clipboard-plus" href="/clinical-safety/key-capabilities">
    The hazard log, the incident log and your clinical documentation.
  </Card>

  <Card title="Share and publish your hazard log" icon="globe" href="/clinical-safety/sharing-and-publishing">
    Give customers a link to your latest hazard logs.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.