Search - tctmd.com

Displaying 21 - 30 of 30

Sort: Relevancy | Date

RESPECT: A Prospective Randomized Trial of PFO Closure in Patients With Cryptogenic Stroke – Long-term Results

Presentation TCT 2015

RESPECT: A Prospective Randomized Trial of PFO Closure in Patients With Cryptogenic Stroke – Long-term Results

Presenter: John D. Carroll

October 15, 2015

News Conference News TCT 2015

RESPECT Confirms Long-term Safety, Efficacy of PFO Closure for Recurrent Stroke

October 15, 2015

News Conference News TCT 2014

PFO Closure for Stroke: A Call to Revise the Guidelines

September 14, 2014

ASA/AHA Guidelines 2014: PFO Closure for Cryptogenic Stroke Is Now Class III LOE A! Is This the Final Word from the Neurology Community?

Presentation TCT 2014

ASA/AHA Guidelines 2014: PFO Closure for Cryptogenic Stroke Is Now Class III LOE A! Is This the Final Word from the Neurology Community?

Presenter: Matthew J. Price, Mark Reisman, Sheldon Goldberg, David E. Thaler

September 13, 2014

News Conference News TCT 2013

Efficacy of PFO Closure Still Undetermined

October 28, 2013

News Conference News TCT 2012

Stroke Prevention Strategies Discussed

October 26, 2012

RESPECT: A Prospective, Randomized Trial of PFO Closure vs. Medical Therapy in Patients with Cryptogenic Stroke

Presentation TCT 2012

RESPECT: A Prospective, Randomized Trial of PFO Closure vs. Medical Therapy in Patients with Cryptogenic Stroke

Presenter: John Carroll

October 25, 2012

News Conference News TCT 2012

Two Trials Examine Device-Based PFO Closure

October 25, 2012

Cryptogenic Stroke vs PFO Stroke? Neurology Perspectives

Presentation TCT 2012

Cryptogenic Stroke vs PFO Stroke? Neurology Perspectives

Presenter: David Thaler

October 22, 2012

News Conference News

Coming to Grips with CLOSURE I: PFO Device Plus Medical Therapy Not Superior to Medical Therapy Alone

November 06, 2011

Country

First Name

Last Name

Email

Profession

Organization

Country

CAPTCHA

This question is for testing whether or not you are a human visitor and to prevent automated spam submissions.