Abstract 17278: Concomitant Use of Ivabradine in the Setting of Cardiogenic Shock: A Case Series
Bibliographic record
Abstract
Background: Ivabradine, a selective sinus node inhibitor, is indicated for patients with chronic heart failure with reduced ejection fraction (HFrEF). Use in cardiogenic shock is currently contraindicated. However, studies have suggested increasing heart rate may be deleterious for patients with HFrEF due to an inverted Bowditch-Treppe response. Limited case series have suggested use of Ivabradine in decompensated HFrEF may be beneficial. We present a case series of patients who presented with severely decompensated HFrEF and received inotropic support and concomitant ivabradine. Methods: We selected four patients with HFrEF presenting with elevated sinus heart rate and cardiogenic shock (cardiac index <2.0L/min*m2with pulmonary artery wedge pressure > 20 mmHg by invasive hemodynamic monitoring) while on inotropic therapy and were intolerant of beta blockade due to hypotension. Ivabradine 2.5 mg 12 h was initiated and subsequently titrated with continued monitoring with baseline, 24 h and latest obtained parameters recorded. Other treatments occurred at the discretion of the attending physician. Results: Four male patients (mean age 44 years) with non-ischemic cardiomyopathy (mean EF 17%, mean NT-pro-BNP 5104 pg/ml) were included. Ivabradine was tolerated in all cases, with a mean dose of 6 mg q12h. Mean heart rate and pulmonary wedge pressure fell 20% and 32% respectively from baseline to last measurement, while stroke volume increased with an overall improvement in cardiac index. (Table 1) There were no changes noted in mean arterial blood pressure. All patients underwent successful wean of inotropic support within 48 hours and were discharged alive on beta blocker and ACE inhibitor therapy. No adverse events attributed to use of Ivabradine were observed. Conclusion: In our small series of patients with cardiogenic shock, beta blocker intolerance and elevated sinus heart rate, Ivabradine was added without any deleterious hemodynamic effect and associated with early clinical improvement. Further studies are needed to better assess its potential use in this population.
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.000 | 0.003 |
| Meta-epidemiology (narrow) | 0.003 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.003 | 0.002 |
| Scholarly communication | 0.002 | 0.002 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.005 | 0.003 |
| 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".