Skip to content

Contour™ M006180223090Recalls & reported problems

Boston Scientific Corporation · Ureteral Stent Set · Class 2 · Implant

All models of Contour (14)

Data updated Oct 16, 2026 from official FDA records · Editorial policy

Adverse event reports
1
Deaths reported
0
Injuries reported
0
Recalls naming it
0

Summary

The FDA's MAUDE database contains 1 adverse event report that list this exact device (DI 08714729424062), received between Sep 20, 2021 and Sep 20, 2021 — classified as 1 malfunction.

The most frequently reported specific device problem is “Break” (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 16, 2026.

Most reported problems

Device problems

  • Break1
  • Detachment of Device or Device Component1

Patient problems

  • No Clinical Signs, Symptoms or Conditions1

Recent adverse event reports

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

  • MalfunctionSep 20, 2021Break; Detachment of Device or Device Component; Break; Detachment of Device or Device Component

    IT WAS REPORTED TO BOSTON SCIENTIFIC CORPORATION THAT A CONTOUR URETERAL STENT WAS USED DURING A STENT REPLACEMENT PROCEDURE IN THE URETER, PERFORMED ON (B)(6) 2021. DURING UNPACKING, IT WAS NOTICED THAT THE STENT SEEMED TO BE SEPARATED. ANOTHER CONTOUR URETERAL STENT WAS OPENED AND SUCCESSFULLY COMPLETED THE PROCEDURE. THERE WERE NO PATIENT COMPLICATIONS REPORTED AS A RESULT OF THIS EVENT. BOSTON SCIENTIFIC HAS BEEN UNABLE TO OBTAIN ADDITIONAL INFORMATION REGARDING THE EVENT TO DATE, DESPITE GOOD FAITH EFFORTS.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 12500826 ↗

Other STENT, URETERAL devices

All STENT, URETERAL devices →

Sources and updates

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