Optimal strategy to identify incidence of diagnostic of diabetes using administrative data
Bibliographic record
Abstract
BACKGROUND: Accurate estimates of incidence and prevalence of the disease is a vital step toward appropriate interventions for chronic disease like diabetes. A growing body of scientific literature is now available on producing accurate information from administrative data. Advantages of use of administrative data to determine disease incidence include feasibility, accessibility and low cost, but straightforward use of administrative data can produce biased information on incident cases of chronic disease like diabetes. The present study aimed to compare criteria for the selection of diabetes incident cases in a medical administrative database. METHODS: An exhaustive retrospective cohort of diabetes cases was constructed for 2002 using the Canadian National Diabetes Surveillance System case definition (one hospitalization or two physician claims with a diagnosis of diabetes over a 2-year period) with the Quebec health service database. To identify previous occurrence of diabetes in the database, a five-year observation period was evaluated using retrograde survival function and kappa agreement. The use of NDSS case definition to identify incident cases was compared to a single occurrence of an ICD-9 code 250 in the records using the McNemar test. RESULTS: Retrograde survival function showed that the probability of being a true incident case after a 5-year diabetes-free observation period was almost constant and near 0.14. Agreement between 10 years (maximum period) and 5 years and more diabetes-free observation periods were excellent (kappa > 0.9). Respectively 41,261 and 37,473 incident cases were identified using a 5-year diabetes-free observation period with NDSS definition and using a single ICD-9 code 250. CONCLUSION: A 5-year diabetes-free observation period was a conservative time to identify incident cases in an administrative database using one ICD-9 code 250 record.
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.021 | 0.089 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.002 | 0.001 |
| Bibliometrics | 0.008 | 0.003 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.002 | 0.001 |
| Open science | 0.001 | 0.002 |
| 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".