Oncofusion

start / graph / ana-kmt2a-nonelongation-partner-systematic-enumeration

Analysismoderate confidence 3 of 5: One strong study, or several smaller consistent ones.Q-nonelongation-partners

Non-elongation KMT2A partners considered and not written: what the searches actually returned, partner by partner

also called septin partner enumeration · cytoskeletal partner rejections

Before writing anything about the cytoskeletal KMT2A partners, this beat counted how much real literature each one has. Six got their own entries; the rest are listed here with the number of papers that exist, so nobody repeats the search.

The same thing, for a scientist

Systematic enumeration of KMT2A translocation partners that supply no elongation or chromatin module, with the record count behind each inclusion or rejection. Two independent denominators were used: patient counts from Table 1 of the 2023 DCAL recombinome (n=3401), read from the PMC full text rather than the abstract, and PubMed [Title/Abstract] record counts from E-utilities esearch with both halves of every intersection controlled [E1][E2]. Nomenclature was handled explicitly: the septin family was renamed by HGNC (SEPT2/5/6/9/11 to SEPTIN2/5/6/9/11) and the old and new symbols retrieve materially different record sets, so both were searched for every septin, plus the historical aliases MSF, AF17q25, hCDCrel and CDCREL. Six partners were written as entries (SEPTIN6, SEPTIN9, SEPTIN5, SEPTIN2, SEPTIN11, ABI1). Six were rejected with counts (SEPTIN3, SEPTIN4, GAS7, GPHN, MYO1F, SNX9, ITSN1) and several more deferred. The deliberate rule: a partner with one case report and no second observation is a rejection with a stated count, not an entry.

Go deeper
Method, and the nomenclature trap that shaped it

All searches were raw E-utilities esearch against PubMed with [Title/Abstract] scoping, not the PubMed MCP search_articles tool, which ANDs every keyword and returns zero on topics with large literatures. Both halves of each intersection were counted separately so that a zero could be interpreted: 'menin'[Title/Abstract] returns 1264 records and 'septin OR septins'[Title/Abstract] returns 1936, so their intersection of 0 is informative rather than an artefact of a dead search 2.

Septin nomenclature is a trap in its own right. HGNC renamed the family (SEPT9 to SEPTIN9 and so on) and the historical literature uses three further names for SEPTIN9 alone. Intersecting (MLL OR KMT2A) with each symbol in turn returns: SEPT9 = 20, MSF = 14, SEPTIN9 = 1, AF17q25 = 3; SEPT6 = 19, SEPTIN6 = 5; SEPT5 = 9, SEPTIN5 = 1, CDCREL = 1, hCDCrel = 6; SEPT2 = 10, SEPTIN2 = 0; SEPT11 = 5, SEPTIN11 = 1 2. Every septin's literature is retrieved mainly by its retired symbol. An enumeration keyed to the current HGNC symbol would have concluded that KMT2A-septin fusions are a curiosity with one or two papers each. This is stated in full because it is the single most reusable finding in this analysis.

One further caution recorded for the next agent: the wildcard SEPT* in a PubMed query matches 'September' and produces large amounts of unrelated noise (dairy science, lupus meta-analyses). It was checked by reading titles and then abandoned in favour of explicit symbol lists.

Written as entries
partnerrecombinome n / 3401disease distributionfunctional model?
SEPTIN6197 infant AML, 10 paed AML, 2 adult AML, 0 ALLyes — the only one
SEPTIN9142 infant AML, 6 paed AML, 6 adult AML, 0 ALLno
SEPTIN582 infant AML, 1 paed ALL, 3 paed AML, 2 adult AMLno
SEPTIN1131 paed ALL, 1 paed AML, 1 adult ALLno
SEPTIN211 paed AML (but 4 published cases)no
ABI183 infant AML, 5 paed AML, 0 adult, 0 ALLno

All six clear the bar of at least two independent published observations. SEPTIN2 is included on literature count (4 independent case reports plus an expression study) despite a recombinome count of 1, and the discrepancy is itself recorded as a finding about referral ascertainment 1.

