System Walkthrough

Welcome and System Orientation

This walkthrough executes real operations against your NurseCentral environment. Each step inserts, reads, or modifies data so you can inspect every transition.

System Architecture

Status Model

Shift

OPEN → CALLING → FILLED | UNFILLED

Candidate

PENDING → CALLING → DONE | SKIPPED

Booking

First successful claim wins, enforced atomically

What nurses see

Nurses receive an SMS with a booking link. They see eligible shifts and can claim one with a single tap.

What coordinators see

Coordinators monitor shift state, queue progress, call outcomes, and can trigger manual retries.

How this works

• Each step executes real operations against your NurseCentral environment.
• Click Next to advance — inspect each transition at your pace.
• Synthetic records are tagged and can be deleted at the end.

Connectivity and Environment Validation

Insert Synthetic Roster and Fixture Data

What this seeds

• 3 ACTIVE nurses + 1 INACTIVE nurse
• Borough coverage + daily availability
• Time-off exclusion for one nurse
• A prior confirmed booking to demonstrate the 8-hour rest-rule exclusion

Create Open Shifts and Build Candidate Queue

Design objective

• Create two OPEN shifts to drive the dispatch, booking, and call escalation flows.
• Build the candidate queue using eligibility rules.
• Observe eligibility filters in action.

Run Dispatch Phase (Scheduled Job Simulation)

This executes

• Trigger the dispatch-shifts job
• Dispatch scans OPEN shifts that haven't had SMS sent yet
• It builds the candidate queue and sends booking SMS to eligible nurses

Dashboard after dispatch

The coordinator dashboard updates in real time to reflect shift state changes.

Booking Walkthrough (Nurse Claim)

This demonstrates

• Token generation → View eligible shifts → Claim a shift
• Atomic claim ensures only one nurse can fill a shift
• Status transition from OPEN/CALLING to FILLED

What the nurse sees

After claiming, the shift status updates instantly on the nurse booking page.

Call Escalation Flow

Scenario setup

• Shift B remains OPEN after dispatch.
• Simulate the SMS wait window expiring.
• Trigger call escalation to advance the queue and attempt phone calls.

Observability and Debugging Snapshot

Key tables to check during incidents

• Job runs: scheduler outcomes and metrics
• Candidate queue: progression and skip reasons
• Bookings: immutable claim history
• SMS messages, call attempts, and webhook events: provider interaction logs

Live dashboard view

All call attempts, SMS messages, and shift statuses are visible on the coordinator dashboard.

Wrap-up and Optional Cleanup

What you should now understand

• How eligibility turns roster + constraints into an ordered candidate queue.
• How dispatch, booking, and call fallback modify shift state transitions.
• Which operations are critical: candidate seeding, atomic shift claims, queue advancement.
• Where to inspect system behavior and diagnose failures in production.