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 transport by P-type ATPases

R-MMU-936837 in Reactome release 97: under Ion channel transport, with 55 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-936837 (human), R-RNO-936837 (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 55 genes in this mouse pathway; showing 1 to 55, 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
GeneAtp10aAuthority11982Mapping file id11982 NCBI fileEvidenceIEA
GeneAtp10bAuthority319767Mapping file id319767 NCBI fileEvidenceIEA
GeneAtp10dAuthority231287Mapping file id231287 NCBI fileEvidenceIEA
GeneAtp11aAuthority50770Mapping file id50770 NCBI fileEvidenceIEA
GeneAtp11bAuthority76295Mapping file id76295 NCBI fileEvidenceIEA
GeneAtp11cAuthority320940Mapping file id320940 NCBI fileEvidenceIEA
GeneAtp12aAuthority192113Mapping file id192113 NCBI fileEvidenceIEA
GeneAtp13a1Authority170759Mapping file id170759 NCBI fileEvidenceIEA
GeneAtp13a2Authority74772Mapping file id74772 NCBI fileEvidenceIEA
GeneAtp13a4Authority224079Mapping file id224079 NCBI fileEvidenceIEA
GeneAtp13a5Authority268878Mapping file id268878 NCBI fileEvidenceIEA
GeneAtp1a1Authority11928Mapping file id11928 NCBI fileEvidenceIEA
GeneAtp1a2Authority98660Mapping file id98660 NCBI fileEvidenceIEA
GeneAtp1a3Authority232975Mapping file id232975 NCBI fileEvidenceIEA
GeneAtp1a4Authority27222Mapping file id27222 NCBI fileEvidenceIEA
GeneAtp1b1Authority11931Mapping file id11931 NCBI fileEvidenceIEA
GeneAtp1b2Authority11932Mapping file id11932 NCBI fileEvidenceIEA
GeneAtp1b3Authority11933Mapping file id11933 NCBI fileEvidenceIEA
GeneAtp2a1Authority11937Mapping file id11937 NCBI fileEvidenceIEA
GeneAtp2a2Authority11938Mapping file id11938 NCBI fileEvidenceIEA
GeneAtp2a3Authority53313Mapping file id53313 NCBI fileEvidenceIEA
GeneAtp2b1Authority67972Mapping file id67972 NCBI fileEvidenceIEA
GeneAtp2b2Authority11941Mapping file id11941 NCBI fileEvidenceIEA
GeneAtp2b3Authority320707Mapping file id320707 NCBI fileEvidenceIEA
GeneAtp2b4Authority381290Mapping file id381290 NCBI fileEvidenceIEA
GeneAtp2c1Authority235574Mapping file id235574 NCBI fileEvidenceIEA
GeneAtp2c2Authority69047Mapping file id69047 NCBI fileEvidenceIEA
GeneAtp4aAuthority11944Mapping file id11944 NCBI fileEvidenceIEA
GeneAtp4bAuthority11945Mapping file id11945 NCBI fileEvidenceIEA
GeneAtp7aAuthority11977Mapping file id11977 NCBI fileEvidenceIEA
GeneAtp7bAuthority11979Mapping file id11979 NCBI fileEvidenceIEA
GeneAtp8a1Authority11980Mapping file id11980 NCBI fileEvidenceIEA
GeneAtp8a2Authority50769Mapping file id50769 NCBI fileEvidenceIEA
GeneAtp8b1Authority54670Mapping file id54670 NCBI fileEvidenceIEA
GeneAtp8b2Authority54667Mapping file id54667 NCBI fileEvidenceIEA
GeneAtp8b3Authority67331Mapping file id67331 NCBI fileEvidenceIEA
GeneAtp8b4Authority241633Mapping file id241633 NCBI fileEvidenceIEA
GeneAtp9aAuthority11981Mapping file id11981 NCBI fileEvidenceIEA
GeneAtp9bAuthority50771Mapping file id50771 NCBI fileEvidenceIEA
GeneCalm1Authority12313Mapping file id12313 NCBI fileEvidenceIEA
GeneCalm2Authority12314Mapping file idENSMUSG00000036438 Ensembl fileEvidenceIEA
GeneCalm3Authority12315Mapping file idENSMUSG00000019370 Ensembl fileEvidenceIEA
GeneCamk2aAuthority12322Mapping file id12322 NCBI fileEvidenceIEA
GeneCamk2bAuthority12323Mapping file id12323 NCBI fileEvidenceIEA
GeneCamk2dAuthority108058Mapping file id108058 NCBI fileEvidenceIEA
GeneCamk2gAuthority12325Mapping file id12325 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
GenePdzd11Authority72621Mapping file id72621 NCBI fileEvidenceIEA
GenePlnAuthority18821Mapping file id18821 NCBI fileEvidenceIEA
GeneSriAuthority109552Mapping file id109552 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.