Key result
Lightning injury is associated with a high incidence of QT prolongation, which may promote episodic Torsades de pointes and explain recovery after prolonged cardiac arrest.
Why the study?
Does lightning injury cause QT prolongation and episodic Torsades de pointes ventricular tachycardia?
Does lightning injury cause QT prolongation and episodic Torsades de pointes ventricular tachycardia?
Lightning injury should be recognized as a cause of QT prolongation, which may explain survival after prolonged cardiac arrest via episodic Torsades de pointes rather than 'cessation of metabolism'.
Lightning injury merits QT assessment in arrest survivors; extends sparse literature but leaves open torsades-mediated recovery mechanism.
An hypothesis is presented to provide an alternative explanation to the ‘cessation of metabolism’ hypothesis often invoked in lightning injury. ‘Cessation of metabolism’ has been proposed to explain the observation of good recovery after a prolonged period of cardiac arrest in some lightning injured patients. Re-examination of the cases used to support ‘cessation of metabolism’, however, reveals little evidence to justify the hypothesis. Re-evaluation of ECGs from lightning injured patients demonstrates a high incidence of QT prolongation. It is hypothesized that QT prolongation could promote a state of episodic induction of and recovery from Torsades de pointes ventricular tachycardia (VT). As lightning injury is not classically regarded as a cause of QT prolongation, the cardiological literature should include it in future tabulations of causes.
No takes yet. Share an insight, caveat, or question.
Andrews et al. (1993) conducted a review in Lightning injury. Lightning injury was evaluated on QT prolongation. Lightning injury is associated with a high incidence of QT prolongation, which may promote episodic Torsades de pointes and explain recovery after prolonged cardiac arrest.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: