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
- Staff credential packets
Staff credential packets
Keep each employee's license, CME requirement, evidence and review status together.
OverviewMy credential packets×
Healthcare Staff HRMS · Staff credential packets
New
My credential packets
Staff credential packets
| Number | Name | Employee | Definition | License expiry | Status | |
|---|---|---|---|---|---|---|
| SCP-92309 | Packet 280 | CR-1013 | 03 Oct | Submitted | ||
| SCP-31224 | Packet 680 | CR-3710 | 25 Oct | Verified | ||
| SCP-64009 | Packet 914 | CR-2491 | 09 Oct | Reviewed | ||
| SCP-52393 | Packet 389 | CR-9577 | 26 Oct | Current | ||
| SCP-11869 | Packet 943 | CR-6388 | 11 Oct | Expired |
6 of 6 records
Packet 280Staff credential packets · SCP-92309
SubmittedDefinitionCR-1013
License expiry03 Oct
What you can do
Keep the packet tied to a person
A staff credential packet connects one employee to an organization and credential requirement. It has a number, name, completion date and named owner. The packet also carries the license number and expiry date, credits recorded, credits required, evidence reference, revision and status. This gives the coordinator a single place to inspect the information that a reviewer will see.
The employee record adds position, department, location and manager context. A packet’s current status is a review outcome for that packet; it should not be confused with the employee’s employment status. A person may be active while one of their credentials is expired or awaiting review.
How the work is organized
- Packet owner. A named owner prepares information, answers reviewer questions and tracks follow-up.
- Source revision. Revision identifies the version presented for a decision, so later edits can be distinguished from the reviewed material.
- Status history. Status changes can be recorded with actor, date, reason and source revision for a usable trail.
The packet begins at Submitted. As evidence is checked, the coordinator and reviewer record the outcomes that support Verified, Reviewed and Current status. An expired license can bring the packet to Expired. Keeping these stages explicit helps a manager avoid treating an unreviewed document as a current credential.
What to agree during setup
Agree when a packet is opened, when a new revision is required and who may record each status. Decide how the organization handles renewed license numbers and dates, and which evidence must travel with a renewal. The reviewer should see the exact revision and supporting documents before recording a decision.
Set the cadence for checking license expiry and packet status. The credentialing team should agree which person owns a packet when an employee moves department or location. Choose a consistent way to distinguish a new credential from a correction to an existing packet.
Check the handoff on an actual case
Take an active employee whose license expires next month. The coordinator opens the packet with the correct organization and requirement, enters the license number, expiry and required credits, then records the supporting CME activity and document. The reviewer reads the same packet revision and records a decision. The coordinator checks that the decision, status and history all point to the same packet.
Repeat with a packet already marked Current whose expiry date has passed. The manager should be able to find it in License dates needing follow-up and assign follow-up to the packet owner. The packet must retain the prior decision while making the new concern visible.
What your team sees
- My credential packets — Owners see the packets assigned to them with license dates and status.
- Current staff credentials — HR can check current packets by employee and requirement.
- License dates needing follow-up — Coordinators can find elapsed license dates even when packet status remains Current.
Follow the work through
See staff credential review and expiry follow-up.
What it keeps track of
Data model- Staff credential packets
- Credential packet for an eligible employee, carried through review to current status.
- Employees
- Central employee record for the clinical and support workforce.
- Organizations
- Healthcare organizations and facilities in scope.
- Credential requirements
- License and credential definitions with policy reference and effective window.
- State history
- Status transition audit trail for a credential packet.
Who uses it
Permissions- Credentialing Coordinator
- Prepares and maintains the packet.
- Credential Reviewer
- Records a decision on its revision.
- HR Manager
- Checks workforce context and expiry.
- Admin
- Maintains the organization and requirement references.
Set up Healthcare Staff HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.