DOI 10.1016/j.artd.2025.101926
Optimizing Daily Surgical Scheduling Improves Operative Time Consumption: A Retrospective Study.
Аннотация
BACKGROUND
Arthroplasty cases represent some of the highest volume and resource-intensive orthopaedic procedures. Most cost containment efforts have focused on restricting access to operating room (OR) time rather than improving efficiency through scheduling optimization. However, approaches such as bin-packing optimization (BPO) can be used to generate more efficient schedules. This study compares manual scheduling with BPO to evaluate their impact on OR efficiency. Our hypothesis is that BPO scheduling produces more efficient OR schedules compared to manual scheduling.
METHODS
Data were collected retrospectively for a mid-sized hospital performing elective orthopaedic surgery (majority hip and knee arthroplasty). Data included operative time, overtime, and number of OR days. BPO model was used to simulate an optimized schedule and compared to the historic manual schedule by comparing the number of OR days required to complete the same surgical volume. The primary outcome was the total number of OR days required.
RESULTS
All surgeons experienced a median 10% reduction (range: 9.2%-18.3%) in OR days required using BPO schedules (mean 183 days) vs historical scheduling (mean 207 days). Daily OR configurations differed from historical ones in 87% of cases, and the number of configurations per surgeon dropped from an average of 6 to 4.
CONCLUSIONS
BPO increased OR throughput by 10% without increasing operative time. This suggests potential for reduced costs, shorter wait lists, and improved surgeon satisfaction for hip and knee arthroplasty. Future work should incorporate predictive modeling using patient- and procedure-specific data.
LEVEL OF EVIDENCE: III - Retrospective study.
Подготовка и перевод публикации
Обработка статьи · этапы, ошибки и управление
Ошибки и ограничения
История · было → стало
Состояние обновляется каждые 5 секунд, пока блок открыт. Процент показывается только там, где известен объём работы. Пауза останавливает продолжение этапа; текущий запрос к источнику может завершиться.
Тип публикации указан по данным источника. Уровень доказательности автоматически не присваивается.