Skip to content

Create an account and get up to 25% off.

Order

Pathway Human Homo sapiens

Phase 0 - rapid depolarisation

R-HSA-5576892 in Reactome release 97: under Cardiac conduction, with 34 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-5576892 (mouse), R-RNO-5576892 (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 34 genes in this human pathway; showing 1 to 34, 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
GeneCACNA1CAuthorityHGNC:1390Mapping file id775 NCBI fileEvidenceTAS
GeneCACNA2D2AuthorityHGNC:1400Mapping file id9254 NCBI fileEvidenceTAS
GeneCACNB1AuthorityHGNC:1401Mapping file id782 NCBI fileEvidenceTAS
GeneCACNB2AuthorityHGNC:1402Mapping file id783 NCBI fileEvidenceTAS
GeneCACNG4AuthorityHGNC:1408Mapping file id27092 NCBI fileEvidenceTAS
GeneCACNG6AuthorityHGNC:13625Mapping file id59285 NCBI fileEvidenceTAS
GeneCACNG7AuthorityHGNC:13626Mapping file id59284 NCBI fileEvidenceTAS
GeneCACNG8AuthorityHGNC:13628Mapping file id59283 NCBI fileEvidenceTAS
GeneCALM1AuthorityHGNC:1442Mapping file id801 NCBI fileEvidenceTAS
GeneCALM2AuthorityHGNC:1445Mapping file id805 NCBI fileEvidenceTAS
GeneCALM3AuthorityHGNC:1449Mapping file id808 NCBI fileEvidenceTAS
GeneCAMK2AAuthorityHGNC:1460Mapping file id815 NCBI fileEvidenceTAS
GeneCAMK2BAuthorityHGNC:1461Mapping file id816 NCBI fileEvidenceTAS
GeneCAMK2DAuthorityHGNC:1462Mapping file id817 NCBI fileEvidenceTAS
GeneCAMK2GAuthorityHGNC:1463Mapping file id818 NCBI fileEvidenceTAS
GeneFGF11AuthorityHGNC:3667Mapping file id2256 NCBI fileEvidenceTAS
GeneFGF12AuthorityHGNC:3668Mapping file id2257 NCBI fileEvidenceTAS
GeneFGF13AuthorityHGNC:3670Mapping file id2258 NCBI fileEvidenceTAS
GeneFGF14AuthorityHGNC:3671Mapping file id2259 NCBI fileEvidenceTAS
GeneRANGRFAuthorityHGNC:17679Mapping file id29098 NCBI fileEvidenceTAS
GeneSCN10AAuthorityHGNC:10582Mapping file id6336 NCBI fileEvidenceTAS
GeneSCN11AAuthorityHGNC:10583Mapping file id11280 NCBI fileEvidenceTAS
GeneSCN1AAuthorityHGNC:10585Mapping file id6323 NCBI fileEvidenceTAS
GeneSCN1BAuthorityHGNC:10586Mapping file id6324 NCBI fileEvidenceTAS
GeneSCN2AAuthorityHGNC:10588Mapping file id6326 NCBI fileEvidenceTAS
GeneSCN2BAuthorityHGNC:10589Mapping file id6327 NCBI fileEvidenceTAS
GeneSCN3AAuthorityHGNC:10590Mapping file id6328 NCBI fileEvidenceTAS
GeneSCN3BAuthorityHGNC:20665Mapping file id55800 NCBI fileEvidenceTAS
GeneSCN4AAuthorityHGNC:10591Mapping file id6329 NCBI fileEvidenceTAS
GeneSCN4BAuthorityHGNC:10592Mapping file id6330 NCBI fileEvidenceTAS
GeneSCN5AAuthorityHGNC:10593Mapping file id6331 NCBI fileEvidenceTAS
GeneSCN7AAuthorityHGNC:10594Mapping file id6332 NCBI fileEvidenceTAS
GeneSCN8AAuthorityHGNC:10596Mapping file id6334 NCBI fileEvidenceTAS
GeneSCN9AAuthorityHGNC:10597Mapping file id6335 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.