Pathway Human Homo sapiens

Class I peroxisomal membrane protein import

R-HSA-9603798 in Reactome release 97: under Protein localization, with 20 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-9603798 (mouse), R-RNO-9603798 (rat). Whether the event was inferred from this one is what the record says.

The record
The genes
Parents and children

Scripts are off

This page reads the pathway's record from its source while you read the rest; with scripts off the card stays at its loading line. Reload with scripts on to see it, or open the source's own page from the link in the card.

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

[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.
[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.
[R10] Reactome, reactome.org. License Agreement. https://reactome.org/license, read 2026-09-09.
[R12] Reactome, reactome.org. Citing us. https://reactome.org/cite, read 2026-09-09.
[R13] Reactome, reactome.org. Download. https://reactome.org/download-data, read 2026-09-09.

Stable id: R-HSA-9603798.3
Class: Pathway
Species: Homo sapiens (human)
Inferred: no: a curated human pathway
Disease pathway: no
Released: 2019-03-20
Events inside: 6, counted from the record

Most peroxisomal membrane proteins (PMPs) are inserted into the peroxisomal membrane by the receptor-chaperone PEX19 and the docking receptor PEX3 (Soukupova et al. 1999, Muntau et al. 2003, Fang et al. 2004, Fujiki et al. 2006, Matsuzono and Fujiki 2006, Matsuzono et al. 2006, Pinto et al. 2006, Sato et al. 2008, Sato et al. 2010, Schmidt et al. 2010, Hattula et al. 2014, reviewed in Fujiki et al. 2014, Mayerhofer 2016). PEX19 binds the PMP as it is translated in the cytosol. Recognition of the PMP by PEX 19 appears to depend on positively charged residues in the transmembrane domain of the PMP (Costello et al. 2017). The PEX19:PMP complex then interacts with PEX3 located in the peroxisomal membrane. Through a mechanism that is not yet clear, the PMP is inserted into the peroxisomal membrane and PEX19 dissociates from PEX3. A current model involves transfer of the PMP from PEX19 to a hydrophobic region of PEX3 followed by insertion of the PMP into the membrane (Chen et al. 2014, reviewed by Giannopoulou et al. 2016). The process does not appear to require hydrolysis of ATP or GTP (Pinto et al. 2006).

Unlike other PMPs, PEX3 is inserted into the peroxisomal membrane by binding PEX19 and then docking with PEX16 (Matsuzaki and Fujiki 2008). Both PEX3 and PEX16 can also be co-translationally inserted into the endoplasmic reticulum membrane (Kim et al. 2006, Yonekawa et al. 2011, Aranovich et al. 2014, Hua et al. 2015, Mayerhofer et al. 2016). This region of the ER membrane then buds to contribute to new peroxisomes. PEX3 is also observed to insert into the mitochondrial outer membrane (Sugiura et al. 2017). Regions of the ER membrane and mitochondrial outer membrane are then released to form pre-peroxisomal vesicles which fuse to form new peroxisomes (Sugiura et al. 2017). Peroxisomes therefore appear to arise from fission of existing peroxisomes and production of new peroxisomes from precursors derived from mitochondria and the ER (Sugiura et al. 2017, reviewed in Fujiki et al. 2014, Hua and Kim 2016).

Literature Reactome attaches

Towards the molecular mechanism of the integration of peroxisomal membrane proteins

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 20 genes in this human pathway; showing 1 to 20, 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
Gene	Authority id	Mapping file id	Evidence codes
GeneABCD1	AuthorityHGNC:61	Mapping file id215 NCBI file	EvidenceTAS
GeneABCD2	AuthorityHGNC:66	Mapping file id225 NCBI file	EvidenceTAS
GeneABCD3	AuthorityHGNC:67	Mapping file id5825 NCBI file	EvidenceTAS
GeneACBD5	AuthorityHGNC:23338	Mapping file id91452 NCBI file	EvidenceTAS
GeneALDH3A2	AuthorityHGNC:403	Mapping file id224 NCBI file	EvidenceTAS
GeneATAD1	AuthorityHGNC:25903	Mapping file id84896 NCBI file	EvidenceTAS
GeneFIS1	AuthorityHGNC:21689	Mapping file id51024 NCBI file	EvidenceTAS
GeneGDAP1	AuthorityHGNC:15968	Mapping file id54332 NCBI file	EvidenceTAS
GenePEX11B	AuthorityHGNC:8853	Mapping file id8799 NCBI file	EvidenceTAS
GenePEX12	AuthorityHGNC:8854	Mapping file id5193 NCBI file	EvidenceTAS
GenePEX13	AuthorityHGNC:8855	Mapping file id5194 NCBI file	EvidenceTAS
GenePEX14	AuthorityHGNC:8856	Mapping file id5195 NCBI file	EvidenceTAS
GenePEX16	AuthorityHGNC:8857	Mapping file id9409 NCBI file	EvidenceIEA, TAS
GenePEX19	AuthorityHGNC:9713	Mapping file id5824 NCBI file	EvidenceIEA, TAS
GenePEX2	AuthorityHGNC:9717	Mapping file id5828 NCBI file	EvidenceTAS
GenePEX26	AuthorityHGNC:22965	Mapping file id55670 NCBI file	EvidenceTAS
GenePEX3	AuthorityHGNC:8858	Mapping file id8504 NCBI file	EvidenceIEA, TAS
GenePXMP2	AuthorityHGNC:9716	Mapping file id5827 NCBI file	EvidenceTAS
GenePXMP4	AuthorityHGNC:15920	Mapping file id11264 NCBI file	EvidenceTAS
GeneSLC25A17	AuthorityHGNC:10987	Mapping file id10478 NCBI file	EvidenceTAS

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 2026-09-09 · 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

Parents

Protein localizationR-HSA-9609507164 genes

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 2026-09-09 · 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.