Linking primary care EMR data and administrative data in Alberta, Canada: experiences, challenges, and potential solutions
Bibliographic record
Abstract
IntroductionAdministrative data are commonly used for a variety of secondary purposes. Although they lack clinical detail and risk factor information, linkage to primary care electronic medical records (EMR) could fill this gap. Primary care EMRs are a relatively new data source available in Alberta and thus, EMR-administrative linkages are novel.
 Objectives and ApproachTo describe the process undertaken for linking de-identified primary care EMR data from two regional Alberta networks of the Canadian Primary Care Sentinel Surveillance Network (CPCSSN) with administrative data (hospital admissions, emergency department visits, pharmacy information) from Alberta Health Services Analytics, specifically as it relates to a study on patients with complex, chronic diseases. As this linkage process is new in Alberta, we will describe the challenges encountered and possible solutions to inform future data linkage for research studies.
 ResultsLinkage steps: 1) approval from research ethics board and individual CPCSSN providers as data custodians; 2) notify Privacy Commissioner on behalf of custodian; 3) send linking key (CPCSSN patient ID, EMR ID) from regional database to Analytics; 4) send linking files (patient personal health number [PHN], EMR ID) from custodian’s EMR system to Analytics; 5) match unique EMR ID from linking key and clinic linking files; 6) PHN from clinic linking file mapped to administrative data; 7) data de-identified before transferring to secure repository; administrative data matched to EMR data using CPCSSN ID.
 Challenges: obtaining individual provider consent for each study; sampling bias; delays/issues generating clinic linkage file; mismatch between patients in clinic \& regional linking files.
 Current and potential solutions will be discussed during the presentation.
 Conclusion/ImplicationsAs primary care EMR and administrative data become more routinely linked and accepted, the process will become more efficient and streamlined. These data will contribute to a better understanding of patients and their care in Alberta.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.006 | 0.003 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.008 |
| Open science | 0.008 | 0.007 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
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; a candidate call from one teacher head, not a consensus.
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".