Sprint Quattro Secure S® 6935M97Recalls & reported problems
Medtronic, Inc. · LEAD 6935M97 US DF4 NG ACI · Class 3 · Implant
All models of Medtronic Sprint Quattro Lead (67) · Sprint Quattro Secure S (19)
Data updated Oct 18, 2026 from official FDA records · Editorial policy
- Adverse event reports
- 7
- Deaths reported
- 0
- Injuries reported
- 5
- Recalls naming it
- 0
Summary
The FDA's MAUDE database contains 7 adverse event reports that list this exact device (DI 00643169550926), received between Jun 20, 2018 and Aug 4, 2025 — classified as 5 injuries, 2 malfunctions.
The most frequently reported specific device problem is “Over-Sensing” (2 reports).
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.
Reports received per month
Most reported problems
Device problems
- Adverse Event Without Identified Device or Use Problem3
- Over-Sensing2
- Device Dislodged or Dislocated1
- Fracture1
- Pacing Problem1
- Signal Artifact/Noise1
Patient problems
- Erosion2
- No Clinical Signs, Symptoms or Conditions2
- Unspecified Infection2
- Impaired Healing1
- No Consequences Or Impact To Patient1
- No Known Impact Or Consequence To Patient1
Recent adverse event reports
The 7 most recent of 7 reports, in the reporter's own words as published by the FDA.
InjuryAug 4, 2025Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem
IT WAS REPORTED THAT THE RIGHT VENTRICULAR (RV) LEAD WAS EXPLANTED DUE TO A POORLY HEALING WOUND. NO FURTHER PATIENT COMPLICATIONS HAVE BEEN REPORTED AS A RESULT OF THIS EVENT.
Patient problems: Impaired Healing
MAUDE report 22708644 ↗MalfunctionJul 29, 2025Signal Artifact/Noise; Over-Sensing; Pacing Problem; Signal Artifact/Noise; Over-Sensing; Pacing Problem
IT WAS REPORTED THAT THE RIGHT VENTRICULAR (RV) LEAD TRIGGERED A LEAD INTEGRITY ALERT (LIA) FOR SENSING INTEGRITY COUNTER (SIC) AND HIGH RATE NON-SUSTAINED EPISODES. IT WAS ALSO NOTED THAT THE RV LEAD EXHIBITED OVERSENSING, NOISE, AND PACING INHIBITION. THE LEAD REMAINS IN USE. NO PATIENT COMPLICATIONS HAVE BEEN REPORTED AS A RESULT OF THIS EVENT.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 22646957 ↗MalfunctionDec 11, 2024Over-Sensing; Over-Sensing
IT WAS REPORTED THAT THE RIGHT VENTRICULAR (RV) LEAD EXHIBITED T-WAVE OVERSENSING (TWOS) POST PACE. THE RV LEAD REMAINS IN USE. NO PATIENT COMPLICATIONS HAVE BEEN REPORTED AS A RESULT OF THIS EVENT.
Patient problems: No Clinical Signs, Symptoms or Conditions
MAUDE report 20905985 ↗InjuryFeb 14, 2022Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem
IT WAS REPORTED THAT THE PATIENT EXPERIENCED AN INFECTION AND EROSION OF THE ABANDONED LEADS FROM A PREVIOUS DEVICE SYSTEM. THE ABANDONED LEADS AND ACTIVE LEADS WERE ALL CUT AT THE TISSUE AND PARTIALLY REMOVED. THE LEAD BODIES REMAIN IN THE PATIENT. THE CARDIAC RESYNCHRONIZATION THERAPY DEFIBRILLATOR (CRT-D) WAS EXPLANTED AND REPLACED BY A LEADLESS IMPLANTABLE PULSE GENERATOR (IPG). THE PATIENT WAS ADMINISTERED ANTIBIOTICS. NO FURTHER PATIENT COMPLICATIONS HAVE BEEN REPORTED AS A RESULT OF THIS EVENT.
Patient problems: Erosion; Unspecified Infection
MAUDE report 13524987 ↗InjuryJun 2, 2020Fracture; Fracture
IT WAS REPORTED THAT THE RIGHT VENTRICULAR (RV) LEAD FRACTURED. THE LEAD WAS CAPPED AND REPLACED. NO PATIENT COMPLICATIONS HAVE BEEN REPORTED AS A RESULT OF THIS EVENT.
Patient problems: No Consequences Or Impact To Patient
MAUDE report 10112005 ↗InjuryMay 6, 2020Adverse Event Without Identified Device or Use Problem; Adverse Event Without Identified Device or Use Problem
IT WAS REPORTED THAT THE CARDIAC RESYNCHRONIZATION THERAPY DEFIBRILLATOR (CRT-D) SYSTEM WAS REMOVED DUE TO EROSION AND SUSPECTED INFECTION. THE PATIENT WAS TREATED WITH ANTIBIOTICS AND WILL RECEIVE A NEW SYSTEM AT A FUTURE DATE. NO FURTHER PATIENT COMPLICATIONS HAVE BEEN REPORTED AS A RESULT OF THIS EVENT.
Patient problems: Erosion; Unspecified Infection
MAUDE report 10028155 ↗InjuryJun 20, 2018Device Dislodged or Dislocated; Device Dislodged or Dislocated
IT WAS REPORTED THAT BOTH THE ATRIAL AND RIGHT VENTRICULAR (RV) LEADS DISLODGED OVER TIME. IT WAS NOTED THAT THE PATIENT WAS (B)(6) TALL, WHICH MAY HAVE PLACED ADDITIONAL STRAIN ON THE LEADS. BOTH LEADS WERE EXPLANTED AND REPLACED. NO PATIENT COMPLICATIONS HAVE BEEN REPORTED AS A RESULT OF THIS EVENT.
Patient problems: No Known Impact Or Consequence To Patient
MAUDE report 7622109 ↗
Other Permanent defibrillator electrodes devices
- CapSureFix Novus MRI™ SureScan® 5076-52Medtronic, Inc. · Permanent defibrillator electrodes333 deaths30,581 reports
- Sprint Quattro Secure S MRI™ SureScan™ 6935M62Medtronic, Inc. · Permanent defibrillator electrodes221 deaths14,405 reports
- Capsurefix® Novus 5076-52Medtronic, Inc. · Permanent defibrillator electrodes111 deaths9,860 reports
- CapSureFix Novus MRI™ SureScan® 5076-52Medtronic, Inc. · Permanent defibrillator electrodes80 deaths8,280 reports
- Sprint Quattro Secure S MRI™ SureScan™ 6935M55Medtronic, Inc. · Permanent defibrillator electrodes116 deaths7,750 reports
- Durata™ 7122Q-58St. Jude Medical, Inc. · Permanent defibrillator electrodes151 deaths6,202 reports
- Durata™ 7122Q-65St. Jude Medical, Inc. · Permanent defibrillator electrodes86 deaths4,773 reports
- Capsurefix® Novus 5076-58Medtronic, Inc. · Permanent defibrillator electrodes47 deaths4,587 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 18, 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