Question 1

How does Thrawn prevent ACGME duty hour violations rather than detect them?

Accepted Answer

The difference is architectural. Rule-based scheduling tools build a schedule first and then run compliance checks — surfacing violations after the fact and leaving someone to manually resolve them. Thrawn's Scheduling Programming Language encodes ACGME duty hour rules as hard mathematical constraints before the optimization runs. The engine cannot generate a schedule that violates the 80-hour weekly cap, 24+4 continuous duty limits, or mandatory rest periods. Compliance isn't a post-processing step — it's baked into what the optimizer is allowed to produce.

Question 2

How is Thrawn's approach architecturally different from rule-based scheduling tools?

Accepted Answer

Rule-based tools apply logic conditionally: if a rule is broken, flag it. That means the schedule is generated first, violations are identified second, and manual fixes happen third. Thrawn's optimization engine works differently — ACGME duty hour rules are constraints that shape the solution space. Every possible output is already compliant. There is no 'flag and fix' loop because a non-compliant schedule is never generated in the first place. Competitors would need to rebuild their engines from the ground up to replicate this — that's a multi-year architectural effort.

Question 3

Does Thrawn track duty hours across block, call, and clinic schedules together?

Accepted Answer

Yes. This is one of the most critical — and most commonly missed — aspects of ACGME compliance. A resident's duty hours accumulate across every schedule type simultaneously. Tracking hours only within the call schedule, for example, creates blind spots where a resident appears compliant on paper but has exceeded limits when clinic and block hours are included. Thrawn's cross-schedule simultaneous optimization treats block, call, and clinic as one interconnected system, enforcing ACGME duty hour compliance on total accumulated hours across all schedules.

Question 4

What happens to ACGME compliance when schedules change mid-year?

Accepted Answer

When a schedule change is needed — an unplanned absence, a rotation swap, a leave of absence — Thrawn re-optimizes around the updated constraints. ACGME duty hour compliance is re-enforced automatically as part of that re-optimization. The revised schedule is compliant by construction, not by a manual audit you have to run afterward. This means program directors don't have to choose between responding quickly to a coverage need and maintaining compliance. Both happen together.

Question 5

How does Thrawn help programs prepare for ACGME accreditation site visits?

Accepted Answer

Thrawn delivers finished schedules that are documented against the ACGME duty hour constraints that governed them. Program directors and GME administrators aren't scrambling to reconstruct compliance evidence before a site visit — the compliance logic is embedded in how the schedule was built. As one clinical fellow put it: *"Scheduling can be one of the most stressful and time-consuming parts of the role, but Thrawn made the entire process seamless. I would highly recommend their services to any program looking for a reliable and efficient way to build equitable schedules!"* — Dr. R. Kapoor, Clinical Fellow, Neurocritical Care Fellowship at a leading academic medical center.

ACGME Compliance Built Into Every Schedule

The ACGME Compliance Gap in Scheduling

The ACGME Compliance Gap in Scheduling

Duty Hour Rules Encoded by Design

Violations Prevented at Generation Time

Schedules Built for Site Visit Scrutiny

Compliance Across Block Call and Clinic

Compliance Survives Schedule Changes

End ACGME Compliance Anxiety

Common Questions