Development of algorithms to identify individuals with Neurofibromatosis type 1 within administrative data and electronic medical records in Ontario, Canada
Bibliographic record
Abstract
BACKGROUND: There is limited population-based data on Neurofibromatosis type 1 (NF1) in North America. We aimed to develop and validate algorithms using administrative health data and electronic medical records (EMRs) to identify individuals with NF1 in Ontario, Canada. METHODS: We conducted an electronic free-text search of 15 commonly-used terms related to NF1 in the Electronic Medical Records Primary Care Database. Records were reviewed by two trained abstractors who classified them as confirmed, possible, and not NF1. An investigator with clinical expertise performed final NF1 classification. Patients were classified as confirmed if there was a documented diagnosis, meeting NIH criteria. Patients were classified as possible if (1) NF1 was recorded in the cumulative patient profile, but no clinical information to support the diagnosis; (2) only one criterion for diagnosis (e.g. child of confirmed case) but no further data to confirm or rule out. We tested different combinations of outpatient and inpatient billing codes, and applied a free-text search algorithm to identify NF1 cases in administrative data and EMRs, respectively. RESULTS: Of 273,440 eligible patients, 2,058 had one or more NF1 terms in their medical records. The terms "NF", "café-au-lait", or "sheath tumour" were constrained to appear in combination with another NF1 term. This resulted in 837 patients: 37 with possible and 71 with confirmed NF1. The population prevalence ranged from 1 in 3851 (confirmed NF1) to 1 in 2532 (possible and confirmed NF1). Billing code algorithms had poor performance, with overall low PPV (highest being 71%). The accuracy of the free-text EMR algorithm in identifying patients with NF1 was: sensitivity 85% (95% CI 74-92%), specificity 100% (95% CI 100-100%), positive predictive value 80% (95% CI 69-88%), negative predictive value 100% (95% CI 100-100%), and false positive rate 20% (95% CI 11-33%). Of false positives, 53% were possible NF1. CONCLUSIONS: A free-text search algorithm within the EMR had high sensitivity, specificity and predictive values. Algorithms using billing codes had poor performance, likely due to the lack of NF-specific codes for outpatient visits. While NF1 ICD-9 and 10 codes are used for hospital admissions, only ~ 30% of confirmed NF1 cases had a hospitalization associated with an NF1 code.
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.005 | 0.029 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.006 | 0.006 |
| Science and technology studies | 0.002 | 0.001 |
| Scholarly communication | 0.003 | 0.001 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 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; 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".