Devices › Defibrillator, automatic implantable cardioverter, with cardiac resynchronization (crt-d)
Device brand name · Programmer pacemaker
Merlin Programmer: medical device reports filed with FDA
1,425 reports name it, 2011–2026. Manufacturer given most often on reports: St Jude Medical Crm-Sylmar. Product code NIK.
- 1,425
- device reports naming the brand
- 0% of all MAUDE reports · about 93 a year
- 26
- reports, 12 months to August 2026
- 25 in the 12 months before
- 92.8%
- classified as malfunction
- 47.2% across the product code
- 0.1%
- classified as death, as reported
- 1 reports · not verified by FDA
FDA's MAUDE database holds 1,425 reports that name the brand "Merlin Programmer" (programmer pacemaker), received between March 2011 and August 2026; the manufacturer given most often on reports is St Jude Medical Crm-Sylmar. Spellings of one product vary from report to report.
26 reports arrived in the 12 months to August 2026, close to the 25 of 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 (92.8%), injury (6.9%) and other (0.1%); across all defibrillator, automatic implantable cardioverter, with cardiac resynchronization (crt-d) reports (product code NIK) death is recorded in 2.8% and malfunction in 47.2%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are incorrect measurement (57.2%), device operates differently than expected (11.9%) and data problem (4.1%). The patient problems coded most often are no patient involvement, arrhythmia and discomfort. 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 170,404 reports carrying product code NIK. 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 |
|---|---|---|---|
| Incorrect measurementthe device measured wrongly | 815 | 57.2% | 0.8% |
| Device operates differently than expectedthe device behaved unexpectedly | 169 | 11.9% | 1.5% |
| Data problem | 59 | 4.1% | 0.5% |
| Failure to interrogate | 44 | 3.1% | 2.3% |
| Program or algorithm execution failure | 43 | 3% | 0% |
| Thermal decomposition of device | 42 | 2.9% | 0% |
| Improper device output | 23 | 1.6% | 0% |
| Smoking | 23 | 1.6% | 0% |
| Application program freezes or fails to launch | 21 | 1.5% | 0% |
| Interrogation problem | 21 | 1.5% | 0.3% |
| Device emits odor | 20 | 1.4% | 0% |
| Defective devicethe device was defective | 19 | 1.3% | 0.7% |
| Sparking | 19 | 1.3% | 0% |
| Failure to power up | 16 | 1.1% | 0% |
| Unintended electrical shock | 15 | 1.1% | 0% |
| Overheating of device | 13 | 0.9% | 0% |
| Noise, audible | 12 | 0.8% | 0.1% |
| Inappropriate/inadequate shock/stimulation | 10 | 0.7% | 5.2% |
| Computer software problema software problem | 9 | 0.6% | 0% |
| Unintended application program shut down | 9 | 0.6% | 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 |
|---|---|---|
| No patient involvement | 59 | 4.1% |
| Arrhythmia | 41 | 2.9% |
| Discomfortdiscomfort | 13 | 0.9% |
| Dizzinesslight-headedness or unsteadiness | 12 | 0.8% |
| Electric shockan electric shock | 12 | 0.8% |
| Shockshock, a collapse of the circulation | 9 | 0.6% |
| Syncope/fainting | 8 | 0.6% |
| Cardiac arrestthe heart stopped | 2 | 0.1% |
| Deaththe patient died; cause not stated by this term | 2 | 0.1% |
| Fainting | 2 | 0.1% |
| Fatiguetiredness | 2 | 0.1% |
| Appropriate clinical signs, symptoms and conditions term/code not available | 1 | 0.1% |
| Asystole | 1 | 0.1% |
| Cardiopulmonary arrest | 1 | 0.1% |
| Electrocution | 1 | 0.1% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Merlin Programmer | Product code NIK | All MAUDE reports |
|---|---|---|---|
| Reports | 1,425 | 170,404 | 26,136,888 |
| Share of that pool | — | 0.8% | 0% |
| Classified as death, per 1,000 reports | 1 | 28 | 9 |
| Classified as injury | 6.9% | 49.8% | 36.2% |
| Classified as malfunction | 92.8% | 47.2% | 62.3% |
| Filed by the manufacturer | 100% | 99.2% | 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 NIK
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Quadra Assura MP ICD | 14,897 | 507 | 2.1% |
| Gallant HF | 8,971 | 1,918 | 0.7% |
| Quadra Assura Crt-D Quad Rf Hv | 7,971 | 14 | 2.5% |
| Quartet | 14,149 | 848 | 5.2% |
| Unify Assura CRT-D RF HV | 6,731 | 186 | 3.7% |
| Unify Crt-D | 5,907 | 10 | 3.4% |
| Consulta Crt-D | 4,623 | 0 | 5.9% |
| Unify Assura ICD | 4,511 | 127 | 1.6% |
| Claria MRI Quad CRT-D SureScan | 3,775 | 274 | 2.2% |
| Cognis | 8,694 | 6 | 1.5% |
| Protecta Xt Crt-D | 3,541 | 3 | 4.5% |
| Quadra Assura Ddqp+ | 3,349 | 0 | 2.3% |
| Contak Renewal | 3,745 | 0 | 4.8% |
| Cobalt XT HF Quad CRT-D MRI SureScan | 2,581 | 791 | 3% |
| Quadra Assura ICD | 2,526 | 67 | 0.8% |
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 Merlin Programmer reports
How many FDA reports name Merlin Programmer?
1,425 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 26 in the latest 12 months.
What kinds of events are reported?
malfunction (92.8%), injury (6.9%) and other (0.1%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
incorrect measurement (57.2%), device operates differently than expected (11.9%), data problem (4.1%), failure to interrogate (3.1%) and program or algorithm execution failure (3%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (100%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Merlin Programmer 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.