Specialty coverage gaps on nights and weekends

System failure identification

A facility listed as offering a service cannot deliver it overnight because the specialist is unavailable. The capability is published as a static attribute of the hospital. A patient is routed to a service that will not exist when they arrive.
Data pipeline diagnostics

Service availability is stored as a configuration value set once. It has no time dimension, so a rota gap cannot be represented even though the rota itself is known well in advance. The schema encodes what a hospital can do and never when it can do it.
Predictive computational model

Model capability as a schedule rather than a flag, derived from the specialty rota. Regional matching then queries availability at the time of the request. A rota is a schedule already, so no new information has to be created.
Workflow integration

Derive it from existing rota systems rather than asking facilities to maintain a second calendar. A duplicate calendar diverges from the real one within weeks. A second calendar becomes wrong the first time somebody swaps a shift.

System failure identification