Devices › Drug eluting permanent left ventricular (lv) pacemaker electrode
Device brand name · Drug eluting permanent left ventricular lv pacemaker electrode
Attain Ability Straight: medical device reports filed with FDA
480 reports name it, 2013–2019. Manufacturer given most often on reports: Mpri. Product code OJX.
- 480
- device reports naming the brand
- 0% of all MAUDE reports · about 36 a year
- 0
- reports, 12 months to August 2026
- 0 in the 12 months before
- 48.1%
- classified as malfunction
- 40.2% across the product code
- 1.5%
- classified as death, as reported
- 7 reports · not verified by FDA
480 medical device reports received by FDA name the brand "Attain Ability Straight" (drug eluting permanent left ventricular lv pacemaker electrode); the manufacturer given most often on reports is Mpri; received from February 2013 to May 2019. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
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 (50.4%), malfunction (48.1%) and death (1.5%); 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 device dislodged or dislocated (29.6%), high capture threshold (20.8%) and positioning problem (12.9%). The patient problems coded most often are muscle stimulation, undesired nerve stimulation and death. 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
No report naming Attain Ability Straight was received in the five years to August 2026; the latest was received in May 2019.
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 |
|---|---|---|---|
| Device dislodged or dislocated | 142 | 29.6% | 23.6% |
| High capture threshold | 100 | 20.8% | 15.9% |
| Positioning problem | 62 | 12.9% | 2.9% |
| Failure to capture | 41 | 8.5% | 15.6% |
| Capturing problem | 30 | 6.3% | 5.4% |
| High impedance | 26 | 5.4% | 8.6% |
| Activation, positioning or separation problem | 22 | 4.6% | 3% |
| Breakthe device broke | 18 | 3.8% | 2.3% |
| Fracturea broken bone | 16 | 3.3% | 3% |
| Unstable capture threshold | 9 | 1.9% | 1.3% |
| Migration or expulsion of device | 6 | 1.3% | 0.4% |
| Accessory incompatible | 4 | 0.8% | 0.1% |
| Device handling problem | 4 | 0.8% | 0.1% |
| Device operates differently than expectedthe device behaved unexpectedly | 4 | 0.8% | 0.5% |
| Extracardiac stimulation | 4 | 0.8% | 1.5% |
| Material integrity problema problem with the device material | 4 | 0.8% | 1% |
| Pacing problem | 4 | 0.8% | 1% |
| Device contamination with body fluid | 3 | 0.6% | 0.3% |
| Signal artifact/noise | 3 | 0.6% | 0.4% |
| Connection problema connection problem | 2 | 0.4% | 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 |
|---|---|---|
| Muscle stimulation | 68 | 14.2% |
| Undesired nerve stimulation | 37 | 7.7% |
| Deaththe patient died; cause not stated by this term | 7 | 1.5% |
| Dyspneashortness of breath | 5 | 1% |
| Vascular dissection | 5 | 1% |
| Complaint, ill-defined | 4 | 0.8% |
| Endocarditis | 3 | 0.6% |
| Erosion | 2 | 0.4% |
| Hematomaa collection of blood under the skin or in tissue | 2 | 0.4% |
| Sepsisa severe body-wide response to infection | 2 | 0.4% |
| Twiddlers syndrome | 2 | 0.4% |
| Atrial fibrillationan irregular heart rhythm | 1 | 0.2% |
| Cardiac perforation | 1 | 0.2% |
| Coma | 1 | 0.2% |
| Device embedded in tissue or plaque | 1 | 0.2% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Attain Ability Straight | Product code OJX | All MAUDE reports |
|---|---|---|---|
| Reports | 480 | 52,462 | 26,136,888 |
| Share of that pool | — | 0.9% | 0% |
| Classified as death, per 1,000 reports | 15 | 35 | 9 |
| Classified as injury | 50.4% | 56.2% | 36.2% |
| Classified as malfunction | 48.1% | 40.2% | 62.3% |
| Filed by the manufacturer | 100% | 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% |
| Attain Ability MRI SureScan | 1,344 | 162 | 0.3% |
| Quartet Lead Double Bend, 86 cm | 1,207 | 91 | 2.6% |
| Drug Eluting Permanent Left Ventricular Lv Pacemaker Electrode | 1,234 | 80 | 0.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 Attain Ability Straight reports
How many FDA reports name Attain Ability Straight?
480 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 (50.4%), malfunction (48.1%) and death (1.5%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
device dislodged or dislocated (29.6%), high capture threshold (20.8%), positioning problem (12.9%), failure to capture (8.5%) and capturing problem (6.3%). 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 Attain Ability Straight 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.