Use of Epic Electronic Health Record System for Health Care Research: Scoping Review
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.
Notice bibliographique
Résumé
BACKGROUND: Electronic health records (EHRs) enable health data exchange across interconnected systems from varied settings. Epic is among the 5 leading EHR providers and is the most adopted EHR system across the globe. Despite its global reach, there is a gap in the literature detailing how EHR systems such as Epic have been used for health care research. OBJECTIVE: The objective of this scoping review is to synthesize the available literature on use cases of the Epic EHR for research in various areas of clinical and health sciences. METHODS: We used established scoping review methods and searched 9 major information repositories, including databases and gray literature sources. To categorize the research data, we developed detailed criteria for 5 major research domains to present the results. RESULTS: We present a comprehensive picture of the method types in 5 research domains. A total of 4669 articles were screened by 2 independent reviewers at each stage, while 206 articles were abstracted. Most studies were from the United States, with a sharp increase in volume from the year 2015 onwards. Most articles focused on clinical care, health services research and clinical decision support. Among research designs, most studies used longitudinal designs, followed by interventional studies implemented at single sites in adult populations. Important facilitators and barriers to the use of Epic and EHRs in general were identified. Important lessons to the use of Epic and other EHRs for research purposes were also synthesized. CONCLUSIONS: The Epic EHR provides a wide variety of functions that are helpful toward research in several domains, including clinical and population health, quality improvement, and the development of clinical decision support tools. As Epic is reported to be the most globally adopted EHR, researchers can take advantage of its various system features, including pooled data, integration of modules and developing decision support tools. Such research opportunities afforded by the system can contribute to improving quality of care, building health system efficiencies, and conducting population-level studies. Although this review is limited to the Epic EHR system, the larger lessons are generalizable to other EHRs.
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 enseignantsNi 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.
Scores Codex et Gemma par catégorie
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,157 | 0,025 |
| Méta-épidémiologie (sens strict) | 0,000 | 0,000 |
| Méta-épidémiologie (sens large) | 0,002 | 0,000 |
| Bibliométrie | 0,002 | 0,003 |
| Études des sciences et des technologies | 0,001 | 0,000 |
| Communication savante | 0,000 | 0,000 |
| Science ouverte | 0,002 | 0,001 |
| Intégrité de la recherche | 0,001 | 0,009 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,001 | 0,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.
score_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