Skip to content

Resolute Onyx™ RONYX25008WRecalls & reported problems

Medtronic, Inc. · STENT RONYX25008W RESOLUTE ONYX 2.50X08 · Class 3 · Implant

All models of Resolute Onyx (101)

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 00643169602304), received between Jun 7, 2019 and Jun 7, 2019 — classified as 1 malfunction.

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

  • Device Dislodged or Dislocated1

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.

  • MalfunctionJun 7, 2019Device Dislodged or Dislocated; Device Dislodged or Dislocated

    DURING A PROCEDURE AN ATTEMPT WAS MADE TO USE A RESOLUTE ONYX RX CORONARY, DRUG ELUTING STENT TO TREAT A MILD TORTUOSITY, MODERATE CALCIFIED DISTAL CIRCUMFLEX (CX) ARTERY. THE DEVICE WAS INSPECTED WITH NO ISSUES. THE LESION WAS PRE DILATED. THE DEVICE DID NOT PASS THROUGH A PREVIOUSLY DEPLOYED STENT. RESISTANCE WAS NOT ENCOUNTERED. EXCESSIVE FORCE WAS NOT USED. IT IS REPORTED THAT THE STENT DISLODGED DURING REMOVAL FROM THE GUIDE LINER FOLLOWING A FAILED DELIVERY. THE PATIENT IS ALIVE WITH NO INJURY.

    Patient problems: No Consequences Or Impact To Patient

    MAUDE report 8677963 ↗

Other Coronary drug-eluting stent devices

All Coronary drug-eluting stent devices →

Sources and updates

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