MétaCan
Menu
Back to cohort
Record W1994715569 · doi:10.1002/clc.20838

Spironolactone Use in Heart Failure Patients With End‐Stage Renal Disease on Hemodialysis: Is It Safe?

2010· review· en· W1994715569 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueClinical Cardiology · 2010
Typereview
Languageen
FieldMedicine
TopicPotassium and Related Disorders
Canadian institutionsEagle Ridge HospitalSt. Paul's Hospital
Fundersnot available
KeywordsHyperkalemiaMedicineSpironolactoneHemodialysisEplerenoneEnd stage renal diseaseInternal medicineKidney diseasePopulationHeart failureIntensive care medicineCardiology

Abstract

fetched live from OpenAlex

BACKGROUND: Spironolactone is used in the treatment of cardiovascular disease, but is contraindicated in renal dysfunction due to the risk of hyperkalemia. It is not known if patients with end-stage renal disease (ESRD) on hemodialysis are at the same risk for hyperkalemia. The objective of this study was to systematically review the evidence evaluating the incidence of hyperkalemia with spironolactone use in ESRD patients on hemodialysis. HYPOTHESIS: Spironolactone use in ESRD patients on hemodialysis may not lead to greater incidence of hyperkalemia. METHODS: We searched the MEDLINE, Embase, CINAHL, Cochrane, and PubMed databases up to January 2010 for English-language, human-subject clinical trials that evaluated the rate of hyperkalemia with spironolactone use in ESRD patients on hemodialysis. Search terms included were "spironolactone," "eplerenone," "aldosterone antagonist," "heart failure," "kidney failure," "hemodialysis," "dialysis," and "renal replacement therapy." RESULTS: Six prospective trials demonstrated that spironolactone use was safe in ESRD patients on hemodialysis. The incidence of hyperkalemia with spironolactone treatment in these studies was similar to control groups. The studies involved a small population of compliant subjects who were at low risk for hyperkalemia. CONCLUSIONS: Small pilot studies demonstrated that spironolactone treatment in ESRD patients on hemodialysis did not result in higher hyperkalemia rates. Larger studies are needed to confirm these preliminary results before spironolactone is routinely considered in hemodialysis patients.

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.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow), Research integrity
Consensus categoriesResearch integrity
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.881
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.001
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0050.002
Bibliometrics0.0000.000
Science and technology studies0.0000.001
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0020.004
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.064
GPT teacher head0.375
Teacher spread0.311 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it