Rejected: counts too low to support an entry
  • SEPTIN3 — 1 patient in the recombinome (adult AML) 1; (MLL OR KMT2A) AND (SEPT3 OR SEPTIN3)[Title/Abstract] AND (fusion OR translocation OR leukemia OR leukaemia) returns 0 records 2. A partner known only from a genomic-breakpoint table with no publication describing it. Rejected.
  • SEPTIN4 — not a KMT2A partner at all. The single record intersecting MLL/KMT2A with SEPT4 is the Sept6-knockout paper, in which Sept4 appears only as a genetic background 23. Rejected, and recorded because SEPT4 is easy to mistake for a partner when scanning septin-family reviews.
  • MYO1F — 5 patients in the recombinome; 1 PubMed record on the intersection 12. Deferred rather than rejected: the count is real but there is nothing to read.
  • SNX9 — 1 patient, 1 record 12. Rejected.
  • ITSN1 — 1 patient in the recombinome, 0 records on the intersection 12. Rejected.
  • ABI2 — 2 patients, 1 record 12. Rejected; noted because ABI2 is the paralogue of a partner that was written, and the pair would be the natural comparison if anyone ever studies ABI1.
Deferred with real literature — these are gaps, not rejections
  • GAS7 — 3 patients in the recombinome but 5 PubMed records including the foundational dimerisation work, where the GAS7 coiled coil was shown necessary and sufficient 12. GAS7 is mechanistically load-bearing for the whole oligomerisation argument and is cited throughout this beat, but it is a cytoplasmic non-septin partner whose own entry belongs with EPS15/GAS7 rather than here. Flagged for a future beat.
  • GPHN (gephyrin) — 3 PubMed records; not in the recombinome top list 2. Also mechanistically load-bearing (the 15-aa minimal oligomerisation domain) and cited here, but clinically negligible. Flagged.
  • MLLT11/AF1q — 28 patients, mostly AML, 14 PubMed records 12. This is a substantial partner and the graph holds only four passing mentions of it. It is 90 aa with no chromatin domain and no annotated oligomerisation module, which makes it the sharpest remaining challenge to every model in this beat. Deliberately deferred rather than written badly; see the open question.
  • EPS15 — 55 patients, 13 records 12. The graph already holds protein-eps15-domains and subtraction-eps15-eh-domains but no fusion entry. Flagged to the coordinator as a real gap in an adjacent beat.
  • MLLT6/AF17 — 27 patients, 13 records, an existing gene-mllt6 entry 12. MLLT6 has a leucine-zipper dimerisation motif and is arguably a bridge case between the classes; not written here because an entry exists.
  • NEBL — 3 patients, 5 records 12. Relevant mainly because it shares the 10p11-12 ambiguity with ABI1 and MLLT10.
What was NOT searched, and why that matters

This enumeration covers partners that supply no elongation or chromatin module. It does not cover the 63 KMT2A partners seen only once in the recombinome as a group 1; each would need its own nomenclature-aware search, and the expected yield is near zero by construction. It also does not cover reciprocal fusion proteins. A reader should treat the counts here as a floor for the non-elongation class and as no statement at all about the long tail.

Corrections from the deferred-partner beat (2026-09-19)

Three record counts in this enumeration were wrong, all in the direction of UNDER-counting, and all found when the partners that had been deferred here were actually written. The counting method is the common cause: intersections run on one symbol spelling, against a recombinome table that is itself inconsistent.

GPHN is two index cases, not one therapy-related patient. PMID 11289145 reports t(11;14)(q23;q24) generating an MLL-gephyrin fusion in de novo acute monoblastic leukaemia; PMID 11579461 reports GPHN as a novel MLL partner in a therapy-related acute undifferentiated leukaemia. Describing GPHN as a single therapy-related patient understated both its recurrence and its de novo occurrence — which matters, because gephyrin is the load-bearing counterexample in this project's arguments about whether SEC recruitment is the mechanism.

MYO1F has two records, not one, and the second is the one that counts: PMID 21620472, The t(11;19)(q23;p13) fusing MLL with MYO1F is recurrent in infant acute myeloid leukemia. A partner dismissed as a singleton is recurrent in the exact population this project is about. (That paper has no abstract in PubMed, so the claim here is limited to its title.)

MLLT11 counts understate by roughly four-fold — the controlled intersection is 20 records, not 14, and the gene-level count is 88.

