Spironolactone Use and Improved Outcomes in Patients With Heart Failure With Preserved Ejection Fraction With Resistant Hypertension
Bibliographic record
Abstract
Background Resistant hypertension is a salt‐retaining condition possibly attributable to inappropriate aldosterone secretion. Methods and Results This study was a secondary analysis of the TOPCAT (Treatment of Preserved Cardiac Function Heart Failure With an Aldosterone Antagonist) trial. Patients with heart failure with preserved ejection fraction (HFpEF) with (n=1004) and without (n=2437) resistant hypertension were included. Resistant hypertension was defined as systolic blood pressure ≥130 mm Hg and/or diastolic blood pressure ≥80 mm Hg in a patient with hypertension, despite the concurrent use of a renin‐angiotensin system blocker (angiotensin‐converting enzyme inhibitor/angiotensin receptor blocker), a calcium channel blocker, and a diuretic; or as those patients using ≥4 classes of antihypertensive medication. The primary outcome was a composite of cardiovascular death, aborted cardiac arrest, or heart failure hospitalization. We analyzed hazard ratios (HRs) for outcomes with 95% CIs in the spironolactone group and compared them with the placebo group using Cox proportional hazard models. The risk of primary outcome events in patients with HFpEF with resistant hypertension was significantly lower in the spironolactone group than in the placebo group (HR, 0.70; 95% CI, 0.53–0.91; P =0.009), whereas the risk of primary outcome events in patients with HFpEF without resistant hypertension was not significantly different between the 2 groups (HR, 1.00; 95% CI, 0.83–1.20; P =0.97). There was a significant interaction between spironolactone use and resistant hypertension ( P =0.03). Similar associations were also observed in patients with HFpEF from the Americas (United States, Canada, Brazil, and Argentina) only. Conclusions Spironolactone may be an effective add‐on medication for patients with HFpEF with resistant hypertension taking angiotensin‐converting enzyme inhibitors/angiotensin receptor blockers, calcium channel blockers, and diuretics.
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.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 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".