Alberta's Data and Analytic Strategy: Leveraging Linked Data to Drive Innovation
Bibliographic record
Abstract
BackgroundThe Province of Alberta, Canada, maintains a mature data environment with linkable administrative and clinical data dating back up to 30 years. Alberta has a single payer, publicly funded and administered, universal health system, which maintains multiple administrative data sets. Main AimThe main aim of the strategy is to fully maximize the data assets in the province to drive health system health system innovation, with a focus on improving health outcomes and quality of life. Methods/ApproachThe Alberta Ministry of Health has created the Secondary Use Data Access (SUDA) initiative to leverage its administrative health data. SUDA envisions strengthening partnerships between the public and private sectors through two main data access approaches. The first is direct access to de-identified data held within the Alberta Health data warehouse by key health system stakeholders (e.g. academic institutions, professional associations, regulatory colleges). The second is indirect access to private and not-for-profit organizations, using a data access safe haven (DASH) approach. Indirect access is achieved through private sector investments to a trusted third party that hires analysts placed within the Ministry of Health offices. ResultsStaffing agreements and privacy impact assessments are in place. Indirect access includes a multiple stakeholder steering committee to vet and prioritize projects. Private and not-for-profit stakeholders do not have access to raw data, but rather receive access to aggregated data and statistical models. All data disclosures are done by Ministry staff to ensure compliance with Alberta's Health Information Act. Direct access has been established for one professional organization and one academic institution, with access restricted to de-identified data. ConclusionThe Secondary Use Data Access initiative uses a safe haven approach to leveraging data to provide a more secure approach to data access. It reduces the need to provision data outside of the data warehouse while improving timely access to data. The approach provides assurances that people's health information is held secure, while also being used to create health system improvements.
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.064 | 0.125 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.010 | 0.014 |
| Science and technology studies | 0.007 | 0.006 |
| Scholarly communication | 0.020 | 0.006 |
| Open science | 0.006 | 0.015 |
| Research integrity | 0.003 | 0.004 |
| Insufficient payload (model declined to judge) | 0.008 | 0.003 |
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 source (direct Gemma or distilled Codex), 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".