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.

Regulated Necrosis

R-MMU-5218859 in Reactome release 97: under Programmed Cell Death, with 53 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-5218859 (human), R-RNO-5218859 (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 53 genes in this mouse pathway; showing 1 to 53, 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
GeneBak1Authority12018Mapping file id12018 NCBI fileEvidenceIEA
GeneBaxAuthority12028Mapping file id12028 NCBI fileEvidenceIEA
GeneBirc2Authority11797Mapping file id11797 NCBI fileEvidenceIEA
GeneBirc3Authority11796Mapping file id11796 NCBI fileEvidenceIEA
GeneCasp1Authority12362Mapping file id12362 NCBI fileEvidenceIEA
GeneCasp3Authority12367Mapping file id12367 NCBI fileEvidenceIEA
GeneCasp4Authority12363Mapping file id12363 NCBI fileEvidenceIEA
GeneCasp8Authority12370Mapping file id12370 NCBI fileEvidenceIEA
GeneCdc37Authority12539Mapping file id12539 NCBI fileEvidenceIEA
GeneCflarAuthority12633Mapping file id12633 NCBI fileEvidenceIEA
GeneChmp2aAuthority68953Mapping file id68953 NCBI fileEvidenceIEA
GeneChmp2bAuthority68942Mapping file id68942 NCBI fileEvidenceIEA
GeneChmp3Authority66700Mapping file id66700 NCBI fileEvidenceIEA
GeneChmp4bAuthority75608Mapping file id75608 NCBI fileEvidenceIEA
GeneChmp4cAuthority66371Mapping file id66371 NCBI fileEvidenceIEA
GeneChmp6Authority208092Mapping file id208092 NCBI fileEvidenceIEA
GeneChmp7Authority105513Mapping file id105513 NCBI fileEvidenceIEA
GeneCycsAuthority13063Mapping file id13063 NCBI fileEvidenceIEA
GeneElaneAuthority50701Mapping file id50701 NCBI fileEvidenceIEA
GeneFaddAuthority14082Mapping file id14082 NCBI fileEvidenceIEA
GeneFasAuthority14102Mapping file id14102 NCBI fileEvidenceIEA
GeneFaslAuthority14103Mapping file id14103 NCBI fileEvidenceIEA
GeneFlot1Authority14251Mapping file id14251 NCBI fileEvidenceIEA
GeneFlot2Authority14252Mapping file id14252 NCBI fileEvidenceIEA
GeneGsdmdAuthority69146Mapping file id69146 NCBI fileEvidenceIEA
GeneGsdmeAuthority54722Mapping file id54722 NCBI fileEvidenceIEA
GeneGzmbAuthority14939Mapping file id14939 NCBI fileEvidenceIEA
GeneHmgb1Authority15289Mapping file id15289 NCBI fileEvidenceIEA
GeneHsp90aa1Authority15519Mapping file id15519 NCBI fileEvidenceIEA
GeneIl18Authority16173Mapping file id16173 NCBI fileEvidenceIEA
GeneIl1aAuthority16175Mapping file id16175 NCBI fileEvidenceIEA
GeneIl1bAuthority16176Mapping file id16176 NCBI fileEvidenceIEA
GeneItchAuthority16396Mapping file id16396 NCBI fileEvidenceIEA
GeneMlklAuthority74568Mapping file id74568 NCBI fileEvidenceIEA
GeneOgtAuthority108155Mapping file id108155 NCBI fileEvidenceIEA
GenePdcd6ipAuthority18571Mapping file id18571 NCBI fileEvidenceIEA
GenePeli1Authority67245Mapping file id67245 NCBI fileEvidenceIEA
GenePrknAuthority50873Mapping file id50873 NCBI fileEvidenceIEA
GeneRipk1Authority19766Mapping file id19766 NCBI fileEvidenceIEA
GeneRipk3Authority56532Mapping file id56532 NCBI fileEvidenceIEA
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneSdcbpAuthority53378Mapping file id53378 NCBI fileEvidenceIEA
GeneStub1Authority56424Mapping file id56424 NCBI fileEvidenceIEA
GeneTnfrsf10bAuthority21933Mapping file id21933 NCBI fileEvidenceIEA
GeneTnfsf10Authority22035Mapping file id22035 NCBI fileEvidenceIEA
GeneTraddAuthority71609Mapping file id71609 NCBI fileEvidenceIEA
GeneTraf2Authority22030Mapping file id22030 NCBI fileEvidenceIEA
GeneUba52Authority22186Mapping file id22186 NCBI fileEvidenceIEA
GeneUba52rtAuthority666586Mapping file idENSMUSG00000068240 Ensembl fileEvidenceIEA
GeneUbbAuthority22187Mapping file id22187 NCBI fileEvidenceIEA
GeneUbcAuthority22190Mapping file id22190 NCBI fileEvidenceIEA
GeneUbe2l3Authority22195Mapping file id22195 NCBI fileEvidenceIEA
GeneXiapAuthority11798Mapping file id11798 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.