MétaCan
Menu
Back to cohort
Record W2801823238 · doi:10.2196/10446

Types and Frequency of Infusion Pump Alarms: Protocol for a Retrospective Data Analysis

2018· article· en· W2801823238 on OpenAlexvenueno aff
Kevin R. Glover, Rachel R. Vitoux, Catherine Schuster, Christopher R. Curtin

Bibliographic record

VenueJMIR Research Protocols · 2018
Typearticle
Languageen
FieldMedicine
TopicHealthcare Technology and Patient Monitoring
Canadian institutionsnot available
Fundersnot available
KeywordsBackupMedicineMedical emergencyProtocol (science)Computer sciencePatient safetyALARMDatabaseEngineering

Abstract

fetched live from OpenAlex

BACKGROUND: The variety of alarms from all types of medical devices has increased from 6 to 40 in the last three decades, with today's most critically ill patients experiencing as many as 45 alarms per hour. Alarm fatigue has been identified as a critical safety issue for clinical staff that can lead to potentially dangerous delays or nonresponse to actionable alarms, resulting in serious patient injury and death. To date, most research on medical device alarms has focused on the nonactionable alarms of physiological monitoring devices. While there have been some reports in the literature related to drug library alerts during the infusion pump programing sequence, research related to the types and frequencies of actionable infusion pump alarms remains largely unexplored. OBJECTIVE: The objectives of this study protocol are to establish baseline data related to the types and frequency of infusion pump alarms from the B. Braun Outlook 400ES Safety Infusion System with the accompanying DoseTrac Infusion Management Software. METHODS: The most recent consecutive 60-day period of backup hospital data received between April 2014 and February 2017 from 32 United States-based hospitals will be selected for analysis. Microsoft SQL Server (2012 - 11.0.5343.0 X64) will be used to manage the data with unique code written to sort data and perform descriptive analyses. A validated data management methodology will be utilized to clean and analyze the data. Data management procedures will include blinding, cleaning, and review of existing infusion data within the DoseTrac Infusion Management Software databases at each hospital. Patient-identifying data will be removed prior to merging into a dedicated and secure data repository. This pooled data will then be analyzed. RESULTS: This exploratory study will analyze the aggregate alarm data for each hospital by care area, drug infused, time of day, and day of week, including: overall infusion pump alarm frequency (number of alarms per active infusion), duration of alarms (average, range, median), and type and frequency of alarms distributed by care area. CONCLUSIONS: Infusion pump alarm data collected and analyzed in this study will be used to help establish a baseline of infusion pump alarm types and relative frequencies. Understanding the incidences and characteristics of infusion pump alarms will result in more informed quality improvement recommendations to decrease and/or modify infusion pump alarms, and potentially reduce clinical staff alarm fatigue and improve patient safety. . REGISTERED REPORT IDENTIFIER: RR1-10.2196/10446.

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.

How this classification was reachedexpand

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: Observational
GenreCandidate signal: Protocol · Consensus signal: Protocol
Teacher disagreement score0.313
Threshold uncertainty score0.334

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
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.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.432
GPT teacher head0.630
Teacher spread0.198 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designObservational
Domainnot available
GenreProtocol

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations3
Published2018
Admission routes1
Has abstractyes

Explore more

Same venueJMIR Research ProtocolsSame topicHealthcare Technology and Patient MonitoringFrench-language works237,207