Skip to content

VIPER PRIME 186750450SRecalls & reported problems

Medos International Sàrl · VIPER PRIME CFX FEN X-TAB POLYAXIAL SCREW 5.5 5 x 50mm · Class 2 · Implant

All models of VIPER PRIME (60)

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 10705034529967), received between Oct 14, 2021 and Oct 14, 2021 — classified as 1 malfunction.

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

  • Device-Device Incompatibility1

Patient problems

  • No Clinical Signs, Symptoms or Conditions1

Recent adverse event reports

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

  • MalfunctionOct 14, 2021Device-Device Incompatibility; Device-Device Incompatibility

    DEVICE REPORT FROM SYNTHES REPORTS AN EVENT IN (B)(6) AS FOLLOWS: IT WAS REPORTED THAT ON (B)(6) 2021 DURING AN UNKNOWN PROCEDURE, THE VIPER PRIME SCREW WAS UNABLE TO DETACH FROM THE VIPER PRIME SCREWDRIVER. THERE WAS NO PATIENT CONSEQUENCE. THERE WAS A SURGICAL DELAY OF TWENTY (20) MINUTES. THE PROCEDURE WAS SUCCESSFULLY COMPLETED USING A SECOND SCREWDRIVER FROM THE SET. THIS REPORT IS FOR ONE (1) VIPER PRIME CFXFN XTB 5X50MM S. THIS IS REPORT 2 OF 3 FOR (B)(4).

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 12632134 ↗

Other APPLIANCE, FIXATION, SPINAL INTERLAMINAL devices

All APPLIANCE, FIXATION, SPINAL INTERLAMINAL devices →

Sources and updates

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