Building A Research Partnership Between Computer Scientists and Health Service Researchers for Access and Analysis of Population-Level Health Datasets
Bibliographic record
Abstract
IntroductionThere is widespread enthusiasm to improve health through the application of artificial intelligence and machine learning (AI/ML) methods to large population-level health datasets. Achieving this may require successful collaboration between institutions as well as between computer scientists (CS), machine learning researchers (MLR) and health service researchers (HSR). The objective is to describe lessons learned in creating the Health Artificial Data and Analysis Platform (HAIDAP) in Ontario, Canada.
 Objectives and ApproachA partnership between a HSR institute (ICES), an AI/ML institute (Vector) and a high-performance computing center (HPC4H) was initiated in 2017 to enable the application of AI/ML methods to population-level health data for the province of Ontario (population 14M). The HAIDAP was launched in 2019. We describe lessons learned (and being learned) following the HAIDAP’s launch.
 ResultsMajor learnings include: 1)importance of institutional partnerships and alignment with institutional strategies; 2)potential of joint institutional risk-sharing models; 3)need for scientific collaborations bridging disciplines around joint research projects; 4)sensitivity to different scientific cultures (e.g., academic prestige of conference proceedings for MLR vs journal publications for HSR; traditional statistical vs. ML model assumptions); 5)differences in research timeline expectations; 6)different experience with and expectations for access to de-identified routinely collected data (e.g., need for research ethics committee project approvals and privacy impact assessments); 7)developing data access models that enable greater flexibility (e.g. importing code or using open source tools); 8) broadening data access models to allow modern high-dimensional exploratory data analysis; 9)obtaining support of information/privacy regulator; 10)hardware is (relatively) easy part compared to other success factors.
 Conclusion / ImplicationsThe HAIDAP has enabled multi-disciplinary collaborations and novel AI/ML research of Ontario’s population-level health data. Collectively we have learned that additional effort is required to develop systems and processes enabling more efficient access to data and analytic tools for the analysis of administrative health data.
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.008 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.000 | 0.002 |
| Open science | 0.001 | 0.000 |
| 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".