MétaCan
Menu
Back to cohort
Record W2314421968 · doi:10.1097/qmh.0b013e3181bee127

Process Improvement in Hospitals

2009· article· en· W2314421968 on OpenAlex
Stefan Nickel, Ursula-Anna Schmidt

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

VenueQuality Management in Health Care · 2009
Typearticle
Languageen
FieldHealth Professions
TopicHealthcare Operations and Scheduling Optimization
Canadian institutionsNickel Institute
Fundersnot available
KeywordsRadiological weaponProcess (computing)Medical emergencyPatient careService (business)IdleDiscrete event simulationComputer scienceEmergency departmentOperations managementMedicineSimulationBusinessRadiologyNursingEngineering

Abstract

fetched live from OpenAlex

To improve processes in hospitals, a case study was conducted at a German university hospital, which consists of more than 30 clinics and institutes on a large campus. The case study focused on the analysis of the patient flow and of machine utilization in the radiology department. Radiological devices are spread over the campus and located in different buildings. Patients with restricted mobility have to be transported by a vehicle transportation service across the campus. However, a vehicle transport can considerably influence the patients' punctual arrival to their appointments. The observations of the case study showed that the current organization of the radiology department results in high patient waiting times and machine idle times. The university hospital is planning to conduct significant organizational changes, especially with regard to the organization of the radiology department. This case study was conducted to support the planning processes of the clinic and to reveal and estimate optimization potential. To analyze the patient flow, a discrete event multicriteria simulation model was designed and implemented. By modeling different scenarios, it was possible to easily compare and assess distinct alternatives. This led to improved machine utilization and reduced waiting times.

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.548
Threshold uncertainty score0.703

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.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
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.059
GPT teacher head0.504
Teacher spread0.445 · 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