Medtronic LINQ II Model LNQ22 Cardiac Monitor May Fail to Detect Critical Episodes
Medtronic recalls LINQ II Model LNQ22 cardiac monitors that may fail to detect critical heart episodes after a reset. Owners should contact Medtronic for guidance.
Use caution until it’s fixed
Device fail to detect Brady episodes, Pause (Asystole) episodes and PVC's after a ride-through POR reset.
Contact the company
What happened, in plain English
Medtronic is recalling LINQ II Model LNQ22 insertable cardiac monitors that may fail to detect critical heart episodes after a reset. This could lead to missed medical events and potential harm. Read more at govinfonow.com/recall/62542-medtronic-linq-ii-model-lnq22-cardiac-monitor-may-fail-to.
Source Summary by GovInfoNow · govinfonow.com/recall/62542-medtronic-linq-ii-model-lnq22-cardiac-monitor-may-fail-to · Updated August 19, 2026 · FDA enforcement record: FDA #Z-2076-2021
Cite this page
“Medtronic LINQ II Model LNQ22 Cardiac Monitor May Fail to Detect Critical Episodes.” GovInfoNow, updated August 19, 2026. https://govinfonow.com/recall/62542-medtronic-linq-ii-model-lnq22-cardiac-monitor-may-fail-to. Based on FDA recall #Z-2076-2021 (https://api.fda.gov/device/enforcement.json?search=recall_number:%22Z-2076-2021%22&limit=1).
Why it’s dangerous
The device may fail to detect critical heart episodes like bradycardia, asystole, or premature ventricular contractions after a reset. This could result in missed medical events and potential harm.
Who’s affected
Patients with Medtronic LINQ II Model LNQ22 cardiac monitors are affected. Those with heart conditions requiring continuous monitoring are at higher risk.
How to tell if you have this one
Check for the model number LNQ22 on the device. The product is an insertable cardiac monitor sold as sterile, EO Rx only.
- Brand
Medtronic- Category
Medical device
What to do — step by step
Contact Medtronic
Reach out to Medtronic for specific guidance on the recall and next steps.
Where it went and when
Where it was distributed
Distributed nationwide and abroad; the notice names 42 states.
FDA distribution: “Worldwide distribution - US Nationwide in the states of AK, AL, AL, AR, AZ, CA, CO, CT, DC, FL, GA, IA, ID, IL, IN, KS, KY, LA, MA, MD, MI, MN, MO, MS, NC, NE, NH, NJ, NM, NV, NY, OH, OK, PA, SC, SD, TN, TX, UT, VA, VT, WA, WI, and WY. The…” States read from FDA’s own wording; “not listed” means the notice does not name it.
Named in the notice: Alabama, Alaska, Arizona, Arkansas, California, Colorado, Connecticut, District of Columbia, Florida, Georgia, Idaho, Illinois, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maryland, Massachusetts, Michigan, Minnesota, Mississippi, Missouri, Nebraska, Nevada, New Hampshire, New Jersey, New Mexico, New York, North Carolina, Ohio, Oklahoma, Pennsylvania, South Carolina, South Dakota, Tennessee, Texas, Utah, Vermont, Virginia, Washington, Wisconsin, Wyoming.
Recall timeline
FDA published this recall 2 months after the firm started it.
- Firm started the recall
- FDA classified it Class II
- Published in FDA’s Enforcement Report
Dates from the agency record only; steps without a date are left out.
Similar recalls
Latest medical device recalls
Keep exploring
Where this comes from
The facts (hazard, remedy, dates, manufacturer) are pulled from the official FDA recall record. The plain-language summary and step-by-step checklist are written by GovInfoNow to make the official notice easier to act on — they don’t replace it.
- Official source: FDA Recall #Z-2076-2021 (May 14, 2021) — FDA publishes no per-recall page; this is the official machine-readable enforcement record. Search FDA recalls for Z-2076-2021 to see it in context.
- Plain-language summary written by qwen3:4b on August 19, 2026, from the official record above. Not reviewed by a person — if it conflicts with the FDA notice, the notice is correct. Report an error on this page.
- GovInfoNow is an independent service and is not a government agency. We republish official FDA recall data; we don’t issue, amend or administer recalls.