Devices › Recorder, event, implantable cardiac, (without arrhythmia detection)
Device brand name · Recorder event implantable cardiac without arrhythmia detection
Assert-IQ ICM: medical device reports filed with FDA
2,350 reports name it, 2023–2026. Manufacturer given most often on reports: St Jude Medical Crm-Sylmar. Product code MXC.
- 2,350
- device reports naming the brand
- 0% of all MAUDE reports · about 743 a year
- 1,162
- reports, 12 months to August 2026
- 741 in the 12 months before
- 88.7%
- classified as malfunction
- 85.7% across the product code
- 0%
- classified as death, as reported
- 0 reports · not verified by FDA
2,350 medical device reports received by FDA name the brand "Assert-IQ ICM" (recorder event implantable cardiac without arrhythmia detection); the manufacturer given most often on reports is St Jude Medical Crm-Sylmar; received from May 2023 to August 2026. Brand names are as the reporter or manufacturer wrote them, so one product can appear under several spellings.
1,162 reports arrived in the 12 months to August 2026, up 57% from 741 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 malfunction (88.7%) and injury (11.3%); across all recorder, event, implantable cardiac, (without arrhythmia detection) reports (product code MXC) death is recorded in 0.2% and malfunction in 85.7%. Event type is the reporter's classification of the report, not a verified outcome.
The device problems coded most often are failure to interrogate (28.9%), under-sensing (26.7%) and premature discharge of battery (12%). The patient problems coded most often are pocket erosion, discomfort and wound dehiscence. 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 11,316 reports carrying product code MXC. 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 interrogate | 679 | 28.9% | 14.7% |
| Under-sensing | 627 | 26.7% | 40.4% |
| Premature discharge of battery | 281 | 12% | 5.6% |
| Over-sensing | 267 | 11.4% | 11.8% |
| Incorrect measurementthe device measured wrongly | 193 | 8.2% | 3.6% |
| Inappropriate or unexpected reset | 110 | 4.7% | 2.2% |
| Interrogation problem | 100 | 4.3% | 1.5% |
| Data problem | 66 | 2.8% | 4.2% |
| Incorrect, inadequate or imprecise result or readings | 54 | 2.3% | 1.6% |
| Signal artifact/noise | 51 | 2.2% | 3.6% |
| Wireless communication problema wireless connection problem | 42 | 1.8% | 1.3% |
| Failure to sense | 37 | 1.6% | 2.4% |
| Migration or expulsion of device | 27 | 1.1% | 1.1% |
| Device sensing problem | 26 | 1.1% | 1.6% |
| Incorrect interpretation of signal | 24 | 1% | 1.1% |
| Battery problema problem with the battery | 13 | 0.6% | 0.3% |
| Unexpected mode switch | 12 | 0.5% | 0.1% |
| Computer software problema software problem | 7 | 0.3% | 0.1% |
| Sensing intermittently | 7 | 0.3% | 1.3% |
| Insufficient device problem information | 4 | 0.2% | 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 |
|---|---|---|
| Pocket erosion | 41 | 1.7% |
| Discomfortdiscomfort | 31 | 1.3% |
| Wound dehiscencea wound reopened | 16 | 0.7% |
| Hypersensitivity/allergic reaction | 4 | 0.2% |
| Arrhythmia | 2 | 0.1% |
| Dizzinesslight-headedness or unsteadiness | 2 | 0.1% |
| Erosion | 2 | 0.1% |
| Hemorrhage/blood loss/bleeding | 2 | 0.1% |
| Appropriate clinical signs, symptoms and conditions term/code not available | 1 | 0% |
| Fatiguetiredness | 1 | 0% |
| Hematomaa collection of blood under the skin or in tissue | 1 | 0% |
Patient problem codes are present mainly in reports filed since 2019 and are often blank.
In context
| Measure | Assert-IQ ICM | Product code MXC | All MAUDE reports |
|---|---|---|---|
| Reports | 2,350 | 11,316 | 26,136,888 |
| Share of that pool | — | 20.8% | 0% |
| Classified as death, per 1,000 reports | 0 | 2 | 9 |
| Classified as injury | 11.3% | 14.1% | 36.2% |
| Classified as malfunction | 88.7% | 85.7% | 62.3% |
| Filed by the manufacturer | 100% | 99.8% | 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 MXC
| Brand | Reports | Latest 12 months | Classified as death |
|---|---|---|---|
| Confirm | 7,755 | 34 | 0.1% |
| Jot Dx ICM | 1,071 | 139 | 0.1% |
| LUX-Dx Insertable Cardiac Monitor | 660 | 83 | 0% |
| Diamondback 360 Coronary Orbital Atherectomy System | 1,512 | 0 | 15.7% |
| Reveal LINQ | 19,184 | 264 | 0% |
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 Assert-IQ ICM reports
How many FDA reports name Assert-IQ ICM?
2,350 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 1,162 in the latest 12 months.
What kinds of events are reported?
malfunction (88.7%) and injury (11.3%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.
What device problems are coded?
failure to interrogate (28.9%), under-sensing (26.7%), premature discharge of battery (12%), over-sensing (11.4%) and incorrect measurement (8.2%). 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 Assert-IQ ICM 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.