Skip to content

APEX CR Knee KC-1420LRecalls & reported problems

Omni Life Science, Inc. · CR Femoral Uncemented, Size 2 Left · Class 2 · Implant

All models of APEX CR Knee (28)

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

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

Summary

The FDA's MAUDE database contains 3 adverse event reports that list this exact device (DI 00841690104193), received between Jul 16, 2019 and Apr 23, 2024 — classified as 3 injuries.

The most frequently reported specific device problem is “Insufficient Device Problem Information” (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.

Reports received per month

Nov 2023: 0 reportsDec 2023: 0 reportsJan 2024: 0 reportsFeb 2024: 0 reportsMar 2024: 0 reportsApr 2024: 1 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: 0 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 Problem1
  • Appropriate Device Problem Term/Code Not Available1
  • Insufficient Device Problem Information1
  • Unstable1

Patient problems

  • Fall1
  • Joint Laxity1
  • No Known Impact Or Consequence To Patient1

Recent adverse event reports

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

  • InjuryApr 23, 2024Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem

    A COMPLAINT WAS INITIATED FOR A PATIENT WHO UNDERWENT A KNEE REVISION SURGERY ON (B)(6) 2024. THE ORIGINAL SURGERY DATE IS (B)(6) 2022. THE REASON FOR REVISION IS REPORTED INSTABILITY OF THE MEDIAL COLLATERAL LIGAMENT. DURING THE REVISION THE FEMUR, TIBIAL TRAY, INSERT AND BOLT WERE REMOVED AND REPLACED WITH NEW COMPONENTS.

    Patient problems: Joint Laxity

    MAUDE report 19164491 ↗
  • InjuryAug 11, 2020Unstable; Appropriate Device Problem Term/Code Not Available

    A COMPLAINT WAS INITIATED FOR A PATIENT WHO UNDERWENT A KNEE REVISION SURGERY ON (B)(6) 2020. THE ORIGINAL SURGERY IS (B)(6) 2014. THE REASON FOR REVISION IS REPORTED INSTABILITY. DURING THE REVISION, ALL ORIGINAL COMPONENTS WERE REMOVED AND REPLACED WITH NON-OMNI PRODUCT.

    Patient problems: No Known Impact Or Consequence To Patient

    MAUDE report 10393280 ↗
  • InjuryJul 16, 2019Insufficient Device Problem Information; Insufficient Device Problem Information

    A COMPLAINT WAS INITIATED FOR A PATIENT WHO UNDERWENT A KNEE REVISION SURGERY ON (B)(6) 2019. THE ORIGINAL SURGERY IS DATED (B)(6) 2017. THE REASON FOR REVISION IS REPORTED PATIENT FALL. DURING THE REVISION, THE ORIGINAL FEMUR, TIBIAL BASEPLATE, INSERT AND RETAINING BOLT WERE REMOVED AND REPLACED WITH NEW COMPONENTS. IN ADDITION TO THE REPLACED COMPONENTS, TIBIAL AUGMENTS, AUMENT BOLTS, A TIBIAL STEM, FEMUR AUGMENTS, AUGMENT BOLTS AND A FEMUR STEM WERE IMPLANTED.

    Patient problems: Fall

    MAUDE report 8795038 ↗

Other PROSTHESIS, KNEE, PATELLO/FEMOROTIBIAL, SEMI-CONSTRAINED, UNCEMENTED, POROUS, COATED, POLYMER/METAL/POLYMER devices

All PROSTHESIS, KNEE, PATELLO/FEMOROTIBIAL, SEMI-CONSTRAINED, UNCEMENTED, POROUS, COATED, POLYMER/METAL/POLYMER devices →

Sources and updates

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