Junior doctor rostering is hard because the people move: interns, residents and registrars rotate through terms of ten to thirteen weeks, each term has its own roster pattern, supervision ratio and unit, and the medical workforce team has to rebuild everything every rotation. HosPortal models terms as first-class objects, so allocating a doctor to a term sets their roster, their team and their distribution lists in one step. Read the JMO case study.
A JMO unit in a large hospital may have 200 to 600 junior doctors across dozens of terms. Each term carries a roster pattern (a 1-in-4 weekend, a nights block, a relief line), a supervisor structure and a set of fatigue rules from the award or the state’s safe hours framework. When the rotation changes, a spreadsheet-based unit re-keys all of it, and the errors show up as unsupervised shifts, breached hours and payroll disputes.
See the Medical Workforce (JMO) page for the module overview, and the guide How to roster junior doctors across terms and rotations.
Rostering where each training term has its own pattern, team and rules, and a doctor’s roster follows from the term they are allocated to rather than being built for them individually. It is how junior doctor units in large hospitals avoid rebuilding rosters every rotation.
Yes. Terms, teams and roster patterns are structured so that one medical workforce unit can manage all JMOs across departments and sites, with department administrators seeing only their own.
Yes. Work Rules and Shift Conflict Rules encode maximum hours, minimum rest and recovery days after nights, and any breach is flagged before the roster is published.
HosPortal’s Term Builder can run a preference round where doctors rank terms, then allocate against training requirements and fairness. Administrators review the draft before it is finalised.