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.

Metabolism of fat-soluble vitamins

R-MMU-6806667 in Reactome release 97: under Metabolism of vitamins and cofactors, with 52 genes placed in it by the mapping files and 3 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-6806667 (human), R-RNO-6806667 (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 52 genes in this mouse pathway; showing 1 to 52, 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
GeneAgrnAuthority11603Mapping file id11603 NCBI fileEvidenceIEA
GeneAkr1b10Authority67861Mapping file id67861 NCBI fileEvidenceIEA
GeneAkr1c12Authority622402Mapping file id622402 NCBI fileEvidenceIEA
GeneAkr1c13Authority27384Mapping file id27384 NCBI fileEvidenceIEA
GeneAkr1c14Authority105387Mapping file id105387 NCBI fileEvidenceIEA
GeneAkr1c18Authority105349Mapping file id105349 NCBI fileEvidenceIEA
GeneAkr1c19Authority432720Mapping file id432720 NCBI fileEvidenceIEA
GeneAkr1c20Authority116852Mapping file id116852 NCBI fileEvidenceIEA
GeneAkr1c21Authority77337Mapping file id77337 NCBI fileEvidenceIEA
GeneAkr1c6Authority83702Mapping file id83702 NCBI fileEvidenceIEA
GeneAkr1clAuthority70861Mapping file id70861 NCBI fileEvidenceIEA
GeneApoa1Authority11806Mapping file id11806 NCBI fileEvidenceIEA
GeneApoa2Authority11807Mapping file id11807 NCBI fileEvidenceIEA
GeneApoa4Authority11808Mapping file id11808 NCBI fileEvidenceIEA
GeneApobAuthority238055Mapping file id238055 NCBI fileEvidenceIEA
GeneApoc2Authority11813Mapping file id11813 NCBI fileEvidenceIEA
GeneApoc2lAuthority105886299Mapping file idENSMUSG00000109350 Ensembl fileEvidenceIEA
GeneApoc3Authority11814Mapping file id11814 NCBI fileEvidenceIEA
GeneApoeAuthority11816Mapping file id11816 NCBI fileEvidenceIEA
GeneApomAuthority55938Mapping file id55938 NCBI fileEvidenceIEA
GeneBco1Authority63857Mapping file id63857 NCBI fileEvidenceIEA
GeneBco2Authority170752Mapping file id170752 NCBI fileEvidenceIEA
GeneClpsAuthority109791Mapping file id109791 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
GeneGpihbp1Authority68453Mapping file id68453 NCBI fileEvidenceIEA
GeneLplAuthority16956Mapping file id16956 NCBI fileEvidenceIEA
GeneLratAuthority79235Mapping file id79235 NCBI fileEvidenceIEA
GeneLrp1Authority16971Mapping file id16971 NCBI fileEvidenceIEA
GeneLrp10Authority65107Mapping file id65107 NCBI fileEvidenceIEA
GeneLrp12Authority239393Mapping file id239393 NCBI fileEvidenceIEA
GeneLrp2Authority14725Mapping file id14725 NCBI fileEvidenceIEA
GeneLrp8Authority16975Mapping file id16975 NCBI fileEvidenceIEA
GenePlb1Authority665270Mapping file id665270 NCBI fileEvidenceIEA
GenePnlipAuthority69060Mapping file id69060 NCBI fileEvidenceIEA
GeneRbp1Authority19659Mapping file id19659 NCBI fileEvidenceIEA
GeneRbp2Authority19660Mapping file id19660 NCBI fileEvidenceIEA
GeneRbp4Authority19662Mapping file id19662 NCBI fileEvidenceIEA
GeneRdh11Authority17252Mapping file id17252 NCBI fileEvidenceIEA
GeneSdc1Authority20969Mapping file id20969 NCBI fileEvidenceIEA
GeneSdc2Authority15529Mapping file id15529 NCBI fileEvidenceIEA
GeneSdc3Authority20970Mapping file id20970 NCBI fileEvidenceIEA
GeneSdc4Authority20971Mapping file id20971 NCBI fileEvidenceIEA
GeneTtpaAuthority50500Mapping file id50500 NCBI fileEvidenceIEA
GeneTtrAuthority22139Mapping file id22139 NCBI fileEvidenceIEA
GeneUbiad1Authority71707Mapping file id71707 NCBI fileEvidenceIEA
GeneVkorc1Authority27973Mapping file id27973 NCBI fileEvidenceIEA
GeneVkorc1l1Authority69568Mapping file id69568 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.