VIPER 186789160Recalls & reported problems
Depuy Spine, LLC · VIPER 2 SYSTEM ROD, STRAIGHT 160mm · Class 2 · Implant
All models of VIPER (60)
Data updated Oct 16, 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 10705034132884), received between Oct 7, 2019 and Oct 7, 2019 — classified as 1 injury.
The most frequently reported specific device problem is “Loose or Intermittent Connection” (1 report).
1 other recall cover devices cleared under the same FDA submission (K071860, K111136); they may or may not involve this specific model.
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.
Most reported problems
Device problems
- Loose or Intermittent Connection1
Patient problems
- No Code Available1
- Unspecified Infection1
Recent adverse event reports
The 1 most recent of 1 reports, in the reporter's own words as published by the FDA.
InjuryOct 7, 2019Loose or Intermittent Connection; Loose or Intermittent Connection
IT WAS REPORTED ON AN UNKNOWN DATE, PATIENT WAS IN AN ACCIDENT IN (B)(6) D AND TAKEN TO A (B)(6) TRAUMA CENTER FOR A T12 COMPRESSION FRACTURE. PATIENT WAS INSTRUMENTED PERCUTANEOUSLY FROM T10-L2 USING DSS VIPER SYSTEM LAST (B)(6) 2019. UPON RETURN TO THE US, PATIENT WAS BENDING AND HEARD / FELT A POP. HE CAME TO THE ER AND IMAGES REVEALED THE HARDWARE HAD DISASSEMBLED. SEVERAL SET SCREWS WERE DISPLACED AND THE ROD HAD COME OUT OF THE SCREW SADDLE. DURING THE REVISION SURGERY, ON (B)(6) 2019, IT WAS FOUND THAT ALL OF THE SET SCREWS WERE LOOSE AND SOME WERE SITTING EXTREMELY PROUD IN THE SCREW SADDLE. HARDWARE WAS REMOVED, REPLACED, AND SUFFICIENTLY LOCKED. THERE WAS A HARDWARE FAILURE AND INFECTION. THERE WAS A PATIENT CONSEQUENCE. PROCEDURE OUTCOME IS UNKNOWN. CONCOMITANT DEVICE REPORTED: VIPER2 STRAIGHT ROD-160 MM (PART # 186789160, LOT # UNKNOWN, QUANTITY 1), VIPER2 STRAIGHT ROD-180 MM (PART # 186789180, LOT # UNKNOWN, QUANTITY 1). THIS COMPLAINT INVOLVES SIXTEEN (16) DEVICES.
Patient problems: No Code Available; Unspecified Infection
MAUDE report 9164294 ↗
Recalls under the same FDA submission
These recalls involve devices cleared under K071860, K111136. One submission often covers many models, so check the product and lot details in each record.
- Z-1674-2015 · Apr 21, 2015 · TerminatedEXPEDIUM Spine System/Synapse System; MODEL: EXPEDIUM Offset Conical Lock Nut 8mm, CATALOG NO. : 1754-91-150, UDI NUMBER (if applicable): GTIN: 10705034032467
Other ORTHOSIS, SPINAL PEDICLE FIXATION devices
- NA 04.614.508Synthes GmbH · ORTHOSIS, SPINAL PEDICLE FIXATION277 reports
- CREO 1134.0010Globus Medical, Inc. · ORTHOSIS, SPINAL PEDICLE FIXATION112 reports
- CREO 1119.0010Globus Medical, Inc. · ORTHOSIS, SPINAL PEDICLE FIXATION80 reports
- VIPER 186731745Medos International Sàrl · ORTHOSIS, SPINAL PEDICLE FIXATION43 reports
- CD HORIZON® Spinal System 1553201090Medtronic Sofamor Danek, Inc. · ORTHOSIS, SPINAL PEDICLE FIXATION38 reports
- EXPEDIUM 179902000Medos International Sàrl · ORTHOSIS, SPINAL PEDICLE FIXATION37 reports
- CD HORIZON® Spinal System 7540220Medtronic Sofamor Danek, Inc. · ORTHOSIS, SPINAL PEDICLE FIXATION36 reports
- EXPEDIUM VERSE 199721640Medos International Sàrl · ORTHOSIS, SPINAL PEDICLE FIXATION35 reports
Sources and updates
- Device record: FDA GUDID, file dated Oct 13, 2026 · View this device in AccessGUDID ↗
- Adverse event reports: FDA MAUDE, file dated Oct 14, 2026 · each report above links to its original FDA record
- Recalls: FDA Medical Device Recalls, file dated Oct 16, 2026
- Page last rebuilt: Oct 16, 2026. Data downloaded through openFDA, which notes it is not validated for clinical or regulatory use.
How reports and recalls are matched · Editorial policy · Report an error on this page