Reported Reactions

Devices › Pulse generator, permanent, implantable

Device brand name · Pulse generator permanent implantable

Medtronic IPG: medical device reports filed with FDA

529 reports name it, 2019–2026. Manufacturer given most often on reports: Medtronic. Product code NVZ.

529
device reports naming the brand
0% of all MAUDE reports · about 74 a year
114
reports, 12 months to August 2026
89 in the 12 months before
34.8%
classified as malfunction
43.5% across the product code
15.1%
classified as death, as reported
80 reports · not verified by FDA

FDA's MAUDE database holds 529 reports that name the brand "Medtronic IPG" (pulse generator permanent implantable), received between May 2019 and August 2026; the manufacturer given most often on reports is Medtronic. Spellings of one product vary from report to report.

114 reports arrived in the 12 months to August 2026, up 28% from 89 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 (49.9%), malfunction (34.8%) and death (15.1%); across all pulse generator, permanent, implantable reports (product code NVZ) death is recorded in 4.1% and malfunction in 43.5%. Event type is the reporter's classification of the report, not a verified outcome.

The device problems coded most often are pacing problem (7%), premature discharge of battery (4.7%) and failure to interrogate (3.6%). The patient problems coded most often are hematoma, heart failure/congestive heart failure and pneumothorax. 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

01223Sep 2021: 3Oct 2021: 0Nov 2021: 2Dec 2021: 52022Jan 2022: 2Feb 2022: 4Mar 2022: 2Apr 2022: 3May 2022: 5Jun 2022: 5Jul 2022: 7Aug 2022: 3Sep 2022: 5Oct 2022: 6Nov 2022: 2Dec 2022: 22023Jan 2023: 8Feb 2023: 7Mar 2023: 6Apr 2023: 7May 2023: 8Jun 2023: 1Jul 2023: 5Aug 2023: 20Sep 2023: 11Oct 2023: 8Nov 2023: 6Dec 2023: 82024Jan 2024: 5Feb 2024: 9Mar 2024: 5Apr 2024: 10May 2024: 3Jun 2024: 2Jul 2024: 13Aug 2024: 8Sep 2024: 12Oct 2024: 16Nov 2024: 4Dec 2024: 42025Jan 2025: 4Feb 2025: 4Mar 2025: 13Apr 2025: 5May 2025: 4Jun 2025: 4Jul 2025: 12Aug 2025: 7Sep 2025: 10Oct 2025: 5Nov 2025: 15Dec 2025: 62026Jan 2026: 23Feb 2026: 11Mar 2026: 6Apr 2026: 10May 2026: 6Jun 2026: 6Jul 2026: 11Aug 2026: 5

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

048952019: 2720192020: 4720202021: 5620212022: 4620222023: 9520232024: 9120242025: 8920252026: 782026

Event type and report source

Event type, as classified on the report

Death15.1%80
Injury49.9%264
Malfunction34.8%184
Other0.2%1
Not given0%0

Who filed the report

Manufacturer report97.5%516
Voluntary report2.5%13
User facility report0%0
Distributor report0%0
Not given0%0

Grey bar: all 95,612 reports carrying product code NVZ. Event type is the filer's classification and is not verified by FDA.

Device problems coded

Device problem (FDA code)ReportsShareShare across product code
Pacing problem377%10.5%
Premature discharge of battery254.7%11.3%
Failure to interrogate193.6%4.6%
Insufficient device problem information152.8%1.8%
Failure to capture132.5%3.4%
Mechanical problema mechanical problem112.1%3.9%
Battery problema problem with the battery101.9%4.7%
Electromagnetic interference101.9%0.9%
Over-sensing101.9%5.6%
Migration or expulsion of device91.7%1.1%
Reset problem81.5%1.4%
Device sensing problem71.3%1.4%
Signal artifact/noise61.1%1.2%
Therapeutic or diagnostic output failure61.1%0.1%
Capturing problem50.9%0.6%
Communication or transmission problemthe device could not communicate or transmit50.9%1.5%
High impedance50.9%1.7%
Device-device incompatibility40.8%0.2%
Output problem40.8%0.6%
Data problem30.6%0.8%

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)ReportsShare
Hematomaa collection of blood under the skin or in tissue377%
Heart failure/congestive heart failure326%
Pneumothoraxa collapsed lung244.5%
Cardiomyopathydisease of the heart muscle224.2%
Cardiac arrestthe heart stopped163%
Endocarditis163%
Tachycardiafast heart rate163%
Bacterial infectiona bacterial infection152.8%
Thrombosis/thrombus152.8%
Dyspneashortness of breath132.5%
Pericardial effusionfluid around the heart132.5%
Sepsisa severe body-wide response to infection132.5%
Syncope/fainting132.5%
Medical device site infectioninfection at the device site122.3%
Atrial fibrillationan irregular heart rhythm112.1%

Patient problem codes are present mainly in reports filed since 2019 and are often blank.

In context

MeasureMedtronic IPGProduct code NVZAll MAUDE reports
Reports52995,61226,136,888
Share of that pool—0.6%0%
Classified as death, per 1,000 reports151419
Classified as injury49.9%52.1%36.2%
Classified as malfunction34.8%43.5%62.3%
Filed by the manufacturer97.5%98.7%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 NVZ

BrandReportsLatest 12 monthsClassified as death
Adapta4,8932797.4%
Advisa MRI SureScan3,5892721.9%
Reply2,81491.5%
Insignia3,79201.3%
Altrua4,12202.4%
Carelink15,005180%
Sensia IPG1,391732.7%
Dextrus 41365,69800.8%
Azure91901.8%
MyCareLink Patient Monitor893470.1%
Pulse Generator Permanent Implantable852241.1%
Fortify Vr U1 6 Sj4 Us1,56481.2%
Ellipse VR1,507453.7%
Symphony1,1631331.6%
Fortify Assura VR ICD, US4,8882132.3%

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 Medtronic IPG reports

How many FDA reports name Medtronic IPG?

529 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 114 in the latest 12 months.

What kinds of events are reported?

injury (49.9%), malfunction (34.8%) and death (15.1%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.

What device problems are coded?

pacing problem (7%), premature discharge of battery (4.7%), failure to interrogate (3.6%), insufficient device problem information (2.8%) and failure to capture (2.5%). These are FDA's device problem codes as entered on the report.

Who files these reports?

manufacturer reports (97.5%) and voluntary reports (2.5%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.

Do these reports show that Medtronic IPG 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.