Credential requirements

A credential review starts with a definition that the organization recognizes. Admin records the requirement name, code, policy reference and effective dates. That definition belongs to an organization and becomes the common reference for staff packets. When two facilities use different requirements, each can retain its own definition and effective window rather than relying on a packet name alone.

The requirement is the standard against which a packet is assembled. The packet carries the employee, license details, credit figures and evidence. Keeping the definition separate lets the credentialing team see which policy item a packet is intended to satisfy and when that item applies.

• Organization first. Admin identifies the organization whose policy applies before adding a credential requirement.
• Stable reference. A name and code distinguish the requirement in packet lists and discussions with reviewers.
• Dated policy. Effective dates and a policy reference give the reviewer context when inspecting older or renewed packets.

A coordinator can then open a packet for an eligible employee and select the right requirement. For example, a nurse moving between facilities may have one current license but different organization requirements. The coordinator checks the packet’s organization against the applicable requirement and attaches the correct definition to each packet being reviewed.

Agree who maintains requirement codes and who decides when a policy changes. Decide which organization owns each definition and which effective date governs an in-flight packet. The people who maintain policy should agree on a clear naming convention that a credential reviewer can recognize without reading the whole policy document.

Set a routine for retiring an old definition and creating its successor. The packet’s reference and review history should remain intelligible after the policy changes. Decide whether a renewed credential uses a new packet or a revised packet, then apply that convention consistently to the source revision reviewed by a person.

Select one employee and a requirement that applies to that employee’s organization. The coordinator opens the packet, enters the license number and expiry, and records the credit requirement. The reviewer follows the packet back to the requirement, checks its policy reference and effective window, then records a decision for the revision that was presented. A second employee in another organization should show the other organization’s applicable definition.

This rehearsal tests whether the intended policy is visible at the point of review. It also exposes duplicate codes or definitions with overlapping effective dates before they confuse a real renewal cycle.

• Packets awaiting credential review — Submitted packets show the employee, organization and linked definition for reviewer triage.
• Credential status board — Packet status stays visible across the review cycle.

See staff credential review and the data model.