Methodological Challenges when Using Routinely Collected Health Data for Research: A scoping review.
Bibliographic record
Abstract
Routinely collected health data (RCD) including electronic health records, disease registries, health administrative data and wearables data are not specifically collected for research purposes. Analysis of these data poses unique methodological challenges that must be addressed when conducting research, particularly as availability and use increase. This scoping review aimed to identify methodological challenges in research using RCD from existing literature (registered protocol: https://doi.org/10.17605/OSF.IO/EBM4D). We searched 6 electronic databases, including medical, health economics, nursing and psychology research databases, between Jan 2015 and Jan 2023, combining multiple “RCD” and “research” search terms (e.g., epidemiologic, informatics, pharmaceutical research). After screening abstracts and full-texts, we doubly extracted methodological themes, categorizing them into different study stages. We screened more than 23,000 records and included 430 papers. Bias and confounding were the most common methodological issues identified, discussed in relation to both study design and data analysis. Data quality, including data accuracy, validation, completeness, timeliness and cleaning, also posed substantial challenges, particularly during data processing stage. Record linkage and conducting analyses using distributed health networks also pose unique methodological challenges. Heterogeneity, incorporating social determinants of health and statistical models that address methodological challenges are also described in the literature. External validity and reporting are important considerations for RCD research. Our review identified several methodological challenges facing researchers using RCD. These issues should be addressed to ensure methodologically sound research. These findings will inform the development of a standardized protocol template and accompanying educational platform aimed at enhancing methodological quality and transparency when conducting research using RCD.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.399 | 0.706 |
| Meta-epidemiology (narrow) | 0.003 | 0.004 |
| Meta-epidemiology (broad) | 0.009 | 0.010 |
| Bibliometrics | 0.037 | 0.041 |
| Science and technology studies | 0.004 | 0.008 |
| Scholarly communication | 0.015 | 0.017 |
| Open science | 0.008 | 0.010 |
| Research integrity | 0.009 | 0.006 |
| Insufficient payload (model declined to judge) | 0.004 | 0.001 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; the direct Gemma label and the distilled Codex classifier agree on what is shown here.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".