Skip to content

Polaris™ Ultra M006192133180Recalls & reported problems

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

All models of Polaris Ultra (40)

Data updated Oct 18, 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 08714729777106), received between Apr 25, 2017 and Apr 25, 2017 — 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 18, 2026.

Most reported problems

Device problems

  • Break1

Patient problems

  • No Consequences Or Impact To Patient1

Recent adverse event reports

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

  • MalfunctionApr 25, 2017Break; Break

    IT WAS REPORTED TO BOSTON SCIENTIFIC CORPORATION THAT A POLARIS ULTRA URETERAL STENT WAS GOING TO BE USED IN A STENT PLACEMENT PROCEDURE PERFORMED ON (B)(6) 2017. ACCORDING TO THE COMPLAINANT, DURING PREPARATION, THE STENT WAS BROKEN AT THE MIDDLE SECTION WHEN REMOVED FROM THE STRAINER. THE PROCEDURE WAS COMPLETED WITH ANOTHER POLARIS ULTRA URETERAL STENT. THERE WERE NO PATIENT COMPLICATIONS REPORTED AS A RESULT OF THIS EVENT. ATTEMPTS TO OBTAIN ADDITIONAL INFORMATION REGARDING THE CIRCUMSTANCES SURROUNDING THIS EVENT HAVE BEEN UNSUCCESSFUL TO DATE. SHOULD ADDITIONAL RELEVANT DETAILS BECOME AVAILABLE, A SUPPLEMENTAL MDR WILL BE SUBMITTED.

    Patient problems: No Consequences Or Impact To Patient

    MAUDE report 6521288 ↗

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