The Reveal LINQ ICM is an insertable automatically-activated and patient-activated monitoring system that records subcutaneous ECG and is indicated in the following cases: · patients with clinical syndromes or situations at increased risk of cardiac arrhythmias · patients who experience transient symptoms such as dizziness, palpitation, syncope, and chest pain that may suggest a cardiac arrhythmia The device has not been tested specifically for pediatric use.
Device Story
Leadless insertable cardiac monitor (ICM) implanted subcutaneously in chest; continuously monitors subcutaneous ECG via two integrated electrodes. Device automatically detects and records arrhythmias (AT/AF, bradyarrhythmia, pause, ventricular tachyarrhythmia) and stores ECG/Marker Channel data during auto-detected or patient-activated events. Used in clinical settings or home environments; operated by patient (activation) and physician (data review). Output allows clinicians to diagnose cardiac rhythm abnormalities and guide clinical decision-making. Modifications include updated Recommended Replacement Time (RRT) algorithm and power supply management (K-factor) to improve efficiency.
Clinical Evidence
Bench testing only. No clinical data presented. Evidence includes firmware regression verification (870 tests passed), design verification, and system design validation confirming that modifications meet design inputs and risk control measures.
Technological Characteristics
Leadless subcutaneous ICM; two electrodes for ECG sensing. Powered by internal battery with optimized power management. Software/firmware-based arrhythmia detection. Complies with ISO 14971:2012 (risk management) and IEC 62304:2008 (software life-cycle).
Indications for Use
Indicated for patients at increased risk of cardiac arrhythmias or experiencing transient symptoms (dizziness, palpitation, syncope, chest pain) suggestive of arrhythmia. Not tested for pediatric use.
Regulatory Classification
Identification
The arrhythmia detector and alarm device monitors an electrocardiogram and is designed to produce a visible or audible signal or alarm when atrial or ventricular arrhythmia, such as premature contraction or ventricular fibrillation, occurs.
Special Controls
*Classification.* Class II (special controls). The guidance document entitled “Class II Special Controls Guidance Document: Arrhythmia Detector and Alarm” will serve as the special control. See § 870.1 for the availability of this guidance document.
{0}------------------------------------------------
Image /page/0/Picture/1 description: The image shows the logo for the Department of Health & Human Services - USA. The logo is a circular seal with the words "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" around the perimeter. Inside the circle is an image of an eagle with three heads.
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-0002
April 22, 2016
Medtronic, Inc. Eric Kalmes Principal Regulatory Affairs Specialist 8200 Coral Sea Street NE Mounds View, Minnesota 55112
Re: K160689
Trade/Device Name: Reveal LINQ LNQ11 Regulation Number: 21 CFR 870.1025 Regulation Name: Arrhythmia Detector and Alarm (including ST-Segment Measurement and Alarm) Regulatory Class: Class II Product Code: DSI Dated: March 24, 2016 Received: March 25, 2016
Dear Eric Kalmes:
We have reviewed your Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply
{1}------------------------------------------------
with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting of medical devicerelated adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please contact the Division of Industry and Consumer Education at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm. Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to
http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm for the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
You may obtain other general information on your responsibilities under the Act from the Division of Industry and Consumer Education at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm.
Sincerely yours,
Mitchell Stein
for Bram D. Zuckerman, M.D. Director Division of Cardiovascular Devices Office of Device Evaluation Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
#### Indications for Use
510(k) Number (if known) K160689
Device Name Reveal LINQTM LNQ11
#### Indications for Use (Describe)
The Reveal LINQ ICM is an insertable automatically-activated monitoring system that records subcutaneous ECG and is indicated in the following cases:
· patients with clinical syndromes or situations at increased risk of cardiac arrhythmias
· patients who experience transient symptoms such as dizziness, palpitation, syncope, and chest pain that may suggest a cardiac arrhythmia
The device has not been tested specifically for pediatric use.
Type of Use (Select one or both, as applicable)
2 Prescription Use (Part 21 CFR 801 Subpart D)
Over-The-Counter Use (21 CFR 801 Subpart C)
#### PLEASE DO NOT WRITE BELOW THIS LINE - CONTINUE ON A SEPARATE PAGE IF NEEDED.
#### FOR FDA USE ONLY
Concurrence of Center for Devices and Radiological Health (CDRH) (Signature)
This section applies only to requirements of the Paperwork Reduction Act of 1995.
#### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff(@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
# 510(k) Summary
| [As required by 21 CFR 807.92] | |
|--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Date Prepared: | March 23, 2016 |
| Submitter: | Medtronic, Inc.<br>Medtronic Cardiac Rhythm Heart Failure<br>8200 Coral Sea Street N.E.<br>Mounds View, MN 55112<br>Establishment Registration Number: 2182208 |
| Contact Person: | Eric Kalmes<br>Principal Regulatory Affairs Specialist<br>Medtronic Cardiac Rhythm Heart Failure<br>Phone: 763.526.2809<br>Fax: 651.367.0603<br>Email: eric.b.kalmes@medtronic.com |
| Alternate Contact: | Ryan Calabrese<br>Director Regulatory Affairs<br>Medtronic Cardiac Rhythm Heart Failure<br>Phone: 763.526.3515<br>Fax: 651.367.0603 |
# General Information
| Trade Name: | Reveal LINQ TM LNQ11 |
|-----------------------|-------------------------------------------------------------------------------|
| Common Name: | Insertable Cardiac Monitor |
| Regulation Number: | CFR 870.1025 |
| Product Code: | DSI |
| Classification: | Class II |
| Classification Panel: | Cardiovascular |
| Special Controls: | Class II Special Controls Guidance Document: Arrhythmia Detector and<br>Alarm |
| Predicate Devices: | Reveal LINQ LNQ11 Insertable Cardiac Monitor (K150614) |
Email: ryan.s.calabrese@medtronic.com
{4}------------------------------------------------
# Device Description
The Reveal LINQ Model LNQ11 Insertable Cardiac Monitors (ICM) is designed to automatically record the occurrence of arrhythmias in a patient. Arrhythmia may be classified as atrial tachyarrhythmia/atrial fibrillation (AT/AF), bradyarrhythmia, pause, or (fast) ventricular tachyarrhythmia. The Reveal LINQ ICM provides storage of ECG and Marker Channel during patient-activated and automatically-detected (auto-activated) events. Auto activation may help to detect abnormal heart rhythms in patients who may not activate/trigger the ICM.
The Reveal LINQ model LNQ11 is a small, leadless device that is typically implanted under the skin, in the chest. Two electrodes on the body of the device continuously monitor the patient's subcutaneous ECG.
### Indications for Use
There are no changes to the Indications for Use. The Indications for Use are provided below:
The Reveal LINQ ICM is an insertable automatically-activated and patient-activated monitoring system that records subcutaneous ECG and is indicated in the following cases:
- · patients with clinical syndromes or situations at increased risk of cardiac arrhythmias
· patients who experience transient symptoms such as dizziness, palpitation, syncope, and chest pain that may suggest a cardiac arrhythmia
The device has not been tested specifically for pediatric use.
### Technological Characteristics
Intended use, design, materials, performance and technological characteristics are substantially equivalent to the predicate devices referenced.
#### Technological Characteristics
When compared to the predicate device (K150614), the modified Reveal LINQ model LNQ11 presented in this submission has the same:
- . Intended use/indications for use
- Operating principle
- Design features
- Device functionality
- Biological safety ●
- Packaging materials ●
- . Shelf life
The modified Reveal LINQ model LNQ11 and the predicate device differ in the following:
- Modify the Recommended Replacement Time (RRT) algorithm ●
{5}------------------------------------------------
- Minor update to the power supply management (K-factor) behavior to improve the power . supply management efficiency.
### Substantial Equivalence and Summary of Studies:
Technological differences between the subject and predicate devices have been evaluated through bench tests to provide evidence of safe and effective use. The modified Reveal LINQ Model LNQ11 Insertable Cardiac Monitor is substantially equivalent to the specified predicate device based on comparisons of the device functionality, technological characteristics, and indications for use.
| Standard<br>Number | Standard<br>Organization | Standard Title |
|--------------------|--------------------------|------------------------------------------------------------------------------------------------------------------------------------|
| 14971:2012 | ISO | Medical Devices - Application of Risk Management to Medical<br>Devices |
| 62304:2008 | IEC EN | Medical device software - Software life-cycle processes |
| Guidance | FDA | Class II Special Controls Guidance Document: Arrhythmia<br>Detector and Alarm Document Issued on October 28, 2003 |
| Guidance | FDA | Guidance for the Content of Premarket Submissions for Software<br>Contained in Medical Devices Document issued on: May 11,<br>2005 |
The following standards and guidance were used for development and testing of this change:
## Summary of Testing
Firmware regression testing, design verification and system design validation testing were performed to demonstrate the Reveal LINQ ICM meet established performance criteria to support equivalency to the referenced predicate device.
### Performance Testing - Bench
- Firmware Regression Verification Testing Verification testing performed for the Reveal . LINQ Firmware with LINQ RRT modification and minor enhancements is complete. All 870 regression tests were executed and passed.
- Design Verification No system or product level requirements were modified by this ● submission. Therefore, design verification was completed by verifying similarity to a previous design. The design outputs meet the design inputs based on: system and finished device similarity to the previous design(s), verification of the previous design(s), verification of no unintended changes to the current design(s), and verification of no unintended RAMware/firmware interactions within the finished device. All acceptance criteria have been met. The Reveal LINQ System and Reveal LINQ Insertable Cardiac Monitor are considered verified against their design input requirements.
- System Design Validation - System Design Validation Plan, activities fell into two general categories: analyses and test execution. Test protocols were developed to provide coverage of
{6}------------------------------------------------
the aspects of the system being validated against the design input requirements and risk control measures being validated.
# Conclusion
The results of the above testing met the specified acceptance criteria and did not raise new safety or performance issues. Therefore, the modifications made to the Reveal LINQ Model LNQ11 Insertable Cardiac Monitor described in this submission result in a device that is substantially equivalent to the predicate.
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.