Myeloid Classification Pipeline
Complete diagnostic logic for AML, CML, MDS, CMML, and ELN risk — WHO 2022, ICC 2022 & ELN 2024
AMLCMLMDSCMML
High-Level Orchestration Flow
Every report enters the AML classifier first. Based on sentinels and intercept checks, the orchestrator routes to CML, MDS, or CMML.
Orchestration Steps
| Step | Check | Result | disease_type |
|---|---|---|---|
| 1 | Run AML classifier | — | — |
| 2 | AML returned error? | Return error | AML |
| 3 | BCR::ABL1+ with blasts <20%? | Run CML classifier | CML |
| 4 | AML result is definitive? | Return AML label | AML |
| 5 | Run MDS classifier | — | — |
| 6 | MDS returned CMML sentinel? | Check for CMML data | — |
| 6a | — CMML data present | Run CMML classifier | CMML |
| 6b | — CMML data missing | Return sentinel to UI | CMML |
| 7 | Otherwise | Return MDS label | MDS |
Sentinel Labels
These exact strings drive routing decisions in the orchestrator:
| Sentinel | Source | Routes to |
|---|---|---|
Not AML, consider MDS classification | AML classifier | MDS classifier |
Needs erythroid confirmation | AML classifier | MDS (ICC only) or UI |
Needs MDS confirmation | MDS classifier | UI (request confirmation) |
Needs CMML confirmation | MDS confirmation gate | CMML classifier (if data) or UI |
Needs CEBPA confirmation | AML classifier | UI (request bZIP status) |
Error: ... | Any classifier | Returned immediately |