Abstract

BackgroundThe role of atrial rate‐responsive (RR) pacing in cardiac resynchronization therapy (CRT) is unclear due to the favorable effect of rate lowering in systolic heart failure. Atrial high rate episodes (AHREs) in CRT recipients are particularly worrisome since they cause loss of CRT, beyond representing a stroke risk factor.HypothesisThe presence of an association between RR and the incidence of AHREs.MethodsDaily remote transmissions from 836 CRT recipients were analyzed. AHREs were classified by duration: ≥15 minutes, ≥5 hours, and ≥ 24 hours. Variables possibly associated to AHREs were included in time‐dependent proportional‐hazard models, averaging over 30‐day periods and adjusting for main baseline variables.ResultsAfter a median follow‐up of 23.9 (12.2‐36.0) months, 507 (60.6%) patients experienced at least one 15‐minute AHRE. RR function was programmed in 166 (19.8%) patients and was associated with an increased AHRE occurrence rate with hazard ratio (HR) ranging from 1.45 to 1.78 for the 3 cutoffs of episode duration. The negative effect of RR function was not observed in the subset of patients with low mean heart rate (<68 bpm). Higher mean heart rates increased AHRE risk (HR:1.02, P = .01), while CRT amount decreased it (HR:0.98, P < .01). The extent of atrial pacing did not predict AHRE occurrence.ConclusionsRR pacing in CRT recipients is associated with increased AHRE occurrence, especially when an average heart rate > 68 bpm is attained.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.