Platform · Garnet Health · 2021
On-Call Scheduling
The hospital's on-call source of truth: 212 live lists, conflict detection, iCal feeds, and escalation that reaches a person.
How it works
One core owns identity, conflict detection, and delivery. Each department keeps its own rotation rules on top.
-
01 · The problem
On-call lists were maintained per department in whatever tool that department preferred. At two in the morning the question is not where the schedule is, it is who is covering and how to reach them, and the answer was taking too long.
-
02 · What I decided
One system, but not one process: departments keep their own rules and rotations. Conflict detection at write time rather than a report afterwards, because a double-booked consultant discovered on Monday has already cost the weekend.
-
03 · The outcome
212 live lists and over 628,000 published shifts, feeding calendars directly and replacing a scheduling licence.
What a surveyor, or a hiring panel, should hear.
Constraint
Every department owned its own rotation and refused to give that up, so a single imposed process was never going to be adopted. Meanwhile the two-in-the-morning question was not where the schedule lives, it was who is covering and how to reach them.
Decision
One system, many processes. Departments keep their own rules; the platform owns identity, conflict detection, and delivery. Conflicts are caught at write time rather than in a Monday report, because a double-booked consultant found on Monday has already cost the weekend.
Ownership
The hospital owns the roster of record and publishes it to calendars directly. 212 live lists and 628,000 shifts, on infrastructure with no per-seat licence attached.
- Live lists
- 212
- Shifts
- 628K+
- Platforms
- Web