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.

Immunoregulatory interactions between a Lymphoid and a non-Lymphoid cell

R-MMU-198933 in Reactome release 97: under Adaptive Immune System, with 149 genes placed in it by the mapping files and 0 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-198933 (human), R-RNO-198933 (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 149 genes in this mouse pathway; showing 101 to 149, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this mouse pathway, page 2 of 2
GeneIgkv1-35Authority620105Mapping file idENSMUSG00000076573 Ensembl fileEvidenceIEA
GeneIgkv11-125Authority243428Mapping file idENSMUSG00000095737 Ensembl fileEvidenceIEA
GeneIgkv12-98Authority435900Mapping file idENSMUSG00000076526 Ensembl fileEvidenceIEA
GeneIgkv13-84Authority692152Mapping file idENSMUSG00000076538 Ensembl fileEvidenceIEA
GeneIgkv13-85Authority434036Mapping file idENSMUSG00000079543 Ensembl fileEvidenceIEA
GeneIgkv15-103Authority692169Mapping file idENSMUSG00000076523 Ensembl fileEvidenceIEA
GeneIgkv17-121Authority667435Mapping file idENSMUSG00000076514 Ensembl fileEvidenceIEA
GeneIgkv18-36Authority620088Mapping file idENSMUSG00000076572 Ensembl fileEvidenceIEA
GeneIgkv2-109Authority628268Mapping file idENSMUSG00000105606 Ensembl fileEvidenceIEA
GeneIgkv2-137Authority692187Mapping file idENSMUSG00000076501 Ensembl fileEvidenceIEA
GeneIgkv8-21Authority620400Mapping file idENSMUSG00000076586 Ensembl fileEvidenceIEA
GeneIglc1Authority110785Mapping file idENSMUSG00000105906 Ensembl fileEvidenceIEA
GeneIglc2Authority110786Mapping file idENSMUSG00000076937 Ensembl fileEvidenceIEA
GeneIgll1Authority16136Mapping file id16136 NCBI fileEvidenceIEA
GeneItga4Authority16401Mapping file id16401 NCBI fileEvidenceIEA
GeneItgalAuthority16408Mapping file id16408 NCBI fileEvidenceIEA
GeneItgb1Authority16412Mapping file id16412 NCBI fileEvidenceIEA
GeneItgb2Authority16414Mapping file id16414 NCBI fileEvidenceIEA
GeneItgb7Authority16421Mapping file id16421 NCBI fileEvidenceIEA
GeneJamlAuthority270152Mapping file id270152 NCBI fileEvidenceIEA
GeneKir3dl1Authority245616Mapping file idENSMUSG00000031424 Ensembl fileEvidenceIEA
GeneKlrb1aAuthority17057Mapping file id17057 NCBI fileEvidenceIEA
GeneKlrk1Authority27007Mapping file id27007 NCBI fileEvidenceIEA
GeneLair1Authority52855Mapping file id52855 NCBI fileEvidenceIEA
GeneMadcam1Authority17123Mapping file idENSMUSG00000020310 Ensembl fileEvidenceIEA
GeneNectin2Authority19294Mapping file id19294 NCBI fileEvidenceIEA
GeneNpdc1Authority18146Mapping file id18146 NCBI fileEvidenceIEA
GenePianpAuthority319352Mapping file id319352 NCBI fileEvidenceIEA
GenePilraAuthority231805Mapping file id231805 NCBI fileEvidenceIEA
GenePvrAuthority52118Mapping file id52118 NCBI fileEvidenceIEA
GeneRaet1eAuthority379043Mapping file id379043 NCBI fileEvidenceIEA
GeneSellAuthority20343Mapping file id20343 NCBI fileEvidenceIEA
GeneSiglec1Authority20612Mapping file id20612 NCBI fileEvidenceIEA
GeneSigleceAuthority83382Mapping file id83382 NCBI fileEvidenceIEA
GeneSiglecfAuthority233186Mapping file id233186 NCBI fileEvidenceIEA
GeneSiglecgAuthority243958Mapping file id243958 NCBI fileEvidenceIEA
GeneSlamf6Authority30925Mapping file id30925 NCBI fileEvidenceIEA
GeneSlamf7Authority75345Mapping file id75345 NCBI fileEvidenceIEA
GeneTrav16Authority195297Mapping file idENSMUSG00000076855 Ensembl fileEvidenceIEA
GeneTrav19Authority547428Mapping file idENSMUSG00000076862 Ensembl fileEvidenceIEA
GeneTrbc2Authority100125263Mapping file idENSMUSG00000076498 Ensembl fileEvidenceIEA
GeneTrbv16Authority100124680Mapping file idENSMUSG00000076473 Ensembl fileEvidenceIEA
GeneTrem1Authority58217Mapping file id58217 NCBI fileEvidenceIEA
GeneTrem2Authority83433Mapping file id83433 NCBI fileEvidenceIEA
GeneTreml1Authority71326Mapping file id71326 NCBI fileEvidenceIEA
GeneTreml2Authority328833Mapping file id328833 NCBI fileEvidenceIEA
GeneTreml4Authority224840Mapping file id224840 NCBI fileEvidenceIEA
GeneUlbp1Authority77777Mapping file id77777 NCBI fileEvidenceIEA
GeneVcam1Authority22329Mapping file idENSMUSG00000027962 Ensembl 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

Children

None: no pathway of this release's list names this one as a parent.

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.