Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

Ion channel transport

R-HSA-983712 in Reactome release 97: under Transport of small molecules, with 185 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-983712 (mouse), R-RNO-983712 (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 185 genes in this human pathway; showing 101 to 185, 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
GeneCLCN6AuthorityHGNC:2024Mapping file id1185 NCBI fileEvidenceTAS
GeneCLCN7AuthorityHGNC:2025Mapping file id1186 NCBI fileEvidenceTAS
GeneCLCNKAAuthorityHGNC:2026Mapping file id1187 NCBI fileEvidenceTAS
GeneCLCNKBAuthorityHGNC:2027Mapping file id1188 NCBI fileEvidenceTAS
GeneCLIC2AuthorityHGNC:2063Mapping file id1193 NCBI fileEvidenceTAS
GeneCUTCAuthorityHGNC:24271Mapping file id51076 NCBI fileEvidenceIEA
GeneFKBP1BAuthorityHGNC:3712Mapping file id2281 NCBI fileEvidenceTAS
GeneFXYD1AuthorityHGNC:4025Mapping file id5348 NCBI fileEvidenceTAS
GeneFXYD2AuthorityHGNC:4026Mapping file id486 NCBI fileEvidenceTAS
GeneFXYD3AuthorityHGNC:4027Mapping file id5349 NCBI fileEvidenceTAS
GeneFXYD4AuthorityHGNC:4028Mapping file id53828 NCBI fileEvidenceTAS
GeneFXYD6AuthorityHGNC:4030Mapping file id53826 NCBI fileEvidenceTAS
GeneFXYD7AuthorityHGNC:4034Mapping file id53822 NCBI fileEvidenceTAS
GeneMCOLN1AuthorityHGNC:13356Mapping file id57192 NCBI fileEvidenceTAS
GeneMCOLN2AuthorityHGNC:13357Mapping file id255231 NCBI fileEvidenceTAS
GeneMCOLN3AuthorityHGNC:13358Mapping file id55283 NCBI fileEvidenceTAS
GeneMLKLAuthorityHGNC:26617Mapping file id197259 NCBI fileEvidenceTAS
GeneNALCNAuthorityHGNC:19082Mapping file id259232 NCBI fileEvidenceTAS
GeneNEDD4LAuthorityHGNC:7728Mapping file id23327 NCBI fileEvidenceTAS
GeneOSTM1AuthorityHGNC:21652Mapping file id28962 NCBI fileEvidenceTAS
GenePDZD11AuthorityHGNC:28034Mapping file id51248 NCBI fileEvidenceTAS
GenePLNAuthorityHGNC:9080Mapping file id5350 NCBI fileEvidenceTAS
GeneRAF1AuthorityHGNC:9829Mapping file id5894 NCBI fileEvidenceTAS
GeneRIPK1AuthorityHGNC:10019Mapping file id8737 NCBI fileEvidenceTAS
GeneRIPK3AuthorityHGNC:10021Mapping file id11035 NCBI fileEvidenceTAS
GeneRPS27AAuthorityHGNC:10417Mapping file id6233 NCBI fileEvidenceTAS
GeneRYR1AuthorityHGNC:10483Mapping file id6261 NCBI fileEvidenceTAS
GeneRYR2AuthorityHGNC:10484Mapping file id6262 NCBI fileEvidenceTAS
GeneRYR3AuthorityHGNC:10485Mapping file id6263 NCBI fileEvidenceTAS
GeneSCNN1AAuthorityHGNC:10599Mapping file id6337 NCBI fileEvidenceTAS
GeneSCNN1BAuthorityHGNC:10600Mapping file id6338 NCBI fileEvidenceTAS
GeneSCNN1DAuthorityHGNC:10601Mapping file id6339 NCBI fileEvidenceTAS
GeneSCNN1GAuthorityHGNC:10602Mapping file id6340 NCBI fileEvidenceTAS
GeneSGK1AuthorityHGNC:10810Mapping file id6446 NCBI fileEvidenceTAS
GeneSGK2AuthorityHGNC:13900Mapping file id10110 NCBI fileEvidenceTAS
GeneSGK3AuthorityHGNC:10812Mapping file id23678 NCBI fileEvidenceTAS
GeneSLC17A3AuthorityHGNC:10931Mapping file id10786 NCBI fileEvidenceTAS
GeneSLC9B1AuthorityHGNC:24244Mapping file id150159 NCBI fileEvidenceTAS
GeneSLC9B2AuthorityHGNC:25143Mapping file id133308 NCBI fileEvidenceTAS
GeneSLC9C1AuthorityHGNC:31401Mapping file id285335 NCBI fileEvidenceIEA
GeneSLC9C2AuthorityHGNC:28664Mapping file id284525 NCBI fileEvidenceTAS
GeneSLNAuthorityHGNC:11089Mapping file id6588 NCBI fileEvidenceTAS
GeneSRIAuthorityHGNC:11292Mapping file id6717 NCBI fileEvidenceTAS
GeneSTOMAuthorityHGNC:3383Mapping file id2040 NCBI fileEvidenceTAS
GeneSTOML3AuthorityHGNC:19420Mapping file id161003 NCBI fileEvidenceTAS
GeneTCIRG1AuthorityHGNC:11647Mapping file id10312 NCBI fileEvidenceTAS
GeneTPCN1AuthorityHGNC:18182Mapping file id53373 NCBI fileEvidenceTAS
GeneTPCN2AuthorityHGNC:20820Mapping file id219931 NCBI fileEvidenceTAS
GeneTRDNAuthorityHGNC:12261Mapping file id10345 NCBI fileEvidenceTAS
GeneTRPA1AuthorityHGNC:497Mapping file id8989 NCBI fileEvidenceTAS
GeneTRPC1AuthorityHGNC:12333Mapping file id7220 NCBI fileEvidenceTAS
GeneTRPC3AuthorityHGNC:12335Mapping file id7222 NCBI fileEvidenceTAS
GeneTRPC4AuthorityHGNC:12336Mapping file id7223 NCBI fileEvidenceTAS
GeneTRPC4APAuthorityHGNC:16181Mapping file id26133 NCBI fileEvidenceTAS
GeneTRPC5AuthorityHGNC:12337Mapping file id7224 NCBI fileEvidenceTAS
GeneTRPC6AuthorityHGNC:12338Mapping file id7225 NCBI fileEvidenceTAS
GeneTRPC7AuthorityHGNC:20754Mapping file id57113 NCBI fileEvidenceTAS
GeneTRPM1AuthorityHGNC:7146Mapping file id4308 NCBI fileEvidenceTAS
GeneTRPM2AuthorityHGNC:12339Mapping file id7226 NCBI fileEvidenceTAS
GeneTRPM3AuthorityHGNC:17992Mapping file id80036 NCBI fileEvidenceTAS
GeneTRPM4AuthorityHGNC:17993Mapping file id54795 NCBI fileEvidenceTAS
GeneTRPM5AuthorityHGNC:14323Mapping file id29850 NCBI fileEvidenceTAS
GeneTRPM6AuthorityHGNC:17995Mapping file id140803 NCBI fileEvidenceTAS
GeneTRPM7AuthorityHGNC:17994Mapping file id54822 NCBI fileEvidenceTAS
GeneTRPM8AuthorityHGNC:17961Mapping file id79054 NCBI fileEvidenceTAS
GeneTRPV1AuthorityHGNC:12716Mapping file id7442 NCBI fileEvidenceTAS
GeneTRPV2AuthorityHGNC:18082Mapping file id51393 NCBI fileEvidenceTAS
GeneTRPV3AuthorityHGNC:18084Mapping file id162514 NCBI fileEvidenceTAS
GeneTRPV4AuthorityHGNC:18083Mapping file id59341 NCBI fileEvidenceTAS
GeneTRPV5AuthorityHGNC:3145Mapping file id56302 NCBI fileEvidenceTAS
GeneTRPV6AuthorityHGNC:14006Mapping file id55503 NCBI fileEvidenceTAS
GeneTSC22D3AuthorityHGNC:3051Mapping file id1831 NCBI fileEvidenceTAS
GeneTTYH1AuthorityHGNC:13476Mapping file id57348 NCBI fileEvidenceTAS
GeneTTYH2AuthorityHGNC:13877Mapping file id94015 NCBI fileEvidenceTAS
GeneTTYH3AuthorityHGNC:22222Mapping file id80727 NCBI fileEvidenceTAS
GeneUBA52AuthorityHGNC:12458Mapping file id7311 NCBI fileEvidenceTAS
GeneUBBAuthorityHGNC:12463Mapping file id7314 NCBI fileEvidenceTAS
GeneUBCAuthorityHGNC:12468Mapping file id7316 NCBI fileEvidenceTAS
GeneUNC79AuthorityHGNC:19966Mapping file id57578 NCBI fileEvidenceTAS
GeneUNC80AuthorityHGNC:26582Mapping file id285175 NCBI fileEvidenceTAS
GeneWNK1AuthorityHGNC:14540Mapping file id65125 NCBI fileEvidenceTAS
GeneWNK2AuthorityHGNC:14542Mapping file id65268 NCBI fileEvidenceTAS
GeneWNK3AuthorityHGNC:14543Mapping file id65267 NCBI fileEvidenceTAS
GeneWNK4AuthorityHGNC:14544Mapping file id65266 NCBI fileEvidenceTAS
GeneWWP1AuthorityHGNC:17004Mapping file id11059 NCBI fileEvidenceTAS

Evidence codes on this page: IEA, 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.