Skip to content

Percuflex™ Nephroureteral Stent M001221380Recalls & reported problems

Boston Scientific Corporation · Nephroureteral Stent System · Class 2

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 08714729114093), received between Jul 10, 2023 and Jul 10, 2023 — classified as 1 malfunction.

The most frequently reported specific device problem is “Detachment of Device or Device Component” (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

  • 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.

  • MalfunctionJul 10, 2023Detachment of Device or Device Component; Detachment of Device or Device Component

    REPORTABLE BASED ON DEVICE ANALYSIS COMPLETED ON (B)(6) 2023. IT WAS REPORTED THAT THE HUB BROKE. A PERCUFLEX NEPHROURETERAL STENT WAS SELECTED FOR USE. DURING THE PROCEDURE, UPON PULLING THE STRING TO FORM THE LOOP, IT WAS NOTED THAT THE HUB BROKE. THE ENTIRE DRAIN WAS PULLED OUT TO COMPLETELY REMOVE THE DEVICE FROM THE PATIENT. THE PROCEDURE WAS COMPLETED WITH AN ALTERNATIVE METHOD. NO PATIENT COMPLICATIONS WERE REPORTED. HOWEVER, DEVICE ANALYSIS REVEALED THAT THE STENT AND SUTURE WAS DETACHED AT PROXIMAL SECTION.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 17289795 ↗

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