MétaCan
Menu
Retour à la cohorte
Enregistrement W2137967128 · doi:10.1197/jamia.m2606

A Randomized Trial of the Effectiveness of On-demand versus Computer-triggered Drug Decision Support in Primary Care

2008· article· en· W2137967128 sur OpenAlex

Pourquoi ce travail est dans la base

Une base qui oublie comment elle a trouvé un travail ne peut pas être vérifiée. Voici les voies qui ont admis celui-ci.

affAu moins un auteur déclare une institution canadienne dans l'instantané OpenAlex épinglé.

Notice bibliographique

RevueJournal of the American Medical Informatics Association · 2008
Typearticle
Langueen
DomaineHealth Professions
ThématiqueElectronic Health Records Systems
Établissements canadiensMcGill University
Organismes subventionnairesnon disponible
Mots-clésMedicineRandomized controlled trialMedical prescriptionClinical decision support systemDecision support systemDrugPersonalizationMedical emergencyCluster (spacecraft)Cluster randomised controlled trialEmergency medicineIntensive care medicineData miningComputer scienceInternal medicineNursingPsychiatry

Résumé

récupéré en direct d'OpenAlex

OBJECTIVES: Prescribing alerts generated by computerized drug decision support (CDDS) may prevent drug-related morbidity. However, the vast majority of alerts are ignored because of clinical irrelevance. The ability to customize commercial alert systems should improve physician acceptance because the physician can select the circumstances and types of drug alerts that are viewed. We tested the effectiveness of two approaches to medication alert customization to reduce prevalence of prescribing problems: on-physician-demand versus computer-triggered decision support. Physicians in each study condition were able to preset levels that triggered alerts. DESIGN: This was a cluster trial with 28 primary care physicians randomized to either automated or on-demand CDDS in the MOXXI drug management system for 3,449 of their patients seen over the next 6 months. MEASUREMENTS: The CDDS generated alerts for prescribing problems that could be customized by severity level. Prescribing problems included dosing errors, drug-drug, age, allergy, and disease interactions. Physicians randomized to on-demand activated the drug review when they considered it clinically relevant, whereas physicians randomized to computer-triggered decision support viewed all alerts for electronic prescriptions in accordance with the severity level they selected for both prevalent and incident problems. Data from administrative claims and MOXXI were used to measure the difference in the prevalence of prescribing problems at the end of follow-up. RESULTS: During follow-up, 50% of the physicians receiving computer-triggered alerts modified the alert threshold (n = 7), and 21% of the physicians in the alert-on-demand group modified the alert level (n = 3). In the on-demand group 4,445 prescribing problems were identified, 41 (0.9%) were seen by requested drug review, and in 31 problems (75.6%) the prescription was revised. In comparison, 668 (10.3%) of the 6,505 prescribing problems in the computer-triggered group were seen, and 81 (12.1%) were revised. The majority of alerts were ignored because the benefit was judged greater than the risk, the interaction was known, or the interaction was considered clinically not important (computer-triggered: 75.8% of 585 ignored alerts; on-demand: 90% of 10 ignored alerts). At the end of follow-up, there was a significant reduction in therapeutic duplication problems in the computer-triggered group (odds ratio 0.55; p = 0.02) but no difference in the overall prevalence of prescribing problems. CONCLUSION: Customization of computer-triggered alert systems is more useful in detecting and resolving prescribing problems than on-demand review, but neither approach was effective in reducing prescribing problems. New strategies are needed to maximize the use of drug decision support systems to reduce drug-related morbidity.

Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.

Prédiction distillée sur la base complète

Imitation des enseignants

Ni prévalence calibrée, ni vérité terrain. Validation humaine à venir. Apprise à partir de 10 348 étiquettes directes de Codex et de 10 348 étiquettes directes de Gemma. Le mode candidate est l'union des têtes enseignantes seuillées; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont ni des étiquettes humaines ni des étiquettes directes de modèles de pointe.

score de la tête « metaresearch » (Codex)0,020
score de la tête « metaresearch » (Gemma)0,011
Version: codex-gemma-dda1882f352aStatut de validation: machine_predicted_unvalidated
Catégories candidatesMétarecherche
Catégories consensuellesaucune
DomaineSignal candidat: aucune · Signal consensuel: aucune
Devis d'étudeSignal candidat: Essai randomisé · Signal consensuel: Essai randomisé
GenreSignal candidat: Empirique · Signal consensuel: Empirique
Score de désaccord entre enseignants0,021
Score d'incertitude au seuil0,998

Scores Codex et Gemma par catégorie

CatégorieCodexGemma
Métarecherche0,0200,011
Méta-épidémiologie (sens strict)0,0000,000
Méta-épidémiologie (sens large)0,0010,000
Bibliométrie0,0000,001
Études des sciences et des technologies0,0000,000
Communication savante0,0000,000
Science ouverte0,0010,000
Intégrité de la recherche0,0000,001
Charge utile insuffisante (le modèle a refusé de juger)0,0000,000

Scores machine (provisoires)

Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.

Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.

Tête enseignante Opus0,020
Tête enseignante GPT0,375
Écart entre enseignants0,355 · la distance entre les deux têtes enseignantes sur ce seul travail
Statut de validationscore_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découle