MED19 - the Mediator subunit curated against an engineered MLL-AFF4 fusion protein, and the one REST uses to deliver G9a
also called LCMR1 · Lung cancer metastasis-related protein 1 · Mediator complex subunit 19 · Mediator of RNA polymerase II transcription subunit 19 · MED19_HUMAN
MED19 is a small piece of Mediator, the adaptor that carries instructions from gene switches to the machine that copies DNA into RNA. It is one of only two proteins in the whole curated interaction record that was ever tested against a laboratory-built MLL fusion protein rather than against normal MLL.
The same thing, for a scientist
MED19 (A0JLT2, 244 aa, HGNC:29600, 11q12.1) is a subunit of the Mediator core module, established by MudPIT across six independent immunoaffinity Mediator preparations, one of which was purified through MED19 itself (then called LCMR1) [E1]. Its relevance here is not what the read queue that nominated it said: IntAct curates MED19, as BAIT, in an anti-tag co-immunoprecipitation whose prey is an engineered chimera - IntAct interactor EBI-2620048, described in the record as "Fusion of Human MLL (N-terminus) and Human AFF4 (518-1163) - C terminal region" - in HeLa cells, from PMID 21729782 [E2]. That construct carries no UniProt accession and no cross-references, so no accession-keyed interactome query in this project can reach it, and the six-bait gap analysis attributed the same single record to both its KMT2A and its AFF4 query [E3]. On epigenetics MED19 is not a writer, eraser or reader - 244 residues, largely disordered, no catalytic or reader module at all [E4] - but it is not not-applicable either: MED19 and MED26 are the two Mediator subunits identified as direct physical and synergistic functional targets of REST in G9a-dependent H3K9me2 silencing [E5]. MED19 is broadly essential in DepMap (-0.5075 across 1,208 lines) and ranks 273 of 17,728 on KMT2A-rearranged-versus-other-leukaemia difference, inside the top 1.6% but confounded by that essentiality [E6]; the repo's own Mediator split shows 25 of 26 core subunits broadly essential and only MED16 clearing both bars [E7].
What the curated evidence actually is, bait by bait
Two IntAct interactions, two publications, one laboratory, and neither is a binding measurement.
| record | partner | method | system | publication |
|---|---|---|---|---|
EBI-394580 | AFF4 (Q9UHB7) | anti-tag co-IP (MI:0007), association (MI:0914) | HeLa | Sato 2004, PMID 15175163 1 |
EBI-4321349 / IM-16559-13 | EBI-2620048 mll_aff4_fusion (no accession) | anti-tag co-IP (MI:0007), association (MI:0914) | HeLa | Takahashi 2011, PMID 21729782 2 |
In both records MED19 is the bait and the elongation-side protein is the prey (experimentalRoleA: bait), fetched from IntAct REST 2026-09-22 2. Nobody has ever pulled on KMT2A, AFF1, AFF4, MEN1, PSIP1 or DOT1L and recovered MED19.
The two publications are not two independent observations. Sato S and Parmely TJ are authors on both; the senior authors are Conaway RC (2004) and Conaway JW (2011) - one laboratory, seven years apart, same HeLa immunoaffinity platform 12. A paper count off a curated database is not an independence count, and here the redundancy is at LABORATORY level rather than at platform level.
Why this row matters more than its MI-score: the partner is a fusion protein
This project's standing caveat on every IntAct-derived partner is that an interactor of KMT2A is not an interactor of KMT2A::AFF1, because the fusion loses everything C-terminal of roughly residue 1444. That caveat does not apply to EBI-4321349. The partner IS a chimera of the MLL N-terminus and AFF4 518-1163 2.
IntAct holds four such engineered KMT2A-fusion interactors, and none has a UniProt accession or a single cross-reference, so findInteractions/<accession> and PSICQUIC id:<accession> both return nothing for them 3:
| IntAct interactor | description in the record | interactions |
|---|---|---|
EBI-2620048 | Fusion of Human MLL (N-terminus) and Human AFF4 (518-1163) - C terminal region | 6 |
EBI-2620075 | Fusion of human MLL (N-terminal region) and human AFF4 (C terminal region) | 1 |
EBI-2620068 | Fusion of human MLL (N-terminal region) with human ENL C-terminal residues 373-559 | 8 |
EBI-2890930 | MLL-AF9 fusion protein | 32 |
The six on EBI-2620048 are MED19 once, MED26 four times and AFF1 once 3. MED19 and MED26 are the only two Mediator subunits in that set, and they are the same two subunits REST uses to reach G9a 5 - a convergence neither literature notes.
Epigenetics: not a writer, and not not-applicable either
Domain architecture, fetched live. A0JLT2 is 244 aa with disordered regions 1-56 and 171-244, a proline-rich bias at 26-47, basic patches at 171-182 and 212-224, and a low-complexity tail at 234-244. There is no SET, JmjC, HAT, HDAC, bromo, chromo, Tudor, PHD, CXXC, YEATS or PWWP module and no annotated DNA-binding region 4. MED19 cannot itself write, erase or read a mark.
What it does instead is carry one. PMID 19049968 identifies MED19 and MED26 as direct physical and synergistic functional targets of the RE1-silencing transcription factor REST, in the route by which REST recruits G9a to deposit H3K9me2 and silence neuronal genes in non-neuronal cells 5. The mark is H3K9me2; the writer is G9a/EHMT2; MED19 is the docking surface.
Bounded, with the queries stated. MED19[tiab] AND histone[tiab] = 2 (20054697, 19049968); MED19[tiab] AND epigenetic[tiab] = 2; MED19[tiab] AND G9a[tiab] = 1 and MED19[tiab] AND REST[tiab] = 1, both 19049968; MED19[tiab] AND MLL[tiab] = 0 and MED19[tiab] AND KMT2A[tiab] = 0 8. Instrument control through the identical code path: H3K79me2[tiab] = 224 8. A PubMed zero bounds titles and abstracts, not supporting figures.
Reopening condition: a ChIP or CUT&RUN for H3K9me2 and G9a at KMT2A::AFF1 target loci under MED19 depletion. If MED19 docks a repressive methyltransferase and also co-purifies with an MLL-AFF4 chimera, the fusion has a route to a silencing enzyme that nothing in this graph describes.
Localization: UniProt's nuclear call is a curator inference, not a measurement
A0JLT2 carries exactly one subcellular-location comment - Nucleus - coded ECO:0000305, curator inference, with no cited experiment at all 4. For a core subunit of the Pol II Mediator complex that is a surprising gap, and it is the same shape Q71 found for SMARCD2. The nuclear assignment is nevertheless safe by complex membership: MED19-containing Mediator was purified from HeLa nuclear extract in six independent preparations 1.
Subnuclear: unpublished. Nothing read for this entry places MED19 in a speckle, a nucleolus, a condensate or any other subnuclear compartment, and no MED19 immunofluorescence was located. Recorded as an absence, not inferred from Mediator's behaviour.
Cell type and state. Every MED19 measurement above is in HeLa (cervical adenocarcinoma) or in a pan-cancer DepMap panel. There is no MED19 measurement in any haematopoietic cell, normal or leukaemic: MED19[tiab] AND leukemia[tiab] = 0 8.
Analogous biology in other fusion families
The Mediator-to-elongation axis this row sits on is not KMT2A-specific. The MED26 N-terminal domain that docks the super elongation complex also docks TFIID, and the paper establishing it used the MLL-AFF4 chimera as a test substrate 2. Two other fusion contexts touch Mediator:
- The CDK8 kinase module is the druggable half of Mediator, and this repo's scan puts it far from the core in dependency terms (kinase-module median rank 4,346 against core 445) 7. A KMT2A-associated Mediator signal that lives in the core is a signal in the undruggable half.
- DEK::NUP214 - MED19/LCMR1 binds DEK through DEK's N-terminal region, by yeast two-hybrid from a lung-cancer cDNA library with co-IP and GST-pulldown confirmation 9. DEK's N-terminus is the portion retained in the t(6;9) DEK::NUP214 fusion of AML, so a contact mapped there is inherited on the same argument this project applies to KMT2A breakpoints. Nobody has tested it in a DEK::NUP214 cell.
Naming traps checked before the searches were run
LCMR1is an alias, not a previous official symbol. HGNC:29600 recordsprev_symbol: null,alias_symbol: [LCMR1], and a previous NAME of "mediator of RNA polymerase II transcription, subunit 19 homolog (S. cerevisiae)" 4. The alias control was run anyway and was not a no-op:MED19[tiab] AND leukemia[tiab]= 0 whileLCMR1[tiab] AND leukemia[tiab]= 1 (PMID 28765911, a lung-cancer paper whose abstract contains "leukemia" only inside a gene's legacy name), andLCMR1[tiab]alone returns 12 records the MED19 symbol never reaches 89.RESTin the epigenetics evidence is the RE1-silencing transcription factor, not the English word - the paper's title says so 5. This graph has been burned by readingRESTas ordinary text, so the disambiguation is stated rather than assumed.- No paralogue length trap. A0JLT2 is the single reviewed human record for
gene_exact:MED194.
| uniprot | A0JLT2 |
|---|---|
| length AA | 244 |
| molecular weight da | 26273 |
| uniprot ID | MED19_HUMAN |
| gene primary | MED19 |
| hgnc ID | HGNC:29600 |
| cytoband | 11q12.1 |
| ensembl gene ID | ENSG00000156603 |
| genomic coordinates grch38 | chr11:57,703,710-57,712,348, minus strand, Ensembl GRCh38, fetched 2026-09-22 |
| alias control run | MED19 has NO previous official symbol - LCMR1 is an alias only (HGNC:29600 prev_symbol null). The control was run anyway and was NOT a no-op: LCMR1[tiab] returns 12 records and LCMR1[tiab] AND leukemia[tiab] returns 1 (PMID 28765911) where MED19[tiab] AND leukemia[tiab] returns 0. The extra record is a lung-cancer paper whose abstract contains the word leukaemia only inside a legacy gene name. |
| domain architecture note | No domain features at all in UniProt A0JLT2: disordered 1-56 and 171-244, Pro-rich bias 26-47, basic patches 171-182 and 212-224, low complexity 234-244. No residue range is asserted as a domain here because none is annotated, and nothing is written with a null boundary. |
| complex membership | Mediator core module (EBI Complex Portal CPX-3227 / CPX-3232 / CPX-3263 as used by analyses/mediator-module-split) |
| localization | Nucleus. UniProt A0JLT2 carries exactly one location comment, Nucleus, coded ECO:0000305 (curator inference) with no cited experiment; the nuclear assignment is supported independently by purification of MED19-containing Mediator from HeLa nuclear extract (PMID 15175163). |
| localization evidence code | ECO:0000305 only - no ECO:0000269 experimental localisation annotation exists for MED19 |
| subnuclear localization | UNPUBLISHED. No speckle, nucleolar, condensate or other subnuclear assignment was found for MED19 in any source read for this entry, and no MED19 immunofluorescence was located. Recorded as an absence rather than inferred from Mediator's behaviour. |
| localization shown for fusion | NO - nobody has looked in any fusion. The only fusion-adjacent MED19 record is a co-IP with an MLL-AFF4 construct in HeLa (PMID 21729782), which reports no localisation. |
| cell type absence | No MED19 measurement in any haematopoietic cell, normal or leukaemic. MED19[tiab] AND leukemia[tiab] = 0, run 2026-09-22. |
| epigenetic readout | NOT A WRITER, ERASER OR READER - AND NOT NOT-APPLICABLE. Domain architecture fetched live 2026-09-22: UniProt A0JLT2 is 244 aa with NO catalytic and NO reader module of any kind (no SET, JmjC, HAT, HDAC, bromo, chromo, Tudor, PHD, CXXC, YEATS, PWWP or annotated DNA-binding region), only disorder and compositional bias, so MED19 cannot itself modify or read chromatin. What it IS is a documented CONDUIT for a histone methyltransferase: PMID 19049968 (Ding N et al., J Biol Chem 2009, Boyer lab) identifies MED19 and MED26 as direct physical and synergistic functional targets of REST in G9a/EHMT2-dependent H3K9me2 silencing of neuronal genes in non-neuronal cells. The mark is H3K9me2, the writer is G9a, and MED19 is the docking surface - an epigenetic FUNCTION without an epigenetic ACTIVITY. BOUNDED with queries stated and querytranslation read back: MED19[tiab] AND histone[tiab] = 2 (PMID 20054697 yeast med19/Set2 and PMID 19049968), MED19[tiab] AND epigenetic[tiab] = 2, MED19[tiab] AND G9a[tiab] = 1, MED19[tiab] AND REST[tiab] = 1, MED19[tiab] AND MLL[tiab] = 0, MED19[tiab] AND KMT2A[tiab] = 0; instrument control H3K79me2[tiab] = 224. REOPENING CONDITION: H3K9me2 and G9a occupancy at KMT2A::AFF1 target loci under MED19 depletion in a t(4;11) line. Because MED19 also co-purifies with an MLL-AFF4 chimera, a positive result would give the fusion a route to a repressive methyltransferase that this graph does not currently describe. |
| epigenetic mark named | H3K9me2, deposited by G9a/EHMT2 and not by MED19 |
| shown for fusion | PARTIAL, and unusually so - the partner in PMID 21729782 is an engineered MLL-AFF4 chimera (IntAct EBI-2620048), not wild-type KMT2A, so this is one of very few rows in the core interactome whose evidence is on a fusion protein at all. It is AFF4 and not AFF1, it is a construct and not an endogenous t(4;11) product, and the cell is HeLa. |
| absence class | measured-not-curated |
| cell type | Measured only in HeLa (cervical adenocarcinoma) and in the DepMap pan-cancer panel. NO MED19 measurement exists in any haematopoietic cell, normal or leukaemic (MED19[tiab] AND leukemia[tiab] = 0, 2026-09-22). |
| cell state | No cell state examined. Every MED19 measurement is in unstimulated HeLa or in a pooled DepMap screen; no differentiation, quiescence or drug-treated state has been assessed. |
hgnc alias symbols
[ "LCMR1" ]
hgnc prev name
[ "mediator of RNA polymerase II transcription, subunit 19 homolog (S. cerevisiae)" ]
domains
[]
cell types measured
[ "HeLa, cervical adenocarcinoma - all MED19 interaction evidence", "DepMap pan-cancer panel, 1,208 lines" ]
intact evidence
{
"n_interactions_with_core_scaffold": 2,
"n_publications": 2,
"n_laboratories": 1,
"independence_note": "Two publications, ONE laboratory. Sato S and Parmely TJ are authors on both PMID 15175163 and PMID 21729782; senior authors Conaway RC and Conaway JW. Same HeLa immunoaffinity platform seven years apart. The read queue's n_publications of 2 is not two independent observations, and the redundancy here is at laboratory level rather than at platform level.",
"records": [
{
"intact_ac": "EBI-394580",
"partner": "AFF4 (Q9UHB7)",
"role": "MED19 bait, AFF4 prey",
"method": "anti tag coimmunoprecipitation (MI:0007)",
"interaction_type": "association (MI:0914)",
"host": "Homo sapiens HeLa epitheloid cervical carcinoma cell",
"pmid": "15175163",
"miscore": 0.35,
"expansion": "spoke expansion"
},
{
"intact_ac": "EBI-4321349",
"imex": "IM-16559-13",
"partner": "EBI-2620048 mll_aff4_fusion - engineered chimera of MLL N-terminus with AFF4 518-1163, NO UniProt accession and NO cross-references",
"role": "MED19 bait, fusion construct prey",
"method": "anti tag coimmunoprecipitation (MI:0007)",
"interaction_type": "association (MI:0914)",
"host": "Homo sapiens HeLa epitheloid cervical carcinoma cell",
"pmid": "21729782",
"miscore": 0.35,
"expansion": "spoke expansion"
}
],
"direction": "In BOTH records MED19 is the bait. No core-scaffold protein has ever been used as a bait to find MED19.",
"not_a_binding_event": "Both rows are MI:0914 association from anti-tag co-IP, i.e. co-complex membership. Neither is MI:0407 direct interaction and no affinity constant exists.",
"queue_artifact": "The six-bait gap analysis reported MED19 with n_baits 2 (KMT2A and AFF4) and 3 IntAct rows. Re-fetched from IntAct REST 2026-09-22, the KMT2A and AFF4 attributions of the PMID 21729782 record are ONE interaction with a fusion CONSTRUCT, matched twice because the PSICQUIC free-text query reached it through the construct's own description. The construct is neither KMT2A nor AFF4, and its gene-name alias field is empty, which is why run.py's gene_of() returned None for it."
}depmap
{
"scan": "analyses/depmap-kmt2a-selective-scan-full/results.json, computed 2026-09-19",
"rank": 273,
"of_genes": 17728,
"percentile": 1.54,
"difference": -0.1937,
"mean_kmt2a_rearranged": -0.8525,
"mean_other_leukemia": -0.6588,
"pan_essentiality_all_lines": -0.5075,
"n_all_lines": 1208,
"n_kmt2a_rearranged_lines": 11,
"n_other_leukemia_lines": 43,
"release_recorded": false,
"release_note": "The stored scan records a compute date and NOT a DepMap release, so this number cannot be distinguished from quarterly drift. Reported as a defect in the stored analysis."
}- MED19 is broadly essential - mean DepMap gene effect -0.5075 across 1,208 lines - so an intervention against it is an essential-function liability rather than a selective one, and the KMT2A-rearranged shift of -0.19 is a shift inside a gene every line needs.
- The selective half of Mediator by DepMap is the CDK8 kinase module, which is the druggable half and the half MED19 is not in. A MED19-directed strategy would have to be a degrader or an interface blocker, and no MED19 structure or mapped interface exists to design against.
- If MED19's documented role is to dock a REPRESSIVE methyltransferase pathway, removing it could de-repress rather than repress, and in a differentiation-blocked KMT2A-rearranged blast the direction of that effect is not predictable from the neuronal system it was measured in.
- Every MED19 measurement relevant here is in HeLa and every fusion-side measurement is on an overexpressed MLL-AFF4 construct, so an intervention justified from these two systems is two imports away from infant B-lineage KMT2A::AFF1.
- Does MED19 depletion change H3K9me2 or G9a occupancy at KMT2A::AFF1 target loci in a t(4;11) line? MED19 docks a repressive methyltransferase pathway and co-purifies with an MLL-AFF4 chimera, and no experiment joins the two.
- Is the MED19 contact with the MLL-AFF4 chimera a MED19 contact at all, or is MED19 a passenger of MED26's mapped TFIIS-like docking domain? A MED26-TND deletion in the same co-IP would separate them.
- Where is MED19 in the nucleus? Its only UniProt localisation comment is a curator inference with no cited experiment and no MED19 immunofluorescence was found, so a single co-stain against a speckle or nucleolar marker would close a gap that should not exist for a core Mediator subunit.
- MED19 and MED26 are the two Mediator subunits both in the REST-G9a route and in the MLL-AFF4 co-IP. Is that a shared surface? The MED26 N-terminal TND is solved; MED19 has no structure of its own and no mapped interface.
- Does the MED19-DEK contact survive in DEK::NUP214, where DEK's N-terminal region is retained? Nobody has tested a MED19 interaction in any t(6;9) cell.
- E1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.paper
MED19, then named LCMR1, is a bona fide subunit of the mammalian Mediator complex, established by multidimensional protein identification technology across six independent immunoaffinity-purified Mediator preparations, one of which was purified through LCMR1/MED19 itself.
A set of consensus mammalian mediator subunits identified by multidimensional protein identification technology. · Sato S, Tomomori-Sato C, Parmely TJ, et al. (12 authors; senior author Conaway RC) · Mol Cell 2004What this evidence cannot show
HeLa cells only, and a proteomic subunit census rather than a functional experiment. IntAct curates from this paper a MED19-bait / AFF4-prey anti-tag co-immunoprecipitation (interaction EBI-394580, MI:0007, MI:0914, MI-score 0.35, spoke-expanded), so the AFF4 row in the read queue is a co-purification inside a Mediator preparation and not a measured MED19-AFF4 contact. The abstract names LCMR1 as MED19 explicitly, which is how the alias was confirmed rather than recalled.
Evidence that argues against this (1)
- A MudPIT census of an immunoaffinity preparation cannot distinguish a stoichiometric subunit from a co-purifying associated factor, and the same laboratory's later work showed Mediator's association with elongation factors is docking-domain-specific rather than whole-complex - so co-purification in 2004 did not establish which subunit the contact runs through. Takahashi H et al. 2011
- E2strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.database
IntAct curates MED19 as the BAIT in an anti-tag co-immunoprecipitation whose prey is an engineered MLL-AFF4 chimera (IntAct interactor EBI-2620048, described in the record as a fusion of the human MLL N-terminus with human AFF4 residues 518-1163), in HeLa cells, typed as association (MI:0914) rather than direct interaction, MI-score 0.35.
IntAct REST findInteractions: interactor EBI-2620048, interaction EBI-4321349 / IMEx IM-16559-13, experimentalRoleA=bait, hostOrganism=Homo sapiens HeLa, retrieved 2026-09-22 · IntAct molecular interaction database (EMBL-EBI) 2026What this evidence cannot show
Retrieved 2026-09-22. MI:0914 association from an anti-tag co-IP is a co-complex statement, not a binary binding event, and the MI-score of 0.35 is low. The system is HeLa, an epithelial cervical adenocarcinoma line with no KMT2A rearrangement, and the fusion is an overexpressed construct, not an endogenous t(4;11) product - it is an MLL-AFF4 chimera, and AFF4 is the 5q31 paralogue of AFF1, not AFF1. The interactor record is untyped for organism (taxName null).
Evidence that argues against this (1)
- In the same paper the functional result is assigned to MED26, not MED19: the N-terminal TFIIS-like domain of MED26 carries the overlapping docking sites for the super elongation complex and for TFIID, and MED19's appearance in the co-IP is not accompanied by any mapped MED19 interface. A co-IP hit inside a Mediator preparation is fully compatible with MED19 being a passenger of MED26's contact. Takahashi H et al. 2011
- E3strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.database
IntAct holds four engineered KMT2A-fusion interactors carrying 47 interaction records between them - EBI-2620048 (6), EBI-2620075 (1), EBI-2620068 mll_enl (8) and EBI-2890930 MLL-AF9 (32) - and none has a UniProt accession or a single cross-reference, so no accession-keyed interactome query in this project can reach any of them.
IntAct REST findInteractor: EBI-2620048, EBI-2620075, mll_enl_human_protein (EBI-2620068), mll_af9_human_protein (EBI-2890930); interactorXrefs empty and interactorPreferredIdentifier equal to the IntAct AC for all four; retrieved 2026-09-22 · IntAct molecular interaction database (EMBL-EBI) 2026What this evidence cannot show
Retrieved 2026-09-22. The per-interactor counts are IntAct's own interactionCount field. A findInteractions query on EBI-2620048 returns 7 rows rather than 6 because IntAct's accession search matches by SUBSTRING and EBI-26200486 contains EBI-2620048 - the spurious row is S100B-NEDD8 from PMID 32814053, identifiable because neither participant is the queried interactor; the same collision adds a SPATS1-SARS1 row to EBI-2620075. All four constructs are overexpressed laboratory chimeras, so their partners are candidates for the endogenous fusion, not members of it.
Evidence that argues against this (1)
- This project has already established that a proteome-scale AP-MS interactome of the index fusion exists in the literature and has never been curated into IntAct at all, so the fusion-construct records found here are a fragment of the fusion-side evidence rather than the whole of it, and an argument built on their scarcity understates how much fusion-side data is uncurated. Skucha A et al. 2018
- E4established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database
UniProt A0JLT2 is the single reviewed human MED19 record at 244 aa (26,273 Da), carries no catalytic or chromatin-reader module of any kind, and its only subcellular-location comment - Nucleus - is coded ECO:0000305, a curator inference with no cited experiment.
UniProtKB A0JLT2 (MED19_HUMAN): features, comments and evidence codes; HGNC:29600 via rest.genenames.org; Ensembl ENSG00000156603 coordinates; retrieved 2026-09-22 · UniProt Consortium / HGNC / Ensembl 2026What this evidence cannot show
Retrieved 2026-09-22. Absence of an annotated domain is absence of an ANNOTATION: A0JLT2's feature table lists only disordered regions and compositional biases, so a cryptic module is unrecorded rather than excluded. Two isoforms are annotated (A0JLT2-1, A0JLT2-2) and 244 aa is the canonical isoform; a RefSeq length may differ and was not checked. ECO:0000305 is weaker than the ECO:0000269 experimental code and weaker still than a named immunofluorescence experiment.
Evidence that argues against this (1)
- UniProt's cited experimental annotations frequently point at a paper that is not about the fact being annotated, and filtering on evidence code keeps the least informative comment while discarding isoform- and fragment-scoped ones - so both the presence and the absence of a coded localisation comment are weak instruments for deciding where a protein is. UniProt Consortium 2025
- E5strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper
MED19 and MED26 are the two Mediator subunits identified as direct physical and synergistic functional targets of the RE1-silencing transcription factor REST, in the pathway by which REST recruits the G9a histone methyltransferase to deposit H3K9me2 and silence neuronal genes in non-neuronal cells.
MED19 and MED26 are synergistic functional targets of the RE1 silencing transcription factor in epigenetic silencing of neuronal gene expression. · Ding N, Tomomori-Sato C, Sato S, et al. (6 authors; senior author Boyer TG) · J Biol Chem 2009What this evidence cannot show
The system is REST-mediated neuronal-gene silencing in non-neuronal cells, not leukaemia and not a KMT2A fusion; the mark is H3K9me2 and the writer is G9a/EHMT2, neither of which MED19 catalyses. This establishes MED19 as a docking surface for a repressive methyltransferase pathway, which is an epigenetic FUNCTION and not an epigenetic ACTIVITY. No H3K9me2 measurement under MED19 perturbation in any haematopoietic cell exists. Read as abstract plus title; the mapped interaction surfaces inside the paper were not read.
Evidence that argues against this (1)
- Mediator's contribution to REST silencing has also been placed on MED12 rather than on MED19/MED26, in work from the same laboratory linking Mediator-dependent G9a recruitment to X-linked intellectual disability - so which subunit carries the G9a route is contested inside one group's own output. Ding N et al. 2008
- E6moderate confidence 3 of 5: One strong study, or several smaller consistent ones.dataset
MED19 is broadly essential in DepMap - mean gene effect -0.5075 across 1,208 lines - and ranks 273 of 17,728 scanned genes on the difference between 11 KMT2A-rearranged and 43 other leukaemia lines (difference -0.1937; -0.8525 in KMT2A-rearranged versus -0.6588 in other leukaemia), the top 1.54% but not separable from that broad essentiality.
analyses/depmap-kmt2a-selective-scan-full/results.json - 17,728 protein-coding genes, 11 Cellosaurus-annotated KMT2A-rearranged versus 43 other leukaemia lines, computed 2026-09-19 · DepMap (Broad Institute), via this repository's scan 2026What this evidence cannot show
A ranked difference between 11 and 43 lines is underpowered, and this project's own null work shows membership of the selective HALF of such a scan is a ~50% base rate; rank 273 of 17,728 is not that null, but the effect is small in absolute terms (-0.19) and MED19's pan-essentiality (-0.51) means the KMT2A-rearranged mean is a shift within a gene every line needs. The stored scan records a compute DATE and NOT a DepMap RELEASE, so this figure cannot be told from quarterly drift - reported as a defect in the stored analysis rather than patched here.
Evidence that argues against this (1)
- Mediator core subunits are broadly essential as a class, so an individual core subunit in the selective half of a KMT2A scan is the expected behaviour of the class rather than a property of that subunit: this repository's module split finds 25 of 26 core subunits broadly essential with a core median rank of 445, and only MED16 clears both a selectivity and a non-pan-essentiality bar. This repository (DepMap-derived) 2026
- E7moderate confidence 3 of 5: One strong study, or several smaller consistent ones.dataset
In this repository's Mediator module split MED19 is assigned to the core module, where the median rank is 445 and median pan-essentiality -0.9084, against the druggable CDK8 kinase module's median rank 4,346 and median pan-essentiality -0.0752 - so any KMT2A-associated Mediator signal that includes MED19 sits in the undruggable half.
analyses/mediator-module-split/result.json - membership from EBI Complex Portal human table CPX-3227 / CPX-3232 / CPX-3263 · This repository / EBI Complex Portal 2026What this evidence cannot show
A stored analysis computed against an earlier state of the data; this repository's staleness reporter found 25 of 36 self-measuring analyses drifted at least 15%, and the rule that followed is to quote ratios and re-run before quoting absolutes. The core/kinase contrast is quoted as a ratio-like statement for that reason. Complex Portal membership is curated, not measured per cell line.
Evidence that argues against this (1)
- Paralogue structure inside the kinase module makes a module-level median misleading: MED13 ranks 13,569 while its paralogue MED13L ranks 9, a spread of 13,560 places, so one median over five subunits conceals the member whose rank would put the kinase module in the selective half. This repository (DepMap-derived) 2026
- E8strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.database
MED19 has no leukaemia and no KMT2A literature under either of its symbols: MED19[tiab] AND leukemia[tiab] = 0, MED19[tiab] AND MLL[tiab] = 0, MED19[tiab] AND KMT2A[tiab] = 0, while the alias control LCMR1[tiab] AND leukemia[tiab] = 1 (off topic) and the instrument control H3K79me2[tiab] = 224.
NCBI E-utilities esearch, db=pubmed, querytranslation read back from every response, run 2026-09-22 · NCBI PubMed 2026What this evidence cannot show
Every query is written one tag per term and never as a parenthesised group, and each querytranslation was read back - "MED19"[Title/Abstract] AND "leukemia"[Title/Abstract] and so on - all clean, with no MeSH explosion and no UID filter. A PubMed zero bounds TITLES AND ABSTRACTS only; supporting figures were not searched, and the likeliest hiding place for a MED19 measurement in a KMT2A model is a supplementary mass-spectrometry table. Absence class for these zeros is measured-not-curated at best and never-measured at worst.
Evidence that argues against this (1)
- A bounded literature zero on a gene symbol is silent on whether the measurement exists in an archive: this project found an MLL fusion used as a BAIT inside a PRIDE deposition while one of its own entries asserted proteomics files had not been swept, so a symbol-level zero should be read as an index limit rather than as an absence of data. Perez-Riverol Y et al. 2022
- E9moderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper
MED19/LCMR1 binds the chromatin architectural protein DEK through DEK's N-terminal region, identified by yeast two-hybrid screening of a 95D lung-cancer cDNA library and confirmed by co-immunoprecipitation in vivo and GST pulldown in vitro.
LCMR1 interacts with DEK to suppress apoptosis in lung cancer cells. · Xu Y, Liang Z, Li C, et al. (5 authors; senior author Chen L) · Mol Med Rep 2017What this evidence cannot show
Non-small-cell lung cancer cells, not leukaemia; a single-laboratory report in a low-impact journal with a two-hybrid origin. The relevance here is by analogy only - DEK's N-terminus is the portion retained in the t(6;9) DEK::NUP214 fusion of AML - and no DEK::NUP214 cell was tested. This record was found only because the MED19 alias LCMR1 was run as a control; the approved symbol does not reach it.
Evidence that argues against this (1)
- Mapping an interaction to the N-terminal region of DEK does not establish that it survives in DEK::NUP214: the fusion replaces DEK's C-terminus with a nucleoporin FG-repeat region that changes what the retained N-terminus is presented in, and retention of a domain is not retention of a contact. Kappes F et al. 2011
CORROBORATES ITS CENTRAL POINT FROM A SECOND DIRECTION: that entry reports MED19 curated against an actual MLL-AFF4 chimera rather than against KMT2A or AFF4. This enumeration recovers MED19 and MED26 as the only two Mediator subunits among the 18 fusion-construct partners, from the mll_aff4_fusion record independently.
MED19 and MED26 are the Mediator subunits REST uses to deliver G9a; the route also requires CDYL
MED19/LCMR1 binds DEK through DEK N-terminal region - the portion retained in DEK::NUP214
MED19 is one of the two Mediator subunits REST uses to deliver G9a
MED19-bait anti-tag co-IP, MI:0914 association, HeLa (IntAct EBI-394580, PMID 15175163)
- related to →KMT2A::AFF1 (MLL-AF4), t(4;11)(q21;q23)
co-IP is with an engineered MLL-AFF4 chimera (IntAct EBI-2620048), not with KMT2A::AFF1 - candidate, not member
the two Mediator subunits that co-purify with the MLL-AFF4 construct and the two REST uses to reach G9a
core module versus CDK8 kinase module: MED19 core (median rank 445), MED12 kinase module
- related to →Plain-English: chromatin and epigenetics — the sticky notes on the DNA, and which ones matter here
no writer/eraser/reader activity; documented conduit for G9a-dependent H3K9me2 via REST
- part of →Plain-English: what transcription elongation is, and why a traffic light explains this leukemia
Mediator core subunit on the MED26-to-super-elongation-complex docking axis
MED19 is one of the 25 of 26 broadly essential core subunits
the MED19 row's n_baits of 2 is one fusion-construct record matched twice, so the queue's bait count is an artifact
both nominated by the same six-bait interactome read queue; MED19's support is one laboratory, PIP4K2A's is two platforms
NF45-NF90 coactivation cooperates with Mediator; MED19 reaches the same axis from the Mediator side and nothing joins the two claims
the one fusion-construct record that leaked into the read queue is MED19's, and it was attributed to two baits it was not tested against