Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

Potential therapeutics for SARS

R-HSA-9679191 in Reactome release 97: under SARS-CoV Infections, with 155 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; neither of the other two lists holds it. 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 155 genes in this human pathway; showing 101 to 155, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this human pathway, page 2 of 2
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
GeneIL1R1AuthorityHGNC:5993Mapping file id3554 NCBI fileEvidenceTAS
GeneIL6RAuthorityHGNC:6019Mapping file id3570 NCBI fileEvidenceTAS
GeneIMPDH1AuthorityHGNC:6052Mapping file id3614 NCBI fileEvidenceTAS
GeneIMPDH2AuthorityHGNC:6053Mapping file id3615 NCBI fileEvidenceTAS
GeneITGA4AuthorityHGNC:6140Mapping file id3676 NCBI fileEvidenceTAS
GeneITGB1AuthorityHGNC:6153Mapping file id3688 NCBI fileEvidenceTAS
GeneJAK1AuthorityHGNC:6190Mapping file id3716 NCBI fileEvidenceTAS
GeneJAK2AuthorityHGNC:6192Mapping file id3717 NCBI fileEvidenceTAS
GeneJAK3AuthorityHGNC:6193Mapping file id3718 NCBI fileEvidenceTAS
GeneKDM1AAuthorityHGNC:29079Mapping file id23028 NCBI fileEvidenceTAS
GeneKEAP1AuthorityHGNC:23177Mapping file id9817 NCBI fileEvidenceTAS
GeneMBD3AuthorityHGNC:6918Mapping file id53615 NCBI fileEvidenceTAS
GeneMTA1AuthorityHGNC:7410Mapping file id9112 NCBI fileEvidenceTAS
GeneMTA2AuthorityHGNC:7411Mapping file id9219 NCBI fileEvidenceTAS
GeneMTA3AuthorityHGNC:23784Mapping file id57504 NCBI fileEvidenceTAS
GeneNCK1AuthorityHGNC:7664Mapping file id4690 NCBI fileEvidenceTAS
GeneNFE2L2AuthorityHGNC:7782Mapping file id4780 NCBI fileEvidenceTAS
GeneNR3C1AuthorityHGNC:7978Mapping file id2908 NCBI fileEvidenceTAS
GenePDCD1AuthorityHGNC:8760Mapping file id5133 NCBI fileEvidenceTAS
GenePHF21AAuthorityHGNC:24156Mapping file id51317 NCBI fileEvidenceTAS
GenePLCG2AuthorityHGNC:9066Mapping file id5336 NCBI fileEvidenceTAS
GenePTGES3AuthorityHGNC:16049Mapping file id10728 NCBI fileEvidenceTAS
GeneRBBP4AuthorityHGNC:9887Mapping file id5928 NCBI fileEvidenceTAS
GeneRBBP7AuthorityHGNC:9890Mapping file id5931 NCBI fileEvidenceTAS
GeneRBX1AuthorityHGNC:9928Mapping file id9978 NCBI fileEvidenceTAS
GeneRCOR1AuthorityHGNC:17441Mapping file id23186 NCBI fileEvidenceTAS
GeneRESTAuthorityHGNC:9966Mapping file id5978 NCBI fileEvidenceTAS
GeneRIPK1AuthorityHGNC:10019Mapping file id8737 NCBI fileEvidenceTAS
GeneROCK1AuthorityHGNC:10251Mapping file id6093 NCBI fileEvidenceTAS
GeneROCK2AuthorityHGNC:10252Mapping file id9475 NCBI fileEvidenceTAS
GeneS1PR1AuthorityHGNC:3165Mapping file id1901 NCBI fileEvidenceTAS
GeneSAP18AuthorityHGNC:10530Mapping file id10284 NCBI fileEvidenceTAS
GeneSAP30AuthorityHGNC:10532Mapping file id8819 NCBI fileEvidenceTAS
GeneSAP30LAuthorityHGNC:25663Mapping file id79685 NCBI fileEvidenceTAS
GeneSH3KBP1AuthorityHGNC:13867Mapping file id30011 NCBI fileEvidenceTAS
GeneSIGMAR1AuthorityHGNC:8157Mapping file id10280 NCBI fileEvidenceTAS
GeneSOS1AuthorityHGNC:11187Mapping file id6654 NCBI fileEvidenceTAS
GeneSTAT2AuthorityHGNC:11363Mapping file id6773 NCBI fileEvidenceTAS
GeneSUDS3AuthorityHGNC:29545Mapping file id64426 NCBI fileEvidenceTAS
GeneSYKAuthorityHGNC:11491Mapping file id6850 NCBI fileEvidenceTAS
GeneTBK1AuthorityHGNC:11584Mapping file id29110 NCBI fileEvidenceTAS
GeneTLR7AuthorityHGNC:15631Mapping file id51284 NCBI fileEvidenceTAS
GeneTLR9AuthorityHGNC:15633Mapping file id54106 NCBI fileEvidenceTAS
GeneTUBBAuthorityHGNC:20778Mapping file id203068 NCBI fileEvidenceTAS
GeneTYK2AuthorityHGNC:12440Mapping file id7297 NCBI fileEvidenceTAS
GeneVAV1AuthorityHGNC:12657Mapping file id7409 NCBI fileEvidenceTAS
GeneVEGFAAuthorityHGNC:12680Mapping file id7422 NCBI fileEvidenceTAS
GeneZBP1AuthorityHGNC:16176Mapping file id81030 NCBI fileEvidenceTAS

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

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 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.