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.

Regulation of PD-L1(CD274) Post-translational modification

R-MMU-9909615 in Reactome release 97: under Regulation of PD-L1(CD274) expression, with 84 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-9909615 (human), R-RNO-9909615 (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 84 genes in this mouse pathway; showing 1 to 84, 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
GeneAdrm1Authority56436Mapping file id56436 NCBI fileEvidenceIEA
GeneB3gnt3Authority72297Mapping file id72297 NCBI fileEvidenceIEA
GeneCcnd1Authority12443Mapping file id12443 NCBI fileEvidenceIEA
GeneCd274Authority60533Mapping file id60533 NCBI fileEvidenceIEA
GeneCdk4Authority12567Mapping file id12567 NCBI fileEvidenceIEA
GeneCops5Authority26754Mapping file id26754 NCBI fileEvidenceIEA
GeneCsnk2a1Authority12995Mapping file id12995 NCBI fileEvidenceIEA
GeneCsnk2a2Authority13000Mapping file id13000 NCBI fileEvidenceIEA
GeneCsnk2bAuthority13001Mapping file id13001 NCBI fileEvidenceIEA
GeneCul1Authority26965Mapping file id26965 NCBI fileEvidenceIEA
GeneCul3Authority26554Mapping file id26554 NCBI fileEvidenceIEA
GeneDad1Authority13135Mapping file id13135 NCBI fileEvidenceIEA
GeneDdostAuthority13200Mapping file id13200 NCBI fileEvidenceIEA
GeneDerl1Authority67819Mapping file id67819 NCBI fileEvidenceIEA
GeneDerl2Authority116891Mapping file id116891 NCBI fileEvidenceIEA
GeneDerl3Authority70377Mapping file id70377 NCBI fileEvidenceIEA
GeneErlec1Authority66753Mapping file id66753 NCBI fileEvidenceIEA
GeneErlin1Authority226144Mapping file id226144 NCBI fileEvidenceIEA
GeneErlin2Authority244373Mapping file id244373 NCBI fileEvidenceIEA
GeneGsk3bAuthority56637Mapping file id56637 NCBI fileEvidenceIEA
GeneMagt1Authority67075Mapping file id67075 NCBI fileEvidenceIEA
GeneMib2Authority76580Mapping file id76580 NCBI fileEvidenceIEA
GeneNek2Authority18005Mapping file id18005 NCBI fileEvidenceIEA
GeneOs9Authority216440Mapping file id216440 NCBI fileEvidenceIEA
GeneOst4Authority67695Mapping file id67695 NCBI fileEvidenceIEA
GeneOstcAuthority66357Mapping file id66357 NCBI fileEvidenceIEA
GenePdcd1Authority18566Mapping file id18566 NCBI fileEvidenceIEA
GenePdcd1lg2Authority58205Mapping file id58205 NCBI fileEvidenceIEA
GenePrkaa1Authority105787Mapping file id105787 NCBI fileEvidenceIEA
GenePrkaa2Authority108079Mapping file id108079 NCBI fileEvidenceIEA
GenePrkab1Authority19079Mapping file id19079 NCBI fileEvidenceIEA
GenePrkab2Authority108097Mapping file id108097 NCBI fileEvidenceIEA
GenePrkag1Authority19082Mapping file id19082 NCBI fileEvidenceIEA
GenePrkag2Authority108099Mapping file id108099 NCBI fileEvidenceIEA
GenePrkag3Authority241113Mapping file id241113 NCBI fileEvidenceIEA
GenePsma1Authority26440Mapping file id26440 NCBI fileEvidenceIEA
GenePsma2Authority19166Mapping file id19166 NCBI fileEvidenceIEA
GenePsma3Authority19167Mapping file id19167 NCBI fileEvidenceIEA
GenePsma4Authority26441Mapping file id26441 NCBI fileEvidenceIEA
GenePsma5Authority26442Mapping file id26442 NCBI fileEvidenceIEA
GenePsma6Authority26443Mapping file id26443 NCBI fileEvidenceIEA
GenePsma7Authority26444Mapping file id26444 NCBI fileEvidenceIEA
GenePsmb1Authority19170Mapping file id19170 NCBI fileEvidenceIEA
GenePsmb2Authority26445Mapping file id26445 NCBI fileEvidenceIEA
GenePsmb3Authority26446Mapping file id26446 NCBI fileEvidenceIEA
GenePsmb4Authority19172Mapping file id19172 NCBI fileEvidenceIEA
GenePsmb5Authority19173Mapping file id19173 NCBI fileEvidenceIEA
GenePsmb6Authority19175Mapping file id19175 NCBI fileEvidenceIEA
GenePsmb7Authority19177Mapping file id19177 NCBI fileEvidenceIEA
GenePsmc1Authority19179Mapping file id19179 NCBI fileEvidenceIEA
GenePsmc2Authority19181Mapping file id19181 NCBI fileEvidenceIEA
GenePsmc3Authority19182Mapping file id19182 NCBI fileEvidenceIEA
GenePsmc4Authority23996Mapping file id23996 NCBI fileEvidenceIEA
GenePsmc5Authority19184Mapping file id19184 NCBI fileEvidenceIEA
GenePsmc6Authority67089Mapping file id67089 NCBI fileEvidenceIEA
GenePsmd1Authority70247Mapping file id70247 NCBI fileEvidenceIEA
GenePsmd11Authority69077Mapping file id69077 NCBI fileEvidenceIEA
GenePsmd12Authority66997Mapping file id66997 NCBI fileEvidenceIEA
GenePsmd13Authority23997Mapping file id23997 NCBI fileEvidenceIEA
GenePsmd14Authority59029Mapping file id59029 NCBI fileEvidenceIEA
GenePsmd2Authority21762Mapping file id21762 NCBI fileEvidenceIEA
GenePsmd3Authority22123Mapping file id22123 NCBI fileEvidenceIEA
GenePsmd6Authority66413Mapping file id66413 NCBI fileEvidenceIEA
GenePsmd7Authority17463Mapping file id17463 NCBI fileEvidenceIEA
GenePsmd8Authority57296Mapping file id57296 NCBI fileEvidenceIEA
GeneRbx1Authority56438Mapping file id56438 NCBI fileEvidenceIEA
GeneRnf185Authority193670Mapping file id193670 NCBI fileEvidenceIEA
GeneRnf5Authority54197Mapping file id54197 NCBI fileEvidenceIEA
GeneRpn1Authority103963Mapping file id103963 NCBI fileEvidenceIEA
GeneRpn2Authority20014Mapping file id20014 NCBI fileEvidenceIEA
GeneRps27aAuthority78294Mapping file id78294 NCBI fileEvidenceIEA
GeneSel1lAuthority20338Mapping file id20338 NCBI fileEvidenceIEA
GeneSkp1Authority21402Mapping file id21402 NCBI fileEvidenceIEA
GeneSpopAuthority20747Mapping file id20747 NCBI fileEvidenceIEA
GeneStt3aAuthority16430Mapping file id16430 NCBI fileEvidenceIEA
GeneStt3bAuthority68292Mapping file id68292 NCBI fileEvidenceIEA
GeneTmem258Authority69038Mapping file id69038 NCBI fileEvidenceIEA
GeneTusc3Authority80286Mapping file id80286 NCBI fileEvidenceIEA
GeneUba52Authority22186Mapping file id22186 NCBI fileEvidenceIEA
GeneUba52rtAuthority666586Mapping file idENSMUSG00000068240 Ensembl fileEvidenceIEA
GeneUbbAuthority22187Mapping file id22187 NCBI fileEvidenceIEA
GeneUbcAuthority22190Mapping file id22190 NCBI fileEvidenceIEA
GeneVcpAuthority269523Mapping file id269523 NCBI fileEvidenceIEA
GeneYwhagAuthority22628Mapping file id22628 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.