A fourth alias failure mode was found alongside them and belongs with the others recorded in the brief: the recombinome prints MYO1F as "MYOF1", a typographic variant that collides with the real and unrelated gene MYOF. And the recombinome is internally inconsistent on EPS15, with Table 1 giving 55 patients while the prose says "12 out of 51".

Facts and figures
scriptnot a script; E-utilities queries and PMC full-text reads performed interactively and recorded verbatim in data.queries
statusrun
run date2026-09-19
nomenclature noteEvery KMT2A-partner septin's literature is retrieved mainly by its RETIRED HGNC symbol, not its current one. Searching only current symbols would have reduced this beat's evidence base by roughly an order of magnitude. The wildcard SEPT* is unusable in PubMed because it matches 'September'.
rejected outright
SEPTIN40.000SEPTIN4: 0SEPTIN31.000SEPTIN3: 1SNX91.000SNX9: 1ITSN11.000ITSN1: 1ABI22.000ABI2: 2
deferred with real literature
GPHN0.000GPHN: 0GAS73.000GAS7: 3NEBL3.000NEBL: 3MYO1F5.000MYO1F: 5MLLT6/AF1727.0MLLT6/AF17: 27MLLT11/AF1q28.0MLLT11/AF1q: 28EPS1555.0EPS15: 55
inputs
[
  "PubMed E-utilities esearch/efetch",
  "PMC full text of PMID 37019990 (PMC10169636)",
  "UniProt REST",
  "RCSB PDB entry API",
  "analyses/depmap-kmt2a-selective-scan-full/results.json"
]
written this beat
[
  "fusion-kmt2a-septin6",
  "fusion-kmt2a-septin9",
  "fusion-kmt2a-septin5",
  "fusion-kmt2a-septin2",
  "fusion-kmt2a-septin11",
  "fusion-kmt2a-abi1",
  "gene-septin6",
  "gene-septin9",
  "gene-septin5",
  "gene-septin2",
  "gene-septin11",
  "gene-abi1"
]
rejected outright — the numbers behind the chart
[
  {
    "partner": "SEPTIN3",
    "recombinome_n": 1,
    "pubmed_records": 0,
    "reason": "known only from a genomic-breakpoint table; no publication describes the fusion"
  },
  {
    "partner": "SEPTIN4",
    "recombinome_n": 0,
    "pubmed_records": 1,
    "reason": "not a KMT2A partner; the single record uses Sept4 only as a knockout background"
  },
  {
    "partner": "SNX9",
    "recombinome_n": 1,
    "pubmed_records": 1,
    "reason": "single patient, single record"
  },
  {
    "partner": "ITSN1",
    "recombinome_n": 1,
    "pubmed_records": 0,
    "reason": "single patient, no literature"
  },
  {
    "partner": "ABI2",
    "recombinome_n": 2,
    "pubmed_records": 1,
    "reason": "two patients, one record"
  }
]
deferred with real literature — the numbers behind the chart
[
  {
    "partner": "MLLT11/AF1q",
    "recombinome_n": 28,
    "pubmed_records": 14,
    "reason": "substantial partner, 90 aa, no chromatin domain and no annotated oligomerisation module — the sharpest remaining challenge to every model in this beat; deferred rather than written thinly"
  },
  {
    "partner": "EPS15",
    "recombinome_n": 55,
    "pubmed_records": 13,
    "reason": "graph holds protein and subtraction entries but no fusion entry; belongs to an adjacent beat"
  },
  {
    "partner": "GAS7",
    "recombinome_n": 3,
    "pubmed_records": 5,
    "reason": "mechanistically load-bearing for the oligomerisation argument and cited throughout, but clinically negligible"
  },
  {
    "partner": "GPHN",
    "recombinome_n": 0,
    "pubmed_records": 3,
    "reason": "the cleanest minimal-oligomerisation-domain result in the field, from a single therapy-related patient"
  },
  {
    "partner": "MYO1F",
    "recombinome_n": 5,
    "pubmed_records": 1,
    "reason": "real patient count, nothing to read"
  },
  {
    "partner": "NEBL",
    "recombinome_n": 3,
    "pubmed_records": 5,
    "reason": "relevant to the 10p11-12 ambiguity with ABI1 and MLLT10"
  },
  {
    "partner": "MLLT6/AF17",
    "recombinome_n": 27,
    "pubmed_records": 13,
    "reason": "an entry already exists (gene-mllt6); MLLT6 carries a leucine-zipper dimerisation motif and is a bridge case between partner classes"
  }
]
queries
{
  "controls": {
    "menin[Title/Abstract]": 1264,
    "septin OR septins [Title/Abstract]": 1936
  },
  "intersection_menin_septin": 0,
  "mll_or_kmt2a_intersections": {
    "SEPT9": 20,
    "MSF": 14,
    "SEPTIN9": 1,
    "AF17q25": 3,
    "SEPT6": 19,
    "SEPTIN6": 5,
    "SEPT5": 9,
    "SEPTIN5": 1,
    "hCDCrel": 6,
    "CDCREL": 1,
    "SEPT2": 10,
    "SEPTIN2": 0,
    "SEPT11": 5,
    "SEPTIN11": 1,
    "SEPT4": 1,
    "SEPTIN4": 0,
    "septin": 30,
    "ABI1": 7,
    "MLLT11": 7,
    "AF1q": 14,
    "EPS15": 13,
    "MLLT6": 13,
    "AF17": 21,
    "GAS7": 5
  }
}
How this could bite us back
  • Counting partners by current gene symbol under-counts the septin class roughly tenfold. Any automated partner enumeration in this project, including future ones, must search retired symbols.
  • Rejecting a partner on a record count of zero is only safe when the count is not an artefact of nomenclature or of the fusion existing solely in a supplementary table. SEPTIN3 shows both failure modes at once.
