MétaCan
Menu
Back to cohort
Record W2782465855 · doi:10.1108/ijppm-12-2015-0193

Hospital capacity management based on the queueing theory

2018· article· en· W2782465855 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

VenueInternational Journal of Productivity and Performance Management · 2018
Typearticle
Languageen
FieldHealth Professions
TopicHealthcare Operations and Scheduling Optimization
Canadian institutionsMcGill University
Fundersnot available
KeywordsQueueing theoryCapacity managementOperations managementComputer scienceValue (mathematics)Capacity planningOperations researchEconomicsMathematics

Abstract

fetched live from OpenAlex

Purpose The purpose of this paper is to focus on the contributions of queueing theory to hospital capacity management to improve organizational performance and deal with increased demand in the healthcare sector. Design/methodology/approach Models were applied to six months of inpatient records from a university hospital to determine operation measures such as utilization rate, waiting probability, estimated bed capacity, capacity simulations and demand behavior assessment. Findings Irrespective of the findings of the queueing model, the results showed that there is room for improvement in capacity management. Balancing admissions and the type of patient over the week represent a possible solution to optimize bed and nurse utilization. Patient mixing results in a highly sensitive delay rate due to length of stay (LOS) variability, with variations in both the utilization rate and the number of beds. Practical implications The outcomes suggest that operational managers should improve patient admission management, as well as reducing variability in LOS and in admissions during the week. Originality/value The queueing theory revealed a quantitative portrait of the day-by-day reality in a fast and flexible manner which is very convenient to the task of management.

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.003
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.550
Threshold uncertainty score0.484

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.000
Scholarly communication0.0000.000
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.041
GPT teacher head0.351
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