MétaCan
Menu
Back to cohort
Record W3011403107 · doi:10.1007/s13753-020-00260-3

Mass-Casualty Distribution for Emergency Healthcare: A Simulation Analysis

2020· article· en· W3011403107 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 Disaster Risk Science · 2020
Typearticle
Languageen
FieldHealth Professions
TopicDisaster Response and Management
Canadian institutionsUniversity of Saskatchewan
FundersLahore University of Management Sciences
KeywordsMass CasualtyQueueMass-casualty incidentMetropolitan areaMedical emergencyPoison controlComputer scienceMedicineInjury prevention

Abstract

fetched live from OpenAlex

Abstract This study focuses on the casualty-load distribution problem that arises when a mass casualty incident (MCI) necessitates the engagement of multiple medical facilities. Employing discrete event simulations, the study analyzed different MCI response regimes in Lahore, Pakistan, that vary in terms of the level of casualty-load distribution and the required coordination between the incident site and the responding hospitals. Past terrorist attacks in this major metropolitan area were considered to set up experiments for comparing delays in treatment under the modeled regimes. The analysis highlights that the number of casualties that are allowed to queue up at the nearest hospital before diverting the casualty traffic to an alternate hospital can be an important factor in reducing the overall treatment delays. Prematurely diverting the casualty traffic from the incident site to an alternate hospital can increase the travel time, while a delay in diversion can overload the nearest hospital, which can lead to overall longer waiting times in the queue. The casualty distribution mechanisms based only on the responding hospitals’ available capacity and current load can perform inefficiently because they overlook the trade-off between the times casualties spend in traveling and in queues.

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.002
metaresearch head score (Gemma)0.001
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: none
Teacher disagreement score0.627
Threshold uncertainty score0.366

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.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.096
GPT teacher head0.491
Teacher spread0.396 · 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