Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

Initial triggering of complement

R-HSA-166663 in Reactome release 97: under Complement cascade, with 88 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-MMU-166663 (mouse), R-RNO-166663 (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.

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. [R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
  5. [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 human pathway

The mapping files place 88 genes in this human pathway; showing 1 to 88, in pages of 100, sorted by symbol for reading. The order carries no ranking. 7 of the rows shown carry an id the identity file does not name, kept as the source wrote it.

Genes Reactome places in this human pathway, page 1 of 1
GeneC1QAAuthorityHGNC:1241Mapping file id712 NCBI fileEvidenceTAS
GeneC1QBAuthorityHGNC:1242Mapping file id713 NCBI fileEvidenceTAS
GeneC1QCAuthorityHGNC:1245Mapping file id714 NCBI fileEvidenceTAS
GeneC1RAuthorityHGNC:1246Mapping file id715 NCBI fileEvidenceTAS
GeneC1SAuthorityHGNC:1247Mapping file id716 NCBI fileEvidenceTAS
GeneC2AuthorityHGNC:1248Mapping file id717 NCBI fileEvidenceTAS
GeneC3AuthorityHGNC:1318Mapping file id718 NCBI fileEvidenceTAS
GeneC4AAuthorityHGNC:1323Mapping file id720 NCBI fileEvidenceTAS
GeneC4A_2AuthorityHGNC:58753Mapping file idENSG00000227746 Ensembl fileEvidenceTAS
GeneC4BAuthorityHGNC:1324Mapping file id721 NCBI fileEvidenceTAS
GeneC4B_2AuthorityHGNC:42398Mapping file id100293534 NCBI fileEvidenceTAS
GeneCFBAuthorityHGNC:1037Mapping file id629 NCBI fileEvidenceTAS
GeneCFDAuthorityHGNC:2771Mapping file id1675 NCBI fileEvidenceTAS
GeneCFPAuthorityHGNC:8864Mapping file id5199 NCBI fileEvidenceTAS
GeneCOLEC10AuthorityHGNC:2220Mapping file id10584 NCBI fileEvidenceTAS
GeneCOLEC11AuthorityHGNC:17213Mapping file id78989 NCBI fileEvidenceTAS
GeneCRPAuthorityHGNC:2367Mapping file id1401 NCBI fileEvidenceTAS
GeneFCN1AuthorityHGNC:3623Mapping file id2219 NCBI fileEvidenceTAS
GeneFCN2AuthorityHGNC:3624Mapping file id2220 NCBI fileEvidenceTAS
GeneFCN3AuthorityHGNC:3625Mapping file id8547 NCBI fileEvidenceTAS
GeneGZMMAuthorityHGNC:4712Mapping file id3004 NCBI fileEvidenceTAS
GeneIGHG1AuthorityHGNC:5525Mapping file idENSG00000211896 Ensembl fileEvidenceTAS
GeneIGHG2AuthorityHGNC:5526Mapping file idENSG00000211893 Ensembl fileEvidenceTAS
GeneIGHG4AuthorityHGNC:5528Mapping file idENSG00000211892 Ensembl fileEvidenceTAS
GeneIGHV1-2AuthorityHGNC:5550Mapping file idENSG00000211934 Ensembl fileEvidenceTAS
GeneIGHV1-46AuthorityHGNC:5554Mapping file idENSG00000211962 Ensembl fileEvidenceTAS
GeneIGHV1-69AuthorityHGNC:5558Mapping file idENSG00000211973 Ensembl fileEvidenceTAS
GeneIGHV2-5AuthorityHGNC:5576Mapping file idENSG00000211937 Ensembl fileEvidenceTAS
GeneIGHV2-70AuthorityHGNC:5577Mapping file idENSG00000274576 Ensembl fileEvidenceTAS
GeneIGHV3-11AuthorityHGNC:5580Mapping file idENSG00000211941 Ensembl fileEvidenceTAS
GeneIGHV3-13AuthorityHGNC:5581Mapping file idENSG00000211942 Ensembl fileEvidenceTAS
GeneIGHV3-23AuthorityHGNC:5588Mapping file idENSG00000211949 Ensembl fileEvidenceTAS
GeneIGHV3-30AuthorityHGNC:5591Mapping file idENSG00000270550 Ensembl fileEvidenceTAS
GeneIGHV3-33AuthorityHGNC:5596Mapping file idENSG00000211955 Ensembl fileEvidenceTAS
GeneIGHV3-48AuthorityHGNC:5606Mapping file idENSG00000211964 Ensembl fileEvidenceTAS
GeneIGHV3-53AuthorityHGNC:5610Mapping file idENSG00000211967 Ensembl fileEvidenceTAS
GeneIGHV3-7AuthorityHGNC:5620Mapping file idENSG00000211938 Ensembl fileEvidenceTAS
GeneIGHV4-34AuthorityHGNC:5650Mapping file idENSG00000211956 Ensembl fileEvidenceTAS
GeneIGHV4-39AuthorityHGNC:5651Mapping file idENSG00000211959 Ensembl fileEvidenceTAS
GeneIGHV4-59AuthorityHGNC:5654Mapping file idENSG00000224373 Ensembl fileEvidenceTAS
GeneIGKV1-12AuthorityHGNC:5730Mapping file idENSG00000243290 Ensembl fileEvidenceTAS
GeneIGKV1-16AuthorityHGNC:5732Mapping file idENSG00000240864 Ensembl fileEvidenceTAS
GeneIGKV1-17AuthorityHGNC:5733Mapping file idENSG00000240382 Ensembl fileEvidenceTAS
GeneIGKV1-33AuthorityHGNC:5737Mapping file idENSG00000242076 Ensembl fileEvidenceTAS
GeneIGKV1-39AuthorityHGNC:5740Mapping file idENSG00000242371 Ensembl fileEvidenceTAS
GeneIGKV1-5AuthorityHGNC:5741Mapping file idENSG00000243466 Ensembl fileEvidenceTAS
GeneIGKV1D-12AuthorityHGNC:5746Mapping file idENSG00000278857 Ensembl fileEvidenceTAS
GeneIGKV1D-16AuthorityHGNC:5748Mapping file idENSG00000241244 Ensembl fileEvidenceTAS
GeneIGKV1D-33AuthorityHGNC:5753Mapping file idENSG00000239975 Ensembl fileEvidenceTAS
GeneIGKV1D-39AuthorityHGNC:5756Mapping file idENSG00000251546 Ensembl fileEvidenceTAS
GeneIGKV2-28AuthorityHGNC:5783Mapping file idENSG00000244116 Ensembl fileEvidenceTAS
GeneIGKV2-30AuthorityHGNC:5785Mapping file idENSG00000243238 Ensembl fileEvidenceTAS
GeneIGKV2D-28AuthorityHGNC:5799Mapping file idENSG00000242534 Ensembl fileEvidenceTAS
GeneIGKV2D-30AuthorityHGNC:5801Mapping file idENSG00000239571 Ensembl fileEvidenceTAS
GeneIGKV2D-40AuthorityHGNC:5804Mapping file idENSG00000251039 Ensembl fileEvidenceTAS
GeneIGKV3-11AuthorityHGNC:5815Mapping file idENSG00000241351 Ensembl fileEvidenceTAS
GeneIGKV3-15AuthorityHGNC:5816Mapping file idENSG00000244437 Ensembl fileEvidenceTAS
GeneIGKV3-20AuthorityHGNC:5817Mapping file idENSG00000239951 Ensembl fileEvidenceTAS
GeneIGKV3D-20AuthorityHGNC:5825Mapping file idENSG00000211625 Ensembl fileEvidenceTAS
GeneIGKV4-1AuthorityHGNC:5834Mapping file idENSG00000211598 Ensembl fileEvidenceTAS
GeneIGKV5-2AuthorityHGNC:5835Mapping file idENSG00000211599 Ensembl fileEvidenceTAS
GeneIGLC2AuthorityHGNC:5856Mapping file idENSG00000211677 Ensembl fileEvidenceTAS
GeneIGLC3AuthorityHGNC:5857Mapping file idENSG00000211679 Ensembl fileEvidenceTAS
GeneIGLV1-40AuthorityHGNC:5877Mapping file idENSG00000211653 Ensembl fileEvidenceTAS
GeneIGLV1-44AuthorityHGNC:5879Mapping file idENSG00000211651 Ensembl fileEvidenceTAS
GeneIGLV1-47AuthorityHGNC:5880Mapping file idENSG00000211648 Ensembl fileEvidenceTAS
GeneIGLV1-51AuthorityHGNC:5882Mapping file idENSG00000211644 Ensembl fileEvidenceTAS
GeneIGLV2-11AuthorityHGNC:5887Mapping file idENSG00000211668 Ensembl fileEvidenceTAS
GeneIGLV2-14AuthorityHGNC:5888Mapping file idENSG00000211666 Ensembl fileEvidenceTAS
GeneIGLV2-23AuthorityHGNC:5890Mapping file idENSG00000211660 Ensembl fileEvidenceTAS
GeneIGLV2-8AuthorityHGNC:5895Mapping file idENSG00000278196 Ensembl fileEvidenceTAS
GeneIGLV3-1AuthorityHGNC:5896Mapping file idENSG00000211673 Ensembl fileEvidenceTAS
GeneIGLV3-19AuthorityHGNC:5903Mapping file idENSG00000211663 Ensembl fileEvidenceTAS
GeneIGLV3-21AuthorityHGNC:5905Mapping file idENSG00000211662 Ensembl fileEvidenceTAS
GeneIGLV3-25AuthorityHGNC:5908Mapping file idENSG00000211659 Ensembl fileEvidenceTAS
GeneIGLV3-27AuthorityHGNC:5910Mapping file idENSG00000211658 Ensembl fileEvidenceTAS
GeneIGLV6-57AuthorityHGNC:5927Mapping file idENSG00000211640 Ensembl fileEvidenceTAS
GeneIGLV7-43AuthorityHGNC:5929Mapping file idENSG00000211652 Ensembl fileEvidenceTAS
GeneMASP1AuthorityHGNC:6901Mapping file id5648 NCBI fileEvidenceTAS
GeneMASP2AuthorityHGNC:6902Mapping file id10747 NCBI fileEvidenceTAS
GeneMBL2AuthorityHGNC:6922Mapping file id4153 NCBI fileEvidenceTAS
Geneno symbol in the identity fileAuthoritynoneMapping file id43740568 NCBI fileEvidenceTAS
Geneno symbol in the identity fileAuthoritynoneMapping file id43740569 NCBI fileEvidenceTAS
Geneno symbol in the identity fileAuthoritynoneMapping file id43740570 NCBI fileEvidenceTAS
Geneno symbol in the identity fileAuthoritynoneMapping file id43740571 NCBI fileEvidenceTAS
Geneno symbol in the identity fileAuthoritynoneMapping file id43740573 NCBI fileEvidenceTAS
Geneno symbol in the identity fileAuthoritynoneMapping file id43740575 NCBI fileEvidenceTAS
Geneno symbol in the identity fileAuthoritynoneMapping file idMN908947.3 as writtenEvidenceTAS

Evidence codes on this page: TAS, 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: of the 138,908 human pathway-gene pairs both files place, 207 (0.149 per cent, over 47 genes) carry TAS in the Ensembl file where the NCBI rows carry IEA alone.

  • Reactome mapping files, the human 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 human 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.