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.

Cellular responses to stress

R-MMU-2262752 in Reactome release 97: under Cellular responses to stimuli, with 501 genes placed in it by the mapping files and 10 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-2262752 (human), R-RNO-2262752 (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 501 genes in this mouse pathway; showing 201 to 300, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 3 of 6
GeneH2ac7Authority319165Mapping file id319165 NCBI fileEvidenceIEA
GeneH2ac8Authority319166Mapping file id319166 NCBI fileEvidenceIEA
GeneH2ajAuthority232440Mapping file id232440 NCBI fileEvidenceIEA
GeneH2axAuthority15270Mapping file id15270 NCBI fileEvidenceIEA
GeneH2az2Authority77605Mapping file id77605 NCBI fileEvidenceIEA
GeneH2bc1Authority319177Mapping file id319177 NCBI fileEvidenceIEA
GeneH2bc11Authority319183Mapping file id319183 NCBI fileEvidenceIEA
GeneH2bc12Authority319184Mapping file id319184 NCBI fileEvidenceIEA
GeneH2bc13Authority319185Mapping file id319185 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
GeneH3f4Authority382523Mapping file id382523 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
GeneHba-a1Authority15122Mapping file idENSMUSG00000069919 Ensembl fileEvidenceIEA
GeneHbb-bsAuthority100503605Mapping file id100503605 NCBI fileEvidenceIEA
GeneHbb-btAuthority101488143Mapping file id101488143 NCBI fileEvidenceIEA
GeneHdac3Authority15183Mapping file id15183 NCBI fileEvidenceIEA
GeneHdac6Authority15185Mapping file id15185 NCBI fileEvidenceIEA
GeneHelz2Authority229003Mapping file id229003 NCBI fileEvidenceIEA
GeneHif1aAuthority15251Mapping file id15251 NCBI fileEvidenceIEA
GeneHif1anAuthority319594Mapping file id319594 NCBI fileEvidenceIEA
GeneHif3aAuthority53417Mapping file id53417 NCBI fileEvidenceIEA
GeneHigd1cAuthority380975Mapping file id380975 NCBI fileEvidenceIEA
GeneHikeshiAuthority67669Mapping file id67669 NCBI fileEvidenceIEA
GeneHiraAuthority15260Mapping file id15260 NCBI fileEvidenceIEA
GeneHmga1Authority15361Mapping file id15361 NCBI fileEvidenceIEA
GeneHmga1bAuthority111241Mapping file idENSMUSG00000078249 Ensembl fileEvidenceIEA
GeneHmga2Authority15364Mapping file id15364 NCBI fileEvidenceIEA
GeneHmox1Authority15368Mapping file id15368 NCBI fileEvidenceIEA
GeneHmox2Authority15369Mapping file id15369 NCBI fileEvidenceIEA
GeneHsbp1Authority68196Mapping file id68196 NCBI fileEvidenceIEA
GeneHsf1Authority15499Mapping file id15499 NCBI fileEvidenceIEA
GeneHsp90aa1Authority15519Mapping file id15519 NCBI fileEvidenceIEA
GeneHsp90ab1Authority15516Mapping file id15516 NCBI fileEvidenceIEA
GeneHspa12aAuthority73442Mapping file id73442 NCBI fileEvidenceIEA
GeneHspa12bAuthority72630Mapping file id72630 NCBI fileEvidenceIEA
GeneHspa13Authority110920Mapping file id110920 NCBI fileEvidenceIEA
GeneHspa14Authority50497Mapping file id50497 NCBI fileEvidenceIEA
GeneHspa1aAuthority193740Mapping file id193740 NCBI fileEvidenceIEA
GeneHspa1bAuthority15511Mapping file id15511 NCBI fileEvidenceIEA
GeneHspa1lAuthority15482Mapping file id15482 NCBI fileEvidenceIEA
GeneHspa2Authority15512Mapping file id15512 NCBI fileEvidenceIEA
GeneHspa4Authority15525Mapping file idENSMUSG00000020361 Ensembl fileEvidenceIEA
GeneHspa4lAuthority18415Mapping file id18415 NCBI fileEvidenceIEA
GeneHspa5Authority14828Mapping file id14828 NCBI fileEvidenceIEA
GeneHspa8Authority15481Mapping file id15481 NCBI fileEvidenceIEA
GeneHspa9Authority15526Mapping file id15526 NCBI fileEvidenceIEA
GeneHspb8Authority80888Mapping file id80888 NCBI fileEvidenceIEA
GeneHsph1Authority15505Mapping file id15505 NCBI fileEvidenceIEA
GeneId1Authority15901Mapping file idENSMUSG00000042745 Ensembl fileEvidenceIEA
GeneItfg2Authority101142Mapping file id101142 NCBI fileEvidenceIEA
GeneJunAuthority16476Mapping file id16476 NCBI fileEvidenceIEA
GeneKat5Authority81601Mapping file id81601 NCBI fileEvidenceIEA
GeneKdm6bAuthority216850Mapping file id216850 NCBI fileEvidenceIEA
GeneKeap1Authority50868Mapping file id50868 NCBI fileEvidenceIEA
GeneKics2Authority270802Mapping file id270802 NCBI fileEvidenceIEA
GeneKptnAuthority70394Mapping file idENSMUSG00000006021 Ensembl fileEvidenceIEA
GeneLamtor1Authority66508Mapping file id66508 NCBI fileEvidenceIEA
GeneLamtor2Authority83409Mapping file id83409 NCBI fileEvidenceIEA
GeneLamtor3Authority56692Mapping file id56692 NCBI fileEvidenceIEA
GeneLamtor4Authority66096Mapping file id66096 NCBI fileEvidenceIEA
GeneLamtor5Authority68576Mapping file id68576 NCBI fileEvidenceIEA
GeneLimd1Authority29806Mapping file id29806 NCBI fileEvidenceIEA
GeneLmnb1Authority16906Mapping file id16906 NCBI fileEvidenceIEA
GeneLy96Authority17087Mapping file id17087 NCBI fileEvidenceIEA
GeneMafkAuthority17135Mapping file id17135 NCBI fileEvidenceIEA
GeneMap1lc3bAuthority67443Mapping file id67443 NCBI fileEvidenceIEA
GeneMap2k3Authority26397Mapping file id26397 NCBI fileEvidenceIEA
GeneMap2k4Authority26398Mapping file id26398 NCBI fileEvidenceIEA
GeneMap2k6Authority26399Mapping file id26399 NCBI fileEvidenceIEA
GeneMap2k7Authority26400Mapping file id26400 NCBI fileEvidenceIEA
GeneMap3k5Authority26408Mapping file id26408 NCBI fileEvidenceIEA
GeneMap4k4Authority26921Mapping file id26921 NCBI fileEvidenceIEA
GeneMapk1Authority26413Mapping file id26413 NCBI fileEvidenceIEA
GeneMapk10Authority26414Mapping file id26414 NCBI fileEvidenceIEA
GeneMapk11Authority19094Mapping file id19094 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

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.