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
- Review decisions
Review decisions
The decision record belongs to an assessment.
OverviewDraft review decisions×
HIPAA Compliance Manager · Review decisions
New
Draft review decisions
Signed waits for the clinical reviewer
| Id | Parent | Reviewer | Decision type | Reason | Decided at | |
|---|---|---|---|---|---|---|
| IDD-906 | ASS-2670 | DT-349 | Draft rd-651 | 08 Oct | ||
| IDD-887 | ASS-1509 | DT-901 | Draft rd-410 | 18 Oct | ||
| IDD-825 | ASS-2390 | DT-598 | Draft rd-392 | 15 Oct | ||
| IDD-639 | ASS-6593 | DT-856 | Draft rd-288 | 12 Oct | ||
| IDD-475 | ASS-3640 | DT-655 | Draft rd-883 | 20 Oct |
6 of 6 records
IDD-906Review decisions · RD-28792
DraftParentASS-2670
Decision typeDT-349
ReasonDraft rd-651
Decided at08 Oct
What you can do
Keep the work in its source record
The decision record belongs to an assessment. It carries a decision type, reason, reviewer, date and status. Draft lets the reviewer examine the case before the decision is signed. Signed and Amended distinguish the original documented decision from a later correction.
How the work is organized
- Keep the assessment link. A decision points to the assessment whose evidence was examined.
- Record the reviewer. The decision identifies a team member reviewer, reason and decision date.
- Sign with authority. The reviewer examines the evidence; Admin records the signed or amended state.
The reviewer should inspect the assessment, dated test results, linked risks and incident records before deciding. The reason needs to explain the actual judgment, including any follow-up requested. Admin records the signed outcome and retains the reviewer reference.
What to agree during setup
Agree who is authorized to sign after the reviewer examines the evidence, how amendments are explained and when a coordinator may complete the assessment. Keep the reviewer and recorded reason together so the decision can be understood later. 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
The coordinator moves an assessment to awaiting review. The reviewer reads the result and asks for a correction to the evidence. Once satisfied, the reviewer gives a reasoned decision. Admin signs that record with the reviewer and date. The coordinator can then manage remaining actions. Reopen the assessment and its draft decision with the reviewer. Admin enters the reason, reviewer and date after the reviewer examines the case, then signs the decision. Check the parent assessment again before the coordinator changes its state.
A decision can be amended after signing. Keep the reason for the later change clear, and check the assessment state before a coordinator acts on the new wording. The reviewer reference should point to the person who considered the evidence. Test both a straightforward sign-off and a correction to see how the team handles each handoff.
What your team sees
- Draft review decisions — Open the working records that need the module’s first decision.
- Assessments awaiting review — Compare related work before handing the case to another owner.
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- Review decisions
- Attributed review decision documentation
- Assessments
- Assessment periods and their operational state
- Team members
- Team members and their roles
Who uses it
Permissions- Clinical Reviewer
- , Admin, 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.