Cross-National Comparative Performance of Three Versions of the ICD-10 Charlson Index
Bibliographic record
Abstract
OBJECTIVE: The Charlson comorbidity index has been widely used for risk adjustment in outcome studies using administrative health data. Recently, 3 International Statistical Classification of Diseases, Tenth Revision (ICD-10) translations have been published for the Charlson comorbidities. This study was conducted to compare the predictive performance of these versions (the Halfon, Sundararajan, and Quan versions) of the ICD-10 coding algorithms using data from 4 countries. METHODS: Data from Australia (N = 2000-2001, max 25 diagnosis codes), Canada (N = 2002-2003, max 16 diagnosis codes), Switzerland (N = 1999-2001, unlimited number of diagnosis codes), and Japan (N = 2003, max 11 diagnosis codes) were analyzed. Only the first admission for patients age 18 years and older, with a length of stay of >/=2 days was included. For each algorithm, 2 logistic regression models were fitted with hospital mortality as the outcome and the Charlson individual comorbidities or the Charlson index score as independent variables. The c-statistic (representing the area under the receiver operating characteristic curve) and its 95% probability bootstrap distribution were employed to evaluate model performance. RESULTS: Overall, within each population's data, the distribution of comorbidity level categories was similar across the 3 translations. The Quan version produced slightly higher median c-statistics than the Halfon or Sundararajan versions in all datasets. For example, in Japanese data, the median c-statistics were 0.712 (Quan), 0.709 (Sundararajan), and 0.694 (Halfon) using individual comorbidity coefficients. In general, the probability distributions between the Quan and the Sundararajan versions overlapped, whereas those between the Quan and the Halfon version did not. CONCLUSIONS: Our analyses show that all of the ICD-10 versions of the Charlson algorithm performed satisfactorily (c-statistics 0.70-0.86), with the Quan version showing a trend toward outperforming the other versions in all data sets.
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.017 | 0.054 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.000 | 0.001 |
| 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".