Devices › Drug eluting permanent right ventricular (rv) or right atrial (ra) pacemaker electrodes
Device brand name · Permanent pacemaker electrode
Isoflex S: medical device reports filed with FDA
1,946 reports name it, 2003–2023. Manufacturer given most often on reports: St Jude Medical Cardiac Rhythm Management Division. Product code NVN.
- 1,946
- device reports naming the brand
- 0% of all MAUDE reports · about 85 a year
- 0
- reports, 12 months to August 2026
- 0 in the 12 months before
- 36.9%
- classified as malfunction
- 41.6% across the product code
- 1.7%
- classified as death, as reported
- 33 reports · not verified by FDA
FDA's MAUDE database holds 1,946 reports that name the brand "Isoflex S" (permanent pacemaker electrode), received between July 2003 and August 2023; the manufacturer given most often on reports is St Jude Medical Cardiac Rhythm Management Division. 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 injury (61.4%), malfunction (36.9%) and death (1.7%); across all drug eluting permanent right ventricular (rv) or right atrial (ra) pacemaker electrodes reports (product code NVN) death is recorded in 2.2% and malfunction in 41.6%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are failure to capture (15.7%), high sensing threshold (13.3%) and over-sensing (13.1%). The patient problems coded most often are surgical procedure, failure of implant and syncope. 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 229,796 reports carrying product code NVN. 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 |
|---|---|---|---|
| Failure to capture | 305 | 15.7% | 12.6% |
| High sensing threshold | 259 | 13.3% | 0.5% |
| Over-sensing | 254 | 13.1% | 17.9% |
| High impedance | 229 | 11.8% | 9.1% |
| Device dislodged or dislocated | 186 | 9.6% | 15.8% |
| Low impedance | 160 | 8.2% | 5.1% |
| High capture threshold | 136 | 7% | 10.7% |
| Breakthe device broke | 129 | 6.6% | 5.2% |
| Fracturea broken bone | 125 | 6.4% | 4.7% |
| Dislodged | 98 | 5% | 0% |
| Intermittent capture | 80 | 4.1% | 1.1% |
| Capturing problem | 78 | 4% | 4.7% |
| Failure to sense | 66 | 3.4% | 2% |
| Device sensing problem | 64 | 3.3% | 3.7% |
| Low sensing threshold | 39 | 2% | 0.2% |
| Under-sensing | 33 | 1.7% | 4.5% |
| Implant, repositioning of | 32 | 1.6% | 0% |
| Impedance problem | 28 | 1.4% | 2.2% |
| Invalid sensing | 26 | 1.3% | 0.1% |
| Device operates differently than expectedthe device behaved unexpectedly | 23 | 1.2% | 0.5% |
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 | 271 | 13.9% |
| Failure of implant | 65 | 3.3% |
| Syncopefainting | 53 | 2.7% |
| Dizzinesslight-headedness or unsteadiness | 36 | 1.8% |
| Deaththe patient died; cause not stated by this term | 34 | 1.7% |
| Muscle stimulation | 32 | 1.6% |
| Bradycardiaslow heart rate | 28 | 1.4% |
| Perforation | 22 | 1.1% |
| Surgical procedure, repeated | 22 | 1.1% |
| Cardiac arrestthe heart stopped | 12 | 0.6% |
| Fainting | 10 | 0.5% |
| Falla fall | 10 | 0.5% |
| Foreign body in patientpart of a device left in the patient | 9 | 0.5% |
| Complaint, ill-defined | 8 | 0.4% |
| Exit block | 8 | 0.4% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Isoflex S | Product code NVN | All MAUDE reports |
|---|---|---|---|
| Reports | 1,946 | 229,796 | 26,136,888 |
| Share of that pool | — | 0.8% | 0% |
| Classified as death, per 1,000 reports | 17 | 22 | 9 |
| Classified as injury | 61.4% | 56.2% | 36.2% |
| Classified as malfunction | 36.9% | 41.6% | 62.3% |
| Filed by the manufacturer | 99.7% | 96.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 NVN
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Tendril Sts | 54,036 | 4,320 | 3.1% |
| SelectSecure MRI SureScan | 20,961 | 4,994 | 1.3% |
| Tendril St | 20,156 | 547 | 5.2% |
| Ingevity Mri | 17,101 | 1,749 | 0.3% |
| Ingevity+ | 15,340 | 2,150 | 0.3% |
| Tendril Sdx Lead | 9,380 | 431 | 4.5% |
| CapSure Fix MRI | 5,755 | 600 | 0.6% |
| Solia S 53 | 4,997 | 647 | 0.5% |
| Tendril Mri | 7,076 | 422 | 4.1% |
| Drug Eluting Permanent Right Ventricular Rv Or Right Atrial Ra Pacemaker Ele | 4,462 | 405 | 0.3% |
| Capsurefix Mri Surescan | 4,247 | 0 | 2.8% |
| Tendril Sdx | 8,316 | 3 | 2.3% |
| Ingevity | 9,039 | 299 | 0.9% |
| Ingevity + | 3,053 | 2,281 | 0.6% |
| Dextrus 4136 | 5,698 | 0 | 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 Isoflex S reports
How many FDA reports name Isoflex S?
1,946 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?
injury (61.4%), malfunction (36.9%) and death (1.7%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
failure to capture (15.7%), high sensing threshold (13.3%), over-sensing (13.1%), high impedance (11.8%) and device dislodged or dislocated (9.6%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (99.7%) and voluntary reports (0.2%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.
Do these reports show that Isoflex S 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.