Key result
Phosphorylation of ryanodine receptors remains controversial regarding its functional consequences, such as FKBP dissociation, and the specific kinases responsible.
This review outlines the major debates in basic science regarding the phosphorylation of ryanodine receptors and its impact on calcium homeostasis in muscle cells.
Uncertainty over ryanodine receptor phosphorylation precludes clinical translation; leaves open mechanistic details and therapeutic targets for further study.
Both cardiac and skeletal muscle ryanodine receptors (RyRs) are parts of large complexes that include a number of kinases and phosphatases. These RyRs have several potential phosphorylation sites in their cytoplasmic domains, but the functional consequences of phosphorylation and the identity of the enzymes responsible have been subjects of considerable controversy. Hyperphosphorylation of Ser-2809 in RyR2 (cardiac isoform) and Ser-2843 in RyR1 (skeletal isoform) has been suggested to cause the dissociation of the FK506-binding protein (FKBP) from RyRs, producing "leaky channels," but some laboratories find no relationship between phosphorylation and FKBP binding. Also debated is the identity of the kinases that phosphorylate these serines: cAMP-dependent protein kinase (PKA) versus calmodulin kinase II (CaMKII). Phosphorylation of other targets of these kinases could also alter calcium homeostasis. For example, PKA also phosphorylates phospholamban (PLB), altering the Sarco-endoplasmic reticulum Ca2+ ATPase (SERCA) activity. This review summarizes the major findings and controversies associated with phosphorylation of RyRs.
No takes yet. Share an insight, caveat, or question.
Danila et al. (2004) conducted a review in Ryanodine receptor phosphorylation. Phosphorylation of ryanodine receptors remains controversial regarding its functional consequences, such as FKBP dissociation, and the specific kinases responsible.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: