Navigating Myelodysplastic and Myelodysplastic/Myeloproliferative Overlap Syndromes
Bibliographic record
Abstract
Myelodysplastic syndromes (MDS) and MDS/myeloproliferative neoplasms (MPNs) are clonal diseases that differ in morphologic diagnostic criteria but share some common disease phenotypes that include cytopenias, propensity to acute myeloid leukemia evolution, and a substantially shortened patient survival. MDS/MPNs share many clinical and molecular features with MDS, including frequent mutations involving epigenetic modifier and/or spliceosome genes. Although the current 2016 World Health Organization classification incorporates some genetic features in its diagnostic criteria for MDS and MDS/MPNs, recent accumulation of data has underscored the importance of the mutation profiles on both disease classification and prognosis. Machine-learning algorithms have identified distinct molecular genetic signatures that help refine prognosis and notable associations of these genetic signatures with morphologic and clinical features. Combined geno-clinical models that incorporate mutation data seem to surpass the current prognostic schemes. Future MDS classification and prognostication schema will be based on the portfolio of genetic aberrations and traditional features, such as blast count and clinical factors. Arriving at these systems will require studies on large patient cohorts that incorporate advanced computational analysis. The current treatment algorithm in MDS is based on patient risk as derived from existing prognostic and disease classes. Luspatercept is newly approved for patients with MDS and ring sideroblasts who are transfusion dependent after erythropoietic-stimulating agent failure. Other agents that address red blood cell transfusion dependence in patients with lower-risk MDS and the failure of hypomethylating agents in higher-risk disease are in advanced testing. Finally, a plethora of novel targeted agents and immune checkpoint inhibitors are being evaluated in combination with a hypomethylating agent backbone to augment the depth and duration of response and, we hope, improve overall survival.
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.001 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.003 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 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".