Skip to content

AMIStem-P 01.18.417Recalls & reported problems

Medacta International SA · AMIStem-P Lat. #7 · Class 2 · Implant

All models of AMIStem-P (18)

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

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

Summary

The FDA's MAUDE database contains 4 adverse event reports that list this exact device (DI 07630040720168), received between Apr 30, 2019 and Dec 20, 2025 — classified as 4 injuries.

The most frequently reported specific device problem is “Device Appears to Trigger Rejection” (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 16, 2026.

Reports received per month

Nov 2023: 0 reportsDec 2023: 0 reportsJan 2024: 0 reportsFeb 2024: 0 reportsMar 2024: 0 reportsApr 2024: 0 reportsMay 2024: 0 reportsJun 2024: 0 reportsJul 2024: 0 reportsAug 2024: 0 reportsSep 2024: 0 reportsOct 2024: 0 reportsNov 2024: 0 reportsDec 2024: 0 reportsJan 2025: 0 reportsFeb 2025: 0 reportsMar 2025: 0 reportsApr 2025: 0 reportsMay 2025: 0 reportsJun 2025: 0 reportsJul 2025: 0 reportsAug 2025: 0 reportsSep 2025: 0 reportsOct 2025: 0 reportsNov 2025: 0 reportsDec 2025: 1 reportsJan 2026: 0 reportsFeb 2026: 0 reportsMar 2026: 0 reportsApr 2026: 0 reportsMay 2026: 0 reportsJun 2026: 0 reportsJul 2026: 0 reportsAug 2026: 0 reportsSep 2026: 0 reportsOct 2026: 0 reports2024202520261
Last 36 months. The most recent month may be incomplete.

Most reported problems

Device problems

  • Adverse Event Without Identified Device or Use Problem2
  • Appropriate Device Problem Term/Code Not Available1
  • Device Appears to Trigger Rejection1
  • Device Dislodged or Dislocated1

Patient problems

  • Bone Fracture(s)2
  • Bacterial Infection1
  • Pain1

Recent adverse event reports

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

  • InjuryDec 20, 2025Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem

    AT ABOUT 1 MONTHS FROM THE PRIMARY, THE PATIENT CAME IN REPORTING PAIN DUE TO A BONE BROKEN FEMUR DISTAL TO THE MEDACTA STEM. THE PATIENT DID NOT REPORT ANY TRAUMA. THE SURGEON CABLED THE FRACTURE AND REVISED THE STEM AND HEAD. THE SURGERY WAS COMPLETED SUCCESSFULLY.

    Patient problems: Bone Fracture(s)

    MAUDE report 23858468 ↗
  • InjuryMay 31, 2023Device Appears to Trigger Rejection; Device Appears to Trigger Rejection

    THE PATIENT HAD A PRIMARY HIP SURGERY ON (B)(6) 2021. ON THE (B)(6) 2021, THE PATIENT CAME WITH SIGNS OF INFECTION AND A WASHOUT WAS PERFORMED. ON THE (B)(6) 2023, THE PATIENT CAME DUE TO SIGNS OF INFECTION AND THE PATHOGEN IS STAPHYLOCOCCUS. ALL THE IMPLANTS HAVE BEEN REVISED AND THE SURGERY WAS COMPLETED SUCCESSFULLY.

    Patient problems: Bacterial Infection

    MAUDE report 17029867 ↗
  • InjuryOct 13, 2020Device Dislodged or Dislocated; Appropriate Device Problem Term/Code Not Available

    THE PATIENT CAME IN REPORTING PAIN DUE TO A SUBSIDED STEM AFTER 1 YEAR AND 5 MONTHS FROM THE PRIMARY SURGERY. THE SURGEON REVISED THE STEM, HEAD, AND LINER. DURING THE PRIMARY HIP SURGERY, WHILE THE SURGEON WAS INSERTING THE STEM, THE PATIENT'S GREATER TROCHANTER FRACTURED. THE SURGEON CABLED THE FRACTURE.

    Patient problems: Pain

    MAUDE report 10668668 ↗
  • InjuryApr 30, 2019Adverse Event Without Identified Device or Use Problem

    DURING THE PRIMARY HIP SURGERY AND WHILE INSERTING THE STEM, THE PATIENT'S GREATER TROCHANTER FRACTURED. THE SURGEON CABLED THE FRACTURE AND THERE WAS A 5-MINUTE DELAY IN THE CASE. THE SURGERY WAS COMPLETED SUCCESSFULLY.

    Patient problems: Bone Fracture(s)

    MAUDE report 8564991 ↗

Other Prosthesis, Hip, Semi-Constrained, Metal/Polymer, Porous Uncemented devices

All Prosthesis, Hip, Semi-Constrained, Metal/Polymer, Porous Uncemented devices →

Sources and updates

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