Epic™ Vascular H74939200074020Recalls & reported problems
Boston Scientific Corporation · Self-Expanding Stent System · Class 3
All models of Epic Vascular (50)
Data updated Oct 18, 2026 from official FDA records · Editorial policy
- Adverse event reports
- 3
- Deaths reported
- 0
- Injuries reported
- 3
- Recalls naming it
- 0
Summary
The FDA's MAUDE database contains 3 adverse event reports that list this exact device (DI 08714729805441), received between Aug 1, 2017 and Aug 11, 2021 — classified as 3 injuries.
The most frequently reported specific device problem is “Activation, Positioning or Separation Problem” (1 report).
Reports come from manufacturers, hospitals and patients and are not verified by the FDA. A report does not prove the device caused the event, and counts can't be used to compare devices or estimate failure rates. What reports can and can't tell you · How this data works · Data updated Oct 18, 2026.
Most reported problems
Device problems
- Activation, Positioning or Separation Problem1
- Migration1
- Positioning Problem1
Patient problems
- No Consequences Or Impact To Patient2
- No Clinical Signs, Symptoms or Conditions1
Recent adverse event reports
The 3 most recent of 3 reports, in the reporter's own words as published by the FDA.
InjuryAug 11, 2021Migration; Migration
IT WAS REPORTED THAT STENT MIGRATION OCCURRED. A 7X40X120 EPIC VASCULAR STENT WAS ADVANCED FOR TREATMENT. HOWEVER, DURING THE PROCEDURE, IT WAS NOTED THAT THE STENT SLIP DOWN STREAM AND DISTALLY MIGRATED AFTER INITIAL IMPLANT. BALLOON ANGIOPLASTY WAS PERFORMED AND THE PROCEDURE WAS COMPLETED. THERE WERE NO PATIENT COMPLICATIONS NOR INJURIES REPORTED AND THE PATIENT WAS FULLY RECOVERED.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 12307490 ↗InjuryMar 12, 2020Positioning Problem; Positioning Problem
IT WAS REPORTED THAT STENT POSITIONING DIFFICULTIES WERE ENCOUNTERED REQUIRING AN ADDITIONAL STENT TO BE PLACED. THE TARGET LESION WAS LOCATED IN THE SUPERFICIAL FEMORAL ARTERY (SFA). A 7X40X120MM EPIC VASCULAR STENT WAS ADVANCED FOR TREATMENT. DURING THE PROCEDURE, THE STENT JUMPED FORWARD PASSED THE STENOSIS AFTER IT WAS ALMOST FULLY DEPLOYED. ANOTHER OF THE SAME STENT WAS USED TO STENT THE STENOSIS. NO PATIENT COMPLICATIONS WERE REPORTED AND NO HARM WAS DONE TO THE PATIENT.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 9823325 ↗InjuryAug 1, 2017Activation, Positioning or Separation Problem; Activation, Positioning or Separation Problem
IT WAS REPORTED THAT STENT DEPLOYMENT DIFFICULTIES OCCURRED. AN 7X40X120 EPIC¿ STENT WAS SELECTED TO TREAT A LESION LOCATED IN THE ILIAC ARTERY. AS THE EPIC¿ STENT WAS DEPLOYED THE STENT JUMPED OUT OF POSITION. ADDITIONAL STENTING OF THE SAME DEVICE WAS REQUIRED TO COMPLETE THE PROCEDURE. NO PATIENT COMPLICATIONS WERE REPORTED AND THE PATIENT'S CONDITION IS FINE.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 6757303 ↗
Other STENT, ILIAC devices
- Cordis S.M.A.R.T. Control Vascular Stent System C10040MLCordis US Corp. · STENT, ILIAC1 recall3 reports
- Absolute Pro 1012534-100Abbott Vascular Inc. · STENT, ILIAC51 reports
- Protégé™ GPS™ SERB65-09-60-80Ev3, Inc · STENT, ILIAC1 recall0 reports
- Cordis S.M.A.R.T. Control Vascular Stent System C09060MLCordis US Corp. · STENT, ILIAC1 recall0 reports
- Absolute Pro 1012535-100Abbott Vascular Inc. · STENT, ILIAC1 death41 reports
- Omnilink Elite 1012631-39Abbott Vascular Inc. · STENT, ILIAC27 reports
- Omnilink Elite 1012632-29Abbott Vascular Inc. · STENT, ILIAC25 reports
- Absolute Pro 1012536-100Abbott Vascular Inc. · STENT, ILIAC21 reports
Sources and updates
- Device record: FDA GUDID, file dated Oct 13, 2026 · View this device in AccessGUDID ↗
- Adverse event reports: FDA MAUDE, file dated Oct 14, 2026 · each report above links to its original FDA record
- Recalls: FDA Medical Device Recalls, file dated Oct 16, 2026
- Page last rebuilt: Oct 18, 2026. Data downloaded through openFDA, which notes it is not validated for clinical or regulatory use.
How reports and recalls are matched · Editorial policy · Report an error on this page