Devices › Programmer, pacemaker
Device brand name · Programmer pacemaker
Pacing System Analyzer: medical device reports filed with FDA
607 reports name it, 2019–2026. Manufacturer given most often on reports: Medtronic. Product code KRG.
- 607
- device reports naming the brand
- 0% of all MAUDE reports · about 84 a year
- 92
- reports, 12 months to August 2026
- 55 in the 12 months before
- 98%
- classified as malfunction
- 96.7% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
607 medical device reports received by FDA name the brand "Pacing System Analyzer" (programmer pacemaker); the manufacturer given most often on reports is Medtronic; received from April 2019 to August 2026. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
92 reports arrived in the 12 months to August 2026, up 67% from 55 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 (98%) and injury (2%); across all programmer, pacemaker reports (product code KRG) death is recorded in 0.1% and malfunction in 96.7%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are electrical /electronic property problem (33.1%), output problem (10.7%) and inadequate user interface (8.7%). The patient problems coded most often are no patient involvement, asystole and cardiac arrest. 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 24,211 reports carrying product code KRG. 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 |
|---|---|---|---|
| Electrical /electronic property probleman electrical or electronic problem | 201 | 33.1% | 8.4% |
| Output problem | 65 | 10.7% | 6.6% |
| Inadequate user interface | 53 | 8.7% | 2.5% |
| Device sensing problem | 48 | 7.9% | 0.8% |
| Connection problema connection problem | 46 | 7.6% | 2.9% |
| Mechanical problema mechanical problem | 44 | 7.2% | 4% |
| Impedance problem | 31 | 5.1% | 0.4% |
| No device output | 16 | 2.6% | 0.3% |
| Computer software problema software problem | 15 | 2.5% | 7.2% |
| Signal artifact/noise | 14 | 2.3% | 1.2% |
| Communication or transmission problemthe device could not communicate or transmit | 12 | 2% | 9.1% |
| Battery problema problem with the battery | 11 | 1.8% | 0.5% |
| Computer operating system problem | 9 | 1.5% | 8.3% |
| Insufficient device problem information | 8 | 1.3% | 0.9% |
| Corrodedthe device corroded | 6 | 1% | 0.6% |
| Loose or intermittent connection | 6 | 1% | 1.7% |
| Failure to power up | 5 | 0.8% | 3.6% |
| Failure to sense | 5 | 0.8% | 0.1% |
| Breakthe device broke | 4 | 0.7% | 1.9% |
| Contamination | 4 | 0.7% | 0.3% |
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 | 79 | 13% |
| Asystole | 2 | 0.3% |
| Cardiac arrestthe heart stopped | 1 | 0.2% |
| Convulsion, clonic | 1 | 0.2% |
| Dizzinesslight-headedness or unsteadiness | 1 | 0.2% |
| Heart block | 1 | 0.2% |
| Loss of consciousnesspassing out | 1 | 0.2% |
| Tachycardiafast heart rate | 1 | 0.2% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Pacing System Analyzer | Product code KRG | All MAUDE reports |
|---|---|---|---|
| Reports | 607 | 24,211 | 26,136,888 |
| Share of that pool | — | 2.5% | 0% |
| Classified as death, per 1,000 reports | 0 | 1 | 9 |
| Classified as injury | 2% | 3.2% | 36.2% |
| Classified as malfunction | 98% | 96.7% | 62.3% |
| Filed by the manufacturer | 100% | 99.9% | 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 KRG
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Carelink | 15,005 | 18 | 0% |
| Carelink Programmer | 6,264 | 546 | 0% |
| CareLink Encore Programmer | 1,343 | 103 | 0% |
| SmartTouch | 668 | 132 | 0% |
| Orchestra | 713 | 0 | 0.1% |
| Merlin Programmer | 1,425 | 26 | 0.1% |
| Vitality 2 | 4,779 | 0 | 1% |
| Carelink Encore | 368 | 0 | 0% |
| Medtronic Carelink Programmer With Analyzer | 173 | 31 | 0% |
| Vitality | 2,095 | 0 | 0.9% |
| Zoom | 441 | 3 | 0% |
| N'vision | 269 | 0 | 0.7% |
| Vitality Avt | 1,235 | 0 | 2.3% |
| Carelink System | 343 | 0 | 0.3% |
| Carelink Program W/Telemetry C | 1,681 | 0 | 0% |
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 Pacing System Analyzer reports
How many FDA reports name Pacing System Analyzer?
607 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 92 in the latest 12 months.
What kinds of events are reported?
malfunction (98%) and injury (2%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
electrical /electronic property problem (33.1%), output problem (10.7%), inadequate user interface (8.7%), device sensing problem (7.9%) and connection problem (7.6%). 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 Pacing System Analyzer 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.