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.

Non-integrin membrane-ECM interactions

R-MMU-3000171 in Reactome release 97: under Extracellular matrix organization, with 56 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-3000171 (human), R-RNO-3000171 (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
GeneActa1Authority11459Mapping file id11459 NCBI fileEvidenceIEA
GeneActa2Authority11475Mapping file id11475 NCBI fileEvidenceIEA
GeneActbAuthority11461Mapping file id11461 NCBI fileEvidenceIEA
GeneActc1Authority11464Mapping file id11464 NCBI fileEvidenceIEA
GeneActg1Authority11465Mapping file id11465 NCBI fileEvidenceIEA
GeneActg2Authority11468Mapping file id11468 NCBI fileEvidenceIEA
GeneAgrnAuthority11603Mapping file id11603 NCBI fileEvidenceIEA
GeneCol10a1Authority12813Mapping file id12813 NCBI fileEvidenceIEA
GeneCol11a1Authority12814Mapping file id12814 NCBI fileEvidenceIEA
GeneCol11a2Authority12815Mapping file id12815 NCBI fileEvidenceIEA
GeneCol2a1Authority12824Mapping file id12824 NCBI fileEvidenceIEA
GeneCol3a1Authority12825Mapping file id12825 NCBI fileEvidenceIEA
GeneCol4a1Authority12826Mapping file id12826 NCBI fileEvidenceIEA
GeneCol4a2Authority12827Mapping file id12827 NCBI fileEvidenceIEA
GeneCol4a5Authority12830Mapping file id12830 NCBI fileEvidenceIEA
GeneCol4a6Authority94216Mapping file id94216 NCBI fileEvidenceIEA
GeneCol5a1Authority12831Mapping file id12831 NCBI fileEvidenceIEA
GeneCol5a2Authority12832Mapping file id12832 NCBI fileEvidenceIEA
GeneCol5a3Authority53867Mapping file id53867 NCBI fileEvidenceIEA
GeneDag1Authority13138Mapping file id13138 NCBI fileEvidenceIEA
GeneDdr1Authority12305Mapping file id12305 NCBI fileEvidenceIEA
GeneDdr2Authority18214Mapping file id18214 NCBI fileEvidenceIEA
GeneDmdAuthority13405Mapping file id13405 NCBI fileEvidenceIEA
GeneDrp2Authority13497Mapping file id13497 NCBI fileEvidenceIEA
GeneDtnaAuthority13527Mapping file id13527 NCBI fileEvidenceIEA
GeneDtnbAuthority13528Mapping file id13528 NCBI fileEvidenceIEA
GeneFgf2Authority14173Mapping file id14173 NCBI fileEvidenceIEA
GeneFn1Authority14268Mapping file id14268 NCBI fileEvidenceIEA
GeneItga2Authority16398Mapping file id16398 NCBI fileEvidenceIEA
GeneItga6Authority16403Mapping file id16403 NCBI fileEvidenceIEA
GeneItgavAuthority16410Mapping file id16410 NCBI fileEvidenceIEA
GeneItgb1Authority16412Mapping file id16412 NCBI fileEvidenceIEA
GeneItgb3Authority16416Mapping file id16416 NCBI fileEvidenceIEA
GeneItgb4Authority192897Mapping file id192897 NCBI fileEvidenceIEA
GeneItgb5Authority16419Mapping file id16419 NCBI fileEvidenceIEA
GeneLama4Authority16775Mapping file id16775 NCBI fileEvidenceIEA
GeneMegf11Authority214058Mapping file id214058 NCBI fileEvidenceIEA
GenePrkcaAuthority18750Mapping file id18750 NCBI fileEvidenceIEA
GeneSdc1Authority20969Mapping file id20969 NCBI fileEvidenceIEA
GeneSdc2Authority15529Mapping file id15529 NCBI fileEvidenceIEA
GeneSdc3Authority20970Mapping file id20970 NCBI fileEvidenceIEA
GeneSdc4Authority20971Mapping file id20971 NCBI fileEvidenceIEA
GeneSgcaAuthority20391Mapping file id20391 NCBI fileEvidenceIEA
GeneSgcbAuthority24051Mapping file id24051 NCBI fileEvidenceIEA
GeneSgcdAuthority24052Mapping file id24052 NCBI fileEvidenceIEA
GeneSgceAuthority20392Mapping file id20392 NCBI fileEvidenceIEA
GeneSgcgAuthority24053Mapping file id24053 NCBI fileEvidenceIEA
GeneSgczAuthority244431Mapping file id244431 NCBI fileEvidenceIEA
GeneSnta1Authority20648Mapping file idENSMUSG00000027488 Ensembl fileEvidenceIEA
GeneSntb1Authority20649Mapping file id20649 NCBI fileEvidenceIEA
GeneSntb2Authority20650Mapping file id20650 NCBI fileEvidenceIEA
GeneSntg2Authority268534Mapping file id268534 NCBI fileEvidenceIEA
GeneSspnAuthority16651Mapping file id16651 NCBI fileEvidenceIEA
GeneTgfb1Authority21803Mapping file id21803 NCBI fileEvidenceIEA
GeneUtrnAuthority22288Mapping file id22288 NCBI fileEvidenceIEA
GeneVtnAuthority22370Mapping file id22370 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.