These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- HIPAA Compliance Manager
- Features
- Incidents and risks
Incidents and risks
An incident record links to an assessment and carries incident type, detection date, accession number and processing state.
OverviewIncident processing×
HIPAA Compliance Manager · Incidents and risks
New
Incident processing
Privacy incidents
Ordered2
IDD-266ASS-4174
14 Oct
IDD-650ASS-6035
03 Oct
Add
Collected2
IDD-594ASS-8755
23 Oct
IDD-776ASS-8510
19 Oct
Add
Received1
IDD-844ASS-9428
18 Oct
Add
Tested1
IDD-691ASS-9892
04 Oct
Add
What you can do
Keep the work in its source record
An incident record links to an assessment and carries incident type, detection date, accession number and processing state. The sequence runs from Ordered through Collected, Received and Tested, with Rejected available when processing cannot continue. Keep that sequence tied to the actual case.
How the work is organized
- Link the incident. The clinician selects the assessment parent and keeps its accession number with the processing state.
- Describe the risk. The clinician selects the assessment and team member owner, then records title, lot, quantity and unit.
- Review together. The reviewer reads each item in the assessment context before asking for further work.
A risk record also links to an assessment. It records title, owner, lot number, quantity and unit. The reviewer can examine the incident and risk records alongside assessment results, using the parent links to keep each item in scope.
What to agree during setup
Agree the meaning of the incident processing states and who corrects a rejected item. Use the accession number consistently with the source process. For risks, settle how quantity and unit are entered so records from different teams remain readable. Walk through a completed case and a correction with the people who will operate the record. Decide where source documents arrive and who checks them before a status is changed. Keep the agreement close to the team’s operating procedure so a new owner can make the same decision.
Check the handoff on an actual case
A clinician records an incident detected during an assessment and follows its processing state as work proceeds. A risk tied to the same assessment names its owner and quantity. The reviewer opens both from the assessment to decide what further work is needed. Reopen the incident and risk from the same assessment and compare their parent references. Use the incident accession number and assessment to identify the item for correction. Check the risk owner separately, then have the coordinator decide whether the assessment is ready for review.
When a processing item is Rejected, keep its accession number and assessment link available for the next review. The risk quantity and unit describe a recorded amount; the team should explain their meaning for its own work before comparing cases. The reviewer examines both items in the assessment before a decision is signed.
What your team sees
- Incident processing — Open the working records that need the module’s first decision.
- Assessments awaiting review — Read the assessment that carries the incident and risk records.
Follow the work through
Follow assessment to decision and follow-up and retest. Set ownership in roles before rehearsing the handoff.
What it keeps track of
Data model- Privacy incidents
- Privacy incidents and their processing state
- Risks
- Domain risks with owner and quantity
- Assessments
- Assessment periods and their operational state
Who uses it
Permissions- Licensed Clinician
- , Clinical Reviewer, Clinical Coordinator.
Set up HIPAA Compliance Manager your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.