Skip to content

Neodent 109.217Recalls & reported problems

JJGC Indústria e Comércio de Materiais Dentários S/A. · ALVIM IMPLANT WITH MOUNT · Class 2 · Implant

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

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

Summary

The FDA's MAUDE database contains 7 adverse event reports that list this exact device (DI 07898237566801), received between Nov 10, 2017 and Aug 10, 2020 — classified as 7 injuries.

The most frequently reported specific device problem is “Failure to Osseointegrate” (7 reports).

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

  • Failure to Osseointegrate7

Patient problems

  • Tissue Damage7
  • Unspecified Infection1

Recent adverse event reports

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

  • InjuryAug 10, 2020Failure to Osseointegrate; Failure to Osseointegrate

    THE CLINICIAN REPORTS THE IMPLANT WAS INSERTED (B)(6) 2009 IN THE PATIENT'S MOUTH. ON (B)(6) 2009, NON-OSSEOINTEGRATION WAS VERIFIED. THE DEVICE WAS FORWARDED TO THE MANUFACTURER. THERE WERE NO REPORTED PATIENT INJURIES OR COMPLICATIONS.

    Patient problems: Tissue Damage

    MAUDE report 10387044 ↗
  • InjuryAug 10, 2020Failure to Osseointegrate; Failure to Osseointegrate

    THE CLINICIAN REPORTS THE IMPLANT WAS INSERTED (B)(6) 2009 IN THE PATIENT'S MOUTH. ON (B)(6) 2009, NON-OSSEOINTEGRATION WAS VERIFIED. THE DEVICE WAS FORWARDED TO THE MANUFACTURER. THERE WERE NO REPORTED PATIENT INJURIES OR COMPLICATIONS.

    Patient problems: Tissue Damage

    MAUDE report 10387033 ↗
  • InjuryAug 10, 2020Failure to Osseointegrate; Failure to Osseointegrate

    THE CLINICIAN REPORTS THE IMPLANT WAS INSERTED (B)(6) 2009 IN THE PATIENT'S MOUTH. ON (B)(6) 2009, NON-OSSEOINTEGRATION WAS VERIFIED. THE DEVICE WAS FORWARDED TO THE MANUFACTURER. THERE WERE NO REPORTED PATIENT INJURIES OR COMPLICATIONS.

    Patient problems: Tissue Damage

    MAUDE report 10387031 ↗
  • InjuryAug 10, 2020Failure to Osseointegrate; Failure to Osseointegrate

    THE CLINICIAN REPORTS THE IMPLANT WAS INSERTED (B)(6) 2009 IN THE PATIENT'S MOUTH. ON (B)(6) 2009, NON-OSSEOINTEGRATION WAS VERIFIED. THE DEVICE WAS FORWARDED TO THE MANUFACTURER. THERE WERE NO REPORTED PATIENT INJURIES OR COMPLICATIONS.

    Patient problems: Tissue Damage

    MAUDE report 10387011 ↗
  • InjuryNov 14, 2017Failure to Osseointegrate; Failure to Osseointegrate

    (B)(4) - THE DENTIST REPORTED THAT, 1 YEAR AFTER THE DENTAL IMPLANT WAS INSTALLED IN INTRAORAL REGION #5, ITS NON-OSSEOINTEGRATION WAS OBSERVED. TWENTY NCM OF PRIMARY STABILITY WAS ACHIEVED AND THE IMPLANT WAS INSTALLED WITHOUT IMMEDIATELY LOAD. THE PATIENT PRESENTED BONE TYPE II.

    Patient problems: Tissue Damage; Unspecified Infection

    MAUDE report 7030396 ↗
  • InjuryNov 10, 2017Failure to Osseointegrate; Failure to Osseointegrate

    (B)(4) - THE DENTIST REPORTED THAT, AFTER THE DENTAL IMPLANT WAS INSTALLED IN PATIENT¿S MOUTH, AT THE TIME OF UNCOVERING TO PERFORM THE PATIENT¿S PROSTHETIC REHABILITATION, IT WAS SEEN THAT THE DENTAL IMPLANT HAD NOT OSSEOINTEGRATED. THE 35 NCM OF PRIMARY STABILITY WAS ACHIEVED.

    Patient problems: Tissue Damage

    MAUDE report 7020490 ↗
  • InjuryNov 10, 2017Failure to Osseointegrate; Failure to Osseointegrate

    (B)(4). THE DENTIST REPORTED THAT 30 DAYS AFTER THE DENTAL IMPLANT WAS INSTALLED IN INTRAORAL REGION #7, IT WAS VERIFIED ITS NON-OSSEOINTEGRATION. A 30 NCM OF PRIMARY STABILITY WAS ACHIEVED AND IMMEDIATE LOAD WAS PERFORMED.

    Patient problems: Tissue Damage

    MAUDE report 7017398 ↗

Other IMPLANT, ENDOSSEOUS, ROOT-FORM devices

All IMPLANT, ENDOSSEOUS, ROOT-FORM devices →

Sources and updates

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