fbpx

Filterlex Medical LTD

About This Project

Aortic stenosis (AS) is the most common and most severe heart valve disease, affecting 20 million people worldwide. For patients with severe AS, the most common treatment is valve replacement through Transcatheter Aortic Valve Implantation (TAVI). The procedure is very risky, since embolic debris are released to the blood stream and may reach the brain and other organs, reducing or blocking the blood flow. Strikingly, embolic debris cause new ischemic brain lesions in 70% of patients post TAVI, major disabling strokes in 9%, and kidney dysfunction 12.3% of cases. Embolic Protection Devices (EPDs) are being developed to reduce the risk posed by embolic debris during TAVI. To date, only one EPD has been commercialised for use in TAVI procedure. Unfortunately, the device is poorly effective since it can only provide partial cerebral protection, interferes with the TAVI delivery system, and requires secondary artery access to the TAVI system, thus increasing procedure time and posing the patient at a higher risk of post-operative side effects.

 

Filterlex developed the CAPTISĀ® system, an innovative intra-aortic Embolic Protection Device (EPD) for deflecting, capturing and removing embolic particles during TAVI procedure. Easily positioned, deployed and retrieved through the same TAVI artery access, this revolutionary EPD provides full-body protection by ensuring the best performance in capturing and safely removing the embolic debris released during TAVI. In this way, CAPTIS strongly reduces the risk of stroke and ischemia to other vital organs.

 

Topic
Health
Year

2019

Cutoff

2019

Country

Israel

Tags
Ageing, Aortic Stenosis, Embolic Protection Device, Heart valve, Heart valve diseases, Stroke, Stroke prevention, TAVI

We use cookies to give you the best online experience. By agreeing you accept the use of cookies in accordance with our cookie policy.


Warning: mysqli_num_fields() expects parameter 1 to be mysqli_result, bool given in /home/alientt8/public_html/wp-includes/wp-db.php on line 3380