z-logo
Premium
Aborted Sudden Cardiac Death Due to Radiofrequency Ablation Within the Coronary Sinus and Subsequent Total Occlusion of the Circumflex Artery
Author(s) -
MAKIMOTO HISAKI,
ZHANG QINGYONG,
TILZ ROLAND RICHARD,
WISSNER ERIK,
CUNEO ALESSANDRO,
KUCK KARLHEINZ,
OUYANG FEIFAN
Publication year - 2013
Publication title -
journal of cardiovascular electrophysiology
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 1.193
H-Index - 138
eISSN - 1540-8167
pISSN - 1045-3873
DOI - 10.1111/jce.12083
Subject(s) - medicine , cardiology , circumflex , coronary sinus , ablation , sudden cardiac death , occlusion , coronary occlusion , radiofrequency ablation , sinus (botany) , artery , botany , biology , genus
Aborted Cardiac Death After Ablation of Coronary Sinus We report a case of aborted sudden cardiac death and subsequent development of malignant drug‐refractory incessant ventricular tachycardia/fibrillation in a patient with acute coronary artery occlusion following radiofrequency ablation within the CS. Catheter ablation is a well‐established therapy for treatment of atrial fibrillation (AF). In patients with longstanding persistent AF extensive left atrial ablation and ablation inside the coronary sinus (CS) is frequently performed. Perimitral flutter following AF ablation is the most common form of left atrial macroreentry, especially in patients with previous ablation of complex fractionated electrograms and incomplete linear lesion sets within the left atrium. Successful ablation of this type of tachycardia is generally difficult and in about 60–70% patients requires additional ablation within the CS to achieve termination of tachycardia or/and left atrial isthmus (LAI) block. A limited number of case reports have been published describing acute coronary artery occlusion during or immediately after LAI ablation within the CS. This case exhibits a potential lethal risk of radiofrequency ablation within the CS.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here