MétaCan
Menu
Back to cohort
Record W2123089480 · doi:10.1177/1460458207079836

Evaluation of accuracy of drug interaction alerts triggered by two electronic medical record systems in primary healthcare

2007· article· en· W2123089480 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueHealth Informatics Journal · 2007
Typearticle
Languageen
FieldHealth Professions
TopicElectronic Health Records Systems
Canadian institutionsNova Scotia Health Research FoundationCanadian Foundation for Healthcare ImprovementDalhousie University
FundersCanadian Institutes of Health ResearchHealth CanadaResearch Nova ScotiaCanadian Health Services Research Foundation
KeywordsWorkflowClinical decision support systemComputer scienceElectronic medical recordAdverse drug eventMedical recordDrugHealth careMedicineMedical emergencyDecision support systemData miningDatabase

Abstract

fetched live from OpenAlex

This article presents a study to evaluate the accuracy of drug interaction (DI) alerts triggered by two electronic medical record (EMR) systems in primary healthcare. A scenario-based software architecture analysis methodology (SAAM) was used with drug-drug interaction (DDI) pairs in hypothetical patient scenarios. A literature search identified common drugs used in the management of conditions in the elderly population. Three reference programs determined the level of severity of drug interactions, and a common severity rating scale was adapted. The EMR systems showed a limited potential to identify 'severe' clinically significant DDIs and considerable probability for triggering spurious alerts. This may explain the overriding of DI alerts and the interruption of the workflow of users of EMR systems. Reasons for EMR system deficiency included unavailable updates or programming, database functioning discrepancies, and controversies in the clinical evidence.

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.100
metaresearch head score (Gemma)0.003
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Meta-epidemiology (narrow), Research integrity
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Other design · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.835
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.1000.003
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.004
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.087
GPT teacher head0.489
Teacher spread0.402 · 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