LINQ II Insertable Cardiac Monitor, LINQ Mobile Manager, Device Command Library, Instrument Command Library, LINQ Tool Kit
Applicant
Medtronic, Inc.
Product Code
MXD · Cardiovascular
Decision Date
Jul 3, 2020
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.1025
Device Class
Class 2
Indications for Use
The LINQ II 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
LINQ II ICM is an insertable, subcutaneous cardiac monitor. It continuously records subcutaneous ECG and physiological parameters. The device automatically detects arrhythmias (tachyarrhythmia, bradyarrhythmia, pause, atrial tachyarrhythmia, atrial fibrillation) and allows patient-initiated symptom recording via mobile app (MyCareLink Heart) or patient assistant. It uses Bluetooth Low Energy (BLE) for communication. Physicians use the CareLink Network to review recorded data, which aids in diagnosing cardiac arrhythmias. The device benefits patients by providing long-term, continuous monitoring for transient symptoms, facilitating clinical decision-making for arrhythmia management.
Clinical Evidence
No clinical data. Substantial equivalence supported by bench testing, including firmware design verification, regression testing, mechanical/electrical/EMC/safety testing, sterilization, biocompatibility, MRI compatibility, sensing/detection performance validation, and human factors testing.
Technological Characteristics
Hybrid sapphire substrate with integrated feedthroughs; titanium foil antenna/electrodes laser-bonded to sapphire; titanium nitride coated sensing electrodes; lithium anode/SVO/CFx battery. Form factor: small implantable. Connectivity: BLE. Materials: Sapphire, Titanium, Parylene, Titanium Nitride. Standards: ISO 14971, IEC 62304, AAMI EC57, ISO 10993-1, ISO 14708-1.
Indications for Use
Indicated for patients with clinical syndromes/situations at increased risk of cardiac arrhythmias or patients experiencing transient symptoms (dizziness, palpitation, syncope, chest pain) suggesting cardiac 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/0 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). The logo consists of two parts: a symbol on the left and the FDA name on the right. The symbol on the left is a stylized image of a human figure, while the FDA name on the right is written in blue letters. The words "U.S. FOOD & DRUG ADMINISTRATION" are written in a clear, sans-serif font.
July 3, 2020
Medtronic, Inc. Eric Kalmes Sr. Principal Regulatory Affairs Specialist 8200 Coral Sea Street NE Mounds View, Minnesota 55112
#### Re: K200795
Trade/Device Name: LINQ II Insertable Cardiac Monitor, LINQ Mobile Manager, Device Command Library, Instrument Command Library, LINQ Tool Kit Regulation Number: 21 CFR 870.1025 Regulation Name: Arrhythmia Detector And Alarm (Including ST-Segment Measurement And Alarm) Regulatory Class: Class II Product Code: MXD, DSI Dated: June 19, 2020 Received: June 22, 2020
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. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database located at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. 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
{1}------------------------------------------------
statutes and regulations administered by other Federal agencies. You must comply 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 device-related adverse events) (21 CFR 803) for devices or postmarketing safety reporting (21 CFR 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reportingcombination-products); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
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 https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medicaldevices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-device-advice-comprehensive-regulatoryassistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
Jennifer Shih Acting Assistant Director Division of Cardiac Electrophysiology, Diagnostics and Monitoring Devices Office of Cardiovascular Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
### Indications for Use
510(k) Number (if known) K200795
Device Name LINQ II Insertable Cardiac Monitor
Indications for Use (Describe)
The LINQ II 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.
| Type of Use (Select one or both, as applicable) | |
|--------------------------------------------------------------------------------|------------------------------------------------------------------------------|
| <div> <span> Prescription Use (Part 21 CFR 801 Subpart D) </span> </div> | <div> <span> Over-The-Counter Use (21 CFR 801 Subpart C) </span> </div> |
CONTINUE ON A SEPARATE PAGE IF NEEDED.
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
| Date Prepared: | March 13, 2019 |
|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 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>Sr. 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>Senior Director Regulatory Affairs<br>Medtronic Cardiac Rhythm Heart Failure<br>Phone: 763.526.3515<br>Fax: 651.367.0603<br>Email: ryan.s.calabrese@medtronic.com |
### General Information
| Trade Name: | LINQ™ II Insertable Cardiac Monitor | | |
|-----------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------|--|--|
| Common Name: | Insertable Cardiac Monitor | | |
| Regulation Number: | CFR 870.1025 | | |
| Product Code: | MXD | | |
| Classification: | Class II | | |
| Classification Panel: | Cardiovascular | | |
| Special Controls: | Class II Special Controls Guidance Document: Arrhythmia Detector and Alarm | | |
| Predicate Device: | Primary Predicate Reveal LINQ Insertable Cardiac Monitor (Model LNQ11) K162855 and additional supporting predicate Reveal XT Model (Model 9529) K071641 | | |
{4}------------------------------------------------
### Device Description
The LINQ II Insertable Cardiac Monitor (ICM) Model LNQ22 is a programmable device that continuously monitors a patient's ECG and other physiological parameters. The device records cardiac information in response to automatically detected arrhythmias and patient-initiated activation or markings. The device is designed to automatically record the occurrence of an episode of arrhythmia in a patient. Note: Arrhythmias are classified as tachyarrhythmia, bradyarrhythmia, pause, atrial tachyarrhythmia, or atrial fibrillation. Patients may also manually record symptoms. In order to manually record symptoms, the patient will also need either the MyCareLink Heart App (patient app on mobile device) or the Patient Assistant Model PA97000. The patient can use the MyCareLink Heart App or the Patient to manually record his or her cardiac rhythm while experiencing or immediately after a symptomatic event. LINQ II ICM and this submission includes the following accessories: LINO Tool Kit Model LNO22TK, Reveal LINQTM Mobile Manager Model MSW002, Device Command Library Model 2692, and Instrument Command Library Model 2691.
### Accessories Subject to this Submission
- The LINQ Tool Kit Model LNQ22TK includes two implant tools: The Incision Tool is used to make a small incision through the patient's skin: and the Insertion Tool is used to insert the device through the incision and into the patient's body at the desired location.
- The Reveal LINQ™ Mobile Manager (LMM) Model MSW002 is the programmer ● designed as a mobile app that communicates with the Reveal LINQ and LINQ II ICM devices via the existing model 24967 telemetry head.
- The 2692 Device Command Library (DCL) software is a component of the Data ● Transformation Services subsystem of the CareLink Network. This software is responsible for understanding command status, implant device state within CareLink, and the initiation of commands for the implanted device.
- The 2691 Instrument Command Library (ICL) software is the logic and data files required for remote programming.
## Indications for Use
Aside from the name of the device, there are no changes as compared to the Reveal LINQ ICM Indications for Use as a result of this submission. The Indications for Use are provided below:
The LINO II 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
The LINO II ICM consists of a hybrid substrate that is made of sapphire. The sapphire provides part of the implantable hermetic enclosure, integrates the feedthroughs directly into the substrate,
{5}------------------------------------------------
and provides a substrate for component attachment/interconnect. The antenna and sense electrodes are titanium foil laser bonded to the outside of the sapphire substrate and connected directly to the embedded feedthroughs. The sense electrodes will be coated with sputtered titanium nitride. The sapphire will be laser bonded to the titanium battery cover, which provides the complete hermetic enclosure. The battery is Lithium anode, silver vanadium oxide/carbon monofluoride cathode with a capacity of 167 mAh.
The LINO II ICM will continue to use the same technology. It is designed to automatically record the occurrence of an arrhythmia in a patient, continuously sense the patient's subcutaneous ECG, and analyze the timing of ventricular events to detect possible episodes of arrhythmia. The LINQ II ICM has a small form factor, and uses Sapphire, Titanium, Parylene, and Titanium Nitride coating on the sensing electrodes as body contacting materials.
When compared to the predicate device, the existing Reveal LINQ ICM (most recently cleared by FDA under K162855), the LINQ II ICM has the same:
- Indications for use
- · Operating principle
- Device functionality
- · Biological safety
When compared to the predicate device, the existing Reveal LINQ ICM (most recently cleared by FDA under K162855), the LINQ II differs as follows:
- · 4.5-year longevity
- · Bluetooth Low Energy (BLE) technology to enable communication with mobile devices via a mobile application.
- · The LINO II ICM includes minor changes to enhance the arrhythmia detection algorithms and diagnostics which include pause detection and PVC detector.
- · The insertion tool is being updated to accommodate the LINQ II device form factor.
- · CareLink Network enhancements to support the LINQ II device remote follow-up. This includes updates to the Instrument Command Library and Device Command Library.
- · Reveal LINO Mobile Manger updates to support LINO II ICM.
### Substantial Equivalence
Technological differences between the subject and predicate devices have been evaluated through bench and animal testing. The LINO II ICM is substantially equivalent to the predicate device, the existing Reveal LINQ ICM (cleared by FDA under K162855) based on comparisons of device functionality, technological characteristics, and indications for use.
### Summary of Testing
Firmware testing, design verification, system verification, and system design validation testing were performed to demonstrate that the subject device, the LINQ II ICM, met established
{6}------------------------------------------------
performance criteria to support equivalency to the referenced predicate device, the existing Reveal LINQ ICM (cleared by FDA under K162855).
- . Firmware design verification: This testing was made up of two parts: verification of the individual design artifacts (firmware units) associated with the development and release of the firmware; and verification of the finished firmware product (implemented design) to confirm that it meets the associated input requirements.
- Firmware regression testing: This testing of unchanged firmware was performed to ● ensure that no unintended side effects were introduced.
- . Verification testing:
- · Mechanical
- · Electrical
- · Electromagnetic compatibility (EMC) and electrical safety
- · Sterilization
- · Biocompatibility
- · MRI Compatibility
- · Sensing and detection performance validation
- · Packaging testing
- Human Factors
- · Security
- System testing: This testing was performed on the subject device (LINO II) and its . accessories which included system verification testing and system validation testing. System design verification ensured that the proposed modifications did not impact the existing system level design inputs. System design validation confirmed through a combination of test and analysis that the stakeholder needs and intended use continued to be met by the subject device.
{7}------------------------------------------------
The following standards and guidance documents were used for development and testing of the LINQ II device:
| Standard<br>Number | Standard<br>Organization | Recognition<br>Number | Standard Title |
|-------------------------------------------------------------|--------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 14971:2012 | ISO | 5-40 | Medical Devices - Application of Risk Management to<br>Medical Devices |
| 62304:2006 | IEC EN | 13-32 | Medical device software - Software life-cycle processes |
| EC57:1998 | AANSI/AAMI | 3-118 | Testing and Reporting Performance Results of Cardiac<br>Rhythm and ST Segment Measurement Algorithms |
| 62366:<br>2007/(R)2013 | AAMI/ANSI/<br>IEC | 5-114 | Medical devices - Application of usability engineering to<br>medical devices |
| 15223-1:2012 | ISO | 5-117 | Medical devices — Symbols to be used with medical<br>device labels, labeling, and information to be supplied -<br>Part 1: General requirements |
| 10993-1:<br>2009/(R)2013 | AAMI/ANSI/<br>ISO | 2-220 | Biological evaluation of medical devices. Evaluation and<br>testing |
| 11135-1:2014 | EN ISO | 14-452 | Medical Devices – validation and routine control of<br>ethylene oxide sterilization |
| 60601-1: 2005<br>(2nd Edition)<br>and 2006 (3rd<br>Edition) | EN | 19-1 | Medical electrical equipment-Part 1: General requirements<br>for basic safety and essential performance |
| 11607-1:2009 | EN ISO | 14-454 | Packaging for terminally sterilized medical devices - Part<br>1: Requirements for materials, sterile barrier systems and<br>packaging systems |
| 14117:2012 | ISO | 3-139 | Active implantable medical devices -- Electromagnetic<br>compatibility -- EMC test protocols for implantable cardiac<br>pacemakers, implantable cardioverter defibrillators and<br>cardiac resynchronization devices. |
| 14708-1:2000 | ISO | 3-156 | Implants for surgery -- Active implantable medical devices<br>-- Part 1: General requirements for safety, marking and for<br>information to be provided by the manufacturer |
| Guidance | FDA | | Class II Special Controls Guidance Document: Arrhythmia Detector and<br>Alarm |
| Guidance | FDA | Guidance for the Content of Premarket Submissions for Software<br>Contained in Medical Devices | |
| Guidance | FDA | Content of Premarket Submissions for Management of Cybersecurity in<br>Medical Devices, 14 June 2013 and revised edition of the pre-market<br>guidance document issued on October 18, 2018 | |
{8}------------------------------------------------
The following standards were used for development and testing of the Reveal LINQ™ Mobile Manager:
| Standard Number | Standard<br>Organization | Recognition<br>Number | Standard Title |
|----------------------|--------------------------|-----------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 14708-1:2014 | ISO | 3-156 | Implants for surgery -- Active implantable<br>medical devices -- Part 1: General requirements<br>for safety, marking and for information to be<br>provided by the manufacturer |
| 14971:2007 | ISO | 5-40 | Medical devices – Application of risk<br>management to medical devices |
| 15223-1:2016 | ISO | 5-117 | Medical devices - Symbols to be used with<br>medical device labels, labelling and information<br>to be supplied - Part 1: General requirements |
| 62304:2006/AMD1:2015 | IEC | 13-79 | Medical device software – Software life cycle<br>processes |
| 62366-1 | IEC | 5-114 | Medical devices - Part 1: Application of usability<br>engineering to medical devices |
The following standards were used for development and testing of the Device Command Library Model 2692:
| Standard Number | Standard Organization | Recognition Number | Standard Title |
|------------------------------|-----------------------|--------------------|--------------------------------------------------------------------------------------------------------------|
| EN ISO 14971: 2012 | ISO | 5-40 | Medical devices – Application of risk<br>management to medical devices |
| EN 60601-1: 2006/<br>A1:2013 | EN | 19-1 | Medical electrical equipment - Part 1: General<br>requirements for basic safety and essential<br>performance |
| EN 62304:2006/<br>A1:2015 | IEC EN | 13-32 | Medical device software. Software life-cycle<br>processes |
{9}------------------------------------------------
The following standards were used for development and testing of the Instrument Command Library, Model 2691:
| Standard Number | Standard Organization | Recognition Number | Standard Title |
|-----------------------------|-----------------------|--------------------|--------------------------------------------------------------------------------------------------------|
| EN ISO 14971:2012 | ISO | 5-40 | Medical devices - Application of risk management to medical devices |
| EN 60601-1:<br>2006/AC:2010 | EN | 19-1 | Medical electrical equipment - Part 1: General requirements for basic safety and essential performance |
| EN 62304:2006/A1:2015 | IEC | 13-32 | Medical device software. Software life-cycle processes |
### Conclusion
The results of the above testing met the specified acceptance criteria and did not raise new safety or performance issues. Therefore, the LINQ II Insertable Cardiac Monitor Model LNQ22 and its accessories, which include: LINQ Tool Kit Model LNQ22TK, Reveal LINQ™M Mobile Manager Model MSW002, Device Command Library Model 2692, and Instrument Command Library Model 2691, 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.