Devices › Implantable pacemaker pulse-generator
Device brand name · Implantable pacemaker
Dash: medical device reports filed with FDA
159 reports name it, 1996–2013. Manufacturer given most often on reports: Sulzer Intermedics. Product code DXY.
- 159
- device reports naming the brand
- 0% of all MAUDE reports · about 5 a year
- 0
- reports, 12 months to August 2026
- 0 in the 12 months before
- 73.6%
- classified as malfunction
- 41.2% across the product code
- 8.8%
- classified as death, as reported
- 14 reports · not verified by FDA
FDA's MAUDE database holds 159 reports that name the brand "Dash" (implantable pacemaker), received between September 1996 and November 2013; the manufacturer given most often on reports is Sulzer Intermedics. Spellings of one product vary from report to report.
0 reports arrived in the 12 months to August 2026, and none 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 malfunction (73.6%), injury (12.6%) and death (8.8%); across all implantable pacemaker pulse-generator reports (product code DXY) death is recorded in 3.4% and malfunction in 41.2%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are other (for use when an appropriate device code cannot be identified) (18.2%), failure to capture (11.3%) and no device output (7.5%). The patient problems coded most often are surgical procedure, other (for use when an appropriate patient code cannot be identified) and erosion. 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
No report naming Dash was received in the five years to August 2026; the latest was received in November 2013.
By year received
Event type and report source
Event type, as classified on the report
Who filed the report
Grey bar: all 57,832 reports carrying product code DXY. 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 |
|---|---|---|---|
| Other (for use when an appropriate device code cannot be identified) | 29 | 18.2% | 4.5% |
| Failure to capture | 18 | 11.3% | 6.3% |
| No device output | 12 | 7.5% | 4.8% |
| Sensing intermittently | 11 | 6.9% | 0.7% |
| Explanted | 10 | 6.3% | 3.3% |
| Invalid sensing | 9 | 5.7% | 0.5% |
| Failure to interrogate | 8 | 5% | 6.1% |
| Connection error | 6 | 3.8% | 0.7% |
| Material erosion | 6 | 3.8% | 0.9% |
| Pacemaker found in back-up mode | 6 | 3.8% | 6.1% |
| Malfunction | 5 | 3.1% | 1.9% |
| Implant, removal of | 4 | 2.5% | 0.2% |
| Over-sensing | 4 | 2.5% | 5.4% |
| Pacing intermittently | 4 | 2.5% | 0.5% |
| Telemetry discrepancy | 4 | 2.5% | 2.3% |
| Device remains implanted | 3 | 1.9% | 0.8% |
| Replace | 3 | 1.9% | 0.9% |
| Under-sensing | 3 | 1.9% | 1.4% |
| Ekg/ECG analysis, failure to perform | 2 | 1.3% | 0% |
| Failure to reset | 2 | 1.3% | 0% |
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 |
|---|---|---|
| Surgical procedure | 19 | 11.9% |
| Other (for use when an appropriate patient code cannot be identified) | 11 | 6.9% |
| Erosion | 5 | 3.1% |
| Deaththe patient died; cause not stated by this term | 3 | 1.9% |
| Surgical procedure, repeated | 3 | 1.9% |
| Allergic reactionan allergic reaction | 2 | 1.3% |
| Asystole | 2 | 1.3% |
| Bradycardiaslow heart rate | 2 | 1.3% |
| Edemaswelling from fluid | 2 | 1.3% |
| Syncopefainting | 2 | 1.3% |
| Therapy/non-surgical treatment, additional | 2 | 1.3% |
| Anaphylaxis | 1 | 0.6% |
| Arrhythmia | 1 | 0.6% |
| Atrial fibrillationan irregular heart rhythm | 1 | 0.6% |
| Cardiac arrestthe heart stopped | 1 | 0.6% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Dash | Product code DXY | All MAUDE reports |
|---|---|---|---|
| Reports | 159 | 57,832 | 26,136,888 |
| Share of that pool | — | 0.3% | 0% |
| Classified as death, per 1,000 reports | 88 | 34 | 9 |
| Classified as injury | 12.6% | 54.4% | 36.2% |
| Classified as malfunction | 73.6% | 41.2% | 62.3% |
| Filed by the manufacturer | 89.9% | 96.6% | 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 DXY
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Tendril Mri | 7,076 | 422 | 4.1% |
| Medtronic Lead | 2,351 | 328 | 9.5% |
| Carelink Program W/Telemetry C | 1,681 | 0 | 0% |
| Carelink | 15,005 | 18 | 0% |
| Assurity Mri | 18,995 | 2,035 | 1.8% |
| Insignia Plus | 940 | 0 | 9.1% |
| Insignia Ultra | 797 | 0 | 5.4% |
| Meta Dddr | 532 | 0 | 0.4% |
| Enpulse | 606 | 3 | 10.4% |
| Medtronic ICD | 404 | 105 | 23.8% |
| Insignia Entra | 374 | 0 | 10.2% |
| Anthem Rf | 372 | 0 | 4.3% |
| Tempo | 721 | 155 | 0.7% |
| Medtronic | 2,953 | 17 | 4.4% |
| Symphony | 1,163 | 133 | 1.6% |
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 Dash reports
How many FDA reports name Dash?
159 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 0 in the latest 12 months.
What kinds of events are reported?
malfunction (73.6%), injury (12.6%) and death (8.8%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
other (for use when an appropriate device code cannot be identified) (18.2%), failure to capture (11.3%), no device output (7.5%), sensing intermittently (6.9%) and explanted (6.3%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (89.9%) and voluntary reports (1.3%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Dash 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.