Skip to content

NA 6203215000Recalls & reported problems

Stryker Corporation · DHS/DCS Quick Lock · Class 1

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

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

Summary

The FDA's MAUDE database contains 2 adverse event reports that list this exact device (DI 04546540501714), received between Oct 29, 2018 and Apr 25, 2022 — classified as 2 malfunctions.

The most frequently reported specific device problem is “Break” (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 16, 2026.

Most reported problems

Device problems

  • Break1
  • Detachment of Device or Device Component1

Patient problems

  • No Clinical Signs, Symptoms or Conditions1
  • No Patient Involvement1

Recent adverse event reports

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

  • MalfunctionApr 25, 2022Detachment of Device or Device Component; Detachment of Device or Device Component

    THIS REPORT SUMMARIZES 1 MALFUNCTION EVENT IN WHICH THE DEVICE HAD A COMPONENT DETACH. 1 EVENT HAD NO PATIENT INVOLVEMENT; NO PATIENT IMPACT.

    Patient problems: No Clinical Signs, Symptoms or Conditions

    MAUDE report 14193330 ↗
  • MalfunctionOct 29, 2018Break; Break

    THIS REPORT SUMMARIZES <NOE> 1 </NOE> MALFUNCTION EVENT IN WHICH THE DEVICE HAD A BROKEN CUTTING ACCESSORY STILL ATTACHED. 1 EVENT HAD NO PATIENT INVOLVEMENT; NO PATIENT IMPACT.

    Patient problems: No Patient Involvement

    MAUDE report 8013865 ↗

Other INSTRUMENT, SURGICAL, ORTHOPEDIC, AC-POWERED MOTOR AND ACCESSORY/ATTACHMENT devices

All INSTRUMENT, SURGICAL, ORTHOPEDIC, AC-POWERED MOTOR AND ACCESSORY/ATTACHMENT devices →

Sources and updates

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