The effect of ramipril and telmisartan on serum potassium and its association with cardiovascular and renal events: Results from the ONTARGET trial
Bibliographic record
Abstract
AIMS: In the Ongoing Telmisartan Alone and in Combination with Ramipril Trial (ONTARGET), dual agent renin-angiotensin-aldosterone system (RAAS) blockade with angiotensin-converting-enzyme inhibitors (ACEIs) and angiotensin receptor blockers (ARBs) did not reduce the risk of renal and cardiovascular outcomes compared with the single use of either agent. Dual therapy however increased the incidence of hyperkalemia. We examined risk factors for hyper- and hyokalemia and hypothesized that both would be associated with worse cardiovascular and renal outcomes. METHODS: A post-hoc analysis of the ONTARGET trial comparing dual therapy (ramipril and telmisartan) vs monotherapy (ramipril or telmisartan) was performed. The association between serum potassium at week 6 on cardiovascular and renal outcomes during the 56 months follow-up was assessed by multivariate Cox analysis. The main cardiovascular outcome was the composite of cardiovascular death, myocardial infarction, stroke, or hospitalization for heart failure. The renal outcome was defined as the composite of a doubling of serum creatinine or chronic dialysis. RESULTS: Six weeks after randomization, hyperkalemia developed in 210 (2.7%) patients on dual therapy vs. 264 (1.6%) patients on monotherapy (p < 0.001 vs. dual therapy). Hypokalemia developed in 87 (1.1%) patients on dual therapy vs. 200 (1.2%)patients on monotherapy. Serum potassium was nonlinearly associated with cardiovascular and renal events with a nadir between 4.0-5.0 mmol/l for cardiovascular and 4.0-4.5 mmol/l for renal events such that subjects above or below these values exhibited higher risks. This association was independent of age, gender, diabetes, estimated glomerular filtration rate, systolic blood pressure and diuretic use. CONCLUSIONS: With the precautions stipulated by the protocol of the ONTARGET trial, hypokalemia and hyperkalemia were infrequent events. Nevertheless, both high and low serum potassium were associated with an increased risk of cardiovascular and renal disease.
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.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
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".