Key result
TriGuard cerebral embolic protection during TAVR fails to meet predefined effectiveness endpoints versus unprotected controls.
Why the study?
Does the TriGuard HDH cerebral embolic deflection device improve clinical and imaging outcomes in patients undergoing TAVR?
RCT (n=258)
Single-blind
2:1
Yes
Does the TriGuard HDH cerebral embolic deflection device improve clinical and imaging outcomes in patients undergoing TAVR?
Absolute Event Rate: -5.3% vs 11.8%
p-value: p=0.31
The TriGuard HDH cerebral embolic deflection device was safe during TAVR but failed to demonstrate superior efficacy in reducing a hierarchical composite of mortality, stroke, cognitive worsening, and ischemic lesions compared to unprotected TAVR.
Captured external expert commentary on this paper, strongest first. Original sources are linked where available.
“Protecting the brain has become a priority to improve our patients' outcomes, and this is a new focus in interventional cardiology.”
“In a world where positive publication bias is a reality, a negative trial like this one seems rare. Seemingly hidden in the text is the fact the authors paused the study early at the recommendation of the Data Safety and Monitoring Board.”
“Knowing what we now know about the significant risks of stroke and other neurological injury associated with TAVI and other cardiovascular procedures, there is a clear unmet clinical need for cerebral embolic protection devices that provide complete protection of all three cerebral branches for patients undergoing these procedures.”
No role for routine TriGuard CEP in TAVR; challenges prior neuroprotection signals and leaves open next-generation devices.
AIMS: The REFLECT I trial investigated the safety and effectiveness of the TriGuard™ HDH (TG) cerebral embolic deflection device in patients undergoing transcatheter aortic valve replacement (TAVR). METHODS AND RESULTS: This prospective, multicentre, single-blind, 2:1 randomized (TG vs. no TG) study aimed to enrol up to 375 patients, including up to 90 roll-in patients. The primary combined safety endpoint (VARC-2 defined early safety) at 30 days was compared with a performance goal. The primary efficacy endpoint was a hierarchical composite of (i) all-cause mortality or any stroke at 30 days, (ii) National Institutes of Health Stroke Scale (NIHSS) worsening at 2-5 days or Montreal Cognitive Assessment worsening at 30 days, and (iii) total volume of cerebral ischaemic lesions detected by diffusion-weighted magnetic resonance imaging at 2-5 days. Cumulative scores were compared between treatment groups using the Finkelstein-Schoenfeld method. A total of 258 of the planned, 375 patients (68.8%) were enrolled (54 roll-in and 204 randomized). The primary safety outcome was met compared with the performance goal (21.8% vs. 35%, P < 0.0001). The primary hierarchical efficacy endpoint was not met (mean efficacy score, higher is better: -5.3 ± 99.8 TG vs. 11.8 ± 96.4 control, P = 0.31). Covert central nervous system injury was numerically lower with TG both in-hospital (46.1% vs. 60.3%, P = 0.0698) and at 5 days (61.7 vs. 76.2%, P = 0.054) compared with controls. CONCLUSION: REFLECT I demonstrated that TG cerebral protection during TAVR was safe in comparison with historical TAVR data but did not meet the predefined effectiveness endpoint compared with unprotected TAVR controls.
No takes yet. Share an insight, caveat, or question.
Lansky et al. (2021) conducted an RCT in Transcatheter aortic valve replacement (TAVR) (n=258). TriGuard™ HDH cerebral embolic deflection device vs. Unprotected TAVR controls was evaluated on Hierarchical composite of all-cause mortality or any stroke at 30 days, NIHSS/MoCA worsening, and total volume of cerebral ischaemic lesions at 2-5 days (p=0.31). The TriGuard HDH cerebral embolic deflection device during TAVR met its primary safety performance goal but did not improve the primary hierarchical efficacy endpoint compared to controls (P=0.31).
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: