Skip to content

Create an account and get up to 25% off.

Order

Pathway Mouse Mus musculus

Read this first

Every mouse pathway in Reactome is electronically inferred from the curated human one; Reactome's own sentence about that stands beside the record below.

HATs acetylate histones

R-MMU-3214847 in Reactome release 97: under Chromatin modifying enzymes, with 74 genes placed in it by the mapping files and 0 child pathways in the hierarchy.

The same number in the other species

Reactome writes the mouse and rat events it infers from a human pathway under the human number with the species token. A door opens only where that species' own list in this release holds the id: R-HSA-3214847 (human), R-RNO-3214847 (rat). Whether the event was inferred from this one is what the record says.

01The record

Reactome's own record of this pathway

What this tells you

The pathway list, the hierarchy and the genes on this page are read from the files Reactome publishes for Reactome release 97, built into this site on 2026-09-09: the pathway list, the hierarchy relationship file and the two gene mapping files. The record card is the one live read, Reactome's own record of this pathway.

Reactome's download page describes the mapping files: Mapping files link the source database identifier to the lowest level pathway diagram or subset of the pathway, all levels of the pathway hierarchy or database identifier to all reactions. [R13] The gene list here is the all-levels mapping of NCBI Gene ids, filled from the all-levels mapping of Ensembl ids where the NCBI file has no row for a gene; each row names which file it came from by the shape of its source id. Each row carries the evidence codes the file writes for it, as written and unranked, and both where the file writes both; no page of Reactome's documentation the survey read defines the codes, so this page does not expand them. A gene id the identity files do not name is kept as the source's own id with no door rather than turned into a symbol.

Every mouse pathway in Reactome is inferred from the curated human one: We use the set of manually curated human reactions to electronically infer reactions in fourteen evolutionarily divergent eukaryotic species for which high-quality whole-genome sequence data are available, and hence a comprehensive and high-quality set of protein predictions exists. [R11] Reactome's own sentence about what that produces is printed beside the record: The electronically inferred reactions presented in Reactome are thus not data, but hypotheses useful to direct the design of confirmatory experiments. [R11]

On citing what a search finds, Reactome says: It should be remembered that while we strive to contain the most current and accurate data, Reactome should not be used in citations where other primary sources of information are available. [R12] The record card prints the literature Reactome attaches to a curated pathway for that reason. The data are public domain: All data in the Reactome database and files derived from that data are licensed under the Creative Commons Public Domain Dedication (CC0). User may copy, modify, and distribute these data, even for commercial purposes, without asking for permission. Attribution is encouraged but not required. [R10] The pathway illustrations are licensed apart, under CC BY 4.0, and none is shown here.

