525 THE EFFECT OF THE 80-HOUR WORK WEEK ON RESIDENTS' OPERATIVE CASE VOLUME.
Bibliographic record
Abstract
Objective In order to meet the new accreditation requirement set by the ACGME on July 1, 2003, yet still maintain the operative experience of our residents, our program underwent many changes. This included decreasing the number of call nights, eliminating rotations that did not have a heavy operative volume as well as the addition of other rotations that provided for more operative experience. This study examined the impact that the decrease in work hours had on the residents9 operative case volume. Methods The major operative cases of categorical surgical residents (clinical PGY I-V) were recorded from July 1, 2000 to December 31, 2004. The number of call nights each resident took per quarter (defined as a 3-month period beginning July 1) was also recorded during this time period. Residents who were in their research year during this time period were not included in the study. The number of cases per quarter that the residents performed was examined. We also compared the number of cases per resident year as well as number of cases per gender. Results From July 1, 2000 to December 31, 2004, there was not a significant change in the number of cases performed by categorical surgical residents (p > .4936). The mean number of cases per quarter for successive levels was PGY I: 11, PGY II: 22, PGY III: 87, PGY IV: 63, and PGY V: 45. On analysis, resident year was a predictor in the average number of cases performed, with the greatest number of cases performed in the PGY III year (p < .0001). From July 1, 2000 to December 31, 2001, the PGY I year performed a statistically significant less number of cases than currently. However, since January 2002, the number of procedures has appeared stable. In the remaining PGY II-V years, the number of procedures performed has remained unchanged. Reanalyzing the data disregarding the number of call nights had the same result. The mean number of cases performed by male and female residents was 42 and 41, respectively. There was no difference in the number of major operative cases performed between genders (p = .8188). Conclusion The 80-hour work week did not make a significant impact on the operative experience of our categorical surgical residents. It is likely that the changes made to the rotational schedule offset the decrease in work hours by increasing the time that the residents spent in the operating room.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.008 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.028 | 0.003 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".