MétaCan
Menu
Back to cohort
Record W4309328075 · doi:10.1089/hs.2022.0059

Rethinking Surge Preparedness After COVID-19: Effective Patient Load Balancing Within Health Systems and Beyond

2022· article· en· W4309328075 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

VenueHealth Security · 2022
Typearticle
Languageen
FieldHealth Professions
TopicHealthcare Operations and Scheduling Optimization
Canadian institutionsBell (Canada)
Fundersnot available
KeywordsSurge CapacityPreparednessPandemicCoronavirus disease 2019 (COVID-19)Healthcare systemHealth careMedical emergencyMedicineViral loadSevere acute respiratory syndrome coronavirus 2 (SARS-CoV-2)Operations managementPolitical scienceInfectious disease (medical specialty)EngineeringFamily medicineDiseaseHuman immunodeficiency virus (HIV)

Abstract

fetched live from OpenAlex

Within weeks of New York State's first confirmed case of COVID-19, New York City became the epicenter of the nation's COVID-19 pandemic. With more than 80,000 COVID-19 hospitalizations during the first wave alone, hospitals in downstate New York were forced to adapt existing procedures to manage the surge and care for patients facing a novel disease. Given the unprecedented surge, effective patient load balancing-moving patients from a hospital with diminishing capacity to another hospital within the same health system with relatively greater capacity-became chief among the capabilities required of New York health systems. The Greater New York Hospital Association invited members of downstate New York's 6 largest health systems to talk about how each of their systems evolved their patient load balancing procedures throughout the pandemic. Informed by their insights, experiences, lessons learned, and collaboration, we collectively present a set of consensus recommendations and best practices for patient load balancing at the facility and health system level, which may inform regional approaches to patient load balancing.

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.010
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Science and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: Qualitative
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.529
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0100.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.001
Science and technology studies0.0070.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.002
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.389
Teacher spread0.354 · 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