• Decrease font size
  • Return font size to normal
  • Increase font size
U.S. Department of Health and Human Services

MAUDE Adverse Event Report: K2M, INC. 751 MILLER DRIVE SE, LEESBURG, VIRGINIA K2M SPINE SCREWS; PEDICLE SCREW SPINAL SYSTEM, ADOLESCENT IDIOPATHIC SCOLIOSIS

  • Print
  • Share
  • E-mail
-
Super Search Devices@FDA
510(k) | DeNovo | Registration & Listing | Adverse Events | Recalls | PMA | HDE | Classification | Standards
CFR Title 21 | Radiation-Emitting Products | X-Ray Assembler | Medsun Reports | CLIA | TPLC
 

K2M, INC. 751 MILLER DRIVE SE, LEESBURG, VIRGINIA K2M SPINE SCREWS; PEDICLE SCREW SPINAL SYSTEM, ADOLESCENT IDIOPATHIC SCOLIOSIS Back to Search Results
Device Problem Therapeutic or Diagnostic Output Failure (3023)
Patient Problem Insufficient Information (4580)
Event Date 12/19/2012
Event Type  Injury  
Event Description
Empire medical; during a mast lumbar fusion the surgeon used a medtronic navlock awl and tap, and then attempted to use a different spine companies screws (k2m).The screws would not thread after attempting multiple times.Therefore, the surgeon became frustrated with the spine rep (non medtronic) and aborted navigation.A c-arm was brought in and used the other spine company's instruments to successfully finish the surgery without navigation.We all agreed that the medtronic tap was not compatible (different threads) with the spine company (k2m).(b)(4).This report reflects information received by fda in the form of a notification per 803.22 (b)(2).
 
Search Alerts/Recalls

  New Search  |  Submit an Adverse Event Report

Brand Name
K2M SPINE SCREWS
Type of Device
PEDICLE SCREW SPINAL SYSTEM, ADOLESCENT IDIOPATHIC SCOLIOSIS
Manufacturer (Section D)
K2M, INC. 751 MILLER DRIVE SE, LEESBURG, VIRGINIA
MDR Report Key17536136
MDR Text Key321140766
Report NumberMW5143026
Device Sequence Number1
Product Code OSH
Combination Product (y/n)N
Number of Events Reported1
Summary Report (Y/N)N
Report Source Voluntary
Reporter Occupation Other
Type of Report Initial
Report Date 02/21/2013
1 Device was Involved in the Event
1 Patient was Involved in the Event
Date FDA Received08/12/2023
Is this an Adverse Event Report? No
Is this a Product Problem Report? No
Patient Sequence Number1
-
-