Choosing a new CD4 technology: Can statistical method comparison tools influence the decision?
Bibliographic record
Abstract
BACKGROUND: Method comparison tools are used to determine the accuracy, precision, agreement, and clinical relevance of a new or improved technology versus a reference technology. Guidelines for the most appropriate method comparison tools as well as their acceptable limits are lacking and not standardized for CD4 counting technologies. METHODS: Different method comparison tools were applied to a previously published CD4 dataset (n = 150 data pairs) evaluating five different CD4 counting technologies (TruCOUNT, Dual Platform, FACSCount, Easy CD4, CyFlow) on a single specimen. Bland-Altman, percentage similarity, percent difference, concordance correlation, sensitivity, specificity and misclassification method comparison tools were applied as well as visualization of agreement with Passing Bablock and Bland-Altman scatter plots. RESULTS: The FACSCount (median CD4 = 245 cells/µl) was considered the reference for method comparison. An algorithm was developed using best practices of the most applicable method comparison tools, and together with a modified heat map was found useful for method comparison of CD4 qualitative and quantitative results. The algorithm applied the concordance correlation for overall accuracy and precision, then standard deviation of the absolute bias and percentage similarity coefficient of variation to identify agreement, and lastly sensitivity and misclassification rates for clinical relevance. CONCLUSION: Combining method comparison tools is more useful in evaluating CD4 technologies compared to a reference CD4. This algorithm should be further validated using CD4 external quality assessment data and studies with larger sample sizes. © 2017 International Clinical Cytometry Society.
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.342 | 0.527 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.003 | 0.003 |
| Bibliometrics | 0.005 | 0.005 |
| Science and technology studies | 0.002 | 0.004 |
| Scholarly communication | 0.009 | 0.005 |
| Open science | 0.004 | 0.004 |
| Research integrity | 0.003 | 0.004 |
| Insufficient payload (model declined to judge) | 0.004 | 0.002 |
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".