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.

Hemostasis

R-MMU-109582 in Reactome release 97: a top-level pathway, with 588 genes placed in it by the mapping files and 7 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-109582 (human), R-RNO-109582 (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 588 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 6
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
GeneDok2Authority13449Mapping file id13449 NCBI fileEvidenceIEA
GeneEcm1Authority13601Mapping file id13601 NCBI fileEvidenceIEA
GeneEgfAuthority13645Mapping file id13645 NCBI fileEvidenceIEA
GeneEhd1Authority13660Mapping file id13660 NCBI fileEvidenceIEA
GeneEhd2Authority259300Mapping file id259300 NCBI fileEvidenceIEA
GeneEhd3Authority57440Mapping file id57440 NCBI fileEvidenceIEA
GeneEndod1Authority71946Mapping file id71946 NCBI fileEvidenceIEA
GeneEpcamAuthority17075Mapping file id17075 NCBI fileEvidenceIEA
GeneEsamAuthority69524Mapping file id69524 NCBI fileEvidenceIEA
GeneF10Authority14058Mapping file id14058 NCBI fileEvidenceIEA
GeneF11Authority109821Mapping file id109821 NCBI fileEvidenceIEA
GeneF11rAuthority16456Mapping file id16456 NCBI fileEvidenceIEA
GeneF12Authority58992Mapping file id58992 NCBI fileEvidenceIEA
GeneF13a1Authority74145Mapping file id74145 NCBI fileEvidenceIEA
GeneF13bAuthority14060Mapping file id14060 NCBI fileEvidenceIEA
GeneF2Authority14061Mapping file id14061 NCBI fileEvidenceIEA
GeneF2rAuthority14062Mapping file id14062 NCBI fileEvidenceIEA
GeneF2rl2Authority14064Mapping file id14064 NCBI fileEvidenceIEA
GeneF2rl3Authority14065Mapping file id14065 NCBI fileEvidenceIEA
GeneF3Authority14066Mapping file id14066 NCBI fileEvidenceIEA
GeneF5Authority14067Mapping file id14067 NCBI fileEvidenceIEA
GeneF7Authority14068Mapping file id14068 NCBI fileEvidenceIEA
GeneF8Authority14069Mapping file id14069 NCBI fileEvidenceIEA
GeneF9Authority14071Mapping file id14071 NCBI fileEvidenceIEA
GeneFam3cAuthority27999Mapping file id27999 NCBI fileEvidenceIEA
GeneFcamrAuthority64435Mapping file id64435 NCBI fileEvidenceIEA
GeneFcer1gAuthority14127Mapping file id14127 NCBI fileEvidenceIEA
GeneFermt3Authority108101Mapping file id108101 NCBI fileEvidenceIEA
GeneFgaAuthority14161Mapping file id14161 NCBI fileEvidenceIEA
GeneFgbAuthority110135Mapping file id110135 NCBI fileEvidenceIEA
GeneFggAuthority99571Mapping file id99571 NCBI fileEvidenceIEA
GeneFgrAuthority14191Mapping file id14191 NCBI fileEvidenceIEA
GeneFlnaAuthority192176Mapping file id192176 NCBI fileEvidenceIEA
GeneFn1Authority14268Mapping file id14268 NCBI fileEvidenceIEA
GeneFynAuthority14360Mapping file id14360 NCBI fileEvidenceIEA
GeneGas6Authority14456Mapping file id14456 NCBI fileEvidenceIEA
GeneGata1Authority14460Mapping file id14460 NCBI fileEvidenceIEA
GeneGata2Authority14461Mapping file id14461 NCBI fileEvidenceIEA
GeneGata3Authority14462Mapping file id14462 NCBI fileEvidenceIEA
GeneGata4Authority14463Mapping file id14463 NCBI fileEvidenceIEA
GeneGata5Authority14464Mapping file id14464 NCBI fileEvidenceIEA
GeneGata6Authority14465Mapping file id14465 NCBI fileEvidenceIEA
GeneGlg1Authority20340Mapping file id20340 NCBI fileEvidenceIEA
GeneGna11Authority14672Mapping file id14672 NCBI fileEvidenceIEA
GeneGna12Authority14673Mapping file id14673 NCBI fileEvidenceIEA
GeneGna13Authority14674Mapping file id14674 NCBI fileEvidenceIEA
GeneGna14Authority14675Mapping file id14675 NCBI fileEvidenceIEA
GeneGnai1Authority14677Mapping file id14677 NCBI fileEvidenceIEA
GeneGnai2Authority14678Mapping file id14678 NCBI fileEvidenceIEA
GeneGnai3Authority14679Mapping file id14679 NCBI fileEvidenceIEA
GeneGnaqAuthority14682Mapping file id14682 NCBI fileEvidenceIEA
GeneGnasAuthority14683Mapping file id14683 NCBI fileEvidenceIEA
GeneGnat3Authority242851Mapping file id242851 NCBI fileEvidenceIEA
GeneGnb1Authority14688Mapping file id14688 NCBI fileEvidenceIEA
GeneGnb2Authority14693Mapping file id14693 NCBI fileEvidenceIEA
GeneGnb3Authority14695Mapping file id14695 NCBI fileEvidenceIEA
GeneGnb4Authority14696Mapping file id14696 NCBI fileEvidenceIEA
GeneGnb5Authority14697Mapping file id14697 NCBI fileEvidenceIEA
GeneGng10Authority14700Mapping file id14700 NCBI fileEvidenceIEA
GeneGng11Authority66066Mapping file id66066 NCBI fileEvidenceIEA
GeneGng12Authority14701Mapping file id14701 NCBI fileEvidenceIEA
GeneGng13Authority64337Mapping file id64337 NCBI fileEvidenceIEA
GeneGng2Authority14702Mapping file id14702 NCBI fileEvidenceIEA
GeneGng3Authority14704Mapping file id14704 NCBI fileEvidenceIEA
GeneGng4Authority14706Mapping file id14706 NCBI fileEvidenceIEA
GeneGng5Authority14707Mapping file id14707 NCBI fileEvidenceIEA
GeneGng7Authority14708Mapping file id14708 NCBI fileEvidenceIEA
GeneGng8Authority14709Mapping file id14709 NCBI fileEvidenceIEA
GeneGngt1Authority14699Mapping file id14699 NCBI fileEvidenceIEA
GeneGngt2Authority14710Mapping file id14710 NCBI fileEvidenceIEA
GeneGp1baAuthority14723Mapping file id14723 NCBI fileEvidenceIEA
GeneGp1bbAuthority14724Mapping file id14724 NCBI fileEvidenceIEA
GeneGp5Authority14729Mapping file idENSMUSG00000047953 Ensembl fileEvidenceIEA
GeneGp6Authority243816Mapping file id243816 NCBI fileEvidenceIEA
GeneGp9Authority54368Mapping file id54368 NCBI fileEvidenceIEA
GeneGpc1Authority14733Mapping file id14733 NCBI fileEvidenceIEA
GeneGpc2Authority71951Mapping file id71951 NCBI fileEvidenceIEA
GeneGpc3Authority14734Mapping file id14734 NCBI fileEvidenceIEA
GeneGpc4Authority14735Mapping file id14735 NCBI fileEvidenceIEA
GeneGpc5Authority103978Mapping file id103978 NCBI fileEvidenceIEA
GeneGpc6Authority23888Mapping file id23888 NCBI fileEvidenceIEA
GeneGrb14Authority50915Mapping file id50915 NCBI fileEvidenceIEA
GeneGrb2Authority14784Mapping file id14784 NCBI fileEvidenceIEA
GeneGrb7Authority14786Mapping file id14786 NCBI fileEvidenceIEA
GeneGtpbp2Authority56055Mapping file id56055 NCBI fileEvidenceIEA
GeneH3c1Authority360198Mapping file id360198 NCBI fileEvidenceIEA
GeneH3c10Authority319152Mapping file id319152 NCBI fileEvidenceIEA
GeneH3c11Authority319153Mapping file id319153 NCBI fileEvidenceIEA
GeneH3c13Authority319154Mapping file id319154 NCBI fileEvidenceIEA
GeneH3c14Authority15077Mapping file id15077 NCBI fileEvidenceIEA
GeneH3c15Authority97114Mapping file id97114 NCBI fileEvidenceIEA
GeneH3c2Authority319150Mapping file id319150 NCBI fileEvidenceIEA
GeneH3c3Authority319148Mapping file id319148 NCBI fileEvidenceIEA
GeneH3c4Authority319149Mapping file id319149 NCBI fileEvidenceIEA
GeneH3c6Authority319151Mapping file id319151 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.