Using your electronic medical record for research: a primer for avoiding pitfalls
Bibliographic record
Abstract
In Canada, use of electronic medical records (EMRs) among primary health care (PHC) providers is relatively low. However, it appears that EMRs will eventually become more ubiquitous in PHC. This represents an important development in the use of health care information technology as well as a potential new source of PHC data for research. However, care in the use of EMR data is required. Four years ago, researchers at the Centre for Studies in Family Medicine, The University of Western Ontario created an EMR-based research project, called Deliver Primary Health Care Information. Implementing this project led us to two conclusions about using PHC EMR data for research: first, additional time is required for providers to undertake EMR training and to standardize the way data are entered into the EMR and second, EMRs are designed for clinical care, not research. Based on these experiences, we offer our thoughts about how EMRs may, nonetheless, be used for research. Family physician researchers who intend to use EMR data to answer timely questions relevant to practice should evaluate the possible impact of the four questions raised by this paper: (i) why are EMR data different?; (ii) how do you extract data from an EMR?; (iii) where are the data stored? and (iv) what is the data quality? In addition, consideration needs to be given to the complexity of the research question since this can have an impact on how easily issues of using EMR data for research can be overcome.
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.412 | 0.556 |
| Meta-epidemiology (narrow) | 0.002 | 0.004 |
| Meta-epidemiology (broad) | 0.005 | 0.004 |
| Bibliometrics | 0.013 | 0.012 |
| Science and technology studies | 0.012 | 0.061 |
| Scholarly communication | 0.036 | 0.094 |
| Open science | 0.010 | 0.031 |
| Research integrity | 0.032 | 0.072 |
| Insufficient payload (model declined to judge) | 0.006 | 0.009 |
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".