Skip to content

CoRoent 6080823P2Recalls & reported problems

Nuvasive, Inc. · CoRoent Large MP, 8x9x23mm 8° · Class 2 · Implant

All models of CoRoent (64)

Data updated Oct 16, 2026 from official FDA records · Editorial policy

Adverse event reports
1
Deaths reported
1
Injuries reported
0
Recalls naming it
0

Summary

The FDA's MAUDE database contains 1 adverse event report that list this exact device (DI 00887517679604), received between Mar 27, 2018 and Mar 27, 2018 — classified as 1 death.

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 16, 2026.

Most reported problems

Device problems

  • Adverse Event Without Identified Device or Use Problem1

Patient problems

  • Death1

Recent adverse event reports

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

  • DeathMar 27, 2018Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem

    ON (B)(6) 2018 A PATIENT UNDERWENT A REVISION PROCEDURE OF ANOTHER MANUFACTURERS TRANSFORAMINAL LUMBAR INTERBODY FUSION. NUVASIVE CAGES WERE PLACED AT L5/S1 LEVELS WITHOUT ANY REPORTED PROBLEMS. DURING THE EXTENSION OF THE PREVIOUSLY PLACED POSTERIOR FIXATION, THE PATIENT'S BLOOD PRESSURE DECREASED. ROD INSERTION, SET SCREW TIGHTENING AND PLACEMENT OF TRANSVERSE CONNECTORS WAS PERFORMED AND PATIENT WAS CLOSED. CARDIAC MASSAGE AND FIRST AID TREATMENT WAS PERFORMED. PATIENT WAS TRANSFERRED TO THE INTENSIVE CARE UNIT AND LATER EXPIRED. THE CAUSE OF THE PATIENT'S DEMISE IS UNKNOWN AT THIS TIME.

    Patient problems: Death

    MAUDE report 7375934 ↗

Other Intervertebral fusion device with bone graft, lumbar devices

All Intervertebral fusion device with bone graft, lumbar devices →

Sources and updates

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