Skip to content

Epic™ Vascular H74939200126020Recalls & 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
2
Deaths reported
0
Injuries reported
1
Recalls naming it
0

Summary

The FDA's MAUDE database contains 2 adverse event reports that list this exact device (DI 08714729805182), received between Aug 15, 2019 and Nov 24, 2025 — classified as 1 injury, 1 malfunction.

The most frequently reported specific device problem is “Activation Failure” (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.

Reports received per month

Nov 2023: 0 reportsDec 2023: 0 reportsJan 2024: 0 reportsFeb 2024: 0 reportsMar 2024: 0 reportsApr 2024: 0 reportsMay 2024: 0 reportsJun 2024: 0 reportsJul 2024: 0 reportsAug 2024: 0 reportsSep 2024: 0 reportsOct 2024: 0 reportsNov 2024: 0 reportsDec 2024: 0 reportsJan 2025: 0 reportsFeb 2025: 0 reportsMar 2025: 0 reportsApr 2025: 0 reportsMay 2025: 0 reportsJun 2025: 0 reportsJul 2025: 0 reportsAug 2025: 0 reportsSep 2025: 0 reportsOct 2025: 0 reportsNov 2025: 1 reportsDec 2025: 0 reportsJan 2026: 0 reportsFeb 2026: 0 reportsMar 2026: 0 reportsApr 2026: 0 reportsMay 2026: 0 reportsJun 2026: 0 reportsJul 2026: 0 reportsAug 2026: 0 reportsSep 2026: 0 reportsOct 2026: 0 reports2024202520261
Last 36 months. The most recent month may be incomplete.

Most reported problems

Device problems

  • Activation Failure1
  • Adverse Event Without Identified Device or Use Problem1
  • Deformation Due to Compressive Stress1
  • Difficult to Advance1

Patient problems

  • No Clinical Signs, Symptoms or Conditions1
  • No Consequences Or Impact To Patient1

Recent adverse event reports

The 2 most recent of 2 reports, in the reporter's own words as published by the FDA.

  • MalfunctionNov 24, 2025Deformation Due to Compressive Stress; Difficult to Advance; Adverse Event Without Identified Device or Use Problem; Deformation Due to Compressive Stress; Difficult to Advance; Adverse Event Without Identified Device or Use Problem

    REPORTABLE BASED ON DEVICE ANALYSIS COMPLETED ON 28OCT2025. IT WAS REPORTED THAT SHAFT KINKED OCCURRED. THE TARGET LESION WAS LOCATED IN THE ILIAC ARTERY. A 12X60X120 EPIC STENT SELF EXPANDING WAS SELECTED FOR ANGIOPLASTY OF ILIAC ARTERY. DURING THE PROCEDURE, THE PHYSICIAN FOUND THAT THE TIP OF THE DELIVERY DEVICE WAS KINKED, AND THE GUIDE WIRE COULD NOT CROSS THE DELIVERY DEVICE. THE PROCEDURE WAS COMPLETED WITH ANOTHER OF THE SAME DEVICE. THERE WERE NO PATIENT COMPLICATIONS AS A RESULT OF THIS EVENT. HOWEVER, DEVICE ANALYSIS REVEALED A PARTIALLY DEPLOYED STENT. IT WAS FURTHER REPORTED THAT THE STENT WAS DEPLOYED INADVERTENTLY DURING TRANSIT.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 23633656 ↗
  • InjuryAug 15, 2019Activation Failure; Activation Failure

    IT WAS REPORTED THAT STENT FORESHORTENING OCCURRED. VASCULAR ACCESS WAS OBTAINED VIA IPSILATERAL APPROACH. THE 70% STENOSED TARGET LESION WAS LOCATED IN THE NON-CALCIFIED PORTAL VEIN. A 12 X 60 X 120 MM EPIC VASCULAR STENT WAS ADVANCED FOR TREATMENT. HOWEVER, DURING STENT DEPLOYMENT, RESISTANCE WAS ENCOUNTERED BUT EVENTUALLY, THE STENT WAS DEPLOYED. POST DEPLOYMENT, THE MEASUREMENT OF THE STENT WAS OBSERVED TO BE 30 MM UNDER RADIOGRAPHY WHICH COULD NOT FULLY COVER THE LESION. SUBSEQUENTLY, THE PHYSICIAN IMPLANTED ANOTHER OF THE SAME DEVICE TO COMPLETE THE PROCEDURE. NO PATIENT COMPLICATIONS WERE REPORTED AND THE PATIENT'S STATUS WAS STABLE.

    Patient problems: No Consequences Or Impact To Patient

    MAUDE report 8898676 ↗

Other STENT, ILIAC devices

All STENT, ILIAC devices →

Sources and updates

How reports and recalls are matched · Editorial policy · Report an error on this page