AMPK alterations in cardiac physiology and pathology: enemy or ally?
Bibliographic record
Abstract
AMP-activated protein kinase (AMPK) has emerged as a key regulator of energy metabolism in the heart. The high energy demands of the heart are primarily met by the metabolism of both fatty acids and glucose, both processes being regulated by AMPK. During myocardial ischaemia a rapid activation of AMPK occurs, resulting in an activation of both glucose uptake and glycolysis, as well as an increase in fatty acid oxidation. This activation of AMPK has the potential to increase energy production and to inhibit apoptosis, thereby protecting the heart during the ischaemic stress. However, at clinically relevant high levels of fatty acids, ischaemic-induced activation of AMPK also stimulates fatty acid oxidation during and following ischaemia. This can contribute to ischaemic injury secondary to an inhibition of glucose oxidation, which results in a decrease in cardiac efficiency. In a number of other non-cardiac tissues, AMPK has been shown to have pro-apoptotic effects. As a result, the question of whether AMPK activation benefits or harms the ischaemic heart remains controversial. The role of AMPK in cardiac hypertrophy is also controversial. Activation of AMPK inhibits protein synthesis, and may be an adaptive response to pathological cardiac hypertrophy. However, none of mouse models of AMPK deficiency (excluding those that may involve the gamma2 subunit mutations) demonstrate increased cardiac mass, suggesting that AMPK is not essential for restriction of cardiac growth. In addition to the potential effects of AMPK on myofibrillar hypertrophy associated with pressure overload, there is also controversy with respect to the cardiac hypertrophy associated with the gamma2 subunit mutations. In the cardiac hypertrophy associated with glycogen overload, both activating and inactivating mutations of AMPK in mice are associated with a marked cardiac hypertrophy. This review will address the issue of whether AMPK activation acts as an enemy or ally to the ischaemic and hypertrophied heart. Resolving this issue has important implications as to whether therapeutic approaches to protect the ischaemic heart should be developed which either activate or inhibit AMPK.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.002 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.005 |
| Scholarly communication | 0.004 | 0.008 |
| Open science | 0.001 | 0.002 |
| Research integrity | 0.004 | 0.007 |
| Insufficient payload (model declined to judge) | 0.005 | 0.001 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".