Device type · MXD
Recorder, Event, Implantable Cardiac, (With Arrhythmia Detection)
Last checked: Nov 19, 2026Source: openFDAMethods & limitations
Product code
MXD
Cardiovascular
Device class
Class II
FDA decisions since 2015
32
510(k), De Novo and PMA
Adverse event reports
3,245
Received Nov 1, 2025 to Nov 19, 2026
How FDA classifies it
- Device type
- Recorder, Event, Implantable Cardiac, (With Arrhythmia Detection)
- Product code
- MXD
- Device class
- Class II
- Review panel
- Cardiovascular
- Regulation
- 21 CFR 870.1025
- Specialty
- Cardiology, Electrophysiology
- FDA record
- Classification database entry for MXD
Latest FDA decisions
The 8 newest of 32 since 2015.
K262735 · Decided Aug 28, 2026 · 28 days after receipt
Device type: Recorder, Event, Implantable Cardiac, (With Arrhythmia Detection) (MXD) · Cardiology
- BIOMONITOR IV (471155)510(k)
K261074 · Decided May 1, 2026 · 30 days after receipt
Device type: Recorder, Event, Implantable Cardiac, (With Arrhythmia Detection) (MXD) · Cardiology
- Assert-IQ (DM5100)510(k)
K253516 · Decided Dec 18, 2025 · 36 days after receipt
Device type: Recorder, Event, Implantable Cardiac, (With Arrhythmia Detection) (MXD) · Cardiology
K251221 · Decided Sep 17, 2025 · 149 days after receipt
Device type: Recorder, Event, Implantable Cardiac, (With Arrhythmia Detection) (MXD) · Cardiology
K252593 · Decided Sep 12, 2025 · 28 days after receipt
Device type: Recorder, Event, Implantable Cardiac, (With Arrhythmia Detection) (MXD) · Cardiology
K240693 · Decided Mar 28, 2024 · 15 days after receipt
Device type: Recorder, Event, Implantable Cardiac, (With Arrhythmia Detection) (MXD) · Cardiology
K233562 · Decided Dec 6, 2023 · 30 days after receipt
Device type: Recorder, Event, Implantable Cardiac, (With Arrhythmia Detection) (MXD) · Cardiology
K233320 · Decided Oct 31, 2023 · 32 days after receipt
Device type: Recorder, Event, Implantable Cardiac, (With Arrhythmia Detection) (MXD) · Cardiology
Reports received
3,245
Received Nov 1, 2025 to Nov 19, 2026. Includes 1 of another or unstated type.
Malfunction reports
2,822
87% of reports
Injury reports
422
13% of reports
Death reports
0
0.0% of reports
Adverse event reports received per month
By the date FDA received each report, stacked by event type. The newest month is incomplete.
- Malfunction
- Injury
- Death
- Other
View as table
| Month | Malfunction | Injury | Death | Other |
|---|---|---|---|---|
| Dec 23 | 115 | 20 | 0 | 0 |
| Jan 24 | 183 | 36 | 0 | 0 |
| Feb 24 | 155 | 32 | 0 | 0 |
| Mar 24 | 247 | 18 | 0 | 0 |
| Apr 24 | 210 | 34 | 1 | 0 |
| May 24 | 369 | 21 | 0 | 0 |
| Jun 24 | 152 | 32 | 0 | 0 |
| Jul 24 | 246 | 36 | 0 | 0 |
| Aug 24 | 210 | 27 | 0 | 0 |
| Sep 24 | 211 | 30 | 0 | 0 |
| Oct 24 | 317 | 47 | 0 | 0 |
| Nov 24 | 205 | 35 | 0 | 0 |
| Dec 24 | 131 | 34 | 0 | 0 |
| Jan 25 | 225 | 32 | 1 | 0 |
| Feb 25 | 223 | 22 | 0 | 0 |
| Mar 25 | 194 | 30 | 0 | 0 |
| Apr 25 | 180 | 26 | 0 | 0 |
| May 25 | 241 | 44 | 0 | 0 |
| Jun 25 | 238 | 28 | 0 | 0 |
| Jul 25 | 257 | 37 | 0 | 0 |
| Aug 25 | 428 | 30 | 0 | 0 |
| Sep 25 | 251 | 48 | 0 | 0 |
| Oct 25 | 324 | 41 | 0 | 0 |
| Nov 25 | 255 | 28 | 0 | 0 |
| Dec 25 | 200 | 32 | 0 | 0 |
| Jan 26 | 223 | 35 | 0 | 0 |
| Feb 26 | 184 | 30 | 0 | 0 |
| Mar 26 | 378 | 35 | 0 | 0 |
| Apr 26 | 362 | 41 | 0 | 0 |
| May 26 | 176 | 49 | 0 | 0 |
| Jun 26 | 252 | 38 | 0 | 0 |
| Jul 26 | 236 | 39 | 0 | 0 |
| Aug 26 | 210 | 40 | 0 | 1 |
| Sep 26 | 165 | 27 | 0 | 0 |
| Oct 26 | 181 | 28 | 0 | 0 |
| Nov 26 | 0 | 0 | 0 | 0 |
Manufacturers named most often
Last 12 months. Bigger sellers get more reports. This is not a ranking of safety.
- Medtronic2,599
Device problems as coded
Last 12 months. FDA's terms. A report can carry several.
- Premature Discharge of Battery872
- Reset Problem795
- Data Problem293
- Inappropriate or Unexpected Reset268
- Output Problem195
- Adverse Event Without Identified Device or Use Problem183
- Signal Artifact/Noise163
- Under-Sensing159
- Over-Sensing122
- Communication or Transmission Problem120
Patient problems as coded
Last 12 months. FDA's terms. A report can carry several.
- No Clinical Signs, Symptoms or Conditions2,992
- Unspecified Infection75
- Discomfort55
- Wound Dehiscence50
- Erosion40
- Pain30
- Implant Pain16
- Erythema14
- Medical device site infection11
- Hypersensitivity/Allergic reaction8
Recent recalls
From FDA's recall database. FDA lists each recalled product separately, so one recall can appear several times. A recall is often a correction or a labeling change, not a removal from the market.
- LUX-Dx, LUX-Dx II, LUX-Dx II+ Insertable Cardiac Monitor System, SERVER SW LAT CLARITY DS US, Model Number 7260, All Versions (Current 7.8)Open, Classified
Z-3081-2026 · Started Aug 6, 2026 · Posted by FDA Sep 2, 2026
Reason given: There is potential for a delay in AF Burden Alert notification affecting the server software which supports the Insertable Cardiac Monitors (ICMs). Delayed notification of an AF Burden Alert may delay clinical evaluation or therapeutic intervention of an atrial arrhythmia.
Cause as FDA categorized it: Software design
- LUX-Dx, LUX-Dx II, LUX-Dx II+ Insertable Cardiac Monitor System, SERVER SW LAT CLARITY DS EU, Model Number 7246, All Versions (Current 7.7)Open, Classified
Z-3082-2026 · Started Aug 6, 2026 · Posted by FDA Sep 2, 2026
Reason given: There is potential for a delay in AF Burden Alert notification affecting the server software which supports the Insertable Cardiac Monitors (ICMs). Delayed notification of an AF Burden Alert may delay clinical evaluation or therapeutic intervention of an atrial arrhythmia.
Cause as FDA categorized it: Software design
- LUX-Dx, LUX-Dx II, LUX-Dx II+ Insertable Cardiac Monitor System, SERVER SW LAT CLARITY DS ANZ, Model Number 7248, All Versions (Current 7.7)Open, Classified
Z-3083-2026 · Started Aug 6, 2026 · Posted by FDA Sep 2, 2026
Reason given: There is potential for a delay in AF Burden Alert notification affecting the server software which supports the Insertable Cardiac Monitors (ICMs). Delayed notification of an AF Burden Alert may delay clinical evaluation or therapeutic intervention of an atrial arrhythmia.
Cause as FDA categorized it: Software design
- LUX-DX II, Arrythmia detector and alarm, Model M302, with SERVER SW LATITUDE DRAGON US, Model 6460, Version 7.5Open, Classified
Z-2048-2026 · Started Mar 30, 2026 · Posted by FDA May 1, 2026
Reason given: For some patients upgraded from a LUX-Dx M301 device to a new Model M302 or M312, the new ICM device is not collecting PVC Burden data (both M302/M312) or monitoring for Bradyarrhythmia and Pause (M312 only). In addition, for these devices that are not being monitored, the LATITUDE Clarity programming screens have...
Cause as FDA categorized it: Under Investigation by firm
Z-2049-2026 · Started Mar 30, 2026 · Posted by FDA May 1, 2026
Reason given: For some patients upgraded from a LUX-Dx M301 device to a new Model M302 or M312, the new ICM device is not collecting PVC Burden data (both M302/M312) or monitoring for Bradyarrhythmia and Pause (M312 only). In addition, for these devices that are not being monitored, the LATITUDE Clarity programming screens have...
Cause as FDA categorized it: Under Investigation by firm
Z-0226-2025 · Started Sep 6, 2024 · Posted by FDA Oct 25, 2024
Reason given: Patients using the Model 2939 myLUX Patient Application on their Apple mobile device (e.g., iPhone) may not be transmitting data from their Insertable Cardiac Monitor to the LATITUDE Clarity website.
Cause as FDA categorized it: Under Investigation by firm
- ICM LNQ22 LINQ II, Model LNQ22; Insertable Cardiac MonitorOpen, Classified
Z-0421-2024 · Started Nov 3, 2023 · Posted by FDA Dec 1, 2023
Reason given: It may create the potential for amplified noise and/or overall signal reduction of the ICM, which may interfere with intended recordings of heart rhythms. This noise pattern is different from occasional noise due to device position/migration, patient activity, or external electromagnetic interference.
Cause as FDA categorized it: Process change control
- LINQ II Insertable Cardiac MonitorTerminated
Medtronic Inc., Cardiac Rhythm and Heart Failure (CRHF)
Z-0782-2022 · Started Jan 18, 2022
Reason given: Devices may lose functionality due to susceptibility to moisture ingress.
Cause as FDA categorized it: Nonconforming Material/Component
Showing the 8 newest of 10 recall records in FDA's data.
For information only. Nothing on this page is investment, legal, tax or medical advice, and nothing here is an offer to sell or a solicitation of an offer to buy any security. The data comes from public government sources, which can be incomplete, delayed or wrong. Check the original record before relying on it.