A cohort study on physician documentation and the accuracy of administrative data coding to improve passive surveillance of transient ischaemic attacks
Bibliographic record
Abstract
BACKGROUND: Administrative health data are valuable in health research and disease surveillance, but have low to moderate sensitivity in identifying transient ischaemic attacks (TIA) in the emergency department (ED). We aimed to identify the predictors of coding accuracy for TIA. METHODS: The study population was obtained from two ongoing studies on the diagnosis of TIA, minor stroke and stroke mimic. ED charts were manually reviewed by a stroke neurologist to obtain the clinical diagnosis, patient characteristics and content of physician documentation. Administrative data codes were compared with the chart-adjudicated diagnosis to determine cases of misclassification by administrative data. Univariable regression was used to evaluate candidate predictors of disagreement, and the significant variables were tested in a multivariable model to obtain an adjusted estimate of effect. RESULTS: Among 417 patients (39.1% TIA, 37.2% minor stroke and 23.7% stroke mimics), there were 122 cases of disagreement between adjudications and administrative data codes for the diagnosis of TIA. The majority of disagreement (n=103/122, 84.4%) arose from adjudicated TIA cases that were misclassified as non-TIA in administrative data coding. There were 78 (18.7%) charts with documented uncertain diagnosis, and 73 (17.5%) charts had no definite diagnosis. The relative risk of disagreement between chart adjudication and administrative data coding when the final diagnosis was uncertain or absent was 1.82(1.36, 2.44) and the risk difference was 18.5%. Multivariable logistic regression analyses confirmed this association using different case definition algorithms. CONCLUSIONS: In suspected patients with TIA and minor stroke presenting to the ED, physician documentation was the dominant factor in coding accuracy, supporting the concept that physicians are active participants in administrative data coding. Strategies to improve chart documentation are predicted to have a positive effect on coding accuracy.
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.010 | 0.023 |
| Meta-epidemiology (narrow) | 0.000 | 0.001 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.002 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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".