Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

Disorders of transmembrane transporters

R-HSA-5619115 in Reactome release 97: under Disease, with 163 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; 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 163 genes in this human pathway; showing 101 to 163, 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
GeneSEM1AuthorityHGNC:10845Mapping file id7979 NCBI fileEvidenceTAS
GeneSLC11A2AuthorityHGNC:10908Mapping file id4891 NCBI fileEvidenceTAS
GeneSLC12A1AuthorityHGNC:10910Mapping file id6557 NCBI fileEvidenceTAS
GeneSLC12A3AuthorityHGNC:10912Mapping file id6559 NCBI fileEvidenceTAS
GeneSLC12A6AuthorityHGNC:10914Mapping file id9990 NCBI fileEvidenceTAS
GeneSLC16A1AuthorityHGNC:10922Mapping file id6566 NCBI fileEvidenceTAS
GeneSLC17A5AuthorityHGNC:10933Mapping file id26503 NCBI fileEvidenceTAS
GeneSLC17A8AuthorityHGNC:20151Mapping file id246213 NCBI fileEvidenceTAS
GeneSLC1A1AuthorityHGNC:10939Mapping file id6505 NCBI fileEvidenceTAS
GeneSLC1A3AuthorityHGNC:10941Mapping file id6507 NCBI fileEvidenceTAS
GeneSLC20A2AuthorityHGNC:10947Mapping file id6575 NCBI fileEvidenceTAS
GeneSLC22A12AuthorityHGNC:17989Mapping file id116085 NCBI fileEvidenceTAS
GeneSLC22A5AuthorityHGNC:10969Mapping file id6584 NCBI fileEvidenceTAS
GeneSLC24A1AuthorityHGNC:10975Mapping file id9187 NCBI fileEvidenceTAS
GeneSLC24A4AuthorityHGNC:10978Mapping file id123041 NCBI fileEvidenceTAS
GeneSLC24A5AuthorityHGNC:20611Mapping file id283652 NCBI fileEvidenceTAS
GeneSLC26A2AuthorityHGNC:10994Mapping file id1836 NCBI fileEvidenceTAS
GeneSLC26A3AuthorityHGNC:3018Mapping file id1811 NCBI fileEvidenceTAS
GeneSLC26A4AuthorityHGNC:8818Mapping file id5172 NCBI fileEvidenceTAS
GeneSLC27A4AuthorityHGNC:10998Mapping file id10999 NCBI fileEvidenceTAS
GeneSLC29A3AuthorityHGNC:23096Mapping file id55315 NCBI fileEvidenceTAS
GeneSLC2A1AuthorityHGNC:11005Mapping file id6513 NCBI fileEvidenceTAS
GeneSLC2A10AuthorityHGNC:13444Mapping file id81031 NCBI fileEvidenceTAS
GeneSLC2A2AuthorityHGNC:11006Mapping file id6514 NCBI fileEvidenceTAS
GeneSLC2A9AuthorityHGNC:13446Mapping file id56606 NCBI fileEvidenceTAS
GeneSLC33A1AuthorityHGNC:95Mapping file id9197 NCBI fileEvidenceTAS
GeneSLC34A1AuthorityHGNC:11019Mapping file id6569 NCBI fileEvidenceTAS
GeneSLC34A2AuthorityHGNC:11020Mapping file id10568 NCBI fileEvidenceTAS
GeneSLC34A3AuthorityHGNC:20305Mapping file id142680 NCBI fileEvidenceTAS
GeneSLC35A1AuthorityHGNC:11021Mapping file id10559 NCBI fileEvidenceTAS
GeneSLC35A2AuthorityHGNC:11022Mapping file id7355 NCBI fileEvidenceTAS
GeneSLC35A3AuthorityHGNC:11023Mapping file id23443 NCBI fileEvidenceTAS
GeneSLC35C1AuthorityHGNC:20197Mapping file id55343 NCBI fileEvidenceTAS
GeneSLC36A2AuthorityHGNC:18762Mapping file id153201 NCBI fileEvidenceTAS
GeneSLC39A4AuthorityHGNC:17129Mapping file id55630 NCBI fileEvidenceTAS
GeneSLC3A1AuthorityHGNC:11025Mapping file id6519 NCBI fileEvidenceTAS
GeneSLC3A2AuthorityHGNC:11026Mapping file id6520 NCBI fileEvidenceTAS
GeneSLC40A1AuthorityHGNC:10909Mapping file id30061 NCBI fileEvidenceTAS
GeneSLC4A1AuthorityHGNC:11027Mapping file id6521 NCBI fileEvidenceTAS
GeneSLC4A4AuthorityHGNC:11030Mapping file id8671 NCBI fileEvidenceTAS
GeneSLC5A1AuthorityHGNC:11036Mapping file id6523 NCBI fileEvidenceTAS
GeneSLC5A2AuthorityHGNC:11037Mapping file id6524 NCBI fileEvidenceTAS
GeneSLC5A5AuthorityHGNC:11040Mapping file id6528 NCBI fileEvidenceTAS
GeneSLC5A7AuthorityHGNC:14025Mapping file id60482 NCBI fileEvidenceTAS
GeneSLC67A1AuthorityHGNC:10964Mapping file id5002 NCBI fileEvidenceTAS
GeneSLC6A14AuthorityHGNC:11047Mapping file id11254 NCBI fileEvidenceTAS
GeneSLC6A19AuthorityHGNC:27960Mapping file id340024 NCBI fileEvidenceTAS
GeneSLC6A2AuthorityHGNC:11048Mapping file id6530 NCBI fileEvidenceTAS
GeneSLC6A20AuthorityHGNC:30927Mapping file id54716 NCBI fileEvidenceTAS
GeneSLC6A3AuthorityHGNC:11049Mapping file id6531 NCBI fileEvidenceTAS
GeneSLC6A5AuthorityHGNC:11051Mapping file id9152 NCBI fileEvidenceTAS
GeneSLC7A7AuthorityHGNC:11065Mapping file id9056 NCBI fileEvidenceTAS
GeneSLC7A9AuthorityHGNC:11067Mapping file id11136 NCBI fileEvidenceTAS
GeneSLC9A6AuthorityHGNC:11079Mapping file id10479 NCBI fileEvidenceTAS
GeneSLC9A9AuthorityHGNC:20653Mapping file id285195 NCBI fileEvidenceTAS
GeneSLCO1B1AuthorityHGNC:10959Mapping file id10599 NCBI fileEvidenceTAS
GeneSLCO1B3AuthorityHGNC:10961Mapping file id28234 NCBI fileEvidenceTAS
GeneSLCO2A1AuthorityHGNC:10955Mapping file id6578 NCBI fileEvidenceTAS
GeneTPRAuthorityHGNC:12017Mapping file id7175 NCBI fileEvidenceTAS
GeneUBA52AuthorityHGNC:12458Mapping file id7311 NCBI fileEvidenceTAS
GeneUBBAuthorityHGNC:12463Mapping file id7314 NCBI fileEvidenceTAS
GeneUBCAuthorityHGNC:12468Mapping file id7316 NCBI fileEvidenceTAS
GeneVCPAuthorityHGNC:12666Mapping file id7415 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

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.