Incidents
IMPORTANT: Functionality for Incident Reporting is also now contained in the Admin Module. Please see the Admin Module Overview knowledge base article for more details.
The Incident Module allows an Organization to manage the Incident Reporting/Response requirements from within The Guard. The Guard also allows for Employees to Report.
TABLE OF CONTENTS
Creating and Managing an Incident
Creating an Incident can be done in 2 ways:
An Officer/Admin may create an Incident via the Incident Module and fill in the form themselves
Any Employee in The Guard may use the Incident Reporting URL/Portal for the Organization. An Officer/Admin may generate this URL and provide it to their team. This can be done in the Admin Module. Please see Admin Module Overview for more details.
When creating an Incident, a Form is provided where basic and immediate information can be entered. Additional features are available once the Incident has been created.
Navigate to Incidents module
Select Add Incident
Location – Select the Location affected by the Incident (If the Org just has the 1 Location, select this)
Vendor Reported – If the Incident is related to a Vendor, select the Vendor from the dropdown. This requires the Vendor to be created in the Vendor Module
Incident Title – Name the Incident
Reported By – Identify the person reporting the Incident; This can also be done Anonymously
Incident Type – Select from preexisting Incident Types provided by The Guard that best fit the scenario; Otherwise, use “Other” and then type out the type of Incident
Investigation Status – When creating an Incident, this cannot be changed
Incident and Discovery Date –
“Incident Date” – The date in which the Incident occurred
“Discovery Date” – The date in which the Incident was discovered – When the Organization was made aware that an Incident/the Incident occurred
Incident Affected More than 500 Members – There is a checkbox that an Organization can select if the Incident affected more than 500 Individuals – This may affect Breach Notification (see policies), if more than 500 individuals are affected by a breach of unsecured PHI.
The Description, Investigation, Notes, and Evidence fields do not need to be filled in to Save New Incident and create the incident. Each of these fields can be updated after creation and continuously as the organization continues to investigate.
Description – Full details on the Incident
Investigation – Task creation for tracking steps of the investigation as well as to-dos related to the Incident overall
Notes – Notes
Evidence – Evidentiary upload, if required
WE DO NOT RECOMMEND UPLOADING ANY DOCUMENTS CONTAINING PHI/ePHI INTO THE GUARD
Once the Incident has been created, it can be selected from the Incidents module via the table. The Status of Incidents may also be adjusted via the Choose Action or Hamburger Button menus.
NOTE: All Incidents have the Not Verified status by-default
Under Investigation Selected – Changes status for the checked objects to Under Investigation
The Organization is investigating the Incident/Breach and making necessary adjustments/updates
Verify Selected – Changes status to Verified for the selected Incidents
The middle-ground between when an Incident is being Investigated and then when the Incident has been Verified that either a Breach has occurred or not
Marking an Incident as “Verified” has no affect on the Incident itself and could be skipped, unless managing multiple Incidents at once as this will help identify those incidents that are still under investigation or those that are nearing “completion”
Complete Selected – Changes status to Completed
Signifies that an Incident has been completed
A Completed Incident cannot be updated once Completed – The Incident’s status must be adjusted in order to “reopen” it
Additional details and steps, with Job Aid documentation, can be located in the Knowledge Base section for (Legacy) Incidents - https://compliancygroup.freshdesk.com/support/solutions/folders/48000693212
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article