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
- Workforce records
Workforce records
Keep the employee, position, department and location context behind credential decisions current.
OverviewActive workforce×
Healthcare Staff HRMS · Workforce records
New
Active workforce
Employees
| Employee ID | First name | Last name | Department | Position | Location | |
|---|---|---|---|---|---|---|
| EI-919 | First 715 | Last 465 | DPR-120 | PST-8383 | LCT-120 | |
| EI-658 | First 990 | Last 894 | DPR-120 | PST-3710 | LCT-120 | |
| EI-214 | First 358 | Last 578 | DPR-140 | PST-2132 | LCT-110 | |
| EI-848 | First 549 | Last 284 | DPR-140 | PST-6406 | LCT-130 | |
| EI-119 | First 581 | Last 413 | DPR-140 | PST-2472 | LCT-110 |
6 of 6 records
EI-919Employees · EMP-84553
ActiveFirst nameFirst 715
Last nameLast 465
DepartmentDPR-120
PositionPST-8383
LocationLCT-120
What you can do
Know who the credential belongs to
The employee record anchors healthcare workforce work. It carries a stable employee ID, name, work email, hire date, employment type, status, entity, country, position, department, location and manager. A staff credential packet references that employee, so the credentialing team can distinguish two people with similar names and understand where each person works.
Positions connect job titles, departments and locations. Departments identify their head and may have a parent department. Employment history records hire, promotion, transfer, manager change, leave and separation events with an effective date. This makes it possible to discuss a credential review in the context of the employee’s current assignment without erasing an earlier assignment.
How the work is organized
- Stable identity. HR Manager uses the employee ID and work record to identify the correct person for each packet.
- Assignment context. Position, department, location and manager place the person in the right operating team.
- Dated change. Employment history captures effective changes that can affect who owns credential follow-up.
For example, a clinician transfers to another department shortly before a license renewal. HR updates the employee’s assignment and records the transfer event. The credentialing coordinator checks the existing packet’s owner and organization context before the next review. The older review decision still refers to the packet revision it covered.
What to agree during setup
Agree who can create an employee and what identifies a person across rehire. Decide which team maintains positions, job titles and departments, and how transfers are recorded. The credentialing team needs a reliable handoff when a manager or location changes, especially when an action is already assigned.
Use the configured employee status values consistently. Active, on leave, Terminated and Rehireable describe employment, while the packet’s status describes credential review. These fields should not be used interchangeably. Agree who checks packets when an employee becomes inactive or returns from leave.
Check the handoff on an actual case
Choose an employee with a position, department and location. Create or inspect a packet and confirm it points to that employee rather than a similar name. Record a department transfer in employment history and update the employee’s current assignment. The coordinator then checks whether the packet owner and follow-up assignee still make sense.
Repeat with an employee marked on leave. The HR Manager should still see the employment record and linked packet, while the credentialing team can inspect the packet’s independent status and license date. This separates workforce context from credential conclusion.
What your team sees
- Active workforce — HR checks employee identity, assignment and manager in one list.
- Current staff credentials — Current packets remain connected to their employee and definition.
Follow the work through
What it keeps track of
Data model- Employees
- Central employee record for the clinical and support workforce.
- Employment history
- Lifecycle events: hire, promotion, transfer, comp change, manager change, leave and termination.
- Positions
- Seat-level org entries that an employee fills.
- Job titles
- Canonical clinical and administrative job titles.
- Departments
- Clinical and administrative departments.
- Locations
- Facilities and remote work locations.
- Staff credential packets
- Credential packet for an eligible employee, carried through review to current status.
Who uses it
Permissions- HR Manager
- Maintains employee and assignment context.
- Department Manager
- Checks the staff in their area.
- Credentialing Coordinator
- Checks the person and assignment behind each packet.
- Admin
- Maintains organization setup.
Set up Healthcare Staff HRMS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.