Incident Root Causes

This article explains how to identify and document compliance-related root causes within an incident. A compliance root cause is the underlying reason an incident occurred, documented to ensure corrective actions address the actual cause and prevent recurrence. The Investigator, Final Approver, Admin user, and Incident Manager or Full Access Manager for the specified location can add the Root Cause details. 

This article includes: 

• Adding a Root Cause
• Editing Root Causes

Adding a Root Cause

Adding a root cause allows you to document the fundamental reason an incident occurred.

Follow these steps to add Root Cause details:

1. Navigate to the Incident Details page and select Root Causes from the left panel of the screen, or scroll down to the Root Causes section.

2. Hover over the More Options icon at the far right of the header and select Add. An Add Root Causes window will be displayed.

   ℹ️ Notes

   When no root causes have been entered, the only available option in the menu is Add.

3. In the selection window, choose one or more applicable root causes.
4. Click Add Root Cause to confirm your selections.
5. To add a custom root cause:
   • Click the Create New Root Cause. A new field appears to add the root cause details
   • Enter the root cause details and select the Add Root Cause button to save the information.
6. Click Save to finalize and document the root causes for the incident.

Editing Root Causes

Follow these steps to edit the Root Causes details:

1. Navigate to the Incident Details page and select Root Causes from the left panel of the screen, or scroll down to the Root Causes section.
2. Hover over the More Options icon at the far right of the header and select Edit. An Add Root Causes window will be displayed.
3. Update the required root cause details, then click Save to apply the changes.
4. Users can also delete the created root cause from the More Options menu.

© Healthicity, LLC