Skip to content

VBOSS 33661405MRRecalls & reported problems

Stryker Corporation · LARGE ROUND ENDCAP · Class 2 · Implant

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

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

  • Break1
  • Detachment of Device or Device Component1
  • Fracture1
  • Material Twisted/Bent1

Patient problems

  • No Code Available1
  • 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 29, 2019Break; Fracture; Detachment of Device or Device Component; Material Twisted/Bent; Fracture

    PHYSICIAN REPORTED THAT FOLLOWING, "A FEW HAMMER BLOWS ON THE IMPLANT HOLDER TO IMPACT THE CAGE," THE UPPER END CAP OF THE VBOSS SYSTEM BROKE AT THE BASE AND DISENGAGED FROM THE CAGE. THE PHYSICIAN REMOVED AND STRAIGHTENED THE CAGE (WHICH HAD "TWISTED") AND REPLACED THE UPPER END CAP. THERE WAS A TWO-HOUR DELAY IN THE SURGERY. ALL BROKEN FRAGMENTS WERE REMOVED, SURGERY WAS SUCCESSFULLY COMPLETED, AND NO OTHER ADVERSE CONSEQUENCE WAS REPORTED.

    Patient problems: No Code Available; No Consequences Or Impact To Patient

    MAUDE report 8562273 ↗

Other SPINAL VERTEBRAL BODY REPLACEMENT DEVICE devices

All SPINAL VERTEBRAL BODY REPLACEMENT DEVICE devices →

Sources and updates

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