MétaCan
Menu
Back to cohort
Record W2778723801

Mitigating Risks Associated with Secondary Intravenous (Iv) Infusions: An Empirical Evaluation of a Technology-Based, A Practice-Based, And a Training-Based Intervention

2013· article· en· W2778723801 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

VenueCMBES Proceedings · 2013
Typearticle
Languageen
FieldEngineering
TopicIntravenous Infusion Technology and Safety
Canadian institutionsUniversity of TorontoUniversity Health Network
Fundersnot available
KeywordsMedicinePsychological interventionPatient safetyIntravenous InfusionsIntervention (counseling)WorkflowSecondary careIntensive care medicineAnesthesiaNursingPrimary careHealth careComputer scienceFamily medicine
DOInot available

Abstract

fetched live from OpenAlex

Multiple intravenous (IV) infusions are commonly used in the clinical setting to administer numerous fluids and medications to patients. Secondary infusion , also known as piggyback infusion , is a specific multiple IV infusion setup to deliver intermittent medications. Errors related to the setup and administration of secondary infusions have led to patient safety concerns[1, 2]. However, there is currently no study that specifically aims to empirically test the effects of interventions on the safety of secondary infusions in the clinical setting. The objective of this experimental study was to empirically evaluate interventions that may reduce errors during the administration of secondary infusions. Three mitigating strategies (a technology-based, a practice-based, and a training-based intervention) were tested. Forty critical care nurse participants performed secondary infusion tasks in a high-fidelity simulated clinical environment, with and without interventions. The types and frequency of errors were collected. The effects of the interventions on workflow and the reduction of secondary infusion errors were investigated.

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 categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.916
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.002
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0010.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.027
GPT teacher head0.290
Teacher spread0.263 · 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