Skip to content
Order

Pathway Human Homo sapiens

Ribosomal scanning and start codon recognition

R-HSA-72702 in Reactome release 97: under Cap-dependent Translation Initiation, with 59 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-72702 (mouse), R-RNO-72702 (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 59 genes in this human pathway; showing 1 to 59, 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
GeneEIF1AXAuthorityHGNC:3250Mapping file id1964 NCBI fileEvidenceTAS
GeneEIF2S1AuthorityHGNC:3265Mapping file id1965 NCBI fileEvidenceTAS
GeneEIF2S2AuthorityHGNC:3266Mapping file id8894 NCBI fileEvidenceTAS
GeneEIF2S3AuthorityHGNC:3267Mapping file id1968 NCBI fileEvidenceTAS
GeneEIF3AAuthorityHGNC:3271Mapping file id8661 NCBI fileEvidenceTAS
GeneEIF3BAuthorityHGNC:3280Mapping file id8662 NCBI fileEvidenceTAS
GeneEIF3CAuthorityHGNC:3279Mapping file id8663 NCBI fileEvidenceTAS
GeneEIF3DAuthorityHGNC:3278Mapping file id8664 NCBI fileEvidenceTAS
GeneEIF3EAuthorityHGNC:3277Mapping file id3646 NCBI fileEvidenceTAS
GeneEIF3FAuthorityHGNC:3275Mapping file id8665 NCBI fileEvidenceTAS
GeneEIF3GAuthorityHGNC:3274Mapping file id8666 NCBI fileEvidenceTAS
GeneEIF3HAuthorityHGNC:3273Mapping file id8667 NCBI fileEvidenceTAS
GeneEIF3IAuthorityHGNC:3272Mapping file id8668 NCBI fileEvidenceTAS
GeneEIF3JAuthorityHGNC:3270Mapping file id8669 NCBI fileEvidenceTAS
GeneEIF3KAuthorityHGNC:24656Mapping file id27335 NCBI fileEvidenceTAS
GeneEIF3LAuthorityHGNC:18138Mapping file id51386 NCBI fileEvidenceTAS
GeneEIF3MAuthorityHGNC:24460Mapping file id10480 NCBI fileEvidenceTAS
GeneEIF4A1AuthorityHGNC:3282Mapping file id1973 NCBI fileEvidenceTAS
GeneEIF4A2AuthorityHGNC:3284Mapping file id1974 NCBI fileEvidenceTAS
GeneEIF4BAuthorityHGNC:3285Mapping file id1975 NCBI fileEvidenceTAS
GeneEIF4EAuthorityHGNC:3287Mapping file id1977 NCBI fileEvidenceTAS
GeneEIF4G1AuthorityHGNC:3296Mapping file id1981 NCBI fileEvidenceTAS
GeneEIF4HAuthorityHGNC:12741Mapping file id7458 NCBI fileEvidenceTAS
GeneEIF5AuthorityHGNC:3299Mapping file id1983 NCBI fileEvidenceTAS
GeneFAUAuthorityHGNC:3597Mapping file id2197 NCBI fileEvidenceTAS
GeneRPS10AuthorityHGNC:10383Mapping file id6204 NCBI fileEvidenceTAS
GeneRPS11AuthorityHGNC:10384Mapping file id6205 NCBI fileEvidenceTAS
GeneRPS12AuthorityHGNC:10385Mapping file id6206 NCBI fileEvidenceTAS
GeneRPS13AuthorityHGNC:10386Mapping file id6207 NCBI fileEvidenceTAS
GeneRPS14AuthorityHGNC:10387Mapping file id6208 NCBI fileEvidenceTAS
GeneRPS15AuthorityHGNC:10388Mapping file id6209 NCBI fileEvidenceTAS
GeneRPS15AAuthorityHGNC:10389Mapping file id6210 NCBI fileEvidenceTAS
GeneRPS16AuthorityHGNC:10396Mapping file id6217 NCBI fileEvidenceTAS
GeneRPS17AuthorityHGNC:10397Mapping file id6218 NCBI fileEvidenceTAS
GeneRPS18AuthorityHGNC:10401Mapping file id6222 NCBI fileEvidenceTAS
GeneRPS19AuthorityHGNC:10402Mapping file id6223 NCBI fileEvidenceTAS
GeneRPS2AuthorityHGNC:10404Mapping file id6187 NCBI fileEvidenceTAS
GeneRPS20AuthorityHGNC:10405Mapping file id6224 NCBI fileEvidenceTAS
GeneRPS21AuthorityHGNC:10409Mapping file id6227 NCBI fileEvidenceTAS
GeneRPS23AuthorityHGNC:10410Mapping file id6228 NCBI fileEvidenceTAS
GeneRPS24AuthorityHGNC:10411Mapping file id6229 NCBI fileEvidenceTAS
GeneRPS25AuthorityHGNC:10413Mapping file id6230 NCBI fileEvidenceTAS
GeneRPS26AuthorityHGNC:10414Mapping file id6231 NCBI fileEvidenceTAS
GeneRPS27AuthorityHGNC:10416Mapping file id6232 NCBI fileEvidenceTAS
GeneRPS27AAuthorityHGNC:10417Mapping file id6233 NCBI fileEvidenceTAS
GeneRPS27LAuthorityHGNC:18476Mapping file id51065 NCBI fileEvidenceTAS
GeneRPS28AuthorityHGNC:10418Mapping file id6234 NCBI fileEvidenceTAS
GeneRPS29AuthorityHGNC:10419Mapping file id6235 NCBI fileEvidenceTAS
GeneRPS3AuthorityHGNC:10420Mapping file id6188 NCBI fileEvidenceTAS
GeneRPS3AAuthorityHGNC:10421Mapping file id6189 NCBI fileEvidenceTAS
GeneRPS4XAuthorityHGNC:10424Mapping file id6191 NCBI fileEvidenceTAS
GeneRPS4Y1AuthorityHGNC:10425Mapping file id6192 NCBI fileEvidenceTAS
GeneRPS4Y2AuthorityHGNC:18501Mapping file id140032 NCBI fileEvidenceTAS
GeneRPS5AuthorityHGNC:10426Mapping file id6193 NCBI fileEvidenceTAS
GeneRPS6AuthorityHGNC:10429Mapping file id6194 NCBI fileEvidenceTAS
GeneRPS7AuthorityHGNC:10440Mapping file id6201 NCBI fileEvidenceTAS
GeneRPS8AuthorityHGNC:10441Mapping file id6202 NCBI fileEvidenceTAS
GeneRPS9AuthorityHGNC:10442Mapping file id6203 NCBI fileEvidenceTAS
GeneRPSAAuthorityHGNC:6502Mapping file id3921 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.