Skip to content
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.

Coagulation pathway

R-MMU-9769740 in Reactome release 97: under Hemostasis, with 56 genes placed in it by the mapping files and 4 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-9769740 (human), R-RNO-9769740 (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 56 genes in this mouse pathway; showing 1 to 56, 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
GeneAdamts13Authority279028Mapping file id279028 NCBI fileEvidenceIEA
GeneAgrnAuthority11603Mapping file id11603 NCBI fileEvidenceIEA
GeneAno5Authority233246Mapping file id233246 NCBI fileEvidenceIEA
GeneAno6Authority105722Mapping file id105722 NCBI fileEvidenceIEA
GeneAppAuthority11820Mapping file id11820 NCBI fileEvidenceIEA
GeneCd177Authority68891Mapping file id68891 NCBI fileEvidenceIEA
GeneF10Authority14058Mapping file id14058 NCBI fileEvidenceIEA
GeneF11Authority109821Mapping file id109821 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
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
GeneFgaAuthority14161Mapping file id14161 NCBI fileEvidenceIEA
GeneFgbAuthority110135Mapping file id110135 NCBI fileEvidenceIEA
GeneFggAuthority99571Mapping file id99571 NCBI fileEvidenceIEA
GeneGp1baAuthority14723Mapping file id14723 NCBI fileEvidenceIEA
GeneGp1bbAuthority14724Mapping file id14724 NCBI fileEvidenceIEA
GeneGp5Authority14729Mapping file idENSMUSG00000047953 Ensembl 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
GeneItga2bAuthority16399Mapping file id16399 NCBI fileEvidenceIEA
GeneItgb3Authority16416Mapping file id16416 NCBI fileEvidenceIEA
GeneKlkb1Authority16621Mapping file id16621 NCBI fileEvidenceIEA
GeneKng2Authority385643Mapping file id385643 NCBI fileEvidenceIEA
GenePf4Authority56744Mapping file id56744 NCBI fileEvidenceIEA
GeneProcAuthority19123Mapping file id19123 NCBI fileEvidenceIEA
GeneProcrAuthority19124Mapping file id19124 NCBI fileEvidenceIEA
GenePros1Authority19128Mapping file id19128 NCBI fileEvidenceIEA
GeneProzAuthority66901Mapping file id66901 NCBI fileEvidenceIEA
GenePrtn3Authority19152Mapping file id19152 NCBI fileEvidenceIEA
GeneSdc1Authority20969Mapping file id20969 NCBI fileEvidenceIEA
GeneSdc2Authority15529Mapping file id15529 NCBI fileEvidenceIEA
GeneSdc3Authority20970Mapping file id20970 NCBI fileEvidenceIEA
GeneSdc4Authority20971Mapping file id20971 NCBI fileEvidenceIEA
GeneSerpina10Authority217847Mapping file id217847 NCBI fileEvidenceIEA
GeneSerpina5Authority268591Mapping file id268591 NCBI fileEvidenceIEA
GeneSerpinc1Authority11905Mapping file id11905 NCBI fileEvidenceIEA
GeneSerpind1Authority15160Mapping file id15160 NCBI fileEvidenceIEA
GeneSerpine1Authority18787Mapping file idENSMUSG00000037411 Ensembl fileEvidenceIEA
GeneSerpine2Authority20720Mapping file id20720 NCBI fileEvidenceIEA
GeneSerping1Authority12258Mapping file id12258 NCBI fileEvidenceIEA
GeneSmpd1Authority20597Mapping file id20597 NCBI fileEvidenceIEA
GeneTfpiAuthority21788Mapping file id21788 NCBI fileEvidenceIEA
GeneThbdAuthority21824Mapping file id21824 NCBI fileEvidenceIEA
GeneVwfAuthority22371Mapping file id22371 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.