Rapid ventricular pacing during transcatheter valve procedures using an internal device and programmer: A demonstration of feasibility.
Аннотация
OBJECTIVES
To develop a protocol for using a pre-existing, permanent pacemaker or defibrillator device for rapid ventricular pacing during transcatheter valve procedures and demonstrate feasibility.
BACKGROUND
Placement of a passive fixation, temporary pacemaker wire is considered routine during most transcatheter valve procedures to facilitate controlled or rapid ventricular pacing at the time of balloon expansion or valve deployment. Many patients presenting for such procedures have a pre-existing, permanent pacemaker or defibrillator device which could be used for the same function, obviating the need for temporary pacemaker wire placement.
METHODS
We developed a strategy for rapid pacing from the pre-existing device using a programmer during transcatheter valve procedures in consecutive patients over a 3-month period. Complications and clinical outcomes were recorded.
RESULTS
There were 135 transcatheter valve procedures performed during the study. Of these, 28 (20.7%) had pre-existing devices (17 transcatheter aortic valve replacement, 3 aortic valve-in-valve, 2 mitral valve-in-valve, and 6 balloon aortic valvuloplasty). All patients underwent rapid ventricular pacing using a commercially available device programmer. There were no adverse events related to device pacing and no patients required placement of a temporary pacemaker wire during the procedure. At 30-days follow-up, there were no deaths, one major vascular complication related to arterial access, and one patient with renal failure requiring dialysis.
CONCLUSION
Pacing from a commercially available device programmer is safe, feasible, and may reduce both procedural cost and complications such as cardiac tamponade by avoiding placement of a temporary pacemaker lead during transcatheter valve procedures.
Предметные рубрики MeSH
Подготовка и перевод публикации
Обработка статьи · этапы, ошибки и управление
Ошибки и ограничения
История · было → стало
Состояние обновляется каждые 5 секунд, пока блок открыт. Процент показывается только там, где известен объём работы. Пауза останавливает продолжение этапа; текущий запрос к источнику может завершиться.
Тип публикации указан по данным источника. Уровень доказательности автоматически не присваивается.