Skip to content

NIRxcell CoCr Coronary Stent on RX System NXL25017USRecalls & reported problems

Medinol Ltd. · Class 3 · Implant

All models of NIRxcell CoCr Coronary Stent on RX System (17)

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 07290107010771), received between Apr 4, 2018 and Apr 4, 2018 — classified as 1 malfunction.

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

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 4, 2018Device Issue; Device Issue

    THE PHYSICIAN HAD PASSED THE NIRXCELL STENT PAST A PROXIMAL / MID RCA LESION THAT THE XIENCE STENT WOULD NOT PASS. UPON PASSING THE LESION THE PHYSICIAN BEGAN THE INFLATION OF THE NIRXCELL STENT AND QUICKLY NOTICED THAT BLOOD WAS FILLING UP THE ENDOFLATER. THE PHYSICIAN IMMEDIATELY STOPPED AS IT WAS APPARENT THAT THE BALLOON THE STENT WAS CRIMPED TO WAS DEFECTIVE OR SOMETHING AND HE REMOVED THE NIRXCELL. UPON REMOVAL HE NOTICED THAT THE NIRXCELL STENT WAS SCRUNCHED ALL THE WAY TO THE DISTAL END. HE THEN OPENED 3 MORE NIRXCELL STENTS WITH NO ISSUES AND FINISHED THE CASE. NO PATIENT INJURY REPORTED.

    Patient problems: No Consequences Or Impact To Patient

    MAUDE report 7395280 ↗

Other Stent, Coronary devices

All Stent, Coronary devices →

Sources and updates

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