MétaCan
Menu
Retour à la cohorte
Enregistrement W7115578257 · doi:10.1016/j.imu.2025.101725

Epic overhaul at a Canadian hospital: Pre-Post evaluation insights from physicians and medical residents

2025· article· en· W7115578257 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é.
fundUn bailleur canadien est enregistré sur le travail.
aboutLe titre ou le résumé porte un signal canadien du lexique géographique.

Notice bibliographique

RevueInformatics in Medicine Unlocked · 2025
Typearticle
Langueen
DomaineHealth Professions
ThématiqueElectronic Health Records Systems
Établissements canadiensUniversity of Ottawa
Organismes subventionnairesTelfer School of Management, University of OttawaUniversity of Ottawa
Mots-clésEPICDocumentationMedical recordDelivery systemElectronic medical recordPatient careQuality managementMedical care

Résumé

récupéré en direct d'OpenAlex

The implementation of Electronic Medical Records (EMRs) in hospitals offers potential benefits but often disrupts clinician workflows, affecting care delivery and outcomes. This study evaluates physicians' and medical residents’ perspectives on the impacts of introducing a new Epic system at a Canadian academic hospital. A pre-post evaluation design was conducted using physician and resident surveys before (T0) and 4- and 9-months post-implementation (T1, T2) that assessed technology use, satisfaction with training and system use, and EMR's perceived impact on care delivery, work practices and quality. Satisfaction with training and system use declined for both groups in the first four months (more sharply for residents) but several measures improved at T2 as users readjusted to the system. There was a significant increase in physicians’ daily computer use (4 h at T0 to 6 h at T1; P < . 001 ). Limited early benefits of the Epic system were observed and a decline in perceived improvement in clinical documentation (P = . 006 and .0012) , order entry (P = . 018 and .002) and patient safety (P = . 044 and .024) were reported at T1 for physicians and residents, respectively. Although some medical practice/work indicators improved by 9 months for physicians, the changes were not statistically significant; these benefits were not observed for residents at T2. Medical training was not significantly affected by the new Epic system either immediately or later post implementation. At T1, 83% of physicians reported that the new system sometimes or often improved the quality of care, as opposed to only 33% of residents; no significant improvements were noted at 9 months post implementation by both groups. Physicians and residents adapt differently to Epic and full system assimilation does not happen in one year. Early perceptions of Epic do not reflect its long-term potential, and meaningful benefits require prolonged stabilization periods for user satisfaction and efficiency gains. We caution hospital leaders not to rely heavily on a vendor-driven implementation, and recommend tailored training, rapid-cycle improvements, transparent communication, and monitoring of agreed-upon performance indicators to strengthen clinician engagement and support long-term success. • Epic implementation improved aspects of clinician workflows, but no quality-of-care impacts were reported up to 9 months. • Training satisfaction and system usability declined early with partial recovery by 9 months, underscoring adaptation challenges until stabilization. • Physicians reported the new system supported their work procedures as early as 4 months post-Epic implementation. • Epic mainly affected clinical documentation, orders entry, patient safety and flow. • Clinicians' adaptation varied, stressing the need for tailored training, rapid-cylce adjustments, and clear performance metrics.

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,002
score de la tête « metaresearch » (Gemma)0,004
Version: codex-gemma-dda1882f352aStatut de validation: machine_predicted_unvalidated
Catégories candidatesaucune
Catégories consensuellesaucune
DomaineSignal candidat: aucune · Signal consensuel: aucune
Devis d'étudeSignal candidat: Observationnel · Signal consensuel: Observationnel
GenreSignal candidat: Empirique · Signal consensuel: Empirique
Score de désaccord entre enseignants0,414
Score d'incertitude au seuil0,878

Scores Codex et Gemma par catégorie

CatégorieCodexGemma
Métarecherche0,0020,004
Méta-épidémiologie (sens strict)0,0000,000
Méta-épidémiologie (sens large)0,0010,000
Bibliométrie0,0010,001
Études des sciences et des technologies0,0010,000
Communication savante0,0000,000
Science ouverte0,0000,000
Intégrité de la recherche0,0010,001
Charge utile insuffisante (le modèle a refusé de juger)0,0010,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,022
Tête enseignante GPT0,414
Écart entre enseignants0,392 · 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