Still open
  1. MLLT11/AF1q is 28 patients with 14 papers, 90 residues long, and has neither a chromatin domain nor an annotated oligomerisation module. If it transforms, neither the elongation-hijack model nor the oligomerisation model accounts for it. It deserves its own beat.
  2. How many KMT2A partners exist only in breakpoint tables with no descriptive publication? SEPTIN3 is one; a systematic pass over the recombinome's 63 singletons would say.
  3. Would systematic transcript typing of karyotype-only t(4;11), t(10;11) and t(11;17) cases raise the non-elongation partner count materially? Three separate impersonation routes are documented in this beat.
Every source behind this entry (5)
  1. E1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.paper

    Patient counts for every partner in this analysis were read from Table 1 and the AML/ALL/T-ALL breakdowns of the 2023 KMT2A recombinome (3401 patients, 107 in-frame fusions identified in total, 37 recurrent and 63 seen only once): SEPTIN6 19, SEPTIN9 14, SEPTIN5 8, SEPTIN11 3, SEPTIN2 1, SEPTIN3 1, ABI1 8, ABI2 2, MYO1F 5, SNX9 1, ITSN1 1, NEBL 3, GAS7 3, MLLT11 28, MLLT6 27, EPS15 55.

    The KMT2A recombinome of acute leukemias in 2023. · Meyer C, Larghero P, Almeida Lopes B, et al. · Leukemia 2023
    What this evidence cannot show

    Read from the PMC full text (PMC10169636), not the abstract, which reports none of these counts. A referral cohort accrued 2003-2022 from 20 countries, so these are ascertainment-weighted counts and not population incidence.

    Evidence that argues against this (1)
    • The recombinome systematically under-counts cryptic and impersonating fusions: KMT2A::SEPTIN6 sits on the der(X) and needed panhandle PCR to find, KMT2A::SEPTIN11 produces an ordinary t(4;11), and ABI1 is cytogenetically indistinguishable from MLLT10. Four independently published MLL-SEPT2 cases against a recombinome count of 1 is the clearest demonstration that these numbers are floors. Cerveira N et al. 2009
  2. E2strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.database

    PubMed [Title/Abstract] record counts run for this beat on 2026-09-19 with both halves of each intersection controlled: menin = 1264, septin OR septins = 1936, and their intersection = 0; (MLL OR KMT2A) intersected with SEPT9 = 20, MSF = 14, SEPTIN9 = 1, AF17q25 = 3, SEPT6 = 19, SEPTIN6 = 5, SEPT5 = 9, SEPTIN5 = 1, hCDCrel = 6, SEPT2 = 10, SEPTIN2 = 0, SEPT11 = 5, SEPTIN11 = 1, septin = 30, ABI1 = 7, MLLT11 = 7, AF1q = 14, EPS15 = 13, MLLT6 = 13, AF17 = 21, GAS7 = 5, gephyrin = 3.

    What this evidence cannot show

    Counts are of records whose title or abstract contains the terms; they are a proxy for literature volume, not for quality or relevance, and were spot-checked by reading titles wherever a count drove an inclusion or rejection decision. PubMed indexing changes, so these are dated.

    Evidence that argues against this (1)
    • Title/abstract counts systematically miss fusions reported only in tables, supplementary data or genomic-breakpoint compendia. SEPTIN3 returns zero records yet appears as a patient in the recombinome table, which proves the two methods disagree and that neither alone enumerates the partner set. Meyer C et al. 2023
  3. E3strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper

    Sept4 appears in the KMT2A/MLL literature only as a genetic background in the Sept6-knockout study, where loss of Sept6 caused no additional change in Sept4-deficient mice; SEPT4 is not a KMT2A fusion partner.

    What this evidence cannot show

    An absence argument resting on one search plus one paper. A SEPT4 fusion reported only in a breakpoint table would not be caught, exactly as happened for SEPTIN3.

    Evidence that argues against this (1)
    • The same failure mode that this analysis documents for SEPTIN3 — present in the recombinome table, absent from the searchable literature — could apply to SEPT4, and the recombinome partner list was checked for SEPTIN3 and SEPTIN2 but was not exhaustively re-read for every septin paralogue. Meyer C et al. 2023
  4. E4established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.review

    Five different septin genes (SEPT2, SEPT5, SEPT6, SEPT9, SEPT11) were already known as MLL fusion partners by 2011, giving rise to chimeric proteins in which the N terminus of MLL is fused in frame to almost the entire open reading frame of the septin partner, with heterogeneous breaks in distinct introns of both genes producing distinct fusion variants, identified repeatedly in de novo and therapy-related myeloid neoplasia in children and adults.

    MLL-SEPTIN gene fusions in hematological malignancies. · Cerveira N, Bizarro S, Teixeira MR · Biol Chem 2011
    What this evidence cannot show

    A review, used as a map of the partner set and of the shared architecture. Its concluding mechanistic speculation — that septin roles in cytokinesis, membrane remodelling and compartmentalisation 'can provide some clues' — was speculation in 2011 and remains untested in 2026.

    Evidence that argues against this (1)
    • The review's own framing assumes septin function is the relevant variable, but the only functional test performed on any KMT2A-septin fusion showed the wild-type septin gene is dispensable (Sept6-null mice, unchanged MLL-SEPT6 disease), which argues the partner contributes a structural module rather than a septin function. Ono R et al. 2005
  5. E_corrections_2026_09_19strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper

    Three partner record counts in this enumeration were under-counted. GPHN has two published index cases rather than one therapy-related patient: a de novo acute monoblastic leukaemia and a therapy-related acute undifferentiated leukaemia, both with t(11;14)(q23;q24). MYO1F has two records rather than one, the second reporting the t(11;19)(q23;p13) MLL-MYO1F fusion as RECURRENT in infant acute myeloid leukaemia. MLLT11 intersects at 20 records rather than 14.

    What this evidence cannot show

    Found by the deferred-partner beat on 2026-09-19 while writing the partners this enumeration had deferred, and routed here by the coordinator rather than edited by that beat. All three PMIDs were fetched and checked. PMID 21620472 has no abstract in PubMed, so the MYO1F recurrence claim rests on its title. PMID 11289145 has no DOI in its PubMed record.

    Evidence that argues against this (2)
    • Two index cases is still two index cases, and the correction should not be read as promoting GPHN to a recurrent partner. What changes is that one of them is DE NOVO rather than therapy-related, which removes the easiest reason to dismiss the fusion as a secondary event of treatment. Genes, Chromosomes & Cancer 2001
    • MYO1F being called recurrent rests on a title with no abstract indexed, and the recombinome lists it at a handful of patients. 'Recurrent in infant AML' from a title alone is weaker than the word suggests, and the partner remains too rare to power anything on its own. Leukemia Research 2011
Connected to