MétaCan
Menu
Back to cohort
Record W2107057736 · doi:10.1197/jamia.m3107

Overcoming Barriers to the Implementation of a Pharmacy Bar Code Scanning System for Medication Dispensing: A Case Study

2009· article· en· W2107057736 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

VenueJournal of the American Medical Informatics Association · 2009
Typearticle
Languageen
FieldHealth Professions
TopicElectronic Health Records Systems
Canadian institutionsUniversity of Toronto
FundersAgency for Healthcare Research and Quality
KeywordsVendorWorkflowPharmacyProcess (computing)Adaptation (eye)MedicineResistance (ecology)Health information technologyComputer scienceMedical educationProcess managementKnowledge managementNursingBusinessHealth carePsychology

Abstract

fetched live from OpenAlex

Technology has great potential to reduce medication errors in hospitals. This case report describes barriers to, and facilitators of, the implementation of a pharmacy bar code scanning system to reduce medication dispensing errors at a large academic medical center. Ten pharmacy staff were interviewed about their experiences during the implementation. Interview notes were iteratively reviewed to identify common themes. The authors identified three main barriers to pharmacy bar code scanning system implementation: process (training requirements and process flow issues), technology (hardware, software, and the role of vendors), and resistance (communication issues, changing roles, and negative perceptions about technology). The authors also identified strategies to overcome these barriers. Adequate training, continuous improvement, and adaptation of workflow to address one's own needs mitigated process barriers. Ongoing vendor involvement, acknowledgment of technology limitations, and attempts to address them were crucial in overcoming technology barriers. Staff resistance was addressed through clear communication, identifying champions, emphasizing new information provided by the system, and facilitating collaboration.

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.013
metaresearch head score (Gemma)0.005
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Qualitative · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.619
Threshold uncertainty score0.643

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0130.005
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0010.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.041
GPT teacher head0.480
Teacher spread0.439 · 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