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.

mRNA Splicing

R-MMU-72172 in Reactome release 97: under Processing of Capped Intron-Containing Pre-mRNA, with 205 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-72172 (human), R-RNO-72172 (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 205 genes in this mouse pathway; showing 101 to 200, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 2 of 3
GenePpil4Authority67418Mapping file id67418 NCBI fileEvidenceIEA
GenePpwd1Authority238831Mapping file id238831 NCBI fileEvidenceIEA
GenePqbp1Authority54633Mapping file id54633 NCBI fileEvidenceIEA
GenePrccAuthority94315Mapping file id94315 NCBI fileEvidenceIEA
GenePrkrip1Authority66801Mapping file id66801 NCBI fileEvidenceIEA
GenePrpf18Authority67229Mapping file id67229 NCBI fileEvidenceIEA
GenePrpf19Authority28000Mapping file id28000 NCBI fileEvidenceIEA
GenePrpf3Authority70767Mapping file id70767 NCBI fileEvidenceIEA
GenePrpf31Authority68988Mapping file id68988 NCBI fileEvidenceIEA
GenePrpf38aAuthority230596Mapping file id230596 NCBI fileEvidenceIEA
GenePrpf4Authority70052Mapping file id70052 NCBI fileEvidenceIEA
GenePrpf40aAuthority56194Mapping file id56194 NCBI fileEvidenceIEA
GenePrpf4bAuthority19134Mapping file id19134 NCBI fileEvidenceIEA
GenePrpf6Authority68879Mapping file id68879 NCBI fileEvidenceIEA
GenePrpf8Authority192159Mapping file id192159 NCBI fileEvidenceIEA
GenePtbp1Authority19205Mapping file id19205 NCBI fileEvidenceIEA
GenePuf60Authority67959Mapping file id67959 NCBI fileEvidenceIEA
GeneRbm10Authority236732Mapping file id236732 NCBI fileEvidenceIEA
GeneRbm17Authority76938Mapping file id76938 NCBI fileEvidenceIEA
GeneRbm22Authority66810Mapping file id66810 NCBI fileEvidenceIEA
GeneRbm25Authority67039Mapping file id67039 NCBI fileEvidenceIEA
GeneRbm39Authority170791Mapping file id170791 NCBI fileEvidenceIEA
GeneRbm42Authority68035Mapping file id68035 NCBI fileEvidenceIEA
GeneRbm5Authority83486Mapping file id83486 NCBI fileEvidenceIEA
GeneRbm7Authority67010Mapping file id67010 NCBI fileEvidenceIEA
GeneRbm8aAuthority60365Mapping file id60365 NCBI fileEvidenceIEA
GeneRbmxAuthority19655Mapping file id19655 NCBI fileEvidenceIEA
GeneRbmx2Authority209003Mapping file id209003 NCBI fileEvidenceIEA
GeneRnf113a1Authority69942Mapping file id69942 NCBI fileEvidenceIEA
GeneRnf113a2Authority66381Mapping file id66381 NCBI fileEvidenceIEA
GeneRnpc3Authority67225Mapping file id67225 NCBI fileEvidenceIEA
GeneRnps1Authority19826Mapping file id19826 NCBI fileEvidenceIEA
GeneSap18Authority20220Mapping file id20220 NCBI fileEvidenceIEA
GeneSart1Authority20227Mapping file id20227 NCBI fileEvidenceIEA
GeneSde2Authority208768Mapping file id208768 NCBI fileEvidenceIEA
GeneSf1Authority22668Mapping file idENSMUSG00000024949 Ensembl fileEvidenceIEA
GeneSf3a1Authority67465Mapping file id67465 NCBI fileEvidenceIEA
GeneSf3a2Authority20222Mapping file idENSMUSG00000020211 Ensembl fileEvidenceIEA
GeneSf3a3Authority75062Mapping file id75062 NCBI fileEvidenceIEA
GeneSf3b1Authority81898Mapping file idENSMUSG00000025982 Ensembl fileEvidenceIEA
GeneSf3b2Authority319322Mapping file id319322 NCBI fileEvidenceIEA
GeneSf3b3Authority101943Mapping file id101943 NCBI fileEvidenceIEA
GeneSf3b4Authority107701Mapping file id107701 NCBI fileEvidenceIEA
GeneSf3b5Authority66125Mapping file id66125 NCBI fileEvidenceIEA
GeneSlu7Authority193116Mapping file id193116 NCBI fileEvidenceIEA
GeneSmndc1Authority76479Mapping file id76479 NCBI fileEvidenceIEA
GeneSmu1Authority74255Mapping file id74255 NCBI fileEvidenceIEA
GeneSnip1Authority76793Mapping file id76793 NCBI fileEvidenceIEA
GeneSnrnp200Authority320632Mapping file id320632 NCBI fileEvidenceIEA
GeneSnrnp25Authority78372Mapping file id78372 NCBI fileEvidenceIEA
GeneSnrnp27Authority66618Mapping file id66618 NCBI fileEvidenceIEA
GeneSnrnp35Authority76167Mapping file id76167 NCBI fileEvidenceIEA
GeneSnrnp40Authority66585Mapping file id66585 NCBI fileEvidenceIEA
GeneSnrnp48Authority67797Mapping file id67797 NCBI fileEvidenceIEA
GeneSnrnp70Authority20637Mapping file id20637 NCBI fileEvidenceIEA
GeneSnrpaAuthority53607Mapping file id53607 NCBI fileEvidenceIEA
GeneSnrpa1Authority68981Mapping file id68981 NCBI fileEvidenceIEA
GeneSnrpbAuthority20638Mapping file id20638 NCBI fileEvidenceIEA
GeneSnrpcAuthority20630Mapping file id20630 NCBI fileEvidenceIEA
GeneSnrpd1Authority20641Mapping file id20641 NCBI fileEvidenceIEA
GeneSnrpd2Authority107686Mapping file id107686 NCBI fileEvidenceIEA
GeneSnrpd3Authority67332Mapping file id67332 NCBI fileEvidenceIEA
GeneSnrpeAuthority20643Mapping file id20643 NCBI fileEvidenceIEA
GeneSnrpfAuthority69878Mapping file id69878 NCBI fileEvidenceIEA
GeneSnrpgAuthority68011Mapping file id68011 NCBI fileEvidenceIEA
GeneSnrpnAuthority20646Mapping file id20646 NCBI fileEvidenceIEA
GeneSnu13Authority20826Mapping file id20826 NCBI fileEvidenceIEA
GeneSnw1Authority66354Mapping file id66354 NCBI fileEvidenceIEA
GeneSrrm1Authority51796Mapping file id51796 NCBI fileEvidenceIEA
GeneSrrm2Authority75956Mapping file id75956 NCBI fileEvidenceIEA
GeneSrrtAuthority83701Mapping file id83701 NCBI fileEvidenceIEA
GeneSrsf1Authority110809Mapping file id110809 NCBI fileEvidenceIEA
GeneSrsf10Authority14105Mapping file id14105 NCBI fileEvidenceIEA
GeneSrsf11Authority69207Mapping file id69207 NCBI fileEvidenceIEA
GeneSrsf19Authority245492Mapping file id245492 NCBI fileEvidenceIEA
GeneSrsf2Authority20382Mapping file id20382 NCBI fileEvidenceIEA
GeneSrsf3Authority20383Mapping file id20383 NCBI fileEvidenceIEA
GeneSrsf5Authority20384Mapping file id20384 NCBI fileEvidenceIEA
GeneSrsf7Authority225027Mapping file id225027 NCBI fileEvidenceIEA
GeneSrsf9Authority108014Mapping file id108014 NCBI fileEvidenceIEA
GeneSteep1Authority77644Mapping file id77644 NCBI fileEvidenceIEA
GeneSugp1Authority70616Mapping file id70616 NCBI fileEvidenceIEA
GeneSyf2Authority68592Mapping file id68592 NCBI fileEvidenceIEA
GeneTcerg1Authority56070Mapping file id56070 NCBI fileEvidenceIEA
GeneTfip11Authority54723Mapping file id54723 NCBI fileEvidenceIEA
GeneTra2bAuthority20462Mapping file id20462 NCBI fileEvidenceIEA
GeneTxnl4aAuthority27366Mapping file id27366 NCBI fileEvidenceIEA
GeneU2af1Authority108121Mapping file id108121 NCBI fileEvidenceIEA
GeneU2af1l4Authority233073Mapping file id233073 NCBI fileEvidenceIEA
GeneU2af2Authority22185Mapping file id22185 NCBI fileEvidenceIEA
GeneU2surpAuthority67958Mapping file id67958 NCBI fileEvidenceIEA
GeneUbl5Authority66177Mapping file id66177 NCBI fileEvidenceIEA
GeneUpf3bAuthority68134Mapping file id68134 NCBI fileEvidenceIEA
GeneUsp39Authority28035Mapping file id28035 NCBI fileEvidenceIEA
GeneWbp11Authority60321Mapping file id60321 NCBI fileEvidenceIEA
GeneWbp4Authority22380Mapping file id22380 NCBI fileEvidenceIEA
GeneWdr70Authority545085Mapping file id545085 NCBI fileEvidenceIEA
GeneXab2Authority67439Mapping file id67439 NCBI fileEvidenceIEA
GeneYbx1Authority22608Mapping file id22608 NCBI fileEvidenceIEA
GeneYju2Authority72886Mapping file id72886 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.