VIPER 186788065Recalls & reported problems
Depuy Spine, LLC · VIPER 2 SYSTEM ROD, PRE-LORDOSED 65mm · 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
- 0
- Recalls naming it
- 0
Summary
The FDA's MAUDE database contains 1 adverse event report that list this exact device (DI 10705034131788), received between Apr 21, 2021 and Apr 21, 2021 — classified as 1 malfunction.
The most frequently reported specific device problem is “Device-Device Incompatibility” (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
- 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.
MalfunctionApr 21, 2021Device-Device Incompatibility; Device-Device Incompatibility
IT WAS REPORTED THAT ON (B)(6) 2021, SURGEON WAS PERFORMING L4-S1 PERCUTANEOUS FUSION WITH VIPER PRIME. FIVE SCREWS WERE IMPLANTED AS INTENDED. WHEN IT CAME TIME TO LOCKING IN THE ROD CONNECTING THE SCREWS, HE STRUGGLED TO CAPTURE THE ROD WITH THE LOCKING CAPS DUE TO THE ROD NOT BEING SEATED LOW ENOUGH FOR THE CAPS TO CATCH ON THE THREADS OF THE PRIME SCREW EXTENDED TAB. HE BEGAN TO TRY TO FORCE THE ROD LOWER SO THAT HE COULD CAPTURE IT WITH THE LOCKING CAPS, BUT HE COULD NOT GET IT LOW ENOUGH TO THE CAP TO CATCH. DURING THIS STRUGGLE, ONE OF THE EXTENDED TABS BROKE OFF MAKING IT EVEN MORE DIFFICULT TO BE ABLE TO CAPTURE THE ROD. THE BROKEN TAB WAS REMOVED WITHOUT INCIDENT. HE CONTINUED TO TRY BUT COULDN¿T GET THE ROD LOW ENOUGH TO ENGAGE MULTIPLE LOCKING CAPS ON EITHER SIDE. SO, THE SURGEON ENDED UP HAVING TO REMOVE ALL 5 SCREWS AND REPLACE THEM WITH ANOTHER SYSTEM. THE BROKEN EXTENDED TAB CERTAINLY CONTRIBUTED TO THE FRUSTRATION AND THE DECISION TO ABANDON THE SYSTEM FOR THIS PATIENT. THE SURGEON REASONED THAT IF HE CAN¿T PUT MORE FORCE ON THE ROD TO BE ABLE TO CAPTURE IT WITHOUT BREAKING THE TABS, OR IF THERE IS NOT ANOTHER REDUCTION TOOL AVAILABLE FOR VIPER PRIME, THEN HE CAN¿T
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 11703739 ↗
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