Reported Reactions

Devices › Detector and alarm, arrhythmia

Device brand name · Detector and alarm arrhythmia

Reveal LINQ: medical device reports filed with FDA

19,184 reports name it, 2014–2026. Manufacturer given most often on reports: Medtronic Europe Sarl. Product code DSI.

19,184
device reports naming the brand
0.1% of all MAUDE reports · about 1,546 a year
264
reports, 12 months to August 2026
327 in the 12 months before
93.6%
classified as malfunction
90.5% across the product code
0%
classified as death, as reported
6 reports · not verified by FDA

FDA's MAUDE database holds 19,184 reports that name the brand "Reveal LINQ" (detector and alarm arrhythmia), received between February 2014 and August 2026; the manufacturer given most often on reports is Medtronic Europe Sarl. Spellings of one product vary from report to report.

264 reports arrived in the 12 months to August 2026, down 19% from 327 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 (93.6%) and injury (6.3%); across all detector and alarm, arrhythmia reports (product code DSI) death is recorded in 1.5% and malfunction in 90.5%. Event type is the reporter's classification of the report, not a verified outcome.

The device problems coded most often are under-sensing (36.8%), over-sensing (23.9%) and premature discharge of battery (17.3%). The patient problems coded most often are pain, erosion and discomfort. 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

0112223Sep 2021: 223Oct 2021: 76Nov 2021: 76Dec 2021: 1022022Jan 2022: 75Feb 2022: 74Mar 2022: 55Apr 2022: 62May 2022: 61Jun 2022: 58Jul 2022: 55Aug 2022: 59Sep 2022: 52Oct 2022: 87Nov 2022: 63Dec 2022: 762023Jan 2023: 58Feb 2023: 70Mar 2023: 70Apr 2023: 43May 2023: 84Jun 2023: 54Jul 2023: 67Aug 2023: 66Sep 2023: 44Oct 2023: 51Nov 2023: 48Dec 2023: 322024Jan 2024: 48Feb 2024: 51Mar 2024: 101Apr 2024: 39May 2024: 53Jun 2024: 30Jul 2024: 45Aug 2024: 18Sep 2024: 38Oct 2024: 30Nov 2024: 30Dec 2024: 162025Jan 2025: 28Feb 2025: 24Mar 2025: 32Apr 2025: 29May 2025: 24Jun 2025: 31Jul 2025: 23Aug 2025: 22Sep 2025: 22Oct 2025: 23Nov 2025: 40Dec 2025: 212026Jan 2026: 18Feb 2026: 16Mar 2026: 26Apr 2026: 21May 2026: 14Jun 2026: 31Jul 2026: 16Aug 2026: 16

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

01,7293,4572014: 32320142015: 7432016: 3,45720162017: 2,6002018: 2,80620182019: 2,7172020: 2,30320202021: 1,7952022: 77720222023: 6872024: 49920242025: 3192026: 1582026

Event type and report source

Event type, as classified on the report

Death0%6
Injury6.3%1,218
Malfunction93.6%17,960
Other0%0
Not given0%0

Who filed the report

Manufacturer report100%19,176
Voluntary report0%6
User facility report0%0
Distributor report0%0
Not given0%2

Grey bar: all 33,398 reports carrying product code DSI. Event type is the filer's classification and is not verified by FDA.

Device problems coded

Device problem (FDA code)ReportsShareShare across product code
Under-sensing7,06336.8%23.7%
Over-sensing4,58423.9%15.6%
Premature discharge of battery3,32317.3%10.2%
Signal artifact/noise1,5668.2%5.6%
Device sensing problem1,4337.5%4.8%
Migration or expulsion of device1,2306.4%3.9%
Communication or transmission problemthe device could not communicate or transmit7233.8%3.3%
Unable to obtain readings6813.5%2.2%
Reset problem6503.4%2.1%
Failure to interrogate4602.4%2.1%
Invalid sensing4602.4%2%
Electromagnetic interference4182.2%1.3%
Battery problema problem with the battery3171.7%1.2%
Decreased sensitivity3171.7%1%
Inappropriate or unexpected reset1610.8%0.6%
Incorrect measurementthe device measured wrongly1220.6%0.6%
Positioning problem570.3%0.2%
False positive result560.3%0.2%
Nonstandard device460.2%0.4%
Data problem440.2%0.5%

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)ReportsShare
Painpain, site not specified3141.6%
Erosion2631.4%
Discomfortdiscomfort1030.5%
Impaired healingslow healing680.4%
Erythemaskin redness510.3%
Purulent discharge260.1%
No patient involvement240.1%
Hypersensitivity/allergic reaction230.1%
Swellingswelling230.1%
Twiddlers syndrome210.1%
Wound dehiscencea wound reopened210.1%
Chest painchest pain200.1%
Burning sensationa burning feeling150.1%
Complaint, ill-defined150.1%
Skin irritationirritated skin150.1%

Patient problem codes are present mainly in reports filed since 2019 and are often blank.

In context

MeasureReveal LINQProduct code DSIAll MAUDE reports
Reports19,18433,39826,136,888
Share of that pool—57.4%0.1%
Classified as death, per 1,000 reports0159
Classified as injury6.3%7.8%36.2%
Classified as malfunction93.6%90.5%62.3%
Filed by the manufacturer100%99.3%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 DSI

BrandReportsLatest 12 monthsClassified as death
MX40 1.4 GHz Smart Hopping5,13561.3%
Reveal Xt2,03700.1%
Mx40 2 4 Ghz Smart Hopping78501.5%
Reveal Dx73000.4%
Acuity Central Monitoring71000%
Mp70 Intellivue Patient Monitor682015.4%
IntelliVue Multi Measurement Server X21,9241351.7%
Intellivue Mx40 802 11a/B/G32903%
Spacelabs Ultraview Sl Command Module20048.5%
IntelliVue MX800 patient monitor5025410.6%
Patient Connector207830%
IntelliVue MX40 2.4GHz192566.8%
Passport 2 Monitor46900.2%
IntelliVue MP52617310.7%
Zio AT711903.5%

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 Reveal LINQ reports

How many FDA reports name Reveal LINQ?

19,184 medical device reports in the openFDA MAUDE release of 28 Sep 2026, covering reports received through August 2026; 264 in the latest 12 months.

What kinds of events are reported?

malfunction (93.6%) and injury (6.3%). "Event type" is how the report was classified when filed: death, injury, malfunction or other.

What device problems are coded?

under-sensing (36.8%), over-sensing (23.9%), premature discharge of battery (17.3%), signal artifact/noise (8.2%) and device sensing problem (7.5%). These are FDA's device problem codes as entered on the report.

Who files these reports?

manufacturer reports (100%) and voluntary reports (0%). Manufacturers and user facilities are required to report; voluntary reports come from health professionals and the public.

Do these reports show that Reveal LINQ 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.