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.

Signal Transduction

R-MMU-162582 in Reactome release 97: a top-level pathway, with 2,247 genes placed in it by the mapping files and 16 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-162582 (human), R-RNO-162582 (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 2,247 genes in this mouse pathway; showing 501 to 600, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 6 of 23
GeneCxcr1Authority227288Mapping file id227288 NCBI fileEvidenceIEA
GeneCxcr2Authority12765Mapping file id12765 NCBI fileEvidenceIEA
GeneCxcr3Authority12766Mapping file id12766 NCBI fileEvidenceIEA
GeneCxcr4Authority12767Mapping file id12767 NCBI fileEvidenceIEA
GeneCxcr5Authority12145Mapping file id12145 NCBI fileEvidenceIEA
GeneCxcr6Authority80901Mapping file id80901 NCBI fileEvidenceIEA
GeneCybaAuthority13057Mapping file id13057 NCBI fileEvidenceIEA
GeneCybbAuthority13058Mapping file id13058 NCBI fileEvidenceIEA
GeneCyfip1Authority20430Mapping file id20430 NCBI fileEvidenceIEA
GeneCyfip2Authority76884Mapping file id76884 NCBI fileEvidenceIEA
GeneCyldAuthority74256Mapping file id74256 NCBI fileEvidenceIEA
GeneCyp26a1Authority13082Mapping file id13082 NCBI fileEvidenceIEA
GeneCyp26b1Authority232174Mapping file id232174 NCBI fileEvidenceIEA
GeneCyp26c1Authority546726Mapping file id546726 NCBI fileEvidenceIEA
GeneCysltr1Authority58861Mapping file id58861 NCBI fileEvidenceIEA
GeneCysltr2Authority70086Mapping file id70086 NCBI fileEvidenceIEA
GeneDaam1Authority208846Mapping file id208846 NCBI fileEvidenceIEA
GeneDab2ipAuthority69601Mapping file id69601 NCBI fileEvidenceIEA
GeneDact1Authority59036Mapping file id59036 NCBI fileEvidenceIEA
GeneDaglaAuthority269060Mapping file id269060 NCBI fileEvidenceIEA
GeneDaglbAuthority231871Mapping file id231871 NCBI fileEvidenceIEA
GeneDbtAuthority13171Mapping file id13171 NCBI fileEvidenceIEA
GeneDdrgk1Authority77006Mapping file id77006 NCBI fileEvidenceIEA
GeneDdx39bAuthority53817Mapping file id53817 NCBI fileEvidenceIEA
GeneDdx4Authority13206Mapping file id13206 NCBI fileEvidenceIEA
GeneDdx5Authority13207Mapping file idENSMUSG00000020719 Ensembl fileEvidenceIEA
GeneDef6Authority23853Mapping file id23853 NCBI fileEvidenceIEA
GeneDepdc1bAuthority218581Mapping file id218581 NCBI fileEvidenceIEA
GeneDerl2Authority116891Mapping file id116891 NCBI fileEvidenceIEA
GeneDgkaAuthority13139Mapping file id13139 NCBI fileEvidenceIEA
GeneDgkbAuthority217480Mapping file id217480 NCBI fileEvidenceIEA
GeneDgkdAuthority227333Mapping file id227333 NCBI fileEvidenceIEA
GeneDgkeAuthority56077Mapping file id56077 NCBI fileEvidenceIEA
GeneDgkgAuthority110197Mapping file id110197 NCBI fileEvidenceIEA
GeneDgkhAuthority380921Mapping file id380921 NCBI fileEvidenceIEA
GeneDgkiAuthority320127Mapping file id320127 NCBI fileEvidenceIEA
GeneDgkkAuthority331374Mapping file idENSMUSG00000062393 Ensembl fileEvidenceIEA
GeneDgkqAuthority110524Mapping file id110524 NCBI fileEvidenceIEA
GeneDgkzAuthority104418Mapping file id104418 NCBI fileEvidenceIEA
GeneDhhAuthority13363Mapping file id13363 NCBI fileEvidenceIEA
GeneDhrs3Authority20148Mapping file id20148 NCBI fileEvidenceIEA
GeneDhrs4Authority28200Mapping file id28200 NCBI fileEvidenceIEA
GeneDhrs9Authority241452Mapping file id241452 NCBI fileEvidenceIEA
GeneDiaph1Authority13367Mapping file id13367 NCBI fileEvidenceIEA
GeneDiaph2Authority54004Mapping file id54004 NCBI fileEvidenceIEA
GeneDiaph3Authority56419Mapping file id56419 NCBI fileEvidenceIEA
GeneDisp2Authority214240Mapping file id214240 NCBI fileEvidenceIEA
GeneDkk1Authority13380Mapping file id13380 NCBI fileEvidenceIEA
GeneDkk2Authority56811Mapping file id56811 NCBI fileEvidenceIEA
GeneDkk4Authority234130Mapping file id234130 NCBI fileEvidenceIEA
GeneDlatAuthority235339Mapping file id235339 NCBI fileEvidenceIEA
GeneDlc1Authority50768Mapping file id50768 NCBI fileEvidenceIEA
GeneDldAuthority13382Mapping file id13382 NCBI fileEvidenceIEA
GeneDlg1Authority13383Mapping file id13383 NCBI fileEvidenceIEA
GeneDlg2Authority23859Mapping file id23859 NCBI fileEvidenceIEA
GeneDlg3Authority53310Mapping file id53310 NCBI fileEvidenceIEA
GeneDlg4Authority13385Mapping file id13385 NCBI fileEvidenceIEA
GeneDlg5Authority71228Mapping file id71228 NCBI fileEvidenceIEA
GeneDll1Authority13388Mapping file id13388 NCBI fileEvidenceIEA
GeneDll4Authority54485Mapping file id54485 NCBI fileEvidenceIEA
GeneDnajb1Authority81489Mapping file id81489 NCBI fileEvidenceIEA
GeneDnal4Authority54152Mapping file id54152 NCBI fileEvidenceIEA
GeneDnmbpAuthority71972Mapping file id71972 NCBI fileEvidenceIEA
GeneDock1Authority330662Mapping file id330662 NCBI fileEvidenceIEA
GeneDock10Authority210293Mapping file id210293 NCBI fileEvidenceIEA
GeneDock11Authority75974Mapping file id75974 NCBI fileEvidenceIEA
GeneDock2Authority94176Mapping file id94176 NCBI fileEvidenceIEA
GeneDock4Authority238130Mapping file id238130 NCBI fileEvidenceIEA
GeneDock5Authority68813Mapping file id68813 NCBI fileEvidenceIEA
GeneDock6Authority319899Mapping file id319899 NCBI fileEvidenceIEA
GeneDock7Authority67299Mapping file idENSMUSG00000028556 Ensembl fileEvidenceIEA
GeneDock8Authority76088Mapping file id76088 NCBI fileEvidenceIEA
GeneDock9Authority105445Mapping file idENSMUSG00000025558 Ensembl fileEvidenceIEA
GeneDok1Authority13448Mapping file id13448 NCBI fileEvidenceIEA
GeneDrc4Authority104346Mapping file id104346 NCBI fileEvidenceIEA
GeneDrd1Authority13488Mapping file id13488 NCBI fileEvidenceIEA
GeneDrd2Authority13489Mapping file id13489 NCBI fileEvidenceIEA
GeneDrd3Authority13490Mapping file id13490 NCBI fileEvidenceIEA
GeneDrd4Authority13491Mapping file id13491 NCBI fileEvidenceIEA
GeneDrd5Authority13492Mapping file id13492 NCBI fileEvidenceIEA
GeneDsg1aAuthority13510Mapping file id13510 NCBI fileEvidenceIEA
GeneDsg2Authority13511Mapping file id13511 NCBI fileEvidenceIEA
GeneDsn1Authority66934Mapping file id66934 NCBI fileEvidenceIEA
GeneDspAuthority109620Mapping file id109620 NCBI fileEvidenceIEA
GeneDstAuthority13518Mapping file id13518 NCBI fileEvidenceIEA
GeneDtx1Authority14357Mapping file id14357 NCBI fileEvidenceIEA
GeneDtx2Authority74198Mapping file id74198 NCBI fileEvidenceIEA
GeneDtx4Authority207521Mapping file id207521 NCBI fileEvidenceIEA
GeneDusp1Authority19252Mapping file id19252 NCBI fileEvidenceIEA
GeneDusp10Authority63953Mapping file id63953 NCBI fileEvidenceIEA
GeneDusp16Authority70686Mapping file id70686 NCBI fileEvidenceIEA
GeneDusp2Authority13537Mapping file id13537 NCBI fileEvidenceIEA
GeneDusp3Authority72349Mapping file id72349 NCBI fileEvidenceIEA
GeneDusp4Authority319520Mapping file id319520 NCBI fileEvidenceIEA
GeneDusp5Authority240672Mapping file id240672 NCBI fileEvidenceIEA
GeneDusp6Authority67603Mapping file id67603 NCBI fileEvidenceIEA
GeneDusp7Authority235584Mapping file id235584 NCBI fileEvidenceIEA
GeneDusp8Authority18218Mapping file id18218 NCBI fileEvidenceIEA
GeneDusp9Authority75590Mapping file id75590 NCBI fileEvidenceIEA
GeneDvl1Authority13542Mapping file id13542 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.