Reported Reactions

Devices › Pulse generator, permanent, implantable

Device brand name · Pulse generator permanent implantable

Sensia IPG: medical device reports filed with FDA

1,391 reports name it, 2016–2026. Manufacturer given most often on reports: Medtronic Singapore Operations. Product code NVZ.

1,391
device reports naming the brand
0% of all MAUDE reports · about 134 a year
73
reports, 12 months to August 2026
89 in the 12 months before
27.7%
classified as malfunction
43.5% across the product code
2.7%
classified as death, as reported
38 reports · not verified by FDA

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

73 reports arrived in the 12 months to August 2026, down 18% 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 (69.5%), malfunction (27.7%) and death (2.7%); 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 premature discharge of battery (27.2%), pacing problem (15.2%) and failure to interrogate (6.8%). The patient problems coded most often are bradycardia, dizziness and syncope/fainting. 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

01326Sep 2021: 15Oct 2021: 14Nov 2021: 20Dec 2021: 252022Jan 2022: 16Feb 2022: 14Mar 2022: 16Apr 2022: 14May 2022: 26Jun 2022: 15Jul 2022: 15Aug 2022: 12Sep 2022: 13Oct 2022: 15Nov 2022: 19Dec 2022: 82023Jan 2023: 17Feb 2023: 15Mar 2023: 18Apr 2023: 16May 2023: 14Jun 2023: 9Jul 2023: 10Aug 2023: 9Sep 2023: 18Oct 2023: 13Nov 2023: 19Dec 2023: 62024Jan 2024: 14Feb 2024: 13Mar 2024: 6Apr 2024: 7May 2024: 12Jun 2024: 6Jul 2024: 16Aug 2024: 7Sep 2024: 6Oct 2024: 10Nov 2024: 8Dec 2024: 92025Jan 2025: 4Feb 2025: 4Mar 2025: 5Apr 2025: 13May 2025: 7Jun 2025: 3Jul 2025: 16Aug 2025: 4Sep 2025: 4Oct 2025: 8Nov 2025: 7Dec 2025: 42026Jan 2026: 9Feb 2026: 7Mar 2026: 2Apr 2026: 7May 2026: 8Jun 2026: 5Jul 2026: 7Aug 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

01613212016: 320162018: 320182019: 32120192020: 23220202021: 24220212022: 18320222023: 16420232024: 11420242025: 7920252026: 502026

Event type and report source

Event type, as classified on the report

Death2.7%38
Injury69.5%967
Malfunction27.7%386
Other0%0
Not given0%0

Who filed the report

Manufacturer report100%1,391
Voluntary report0%0
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
Premature discharge of battery37927.2%11.3%
Pacing problem21215.2%10.5%
Failure to interrogate956.8%4.6%
Mechanical problema mechanical problem594.2%3.9%
Battery problema problem with the battery574.1%4.7%
Failure to capture423%3.4%
Communication or transmission problemthe device could not communicate or transmit362.6%1.5%
Reset problem261.9%1.4%
Electromagnetic interference181.3%0.9%
Over-sensing181.3%5.6%
Unable to obtain readings181.3%1.9%
Capturing problem161.2%0.6%
High impedance161.2%1.7%
Incorrect measurementthe device measured wrongly161.2%1.6%
Device sensing problem141%1.4%
False positive result141%0.2%
Insufficient device problem information141%1.8%
Migration or expulsion of device130.9%1.1%
Output problem130.9%0.6%
Signal artifact/noise130.9%1.2%

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
Bradycardiaslow heart rate906.5%
Dizzinesslight-headedness or unsteadiness402.9%
Syncope/fainting362.6%
Dyspneashortness of breath261.9%
Cardiac arrestthe heart stopped221.6%
Arrhythmia181.3%
Non specific ekg/ECG changes171.2%
Syncopefainting171.2%
Tachycardiafast heart rate161.2%
Falla fall141%
Appropriate clinical signs, symptoms and conditions term/code not available130.9%
Painpain, site not specified130.9%
Deaththe patient died; cause not stated by this term120.9%
Pocket erosion120.9%
Heart failure/congestive heart failure110.8%

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

In context

MeasureSensia IPGProduct code NVZAll MAUDE reports
Reports1,39195,61226,136,888
Share of that pool—1.5%0%
Classified as death, per 1,000 reports27419
Classified as injury69.5%52.1%36.2%
Classified as malfunction27.7%43.5%62.3%
Filed by the manufacturer100%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%
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%
Consulta Crt-P68054.7%

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

How many FDA reports name Sensia IPG?

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

What kinds of events are reported?

injury (69.5%), malfunction (27.7%) and death (2.7%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.

What device problems are coded?

premature discharge of battery (27.2%), pacing problem (15.2%), failure to interrogate (6.8%), mechanical problem (4.2%) and battery problem (4.1%). 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 Sensia 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.