Edwards Lifesciences IntraClude Intra-Aortic Occlusion… recallZ-1758-2015 · Edwards Lifesciences, LLC · initiated May 5, 2015
Class II Terminated All recalls posted in June 2015
Is my device affected?
- Compare the model, catalog and lot or serial numbers on your device or its packaging with the code information below. A recall usually covers only specific models or lots.
- If yours is listed, follow the instructions from Edwards Lifesciences, LLC or your healthcare provider. The company's action is summarized under what the company is doing.
- Do not stop using a prescribed or implanted device on your own — talk to your healthcare provider first.
Where to find your model and lot numbers · What recall classes and statuses mean
Why it was recalled
Potential device damage on the strain relief near the hub area, which may result in blood leakage.
FDA root cause category: Device Design
What the company is doing
Urgent Medical Device Safety Notice letters were sent via Fed-Ex by May 05, 2015. As part of the customer instructions in the safety notice, customers were requested to review the notice to understand the potential hazard, complete and return the acknowledgement form, and forward copies of the Safety Notice to any organization where the potentially affected devices have been transferred. The device will only be distributed to customers who have returned the acknowledgement form. Questions should be directed to Edwards Customer Service at 800-424-3278.
Recall details
- Recall number
- Z-1758-2015
- Recall class
- Class II
- Status
- Terminated
- Initiated by the company
- May 5, 2015
- Posted by the FDA
- Jun 11, 2015
- Recalling firm
- Edwards Lifesciences, LLC
- Quantity
- 3,360 units.
- Product code
- DXC
- FDA submissions
- K132175
- Distribution
- Nationwide Distribution -- US, including the states of Alabama, Arizona, California, Colorado, Connecticut, Florida, Georgia, Idaho, Illinois, Kentucky, Louisiana, Massachusetts, Maine, Michigan, Missouri, Mississippi, North Carolina, Nebraska, New Jersey, New York, Ohio, Oklahoma, Oregon, Pennsylvania, South Carolina, South Dakota, Tennessee, Texas, Utah, Virginia, Washington, Wisconsin, and West Virginia.
Product description
Edwards Lifesciences IntraClude Intra-Aortic Occlusion Device, model number ICF100, 10.5 Fr (3.5 mm) x 39.4" (100 cm) ThruPort System. Packaged sterile and non-pyrogenic in a sealed, peel-type pouch For use in patients undergoing cardiopulmonary bypass.
Code information (models, lots, serial numbers)
Show the full code information (1k characters)
All lots within expiration. 59443555 59613944 59655681 59718185 59751955 59829691 59913251 59973802 59473497 59613945 59655682 59718186 59757492 59829692 59914824 59973803 59478792 59630641 59655683 59718187 59767963 59842135 59914825 59979641 59478793 59644480 59677638 59721969 59790316 59853386 59914826 59979642 59490124 59644481 59695842 59721970 59790317 59853387 59936991 59999093 59523568 59644482 59695843 59721971 59801106 59856575 59936992 60016315 59559537 59649627 59695844 59734231 59801107 59872381 59962951 60031031 59585111 59649628 59718182 59734232 59806707 59895500 59962952 59597667 59655679 59718183 59751953 59812135 59901268 59962953 59598246 59655680 59718184 59751954 59824839 59904370 59967598
Other devices under the same FDA submission
2 devices cleared under K132175 — the recall does not name any of them by identifier. One submission often covers many models, so they may or may not be affected.
- THRUPORT SYSTEMS INTRACLUDE INTRA-AORTIC OCCLUSION DEVICE ICF100Edwards Lifesciences LLC · CLAMP, VASCULAR8 reports
- enableCV IntraClude™ Intra-Aortic Occlusion Device ICF100Enablecv Inc. · Clamp, Vascular1 death1 report
Sources and updates
- Recall record: FDA Medical Device Recalls, file dated Oct 16, 2026 · View the FDA recall notice ↗
- Devices: FDA GUDID, file dated Oct 13, 2026. Devices are linked when their identifier (with a valid check digit) appears in the recall's code information.
- Page last rebuilt: Oct 18, 2026. Text above is shown as published by the FDA.
How recalls are matched to devices · Editorial policy · Report an error on this page