A gene on this list is one Reactome places in this pathway in this release, and that is all the row says: it does not say the gene is expressed in a tissue or associated with a disease, which are the other two explorers' questions, read from other sources. Reactome's papers of record are [R01] [R02].

  1. [R01] Ragueneau E, Gong C, Sinquin P, Sevilla C, Beavers D, Grentner A, et al. (2026). The Reactome Knowledgebase 2026. Nucleic Acids Research 54:D673-D681. PMID 41251150, doi 10.1093/nar/gkaf1223.
  2. [R02] Milacic M, Beavers D, Conley P, Gong C, Gillespie M, Griss J, et al. (2024). The Reactome Pathway Knowledgebase 2024. Nucleic Acids Research 52:D672-D678. PMID 37941124, doi 10.1093/nar/gkad1025.
  3. [R10] Reactome, reactome.org. License Agreement. https://reactome.org/license, read 2026-09-09.
  4. [R11] Reactome, reactome.org. Computationally inferred events. https://reactome.org/documentation/inferred-events, read 2026-09-09.
  5. [R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
  6. [R13] Reactome, reactome.org. Download. https://reactome.org/download-data, read 2026-09-09.
Reading this pathway's record from Reactome (the pathway record).Still reading. A first read of a pathway can take a while; this page waits up to 35 seconds for it, and its scripts then bring in the panel, or a line saying what did not arrive.

02The genes

Genes Reactome places in this mouse pathway

The mapping files place 74 genes in this mouse pathway; showing 1 to 74, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 1 of 1
GeneAtf2Authority11909Mapping file id11909 NCBI fileEvidenceIEA
GeneBrd1Authority223770Mapping file id223770 NCBI fileEvidenceIEA
GeneBrpf1Authority78783Mapping file id78783 NCBI fileEvidenceIEA
GeneBrpf3Authority268936Mapping file id268936 NCBI fileEvidenceIEA
GeneH2bc1Authority319177Mapping file id319177 NCBI fileEvidenceIEA
GeneH2bc11Authority319183Mapping file id319183 NCBI fileEvidenceIEA
GeneH2bc12Authority319184Mapping file id319184 NCBI fileEvidenceIEA
GeneH2bc13Authority319185Mapping file id319185 NCBI fileEvidenceIEA
GeneH2bc14Authority319186Mapping file id319186 NCBI fileEvidenceIEA
GeneH2bc15Authority319187Mapping file id319187 NCBI fileEvidenceIEA
GeneH2bc18Authority319189Mapping file id319189 NCBI fileEvidenceIEA
GeneH2bc21Authority319190Mapping file id319190 NCBI fileEvidenceIEA
GeneH2bc22Authority319188Mapping file id319188 NCBI fileEvidenceIEA
GeneH2bc23Authority665596Mapping file idENSMUSG00000069307 Ensembl fileEvidenceIEA
GeneH2bc24Authority665622Mapping file idENSMUSG00000069303 Ensembl fileEvidenceIEA
GeneH2bc26Authority382522Mapping file id382522 NCBI fileEvidenceIEA
GeneH2bc27Authority78303Mapping file id78303 NCBI fileEvidenceIEA
GeneH2bc3Authority319178Mapping file id319178 NCBI fileEvidenceIEA
GeneH2bc4Authority68024Mapping file id68024 NCBI fileEvidenceIEA
GeneH2bc6Authority319179Mapping file id319179 NCBI fileEvidenceIEA
GeneH2bc7Authority319180Mapping file id319180 NCBI fileEvidenceIEA
GeneH2bc8Authority319181Mapping file id319181 NCBI fileEvidenceIEA
GeneH2bc9Authority319182Mapping file id319182 NCBI fileEvidenceIEA
GeneH3c1Authority360198Mapping file id360198 NCBI fileEvidenceIEA
GeneH3c10Authority319152Mapping file id319152 NCBI fileEvidenceIEA
GeneH3c11Authority319153Mapping file id319153 NCBI fileEvidenceIEA
GeneH3c13Authority319154Mapping file id319154 NCBI fileEvidenceIEA
GeneH3c14Authority15077Mapping file id15077 NCBI fileEvidenceIEA
GeneH3c15Authority97114Mapping file id97114 NCBI fileEvidenceIEA
GeneH3c2Authority319150Mapping file id319150 NCBI fileEvidenceIEA
GeneH3c3Authority319148Mapping file id319148 NCBI fileEvidenceIEA
GeneH3c4Authority319149Mapping file id319149 NCBI fileEvidenceIEA
GeneH3c6Authority319151Mapping file id319151 NCBI fileEvidenceIEA
GeneH3c7Authority260423Mapping file id260423 NCBI fileEvidenceIEA
GeneH3c8Authority97908Mapping file id97908 NCBI fileEvidenceIEA
GeneH4c1Authority326619Mapping file id326619 NCBI fileEvidenceIEA
GeneH4c11Authority319159Mapping file id319159 NCBI fileEvidenceIEA
GeneH4c12Authority319160Mapping file id319160 NCBI fileEvidenceIEA
GeneH4c14Authority97122Mapping file id97122 NCBI fileEvidenceIEA
GeneH4c16Authority320332Mapping file id320332 NCBI fileEvidenceIEA
GeneH4c17Authority100041230Mapping file id100041230 NCBI fileEvidenceIEA
GeneH4c18Authority319161Mapping file id319161 NCBI fileEvidenceIEA
GeneH4c2Authority326620Mapping file id326620 NCBI fileEvidenceIEA
GeneH4c3Authority319155Mapping file id319155 NCBI fileEvidenceIEA
GeneH4c4Authority319156Mapping file id319156 NCBI fileEvidenceIEA
GeneH4c6Authority319157Mapping file id319157 NCBI fileEvidenceIEA
GeneH4c8Authority69386Mapping file id69386 NCBI fileEvidenceIEA
GeneH4c9Authority319158Mapping file id319158 NCBI fileEvidenceIEA
GeneHat1Authority107435Mapping file id107435 NCBI fileEvidenceIEA
GeneHcfc1Authority15161Mapping file id15161 NCBI fileEvidenceIEA
GeneIng4Authority28019Mapping file id28019 NCBI fileEvidenceIEA
GeneIng5Authority66262Mapping file id66262 NCBI fileEvidenceIEA
GeneJade1Authority269424Mapping file id269424 NCBI fileEvidenceIEA
GeneJade2Authority76901Mapping file id76901 NCBI fileEvidenceIEA
GeneJade3Authority382207Mapping file id382207 NCBI fileEvidenceIEA
GeneKansl1Authority76719Mapping file id76719 NCBI fileEvidenceIEA
GeneKansl2Authority69612Mapping file id69612 NCBI fileEvidenceIEA
GeneKansl3Authority226976Mapping file id226976 NCBI fileEvidenceIEA
GeneKat6aAuthority244349Mapping file idENSMUSG00000031540 Ensembl fileEvidenceIEA
GeneKat6bAuthority54169Mapping file id54169 NCBI fileEvidenceIEA
GeneKat7Authority217127Mapping file id217127 NCBI fileEvidenceIEA
GeneKat8Authority67773Mapping file id67773 NCBI fileEvidenceIEA
GeneMcrs1Authority51812Mapping file id51812 NCBI fileEvidenceIEA
GeneMeaf6Authority70088Mapping file id70088 NCBI fileEvidenceIEA
GeneMsl1Authority74026Mapping file id74026 NCBI fileEvidenceIEA
GeneMsl2Authority77853Mapping file id77853 NCBI fileEvidenceIEA
GeneMsl3Authority17692Mapping file id17692 NCBI fileEvidenceIEA
GeneNcoa1Authority17977Mapping file id17977 NCBI fileEvidenceIEA
GeneNcoa2Authority17978Mapping file id17978 NCBI fileEvidenceIEA
GeneOgtAuthority108155Mapping file id108155 NCBI fileEvidenceIEA
GenePax3Authority18505Mapping file id18505 NCBI fileEvidenceIEA
GenePhf20Authority228829Mapping file id228829 NCBI fileEvidenceIEA
GeneRbbp7Authority245688Mapping file id245688 NCBI fileEvidenceIEA
GeneWdr5Authority140858Mapping file id140858 NCBI fileEvidenceIEA

Evidence codes on this page: IEA, as the mapping file writes them; a row carrying two was written twice by the file, once under each. The mapping file id says which file placed the gene: an NCBI Gene id from NCBI2Reactome_All_Levels.txt, an Ensembl gene id from Ensembl2Reactome_All_Levels.txt. The two files can disagree about a code, so a row's codes are the one file's view. Measured by this site's build over this release on 2026-09-09: the two files disagree on none of the 87,729 mouse pairs both place.

  • Reactome mapping files, the mouse rows for this pathway · Reactome release 97 · read · Reactome downloads"NCBI2Reactome_All_Levels.txt" and "Ensembl2Reactome_All_Levels.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.

03The hierarchy

Parents and children in this release's hierarchy

Children

None: no pathway of this release's list names this one as a parent.

Reactome's hierarchy is a graph rather than a tree: a pathway can sit under more than one parent, and the gene counts are each pathway's own placements at every level under it, so a parent's count is not the sum of its children's.

  • Reactome, the mouse pathway list and hierarchy relationship file · Reactome release 97 · read · Reactome downloads"ReactomePathways.txt" and "ReactomePathwaysRelation.txt", Reactome, release 97, https://reactome.org/download-data/ (date of access 2026-09-09). Data CC0; attribution encouraged.