Skip to content

Mectalif Transforaminal Cages TiPEEK 03.23.154Recalls & reported problems

Medacta International SA · Transforaminal Interbody Fusion Device TiPEEK 12x30x13 L5° · Class 2 · Implant

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 07630030829314), received between Nov 18, 2021 and Nov 18, 2021 — classified as 1 injury.

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

  • Appropriate Device Problem Term/Code Not Available1
  • Fracture1
  • Migration or Expulsion of Device1

Patient problems

  • Inadequate Osseointegration1

Recent adverse event reports

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

  • InjuryNov 18, 2021Fracture; Migration or Expulsion of Device; Appropriate Device Problem Term/Code Not Available

    AT 6 MONTHS AFTER THE PRIMARY SURGERY, THE PATIENT WAS REVISED DUE TO ACUTE LUMBALGIA SUSPECTED AND SUSPICION OF INTERBODY CAGE MIGRATION. DURING THE REVISION SURGERY, IN A POSTERIOR APPROACH, THE CAGE WAS PARTIALLY REMOVED BECAUSE WAS FIXED AND DIFFICULT TO REMOVE. AFTER MANY ATTEMPTS, IT FRACTURED IN HALF AND THE HALF PART OF THE CAGE WAS LEFT IN PLACE. TWO PEDICLE SCREWS AND TWO RODS WERE REMOVED.

    Patient problems: Inadequate Osseointegration

    MAUDE report 12834828 ↗

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