Devices › Implantable cardioverter defibrillator (non-crt)
Device brand name · Implantable lead
Endotak Reliance G: medical device reports filed with FDA
10,115 reports name it, 2004–2026. Manufacturer given most often on reports: Boston Scientific. Product code LWS.
- 10,115
- device reports naming the brand
- 0% of all MAUDE reports · about 456 a year
- 1,049
- reports, 12 months to August 2026
- 1,470 in the 12 months before
- 39.1%
- classified as malfunction
- 37.4% across the product code
- 0.6%
- classified as death, as reported
- 65 reports · not verified by FDA
FDA's MAUDE database holds 10,115 reports that name the brand "Endotak Reliance G" (implantable lead), received between May 2004 and August 2026; the manufacturer given most often on reports is Boston Scientific. Spellings of one product vary from report to report.
1,049 reports arrived in the 12 months to August 2026, down 29% from 1,470 in the 12 months before. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases. The event types recorded are injury (60.2%), malfunction (39.1%) and death (0.6%); across all implantable cardioverter defibrillator (non-crt) reports (product code LWS) death is recorded in 2.7% and malfunction in 37.4%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are high impedance (48.9%), over-sensing (13.2%) and pacing problem (8.6%). The patient problems coded most often are sepsis, electric shock and other (for use when an appropriate patient code cannot be identified). FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Reports by month, five years
Reports by the month FDA received them. FDA releases MAUDE data monthly; reports can arrive months after an event, so the newest months grow in later releases.
By year received
Event type and report source
Event type, as classified on the report
Who filed the report
Grey bar: all 380,959 reports carrying product code LWS. Event type is the filer's classification and is not verified by FDA.
Device problems coded
| Device problem (FDA code) | Reports | Share | Share across product code |
|---|---|---|---|
| High impedance | 4,946 | 48.9% | 15.6% |
| Over-sensing | 1,332 | 13.2% | 21.1% |
| Pacing problem | 870 | 8.6% | 3.8% |
| Signal artifact/noise | 870 | 8.6% | 8% |
| High capture threshold | 758 | 7.5% | 3.6% |
| Dislodged | 733 | 7.2% | 0.7% |
| Failure to capture | 643 | 6.4% | 2.6% |
| Low impedance | 466 | 4.6% | 2.8% |
| Inappropriate/inadequate shock/stimulation | 463 | 4.6% | 12.8% |
| Noise | 436 | 4.3% | 1.3% |
| Fracturea broken bone | 350 | 3.5% | 5.8% |
| Normal | 332 | 3.3% | 1.8% |
| Defective devicethe device was defective | 314 | 3.1% | 1.3% |
| Loss of threshold | 298 | 2.9% | 0.4% |
| Material integrity problema problem with the device material | 249 | 2.5% | 0.6% |
| Device sensing problem | 226 | 2.2% | 3.9% |
| Device damaged prior to usethe device was damaged before use | 218 | 2.2% | 0.8% |
| Failure to read input signal | 184 | 1.8% | 2.1% |
| Low readingsreadings were too low | 157 | 1.6% | 0.2% |
| Failure to convert rhythm | 138 | 1.4% | 0.9% |
FDA's device problem codes as entered on the report; one report can carry several. Generic codes such as "no apparent adverse event" are left out.
Patient problems coded
| Patient problem (FDA code) | Reports | Share |
|---|---|---|
| Sepsisa severe body-wide response to infection | 363 | 3.6% |
| Electric shockan electric shock | 303 | 3% |
| Other (for use when an appropriate patient code cannot be identified) | 177 | 1.7% |
| Surgical procedure, repeated | 135 | 1.3% |
| Shock from patient lead(s) | 123 | 1.2% |
| Pocket erosion | 105 | 1% |
| Asystole | 84 | 0.8% |
| Twiddlers syndrome | 82 | 0.8% |
| Calcium deposits/calcification | 69 | 0.7% |
| Bacterial infectiona bacterial infection | 62 | 0.6% |
| Perforation | 48 | 0.5% |
| Bradycardiaslow heart rate | 41 | 0.4% |
| Syncopefainting | 41 | 0.4% |
| Endocarditis | 40 | 0.4% |
| Ventricular fibrillationa chaotic rhythm from the lower heart chambers | 38 | 0.4% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Endotak Reliance G | Product code LWS | All MAUDE reports |
|---|---|---|---|
| Reports | 10,115 | 380,959 | 26,136,888 |
| Share of that pool | — | 2.7% | 0% |
| Classified as death, per 1,000 reports | 6 | 27 | 9 |
| Classified as injury | 60.2% | 59.6% | 36.2% |
| Classified as malfunction | 39.1% | 37.4% | 62.3% |
| Filed by the manufacturer | 99.8% | 97.8% | 94.9% |
Shares are of reports, not of devices in use. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data."
Other brands with product code LWS
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Sprint Quattro Secure S MRI SureScan | 36,895 | 6,436 | 1.4% |
| Emblem Mri S-Icd | 21,480 | 3,088 | 0.2% |
| Sprint Quattro Secure | 24,237 | 2 | 5.2% |
| Emblem S-Icd | 17,250 | 2,237 | 0.1% |
| Sprint Fidelis | 17,005 | 340 | 14.1% |
| Sprint Quattro Secure S | 14,398 | 0 | 2.4% |
| Endotak Reliance | 25,897 | 238 | 1.2% |
| Sprint Quattro Secure MRI SureScan | 15,606 | 1,903 | 1.4% |
| Teligen | 16,537 | 47 | 0.6% |
| Durata Sts Optim Active Fixation | 9,681 | 301 | 5.6% |
| Sprint Quattro | 5,591 | 0 | 2.6% |
| Reliance 4-Front | 9,852 | 2,024 | 0.4% |
| Sprint | 6,131 | 161 | 2.4% |
| Vitality 2 | 4,779 | 0 | 1% |
| S-Icd System | 5,104 | 0 | 1.1% |
Ordered by report count for navigation only. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA also states that "common products may have a higher number of adverse events due to the higher total number of people using the product."
Questions about Endotak Reliance G reports
How many FDA reports name Endotak Reliance G?
10,115 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 1,049 in the latest 12 months.
What kinds of events are reported?
injury (60.2%), malfunction (39.1%) and death (0.6%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
high impedance (48.9%), over-sensing (13.2%), pacing problem (8.6%), signal artifact/noise (8.6%) and high capture threshold (7.5%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (99.8%) and voluntary reports (0.1%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Endotak Reliance G was at fault?
No. FDA states that "MDR data alone cannot be used to establish rates of events, evaluate a change in event rates over time or compare event rates between devices. The number of reports cannot be interpreted or used in isolation to reach conclusions about the existence, severity, or frequency of problems associated with devices." It adds that the reporting system "has limitations, including the potential submission of incomplete, inaccurate, untimely, unverified, or biased data." FDA adds that "a causal relationship cannot be established between product and reactions listed in a report."
How do I report a problem with a medical device?
Through FDA MedWatch (Form FDA 3500 for health professionals and consumers), or to the manufacturer. See the guide on how to report.
Where this comes from. Counts are built from the openFDA Device Adverse Event (MAUDE) bulk export released 28 Sep 2026, which holds reports FDA received through 31 Aug 2026. Brand, generic and manufacturer names are as written on the reports; product code names come from FDA's device classification. A report counts here when any device it lists carries this brand name after punctuation and capitalisation are normalised. No report narrative, lot number, patient detail or reporter identity is published. See the methodology and sources; FDA's record is authoritative, and corrections are handled within five working days.
Drug data (FAERS) through 30 Jun 2026; device data (MAUDE) through 31 Aug 2026. Not medical advice.