> ## 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. # Create an incident > Record a clinical or security incident, fill in its details and link it to the hazard or risk it relates to. **Quick summary** * **New Incident** opens a dialog to start an incident; the *Incident Details* sheet then holds its record. * What you tick under *Clinical Incident* and *Data Security Incident* decides where an incident appears: **Clinical Safety**, **Privacy & Security** or both. * Fill in *Outcomes* and *Lessons Learned* before closing an incident: assessors read them first. Incidents also arrive by [import from incident.io](/clinical-safety/importing-incidents) and by [staff and Trust Centre reports](/clinical-safety/reporting-an-incident). ## Create the incident Click **Clinical Safety → Incidents** or **Privacy & Security → Incidents**, then click **New Incident**. Fill in the *Add New Incident* dialog. The Add New Incident dialog showing Incident ID, Incident Date, Reported By, Incident Title, Summary, Initial Actions Taken, Cause(s) and Severity Tick *Clinical Incident*, *Data Security Incident* or both, to decide where the incident appears. Both start unticked, whichever log you came from. Then click **New Incident** to open the *Incident Details* sheet. ### Fields in the dialog | Field | What to enter | | - | - | | *Incident ID* | Assuric suggests the next ID, such as `INC-018`, which you can change if needed. | | *Report anonymously* | Tick it to leave out who reported it. | | *Reporting on behalf of a 3rd party* | Tick it if someone outside your team told you about it, then say who in *Third Party Details*. | | *Cause(s)* | Pick an existing cause, or click **Create New**: your common causes show up in the **Incident Causes** tile. | | *Severity* | Hover over a level, such as *Minor* or *Critical*, to read what it means, or click **Create New** to add your own. | ## Complete the record The *Incident Details* sheet has 5 sections: **Incident Information**, **Clinical Details**, **Data Security Details**, **Investigation & Response** and **Additional Information**. To reopen it later, click **...** on the incident's row, then **Edit**. The Incident Details sheet showing Incident Information fields and the Clinical Incident and Data Security Incident ticks Fill in the sections that apply. *Root Cause Analysis*, *Outcomes* and *Lessons Learned* go in **Investigation & Response**, and assessors read *Outcomes* and *Lessons Learned* first, so complete them before closing. Update *Status* as the incident moves on (see [Statuses](/clinical-safety/managing-incidents#statuses)). ## Link the incident If the hazard isn't in your hazard log yet, [create it](/clinical-safety/hazard-log) first. * **Clinical incident:** in **Clinical Details**, click **Link or add hazards** under **Hazard Log** and pick the hazard. * **Security incident:** in **Data Security Details**, click **Link or add risks** under **Risk Register** and pick the risk. To change the links later, click **Edit linked Hazards** or **Edit linked Risks**. ## Related articles Filter the log and track each incident to closure. Let staff and anyone else report into your log. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.