Machine Learning for JAK2 Mutation Prediction in Erythrocytosis: Context Matters
Notice bibliographique
Résumé
To the Editor.—Schifman et al1 present a machine learning (ML) classifier using blood count parameters and erythropoietin (EPO) levels to predict JAK2 mutations in patients with elevated hemoglobin. Their contribution to this evolving area is commendable. However, we wish to highlight several methodologic and practical issues that limit the relevance and clinical applicability of this approach.First, the authors define erythrocytosis by using hemoglobin thresholds greater than 15 g/dL for females and greater than 17 g/dL for males—values that diverge from World Health Organization and International Consensus Classification criteria (>16.0 g/dL and >16.5 g/dL, respectively).2,3 The female threshold in particular may capture individuals who would not be evaluated for erythrocytosis under standard diagnostic frameworks. As a result, the model may be trained on a population that differs substantially from those typically referred to hematology clinics.Second, the inclusion of EPO introduces practical constraints, with turnaround times exceeding 1 week in most laboratories. As the authors note, EPO has limited standalone diagnostic utility,4 further underscored by the recent discovery of hepatic-like EPO variants that cause erythrocytosis despite normal EPO levels.5 While EPO may add value combined with parameters, its use may necessitate additional clinic visits, introducing diagnostic delays and limiting timely decision support. In contrast, the JAKPOT rule6 relies only on parameters available at the initial clinic visit, enabling real-time decision-making about JAK2 testing.A more fundamental concern lies in the nature of the training and validation data. The models were trained on Veterans Affairs registry data, which may represent an older population and be validated with an independent hospital laboratory system. While large, there is lack of clinical context, particularly referral indication, inpatient versus outpatient setting, and final diagnosis. Further, the training cohort was overwhelmingly male (8190 of 8479; 96.6%), which, combined with the nonstandard hemoglobin threshold for women, raises questions about the model’s applicability to female patients in real-world practice.1 In contrast, the JAKPOT cohort comprised patients referred for elevated hemoglobin levels in outpatient internal medicine and hematology clinics,6 more closely reflecting the population in which such tools are likely to have the greatest clinical impact.While both the ML model and the JAKPOT rule achieved 100% sensitivity and negative predictive value in validation, the authors cite greater test reduction with their model (89% versus 50%) as a key advantage. It should be noted that the population analyzed had a lower JAK2 mutation prevalence (2.7%) than that observed in real-world hematology clinics,7 raising further questions about the model’s applicability.Machine learning holds promise to support clinical decision-making in hematology-oncology, where there is a need for tools to improve diagnostic stewardship.8 Schifman et al1 take an important step in this direction and the results presented may be promising, but any clinical benefit must be verified in larger data sets with age, sex, and JAK2 characteristics reflective of anticipated clinical application. Further, to be truly useful such tools must be developed and validated in clinically relevant populations and rely on variables that are readily available to support real-time decision-making. Toward these ends, simpler rules like JAKPOT—now undergoing prospective validation (NCT06785870), essential before adoption of any such tool—may offer a more practical path forward to support JAK2 testing decisions in everyday hematology practice.
Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.
Comment cette classification a été obtenuedéplier
Prédiction machine sur la base complète
Imitation des enseignantsNi prévalence calibrée, ni vérité terrain. Validation humaine à venir. Le volet Gemma est une étiquette directe du modèle pour chaque travail de la base, lue sur la notice réduite au titre. Le volet Codex est un classifieur appris des 10 348 étiquettes directes de Codex et calibré sur les taux pondérés de l'échantillon; les champs sans appui suffisant ne portent aucun appel Codex. Le mode candidate est l'union des deux volets; le consensus est leur intersection. Ces sorties portent le statut machine_predicted_unvalidated et ne sont pas des étiquettes humaines.
Scores du classifieur distillé par catégorie (deux têtes)
| Catégorie | Codex | Gemma |
|---|---|---|
| Métarecherche | 0,008 | 0,081 |
| Méta-épidémiologie (sens strict) | 0,002 | 0,001 |
| Méta-épidémiologie (sens large) | 0,002 | 0,001 |
| Bibliométrie | 0,001 | 0,001 |
| Études des sciences et des technologies | 0,001 | 0,002 |
| Communication savante | 0,005 | 0,004 |
| Science ouverte | 0,003 | 0,001 |
| Intégrité de la recherche | 0,008 | 0,016 |
| Charge utile insuffisante (le modèle a refusé de juger) | 0,008 | 0,005 |
Scores machine (provisoires)
Les deux têtes enseignantes du modèle étudiant, lues sur ce travail. Un score ordonne la base pour la relecture; il n'affirme jamais une catégorie, et le statut de validation accompagne chaque rangée tel quel.
Scores de référence d'un modèle non mature (critères de maturité non atteints, 7 itérations). Un score ordonne; il n'affirme jamais une catégorie.
score_only:v0-immature-baseline · tel quel depuis la passe de notation : score_only signifie que le nombre peut ordonner les travaux, et qu'aucune étiquette de catégorie n'en découleClassification
machine, non validéePrédiction automatique; un appel candidat d’une seule source (Gemma direct ou Codex distillé), pas un consensus.
Le détail, modèle par modèle et score par score, se trouve en fin de page sous « Comment cette classification a été obtenue ».