Skip to content
SkyRosterBook a working session

Beyond ATC · Healthcare

A ward instead of a sector, but the same currency problem underneath the licence

SkyRoster has never rostered a nurse. Everything on this page is a mapping exercise against the product's own architecture, stated here in the open, not a description of a deployment. What makes healthcare worth mapping at all is how closely its central difficulty, a credential that is only as good as the requirement underneath it, matches the mechanism SkyRoster already built for a licence that is only as good as the medical check underneath it.

The scheduling problem

What ward scheduling actually has to hold

Coverage shape

Three-shift or twelve-hour rotations, around the clock, on a ward that cannot simply run short the way an office can absorb an empty desk for a day.

Qualifications

Nursing registration itself, plus specialty endorsements, plus mandatory training that must be refreshed on a fixed cycle. Each behaves like a licence with an expiry, not a one-time check completed at hiring.

Statutory rest

A minimum rest between shifts and a cap on consecutive nights are common across health systems. The specific limits vary enormously by country and by collective agreement, so none are stated here.

Demand pattern

Acuity, not just headcount, drives how many staff a ward needs on a given shift, and that figure can move within the same day as patients are admitted or discharged.

What maps directly

Mechanisms already built for a different name

Every item below is an illustrative mapping against SkyRoster's existing data model.modelled None of it has been configured for a health system, and none of it has been proven on a real ward.

Expiring credentials stop an assignment on their own

A lapsed resuscitation certificate would stop the engine assigning that nurse to a position requiring it, the same way a lapsed medical certificate already stops it assigning a controller. The mechanism does not know or care what the credential is called. See /platform/competency.

Preceptorship as a support period

A newly qualified nurse working under a preceptor maps onto the same support-period mechanism built for a controller under a mentor: excluded from independent assignment on that qualification until the mentoring window closes. See /platform/competency.

Fair distribution of nights and weekends

A scored fairness table an administrator defines, so a request for a popular date can be weighed against a quiet one, is a mechanism that does not care whether the calendar is measuring a controller's leave or a nurse's weekend rota. See /platform/configuration.

Approval chains per unit

Ward-manager sign-off on leave, duty and shift changes is the same ordered, configurable chain already built for an ATC unit, not a separate workflow. See /platform/leave-management.

Swap re-verification, not informal agreement

Two staff agreeing to trade a shift would need the same automatic re-check a controller's swap already gets: qualification current, rest intact, before either side can confirm it. See /platform/shift-swaps.

A resuscitation certificate that lapses mid-roster

modelled
The shape
A ward running a fixed three-shift pattern, where two of the nurses on it hold a resuscitation certificate due to expire partway through the published month.
What it shows
The same expiry mechanism that already governs an ATC medical certificate would apply here without modification: from the moment the certificate lapses, that nurse is no longer a candidate for a position requiring it, department-wide, not just on whichever roster a manager happens to be looking at.
What it does not show
This describes a mechanism, not a staffing outcome. Whether the ward has enough certified cover to absorb the gap is a staffing question the mechanism does not answer.

What would need new rules or new work

Where the honest answer is development, not a settings screen

Skill-mix ratio enforcement

A rule stating at least one registered nurse per a given number of patients, or a minimum ratio of senior to junior staff on a shift, reasons about the composition of a group of assignments together, not about any one assignment's own qualification. That is a different rule shape from anything in today's catalogue, and building it is new rule development, not a settings change.

Acuity-linked demand

Today's demand model is a number an administrator sets ahead of time. Ward demand that should move with a live patient census would need a feed from a hospital system, an integration this product does not have.

Clinical on-call and recall

On-call and recall rules for clinical staff carry their own legal and contractual shape, distinct from an ATC standby arrangement, and would need their own rule design rather than a reuse of an existing one.

Bring your credentialing structure, not a description of it.

A working session with your own requirements, refresh cycles and ratio rules shows exactly which of this page's mappings hold, and which of the open questions above would actually need building first.