Resolute Onyx™ RONYX45030UXRecalls & reported problems
Medtronic, Inc. · STENT RONYX45030UX RESOLUTE ONYX 4.50X30 · Class 3 · Implant
All models of Resolute Onyx (101)
Data updated Oct 18, 2026 from official FDA records · Editorial policy
- Adverse event reports
- 4
- Deaths reported
- 1
- Injuries reported
- 1
- Recalls naming it
- 0
Summary
The FDA's MAUDE database contains 4 adverse event reports that list this exact device (DI 00643169557284), received between Mar 13, 2018 and Jun 8, 2020 — classified as 1 death, 1 injury, 2 malfunctions.
The most frequently reported specific device problem is “Material Deformation” (2 reports).
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
- Adverse Event Without Identified Device or Use Problem2
- Material Deformation2
- Device Damaged by Another Device1
Patient problems
- No Consequences Or Impact To Patient2
- Death1
- Myocardial Infarction1
Recent adverse event reports
The 4 most recent of 4 reports, in the reporter's own words as published by the FDA.
DeathJun 8, 2020Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem
DURING THE INDEX PROCEDURE THREE RESOLUTE ONYX DES WERE IMPLANTED IN THE 2ND OBTUSE MARGINAL. TWO DAYS LATER DURING A STAGED PROCEDURE, THREE RESOLUTE ONYX DES WERE IMPLANTED; TWO IN THE RAMUS AND ONE IN THE LCMA. APPROXIMATELY 20 MONTHS LATER, THE PATIENT SUFFERED CARDIOGENIC SHOCK, SEVERE MITRAL REGURGITATION, WORSENING RENAL FAILURE AND DIED. DEATH WAS CLASSIFIED AS NON SUDDEN CARDIAC DEATH. INVESTIGATOR AND SPONSOR ASSESSED THE EVENT AS NOT RELATED TO INDEX DEVICE OR ANTI-PLATELET MEDICATION.
Patient problems: Death
MAUDE report 10127337 ↗InjuryOct 31, 2019Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem
DURING THE INDEX PROCEDURE, THREE RESOLUTE ONYX DES WERE IMPLANTED IN THE RCA AND THREE RESOLUTE ONYX DES WERE IMPLANTED IN THE LAD DURING STAGED PROCEDURE. APPROXIMATELY 4 MONTHS POST INDEX PROCEDURE, PATIENT SUFFERED FROM ATYPICAL CHEST PAIN . EVENT WAS TREATED WITH MEDICATION. CEC AND SAFETY ADJUDICATED THE EVENT AS NON-Q-WAVE MI, 3RD UDMI SPONTANEOUS (VESSEL UNKNOWN). INVESTIGATOR AND SAFETY ASSESSED THAT THE EVENT WAS NOT RELATED TO INDEX DEVICE OR ANTIPLATELETS MEDICATION. PATIENT RECOVERED.
Patient problems: Myocardial Infarction
MAUDE report 9260149 ↗MalfunctionJan 7, 2019Material Deformation; Material Deformation
AN ATTEMPT WAS MADE TO USE ONE RESOLUTE ONYX RX CORONARY DRUG ELUTING STENT TO TREAT A MODERATELY TORTUOUS, SEVERELY CALCIFIED LESION EXHIBITING 90% STENOSIS LOCATED ON THE RCA. THE DEVICE WAS INSPECTED WITH NO ISSUES. 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. EXCESSIVE FORCE WAS NOT USED DURING DELIVERY. IT WAS REPORTED THAT WHEN THE STENT EXITED THE GUIDE CATHETER IT WAS UNABLE TO CROSS THE LESION AND BECAME HUNG UP ON THE CALCIUM, THE STENT WAS REMOVED FROM THE PATIENT, UPON REMOVAL IT WAS OBSERVED THAT STENT DEFORMATION OCCURRED WITH A STRUT OF THE STENT BECOMING LIFTED. THE PROCEDURE WAS COMPLETED USING A SHORTER STENT. THE PATIENT IS REPORTED TO BE ALIVE WITH NO INJURY IN RELATION TO THE RESOLUTE ONYX STENT.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 8221330 ↗MalfunctionMar 13, 2018Device Damaged by Another Device; Material Deformation; Device Damaged by Another Device; Material Deformation
AN ATTEMPT WAS MADE TO USE A RESOLUTE ONYX RX DRUG ELUTING STENT TO TREAT A SEVERELY CALCIFIED AND MODERATELY TORTUOUS LESION. IT WAS REPORTED THAT NO DAMAGE WAS NOTED TO THE DEVICE PACKAGING AND THERE WERE NO ISSUES REMOVING THE DEVICE FROM THE HOOP/TRAY. THE DEVICE WAS INSPECTED WITH NO ISSUES NOTED. 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 AND NO EXCESSIVE FORCE USED. IT WAS REPORTED THAT THE DEVICE FAILED TO CROSS THE TARGET LESION. THE STENT FAILED TO CROSS AND WAS REMOVED. UPON REMOVAL OF THE STENT, THE GUIDE MOVED OUT OF THE LEFT MAIN AND THE PHYSICIAN TRIED TO PUT THE STENT BACK INTO THE GUIDE BUT THE STRUTS HAD BEEN DAMAGED WHEN IT RUBBED AGAINST THE GUIDE UPON INITIAL REMOVAL AND STRUTS WERE LIFTED. THE PHYSICIAN USED TWO SMALLER SIZED ONYX STENTS TO COMPLETE THE PROCEDURE. NO PATIENT INJURY IS REPORTED.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 7333339 ↗
Other Coronary drug-eluting stent devices
- SYNERGY™ H7493926038300Boston Scientific Corporation · Coronary drug-eluting stent8 deaths124 reports
- SYNERGY™ H7493926016300Boston Scientific Corporation · Coronary drug-eluting stent7 deaths106 reports
- SYNERGY™ H7493926020300Boston Scientific Corporation · Coronary drug-eluting stent9 deaths90 reports
- SYNERGY™ H7493926016250Boston Scientific Corporation · Coronary drug-eluting stent6 deaths82 reports
- XIENCE Sierra™ 1550350-33Abbott Vascular Inc. · Coronary drug-eluting stent1 recall32 reports
- Resolute Onyx™ RONYX30022UXMedtronic, Inc. · Coronary drug-eluting stent6 deaths76 reports
- SYNERGY™ H7493926024300Boston Scientific Corporation · Coronary drug-eluting stent3 deaths75 reports
- Resolute Onyx™ RONYX30015UXMedtronic, Inc. · Coronary drug-eluting stent3 deaths73 reports
Sources and updates
- Device record: FDA GUDID, file dated Oct 13, 2026 · View this device in AccessGUDID ↗
- Adverse event reports: FDA MAUDE, file dated Oct 14, 2026 · each report above links to its original FDA record
- Recalls: FDA Medical Device Recalls, file dated Oct 16, 2026
- Page last rebuilt: Oct 18, 2026. Data downloaded through openFDA, which notes it is not validated for clinical or regulatory use.
How reports and recalls are matched · Editorial policy · Report an error on this page