Prevent ACGME duty hour violations by design

Thrawn's Scheduling Programming Language encodes ACGME duty hour rules as hard mathematical constraints before any schedule is generated. This means the optimization engine cannot produce a schedule that violates the 80-hour weekly limit, 24+4 shift cap, required rest periods, or day-off rules. Violations are structurally impossible to generate, unlike rule-based tools that check for violations after the schedule is already built.

Yes. Thrawn's optimization engine encodes the full set of ACGME duty hour requirements as constraints, including the 80-hour weekly limit, the 24+4 consecutive hour cap, minimum rest periods between shifts, and required days off. All of these are enforced simultaneously at schedule generation time across block, call, and clinic schedules.

When an unplanned absence occurs, Thrawn re-optimizes the affected schedule with ACGME duty hour rules still in place as hard constraints. The resulting coverage solution maintains compliance automatically. Programs are not left manually patching schedules in ways that could inadvertently introduce new duty hour violations.

Most scheduling tools, including rule-based platforms and spreadsheet workflows, generate a schedule first and then surface duty hour violations for the user to fix manually. Thrawn's approach is architecturally different: ACGME duty hour rules are constraints the optimization engine must satisfy before producing any output. The finished schedule arrives compliant, with no downstream correction required.

Thrawn operates as a fully managed service. Programs send their constraints, including ACGME duty hour rules, resident preferences, rotation requirements, and vacation requests. Thrawn's scheduling specialists and optimization engine produce finished schedules for review. There is no software to learn or configure. Program directors and chief residents become reviewers, not builders.