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.
- Healthcare Staff HRMS
- Features
- Review and follow-up
Review and follow-up
Record a reviewer decision on the exact packet revision and assign missing-evidence work.
OverviewReview decisions to record×
Healthcare Staff HRMS · Review and follow-up
New
Review decisions to record
Approval conditions
| Source | Source revision | Decision | Reviewer | Decided at | Evidence reference | |
|---|---|---|---|---|---|---|
| 340 | Pending | 14 Oct | ER-831 | |||
| 450 | Pending | 18 Oct | ER-136 | |||
| 750 | Pending | 07 Oct | ER-862 | |||
| 60 | Pending | 25 Oct | ER-866 | |||
| 450 | Pending | 11 Oct | ER-990 |
6 of 6 records
ER-831Review decisions · RD-74083
PendingSource revision340
Decided at14 Oct
What you can do
Make the decision inspectable
A review decision belongs to a staff credential packet and names the reviewer. It records the source revision, decision, date, reason and evidence reference. Pending, Approved, Returned and Rejected are distinct decision values. The reviewer can return a packet for correction without presenting that outcome as an approval. A later packet edit can be recognized as a different revision.
State history records the packet’s status transitions with actor, time, source revision, operation key and reason. This is useful when a manager asks when a packet became Current or why it later became Expired. The decision and the status change serve different purposes, and both should be visible during an audit of the work.
How the work is organized
- Independent decision. Credential Reviewer inspects the presented revision and records Approved, Returned or Rejected with a reason where needed.
- Assigned correction. A follow-up action links to the packet, names an assignee, due date and resolution.
- Status trail. The team records packet status changes in state history so a later review can follow the sequence.
Consider a license document whose number differs from the packet. The reviewer returns that revision and cites the document. The coordinator assigns an action to resolve the discrepancy. After correction, the packet revision and evidence can be presented again. The original return remains part of the decision history.
What to agree during setup
Agree who may review a packet and how separation from the preparer is maintained. Set a standard for reasons on returned or rejected decisions. Decide who can record a Verified, Reviewed or Current packet status after the review, and how that person checks the underlying decision.
Agree a due-date rule for follow-up and a resolution convention. A completed action should describe what changed or what evidence was obtained. A canceled action should have a reason so it cannot be mistaken for a completed correction. The team should periodically inspect open actions and packet expiry together.
Check the handoff on an actual case
Prepare a submitted packet with a document and CME activity. Have Credential Reviewer record an Approved decision for the packet’s current revision. Then record the supported status change and inspect its history entry. The revision in the decision should match the material reviewed.
Run a second case with a missing primary-source document. The reviewer records Returned with a reason, and the coordinator assigns a follow-up action. Complete the action after a document arrives, then present the changed revision again. The earlier decision, later decision and action resolution should all remain understandable.
What your team sees
- Review decisions to record — Pending decisions identify the packet revision awaiting a reviewer.
- Open credential follow-up — Due dates and assignees make unresolved work visible.
- My follow-up actions — Each assignee sees the actions directed to them.
Follow the work through
See staff credential review and expiry follow-up.
What it keeps track of
Data model- Review decisions
- Independent reviewer decision recorded against an exact source revision.
- State history
- Status transition audit trail for a credential packet.
- Follow up actions
- Actions assigned to close missing evidence or held conditions.
- Staff credential packets
- Credential packet for an eligible employee, carried through review to current status.
- Evidence documents
- Primary-source documents attached to a credential packet.
- People
- Named internal owners, reviewers and actors referenced across the domain records.
Who uses it
Permissions- Credential Reviewer
- Records the independent decision.
- Credentialing Coordinator
- Prepares corrections and tracks actions.
- HR Manager
- Checks exceptions across the workforce.
- Admin
- Controls access and reference setup.
Set up Healthcare Staff HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.