MétaCan
Menu
Back to cohort
Record W2130874622 · doi:10.1093/pubmed/fdp044

How much do operational processes affect hospital inpatient discharge rates?

2009· article· en· W2130874622 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueJournal of Public Health · 2009
Typearticle
Languageen
FieldMedicine
TopicHospital Admissions and Outcomes
Canadian institutionsToronto General HospitalUniversity of TorontoUniversity Health Network
Fundersnot available
KeywordsMedicinePatient dischargeDemographyHospital dischargeEmergency medicineMEDLINEInternal medicine

Abstract

fetched live from OpenAlex

BACKGROUND: The objective of this study is to determine the effect of day of the week, holiday, team admission and rotation schedules, individual attending physicians and their length of coverage on daily team discharge rates. METHODS: We conducted a retrospective analysis of the General Internal Medicine (GIM) inpatient service at our institution for years 2005 and 2006, which included 5088 patients under GIM care. RESULTS: Weekend discharge rate was more than 50% lower compared with reference rates whereas Friday rates were 24% higher. Holiday Monday discharge rates were 65% lower than regular Mondays, with an increase in pre-holiday discharge rates. Teams that were on-call or that were on call the next day had 15% higher discharge rates compared with reference whereas teams that were post-call had 20% lower rates. Individual attending physicians and length of attending coverage contributed small variations in discharge rates. Resident scheduling was not a significant predictor of discharge rates. CONCLUSIONS: Day of the week and holidays followed by team organization and scheduling are significant predictors of daily variation in discharge rates. Introducing greater holiday and weekend capacity as well as reorganizing internal processes such as admitting and attending schedules may potentially optimize discharge rates.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.327
Threshold uncertainty score0.525

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

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.

Opus teacher head0.035
GPT teacher head0.345
Teacher spread0.311 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it