Devices › Drug eluting permanent left ventricular (lv) pacemaker electrode
Device brand name · Drug eluting permanent left ventricular lv p
Attain Ability MRI SureScan: medical device reports filed with FDA
1,344 reports name it, 2011–2026. Manufacturer given most often on reports: Mpri. Product code OJX.
- 1,344
- device reports naming the brand
- 0% of all MAUDE reports · about 90 a year
- 162
- reports, 12 months to August 2026
- 162 in the 12 months before
- 42.8%
- classified as malfunction
- 40.2% across the product code
- 0.3%
- classified as death, as reported
- 4 reports · not verified by FDA
FDA's MAUDE database holds 1,344 reports that name the brand "Attain Ability MRI SureScan" (drug eluting permanent left ventricular lv p), received between August 2011 and August 2026; the manufacturer given most often on reports is Mpri. Spellings of one product vary from report to report.
162 reports arrived in the 12 months to August 2026, close to the 162 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 injury (56.9%), malfunction (42.8%) and death (0.3%); across all drug eluting permanent left ventricular (lv) pacemaker electrode reports (product code OJX) death is recorded in 3.5% and malfunction in 40.2%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are high capture threshold (28.1%), device dislodged or dislocated (13.8%) and failure to capture (10.9%). The patient problems coded most often are device overstimulation of tissue, undesired nerve stimulation and erosion. 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 52,462 reports carrying product code OJX. 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 |
|---|---|---|---|
| High capture threshold | 377 | 28.1% | 15.9% |
| Device dislodged or dislocated | 186 | 13.8% | 23.6% |
| Failure to capture | 146 | 10.9% | 15.6% |
| High impedance | 108 | 8% | 8.6% |
| Capturing problem | 90 | 6.7% | 5.4% |
| Positioning problem | 85 | 6.3% | 2.9% |
| Fracturea broken bone | 52 | 3.9% | 3% |
| Impedance problem | 43 | 3.2% | 2.4% |
| Breakthe device broke | 40 | 3% | 2.3% |
| Unstable capture threshold | 38 | 2.8% | 1.3% |
| Material integrity problema problem with the device material | 30 | 2.2% | 1% |
| Activation, positioning or separation problem | 21 | 1.6% | 3% |
| Low impedance | 21 | 1.6% | 2.3% |
| Pacing problem | 15 | 1.1% | 1% |
| Extracardiac stimulation | 11 | 0.8% | 1.5% |
| Intermittent capture | 11 | 0.8% | 1.1% |
| Over-sensing | 9 | 0.7% | 1% |
| Signal artifact/noise | 4 | 0.3% | 0.4% |
| Device sensing problem | 2 | 0.1% | 0.7% |
| Difficult to removethe device was hard to remove | 2 | 0.1% | 0.9% |
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 |
|---|---|---|
| Device overstimulation of tissue | 75 | 5.6% |
| Undesired nerve stimulation | 56 | 4.2% |
| Erosion | 22 | 1.6% |
| Dyspneashortness of breath | 21 | 1.6% |
| Pocket erosion | 20 | 1.5% |
| Discomfortdiscomfort | 18 | 1.3% |
| Muscle stimulation | 18 | 1.3% |
| Heart failure/congestive heart failure | 15 | 1.1% |
| Erythemaskin redness | 14 | 1% |
| Swelling/ edema | 14 | 1% |
| Medical device site infectioninfection at the device site | 9 | 0.7% |
| Bacteremia | 8 | 0.6% |
| Purulent discharge | 8 | 0.6% |
| Chest painchest pain | 7 | 0.5% |
| Pericardial effusionfluid around the heart | 7 | 0.5% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Attain Ability MRI SureScan | Product code OJX | All MAUDE reports |
|---|---|---|---|
| Reports | 1,344 | 52,462 | 26,136,888 |
| Share of that pool | — | 2.6% | 0% |
| Classified as death, per 1,000 reports | 3 | 35 | 9 |
| Classified as injury | 56.9% | 56.2% | 36.2% |
| Classified as malfunction | 42.8% | 40.2% | 62.3% |
| Filed by the manufacturer | 99.8% | 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 OJX
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Quartet | 14,149 | 848 | 5.2% |
| Attain Ability | 5,253 | 0 | 4.4% |
| Attain Performa MRI SureScan | 4,795 | 647 | 1.4% |
| Attain Stability Quad MRI SureScan | 4,176 | 837 | 1.3% |
| Attain Performa | 3,995 | 0 | 1.8% |
| Attain Performa S MRI SureScan | 3,158 | 440 | 1.6% |
| Quickflex Micro Lv Lead | 3,702 | 116 | 5.9% |
| Attain Performa Straight MRI SureScan | 2,065 | 271 | 1.7% |
| Easytrak 2 | 4,260 | 18 | 0.8% |
| Attain Ability Plus | 1,887 | 0 | 2.9% |
| Sentus ProMRI OTW QP L-85/49 | 1,684 | 249 | 0.5% |
| Acuity | 3,848 | 6 | 1% |
| Quartet Lead Double Bend, 86 cm | 1,207 | 91 | 2.6% |
| Drug Eluting Permanent Left Ventricular Lv Pacemaker Electrode | 1,234 | 80 | 0.3% |
| Quicksite Lv | 1,718 | 13 | 7.2% |
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 Attain Ability MRI SureScan reports
How many FDA reports name Attain Ability MRI SureScan?
1,344 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 162 in the latest 12 months.
What kinds of events are reported?
injury (56.9%), malfunction (42.8%) and death (0.3%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
high capture threshold (28.1%), device dislodged or dislocated (13.8%), failure to capture (10.9%), high impedance (8%) and capturing problem (6.7%). These are FDA's device problem codes as entered on the report.
Who files these reports?
manufacturer reports (99.8%) 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 Attain Ability MRI SureScan 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.