Skip to content

Resolute Onyx™ RONYX27512WRecalls & reported problems

Medtronic, Inc. · STENT RONYX27512W RESOLUTE ONYX 2.75X12 · 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
1
Recalls naming it
0

Summary

The FDA's MAUDE database contains 1 adverse event report that list this exact device (DI 00643169602403), received between Jun 9, 2022 and Jun 9, 2022 — classified as 1 injury.

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

  • Insufficient Information1

Recent adverse event reports

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

  • InjuryJun 9, 2022Device Dislodged or Dislocated; Device Dislodged or Dislocated

    AN ATTEMPT WAS MADE TO USE A RESOLUTE ONYX OTW CORONARY DRUG ELUTING STENT TO TREAT A TORTUOUS LESION IN THE MID DIAGONAL BRANCH. NEGATIVE PREP WAS NOT PERFORMED. THE LESION WAS PRE-DILATED. THE DEVICE DID NOT PASS THROUGH A PREVIOUSLY-DEPLOYED STENT. RESISTANCE WAS ENCOUNTERED WHEN ADVANCING THE DEVICE. IT WAS REPORTED THAT THE STENT DISLODGEMENT OCCURRED DURING THE REMOVAL FOLLOWING FAILED DELIVERY. THE DISLODGED STENT WAS RETRIEVED WITH WITH SMALLER BALLOON INSIDE THE STENT. THE PATIENT WAS REPORTED ALIVE WITH NO FURTHER INJURY.

    Patient problems: Insufficient Information

    MAUDE report 14641549 ↗

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