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.

Ion channel transport

R-MMU-983712 in Reactome release 97: under Transport of small molecules, with 176 genes placed in it by the mapping files and 2 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-983712 (human), R-RNO-983712 (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 176 genes in this mouse pathway; showing 101 to 176, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 2 of 2
GeneClcnkaAuthority12733Mapping file id12733 NCBI fileEvidenceIEA
GeneClcnkbAuthority56365Mapping file id56365 NCBI fileEvidenceIEA
GeneFkbp1bAuthority14226Mapping file id14226 NCBI fileEvidenceIEA
GeneFxyd1Authority56188Mapping file id56188 NCBI fileEvidenceIEA
GeneFxyd2Authority11936Mapping file id11936 NCBI fileEvidenceIEA
GeneFxyd3Authority17178Mapping file id17178 NCBI fileEvidenceIEA
GeneFxyd4Authority108017Mapping file id108017 NCBI fileEvidenceIEA
GeneFxyd6Authority59095Mapping file id59095 NCBI fileEvidenceIEA
GeneFxyd7Authority57780Mapping file id57780 NCBI fileEvidenceIEA
GeneLrrk1Authority233328Mapping file id233328 NCBI fileEvidenceIEA
GeneMcoln1Authority94178Mapping file id94178 NCBI fileEvidenceIEA
GeneMcoln2Authority68279Mapping file id68279 NCBI fileEvidenceIEA
GeneMcoln3Authority171166Mapping file id171166 NCBI fileEvidenceIEA
GeneMlklAuthority74568Mapping file id74568 NCBI fileEvidenceIEA
GeneNalcnAuthority338370Mapping file id338370 NCBI fileEvidenceIEA
GeneNedd4lAuthority83814Mapping file idENSMUSG00000024589 Ensembl fileEvidenceIEA
GeneNek4Authority23955Mapping file id23955 NCBI fileEvidenceIEA
GeneOstm1Authority14628Mapping file id14628 NCBI fileEvidenceIEA
GenePdzd11Authority72621Mapping file id72621 NCBI fileEvidenceIEA
GenePlnAuthority18821Mapping file id18821 NCBI fileEvidenceIEA
GeneRaf1Authority110157Mapping file id110157 NCBI fileEvidenceIEA
GeneRipk1Authority19766Mapping file id19766 NCBI fileEvidenceIEA
GeneRipk3Authority56532Mapping file id56532 NCBI fileEvidenceIEA
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneRyr1Authority20190Mapping file id20190 NCBI fileEvidenceIEA
GeneRyr2Authority20191Mapping file id20191 NCBI fileEvidenceIEA
GeneRyr3Authority20192Mapping file id20192 NCBI fileEvidenceIEA
GeneScnn1aAuthority20276Mapping file id20276 NCBI fileEvidenceIEA
GeneScnn1bAuthority20277Mapping file id20277 NCBI fileEvidenceIEA
GeneScnn1gAuthority20278Mapping file id20278 NCBI fileEvidenceIEA
GeneSgk1Authority20393Mapping file id20393 NCBI fileEvidenceIEA
GeneSgk2Authority27219Mapping file id27219 NCBI fileEvidenceIEA
GeneSgk3Authority170755Mapping file id170755 NCBI fileEvidenceIEA
GeneSlc17a3Authority105355Mapping file idENSMUSG00000036083 Ensembl fileEvidenceIEA
GeneSlc9b1Authority74446Mapping file idENSMUSG00000050150 Ensembl fileEvidenceIEA
GeneSlc9b2Authority97086Mapping file id97086 NCBI fileEvidenceIEA
GeneSriAuthority109552Mapping file id109552 NCBI fileEvidenceIEA
GeneStomAuthority13830Mapping file id13830 NCBI fileEvidenceIEA
GeneStoml3Authority229277Mapping file id229277 NCBI fileEvidenceIEA
GeneTcirg1Authority27060Mapping file id27060 NCBI fileEvidenceIEA
GeneTpcn1Authority252972Mapping file id252972 NCBI fileEvidenceIEA
GeneTpcn2Authority233979Mapping file id233979 NCBI fileEvidenceIEA
GeneTrdnAuthority76757Mapping file id76757 NCBI fileEvidenceIEA
GeneTrpa1Authority277328Mapping file id277328 NCBI fileEvidenceIEA
GeneTrpc1Authority22063Mapping file id22063 NCBI fileEvidenceIEA
GeneTrpc3Authority22065Mapping file id22065 NCBI fileEvidenceIEA
GeneTrpc4Authority22066Mapping file id22066 NCBI fileEvidenceIEA
GeneTrpc4apAuthority56407Mapping file id56407 NCBI fileEvidenceIEA
GeneTrpc5Authority22067Mapping file id22067 NCBI fileEvidenceIEA
GeneTrpc6Authority22068Mapping file id22068 NCBI fileEvidenceIEA
GeneTrpc7Authority26946Mapping file id26946 NCBI fileEvidenceIEA
GeneTrpm1Authority17364Mapping file id17364 NCBI fileEvidenceIEA
GeneTrpm2Authority28240Mapping file id28240 NCBI fileEvidenceIEA
GeneTrpm3Authority226025Mapping file id226025 NCBI fileEvidenceIEA
GeneTrpm4Authority68667Mapping file id68667 NCBI fileEvidenceIEA
GeneTrpm5Authority56843Mapping file id56843 NCBI fileEvidenceIEA
GeneTrpm6Authority225997Mapping file id225997 NCBI fileEvidenceIEA
GeneTrpm7Authority58800Mapping file id58800 NCBI fileEvidenceIEA
GeneTrpm8Authority171382Mapping file id171382 NCBI fileEvidenceIEA
GeneTrpv1Authority193034Mapping file id193034 NCBI fileEvidenceIEA
GeneTrpv2Authority22368Mapping file id22368 NCBI fileEvidenceIEA
GeneTrpv3Authority246788Mapping file id246788 NCBI fileEvidenceIEA
GeneTrpv4Authority63873Mapping file id63873 NCBI fileEvidenceIEA
GeneTrpv5Authority194352Mapping file id194352 NCBI fileEvidenceIEA
GeneTrpv6Authority64177Mapping file id64177 NCBI fileEvidenceIEA
GeneTsc22d3Authority14605Mapping file id14605 NCBI fileEvidenceIEA
GeneTtyh1Authority57776Mapping file id57776 NCBI fileEvidenceIEA
GeneTtyh2Authority117160Mapping file id117160 NCBI fileEvidenceIEA
GeneTtyh3Authority78339Mapping file id78339 NCBI fileEvidenceIEA
GeneUba52Authority22186Mapping file id22186 NCBI fileEvidenceIEA
GeneUba52rtAuthority666586Mapping file idENSMUSG00000068240 Ensembl fileEvidenceIEA
GeneUbbAuthority22187Mapping file id22187 NCBI fileEvidenceIEA
GeneUbcAuthority22190Mapping file id22190 NCBI fileEvidenceIEA
GeneUnc79Authority217843Mapping file id217843 NCBI fileEvidenceIEA
GeneUnc80Authority329178Mapping file id329178 NCBI fileEvidenceIEA
GeneWwp1Authority107568Mapping file id107568 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.