Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

Regulation of HSF1-mediated heat shock response

R-HSA-3371453 in Reactome release 97: under Cellular response to heat stress, with 82 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-MMU-3371453 (mouse), R-RNO-3371453 (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 82 genes in this human pathway; showing 1 to 82, in pages of 100, sorted by symbol for reading. The order carries no ranking.

Genes Reactome places in this human pathway, page 1 of 1
GeneAAASAuthorityHGNC:13666Mapping file id8086 NCBI fileEvidenceTAS
GeneATMAuthorityHGNC:795Mapping file id472 NCBI fileEvidenceTAS
GeneATRAuthorityHGNC:882Mapping file id545 NCBI fileEvidenceTAS
GeneBAG1AuthorityHGNC:937Mapping file id573 NCBI fileEvidenceTAS
GeneBAG2AuthorityHGNC:938Mapping file id9532 NCBI fileEvidenceTAS
GeneBAG3AuthorityHGNC:939Mapping file id9531 NCBI fileEvidenceTAS
GeneBAG4AuthorityHGNC:940Mapping file id9530 NCBI fileEvidenceTAS
GeneBAG5AuthorityHGNC:941Mapping file id9529 NCBI fileEvidenceTAS
GeneCCAR2AuthorityHGNC:23360Mapping file id57805 NCBI fileEvidenceTAS
GeneCOL4A6AuthorityHGNC:2208Mapping file idENSG00000197565 Ensembl fileEvidenceTAS
GeneCRYBA4AuthorityHGNC:2396Mapping file idENSG00000196431 Ensembl fileEvidenceTAS
GeneDEDD2AuthorityHGNC:24450Mapping file idENSG00000160570 Ensembl fileEvidenceTAS
GeneDNAJB1AuthorityHGNC:5270Mapping file id3337 NCBI fileEvidenceTAS
GeneDNAJB6AuthorityHGNC:14888Mapping file id10049 NCBI fileEvidenceTAS
GeneDNAJC2AuthorityHGNC:13192Mapping file id27000 NCBI fileEvidenceTAS
GeneDNAJC7AuthorityHGNC:12392Mapping file id7266 NCBI fileEvidenceTAS
GeneFKBP4AuthorityHGNC:3720Mapping file idENSG00000004478 Ensembl fileEvidenceTAS
GeneGMLAuthorityHGNC:4375Mapping file idENSG00000104499 Ensembl fileEvidenceTAS
GeneGSK3BAuthorityHGNC:4617Mapping file id2932 NCBI fileEvidenceTAS
GeneHIKESHIAuthorityHGNC:26938Mapping file id51501 NCBI fileEvidenceTAS
GeneHSF1AuthorityHGNC:5224Mapping file id3297 NCBI fileEvidenceTAS
GeneHSPA12AAuthorityHGNC:19022Mapping file id259217 NCBI fileEvidenceTAS
GeneHSPA12BAuthorityHGNC:16193Mapping file id116835 NCBI fileEvidenceTAS
GeneHSPA13AuthorityHGNC:11375Mapping file id6782 NCBI fileEvidenceTAS
GeneHSPA14AuthorityHGNC:29526Mapping file id51182 NCBI fileEvidenceTAS
GeneHSPA1AAuthorityHGNC:5232Mapping file id3303 NCBI fileEvidenceTAS
GeneHSPA1BAuthorityHGNC:5233Mapping file id3304 NCBI fileEvidenceTAS
GeneHSPA1LAuthorityHGNC:5234Mapping file id3305 NCBI fileEvidenceTAS
GeneHSPA2AuthorityHGNC:5235Mapping file id3306 NCBI fileEvidenceTAS
GeneHSPA4AuthorityHGNC:5237Mapping file id3308 NCBI fileEvidenceTAS
GeneHSPA4LAuthorityHGNC:17041Mapping file id22824 NCBI fileEvidenceTAS
GeneHSPA5AuthorityHGNC:5238Mapping file id3309 NCBI fileEvidenceTAS
GeneHSPA6AuthorityHGNC:5239Mapping file id3310 NCBI fileEvidenceTAS
GeneHSPA8AuthorityHGNC:5241Mapping file id3312 NCBI fileEvidenceTAS
GeneHSPA9AuthorityHGNC:5244Mapping file id3313 NCBI fileEvidenceTAS
GeneHSPB1AuthorityHGNC:5246Mapping file idENSG00000106211 Ensembl fileEvidenceTAS
GeneHSPB2AuthorityHGNC:5247Mapping file idENSG00000170276 Ensembl fileEvidenceTAS
GeneHSPH1AuthorityHGNC:16969Mapping file id10808 NCBI fileEvidenceTAS
GeneMAPK1AuthorityHGNC:6871Mapping file id5594 NCBI fileEvidenceTAS
GeneMAPK3AuthorityHGNC:6877Mapping file id5595 NCBI fileEvidenceTAS
GeneMAPKAPK2AuthorityHGNC:6887Mapping file id9261 NCBI fileEvidenceTAS
GeneMRPL18AuthorityHGNC:14477Mapping file idENSG00000112110 Ensembl fileEvidenceTAS
GeneNDC1AuthorityHGNC:25525Mapping file id55706 NCBI fileEvidenceTAS
GeneNUP107AuthorityHGNC:29914Mapping file id57122 NCBI fileEvidenceTAS
GeneNUP133AuthorityHGNC:18016Mapping file id55746 NCBI fileEvidenceTAS
GeneNUP153AuthorityHGNC:8062Mapping file id9972 NCBI fileEvidenceTAS
GeneNUP155AuthorityHGNC:8063Mapping file id9631 NCBI fileEvidenceTAS
GeneNUP160AuthorityHGNC:18017Mapping file id23279 NCBI fileEvidenceTAS
GeneNUP188AuthorityHGNC:17859Mapping file id23511 NCBI fileEvidenceTAS
GeneNUP205AuthorityHGNC:18658Mapping file id23165 NCBI fileEvidenceTAS
GeneNUP210AuthorityHGNC:30052Mapping file id23225 NCBI fileEvidenceTAS
GeneNUP214AuthorityHGNC:8064Mapping file id8021 NCBI fileEvidenceTAS
GeneNUP35AuthorityHGNC:29797Mapping file id129401 NCBI fileEvidenceTAS
GeneNUP37AuthorityHGNC:29929Mapping file id79023 NCBI fileEvidenceTAS
GeneNUP42AuthorityHGNC:17010Mapping file id11097 NCBI fileEvidenceTAS
GeneNUP43AuthorityHGNC:21182Mapping file id348995 NCBI fileEvidenceTAS
GeneNUP50AuthorityHGNC:8065Mapping file id10762 NCBI fileEvidenceTAS
GeneNUP54AuthorityHGNC:17359Mapping file id53371 NCBI fileEvidenceTAS
GeneNUP58AuthorityHGNC:20261Mapping file id9818 NCBI fileEvidenceTAS
GeneNUP62AuthorityHGNC:8066Mapping file id23636 NCBI fileEvidenceTAS
GeneNUP85AuthorityHGNC:8734Mapping file id79902 NCBI fileEvidenceTAS
GeneNUP88AuthorityHGNC:8067Mapping file id4927 NCBI fileEvidenceTAS
GeneNUP93AuthorityHGNC:28958Mapping file id9688 NCBI fileEvidenceTAS
GeneNUP98AuthorityHGNC:8068Mapping file id4928 NCBI fileEvidenceTAS
GenePOM121AuthorityHGNC:19702Mapping file id9883 NCBI fileEvidenceTAS
GenePOM121CAuthorityHGNC:34005Mapping file idENSG00000272391 Ensembl fileEvidenceTAS
GeneRAE1AuthorityHGNC:9828Mapping file id8480 NCBI fileEvidenceTAS
GeneRANBP2AuthorityHGNC:9848Mapping file id5903 NCBI fileEvidenceTAS
GeneRLN1AuthorityHGNC:10026Mapping file idENSG00000107018 Ensembl fileEvidenceTAS
GeneRPA1AuthorityHGNC:10289Mapping file id6117 NCBI fileEvidenceTAS
GeneRPA2AuthorityHGNC:10290Mapping file id6118 NCBI fileEvidenceTAS
GeneRPA3AuthorityHGNC:10291Mapping file id6119 NCBI fileEvidenceTAS
GeneRPS19BP1AuthorityHGNC:28749Mapping file id91582 NCBI fileEvidenceTAS
GeneSEC13AuthorityHGNC:10697Mapping file id6396 NCBI fileEvidenceTAS
GeneSEH1LAuthorityHGNC:30379Mapping file id81929 NCBI fileEvidenceTAS
GeneSERPINH1AuthorityHGNC:1546Mapping file idENSG00000149257 Ensembl fileEvidenceTAS
GeneSIRT1AuthorityHGNC:14929Mapping file id23411 NCBI fileEvidenceTAS
GeneST13AuthorityHGNC:11343Mapping file id6767 NCBI fileEvidenceTAS
GeneTNFRSF21AuthorityHGNC:13469Mapping file idENSG00000146072 Ensembl fileEvidenceTAS
GeneTPRAuthorityHGNC:12017Mapping file id7175 NCBI fileEvidenceTAS
GeneUBBAuthorityHGNC:12463Mapping file idENSG00000170315 Ensembl fileEvidenceTAS
GeneYWHAEAuthorityHGNC:12851Mapping file id7531 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.