MedElevator Войти в исследования
← Поиск публикаций

DOI 10.1186/s13256-025-05781-3

Медицинская библиотека · Journal of medical case reports · 2026

Competing therapy options for severe amlodipine poisoning-lessons learned: a case report.

Kuhn Yvonne, Fischbach Julia, Putensen Christian, Ehrentraut Stefan Felix

СтатьяКлинический случайПеревод в очереди

Аннотация

BACKGROUND

We report two cases of severe amlodipine poisoning (> 1000 mg) during a suicide attempt.

CASE PRESENTATION: Both patients (male, white, aged 70 and 28 years, respectively) experienced severe vasoplegic shock and were referred to us from regional hospitals via our extracorporeal membrane oxygenation hotline. In addition to the recommended therapy, both patients underwent albumin dialysis. Despite this, the vasopressor demand remained sky high, in both cases above 2 µg/kg/minute norepinephrine. Ultimately, both patients required veno-arterial extracorporeal membrane oxygenation support. There were slight differences in treatment; one patient received lipid emulsion and the other hydroxycobalamin, both of which caused interesting technical difficulties with continuous renal replacement therapy. Finally, we were able to wean both patients off extracorporeal support as well as all vasopressors. Both were discharged from the intensive care unit.

CONCLUSION

In cases so severe, swift action is of the essence and some of the available treatments cancel each other out and should be timed accordingly. Therefore, on the basis of our experiences and the standing recommendations we developed a treatment algorithm that takes not only the case severity but also the time frame in which the treatment should be administered into account.

Для цитирования: Kuhn Yvonne, Fischbach Julia, Putensen Christian, Ehrentraut Stefan Felix. Competing therapy options for severe amlodipine poisoning-lessons learned: a case report.. Journal of medical case reports. 2026. DOI: 10.1186/s13256-025-05781-3.

Предметные рубрики MeSH

Подготовка и перевод публикации
Обработка статьи · этапы, ошибки и управление
Загрузка состояния…

История · было → стало

Состояние обновляется каждые 5 секунд, пока блок открыт. Процент показывается только там, где известен объём работы. Пауза останавливает продолжение этапа; текущий запрос к источнику может завершиться.

Тип публикации указан по данным источника. Уровень доказательности автоматически не присваивается.