Using Administrative Data to Ascertain True Cases of Muscular Dystrophy: Rare Disease Surveillance
Bibliographic record
Abstract
BACKGROUND: Administrative records from insurance and hospital discharge data sources are important public health tools to conduct passive surveillance of disease in populations. Identifying rare but catastrophic conditions is a challenge since approaches for maximizing valid case detection are not firmly established. OBJECTIVE: The purpose of our study was to explore a number of algorithms in which International Classification of Diseases, Ninth Revision, Clinical Modification (ICD-9-CM) codes and other administrative variables could be used to identify cases of muscular dystrophy (MD). METHODS: We used active surveillance to identify possible cases of MD in medical practices in neurology, genetics, and orthopedics in 5 urban South Carolina counties and to identify the cases that had diagnostic support (ie, true cases). We then developed an algorithm to identify cases based on a combination of ICD-9-CM codes and administrative variables from a public (Medicaid) and private insurer claims-based system and a statewide hospital discharge dataset (passive surveillance). Cases of all types of MD and those with Duchenne or Becker MD (DBMD) that were common to both surveillance systems were examined to identify the most specific administrative variables for ascertainment of true cases. RESULTS: Passive statewide surveillance identified 3235 possible cases with MD in the state, and active surveillance identified 2057 possible cases in 5 actively surveilled counties that included 2 large metropolitan areas where many people seek medical care. There were 537 common cases found in both the active and passive systems, and 260 (48.4%) were confirmed by active surveillance to be true cases. Of the 260 confirmed cases, 70 (26.9%) were recorded as DBMD. CONCLUSIONS: Accuracy of finding a true case in a passive surveillance system was improved substantially when specific diagnosis codes, number of times a code was used, age of the patient, and specialty provider variables were used.
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.009 | 0.031 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.005 | 0.003 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| 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 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".