K183195 · Catheter Precision, Inc. · DQK · Jun 14, 2019 · Cardiovascular
Device Facts
Record ID
K183195
Device Name
VIVO
Applicant
Catheter Precision, Inc.
Product Code
DQK · Cardiovascular
Decision Date
Jun 14, 2019
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.1425
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
VIVO is intended for acquisition, analysis, display and storage of cardiac electrophysiological data and maps for analysis by a physician. VIVO is intended to be used as a pre-procedure planning tool for patients with structurally normal hearts undergoing ablation treatment for idiopathic ventricular arrhythmias.
Device Story
VIVO is a noninvasive pre-procedure planning tool for focal ventricular arrhythmias. Inputs include patient-specific CT or MR DICOM images, standard 12-lead ECG recordings, and a 3D photograph of the patient's chest (captured via handheld 3D camera) to record electrode positions. The system segments DICOM images to create a 3D model of the heart and torso; it then merges this model with the 3D photograph to determine the spatial relationship between ECG electrodes and cardiac anatomy. A mathematical algorithm solves the cardiac inverse problem to transform body surface potentials into myocardial potentials. The system outputs a 3D rendering of the heart with color-coded activation maps indicating the earliest activation site. Used in clinical settings by physicians to identify arrhythmia foci prior to ablation procedures. Benefits include improved pre-procedure planning and localization accuracy, potentially streamlining ablation treatment.
Clinical Evidence
Prospective, non-randomized study (N=45) in patients with structurally normal hearts and <10% scar undergoing PVC/VT ablation. Primary endpoint: accuracy of VIVO in identifying PVC/VT foci compared to CARTO localization. Results showed 100% agreement (95% CI: 93.6%, 100%). No adverse events reported.
Technological Characteristics
System includes laptop computer and handheld 3D camera (Kinect). Uses DICOM (CT/MR) for anatomical modeling. Employs mathematical algorithms to solve the cardiac inverse problem, transforming body surface potentials to myocardial potentials. Software-based analysis. No specific material standards cited.
Indications for Use
Indicated for patients with structurally normal hearts undergoing ablation treatment for idiopathic ventricular arrhythmias.
Regulatory Classification
Identification
A programmable diagnostic computer is a device that can be programmed to compute various physiologic or blood flow parameters based on the output from one or more electrodes, transducers, or measuring devices; this device includes any associated commercially supplied programs.
Predicate Devices
Medtronic CardioInsight Cardiac Mapping System (K162440)
Submission Summary (Full Text)
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image shows the logo of the U.S. Food & Drug Administration (FDA). The logo consists of two parts: the Department of Health & Human Services logo on the left and the FDA logo on the right. The FDA logo is in blue and includes the letters "FDA" in a square, followed by the words "U.S. FOOD & DRUG ADMINISTRATION" in a sans-serif font.
June 14, 2019
Catheter Precision, Inc. Karen Bannick Regulatory Affairs Consultant 500 International Drive Suite 333 Mt. Olive, New Jersey 07828
Re: K183195
Trade/Device Name: VIVO Regulation Number: 21 CFR 870.1425 Regulation Name: Programmable Diagnostic Computer Regulatory Class: Class II Product Code: DOK Dated: May 9, 2019 Received: May 15, 2019
Dear Karen Bannick:
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,
Mark Fellman Assistant Director DHT2A: Division of Cardiac Electrophysiology, Diagnostics and Monitoring Devices OHT2: Office of Cardiovascular Devices Office of Product Evaluation and Ouality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
## Indications for Use
510(k) Number (if known) K183195
Device Name VIVO
#### Indications for Use (Describe)
VIVO is intended for acquisition, analysis, display and storage of cardiac electrophysiological data and maps for analysis by a physician.
VIVO is intended to be used as a pre-procedure planning tool for patients with structurally normal hearts undergoing ablation treatment for idiopathic ventricular arrhythmias.
Type of Use (Select one or both, as applicable)
| Prescription Use (Part 21 CFR 801 Subpart D) | <span style="font-size: 20px;">☑</span> |
|----------------------------------------------|-----------------------------------------|
| Over-The-Counter Use (21 CFR 801 Subpart C) | ☐ |
#### 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}------------------------------------------------
Image /page/3/Picture/1 description: The image shows the logo for Catheter Precision. The logo consists of a blue graphic on the left and the words "Catheter Precision" on the right. The graphic is made up of three curved lines that are stacked on top of each other. The words "Catheter Precision" are written in a sans-serif font.
| Applicant's Name | Catheter Precision, Inc. (Owner/Operator)<br>500 International Drive<br>Suite 333<br>Mt. Olive, NJ 07828<br>Telephone: (973) 691-2000<br>Establishment Registration No: 3010728615 |
|-----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Primary Contact: | Mr. Steve Adler<br>Chief Executive Officer<br>Telephone: (973) 691-2000<br>Email: steve.adler@catheterprecision.com |
| Alternate Contact: | Ms. Karen Bannick<br>Regulatory Affairs Consultant<br>Bannick Consulting, LLC<br>Telephone: (320) 630-5171<br>Email: Karen@bannickconsulting.com |
| Trade Name: | VIVO™ |
| Common Name: | Electrophysiological cardiac mapping system |
| Classification Name: | Programmable diagnostic computer |
| Date Revised: | June 13, 2019 |
| Classification/Panel: | Class II, Cardiovascular |
| Product Code: | DQK |
{4}------------------------------------------------
### Regulation Number: 21 CFR 870.1425
Predicate Device: Medtronic CardioInsight® Cardiac Mapping System (K162440)
#### Device Description:
The VIVO system is a noninvasive pre-procedure planning tool that provides a 3D mapping of the heart to aid in the identification of the general location of the origin of focal ventricular arrhythmias prior to electrophysiology procedures. VIVO requires acquisition of MRI or CT images and standard ECG recordings and lead (electrode) placement. Electrocardiographic potentials are measured from the torso using standard 12 lead electrocardiogram (ECG) sensors placed on the surface of the body. A DICOM image (CT or MR scan) of the thorax and heart is acquired and then segmented to provide a detailed, three-dimensional (3D) anatomy of the endocardial and epicardial surface of the heart. A 3D photograph of the patient's chest with the precise ECG lead positions used to acquire the 12 lead ECG is merged with the torso and heart model to determine the spatial relationship between the electrodes and the heart. From these data, the system uses a mathematical algorithm to use the geometrical information to transform the measured body surface potentials into myocardial potentials via solving the cardiac inverse problem. The VIVO system uses an off the shelf laptop computer and a handheld 3D camera. The VIVO software creates, displays, and stores a cardiac model that displays the site of earliest activation of ventricular arrhythmias.
To develop the cardiac model, VIVO requires the following inputs:
- · MR or CT scan images in the DICOM file format are imported and combined with preloaded reference models in the VIVO software
- · Standard 12-lead ECG recordings acquired during the arrhythmia are imported to VIVO software
- A 3D photograph of the placement of the ECG leads is created using the VIVO 3D camera
{5}------------------------------------------------
VIVO software is comprised of two software applications, VIVO Anatomy and VIVO Analysis.
VIVO Anatomy merges the imported cardiac MR/CT image data with a model to create a heart and torso model representative of a patient's specific anatomy. The MR/CT image data must be imported via a DVD containing the images in DICOM format (Note: VIVO does not have a web interface). The DICOM image is then overlayed on top of one of a number of preloaded anatomical models to fine tune the preloaded model. The model that best matches the patient's anatomical profile is chosen. Specific cardiac structures and tissues are identified by the User within the images to better match the patient anatomy. An outline of the chambers and tissue walls is automatically created by VIVO which is then finetuned by the User for a precise match to the patient's anatomy.
VIVO Analysis combines the heart and torso model generated from VIVO Anatomy with ECG data, and a 3D photograph of the ECG lead placement to identify the location of the arrhythmia foci. After ECG leads are placed on the patient, a 3D photograph of the patient's chest is captured to accurately record lead locations. Arrhythmic ECG signals are recorded from these electrodes and imported into the VIVO software. This data is combined and a mathematical algorithm is used create a 3D rendering of the patient's heart with superimposed color coding to indicate the area of earliest activation.
{6}------------------------------------------------
Model Number of VIVO System: 9001.
### Comparison of Technical Characteristics with Predicate Device
This submission is seeking the clearance of the VIVO system which, like the predicate device, provides a 3D mapping of the heart to aid in the identification of the general location of the origin of focal cardiac arrhythmias prior to electrophysiology procedures.
The predicate device and the VIVO system have the same intended use, fundamental technology, principal of operation and performance. Both VIVO and the predicate require a DICOM image and location data of the electrodes to create a patient specific model.
VIVO users review and adjust a merged 3D image of the 12 lead ECG electrode locations and the torso. Users of the predicate add and delete electrodes after the algorithm merges ECG location with the torso using a segmentation process.
Where there are technological differences, they do not affect the safety and effectiveness of the device when used as labeled. Table 1 provides a comparison of the technological characteristics for the VIVO system against the predicate device.
{7}------------------------------------------------
| Characteristic | VIVO™<br>Subject Device | Medtronic<br>CardioInsight™<br>K162440 | Rationale for Difference<br>(if applicable) | |
|--------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Product Code | DQK | DQK | Same | |
| Regulation | 21 CFR 870.1425 | 21 CFR 870.1425 | Same | |
| Intended Use | For individuals undergoing<br>an EP study for focal<br>ventricular arrhythmias. | For individuals undergoing<br>an EP study. | VIVO software has not<br>been validated for atrial<br>use. | |
| Indications for Use | VIVO is intended for<br>acquisition, analysis, display<br>and storage of cardiac<br>electrophysiological data<br>and maps for analysis by a<br>physician.<br><br>VIVO is intended to be used<br>as a pre-procedure planning<br>tool for patients with<br>structurally normal hearts<br>undergoing ablation<br>treatment for idiopathic<br>ventricular arrhythmias. | The Medtronic<br>CardioInsight Mapping<br>System is intended for<br>acquisition, analysis,<br>display and storage of<br>cardiac<br>electrophysiological data<br>and maps for analysis by a<br>physician. | | |
| System | Monitor, Core Processor,<br>Keyboard, and Mouse (all<br>part of the laptop<br>computer), 3D Camera<br>(Kinect™). | Cart, Monitor, Core<br>Processor, Keyboard,<br>Mouse, Isolation<br>Transformer, Cabling,<br>Sensor Array, Second<br>Monitor connection. | | |
| DICOM Compliance | Yes | Yes | Same | |
| Image Scan<br>Modalities Accepted | CT, MR | CT | | |
| Principles of<br>Operation | Electrocardiographic<br>potentials are measured<br>from standard 12-lead ECG.<br>VIVO establishes patient<br>torso geometry via<br>segmented DICOM images<br>and ECG electrode<br>placement via a 3D<br>photograph. From these<br>data, the system uses<br>mathematical algorithms to<br>use the geometrical<br>information to transform the<br>measured body surface<br>signals into epicardial signals<br>via solving the cardiac<br>inverse problem. | Electrocardiographic<br>potentials are measured<br>from the torso sensors on<br>the surface of the body. A CT<br>scan is segmented to obtain<br>the 3- dimensional location<br>of each sensor and the<br>detailed anatomy of the<br>epicardial surface of the<br>heart. From these data, the<br>system uses mathematical<br>algorithms to use the<br>geometrical information to<br>transform the measured<br>body surface signals into<br>epicardial signals via solving<br>the cardiac inverse problem. | | |
| Functional Overview | Basic Steps to Mapping:<br>1. MR/CT images are<br>imported and used to<br>build 3D model of the<br>patient's heart and<br>torso<br>2. Overlay ECG<br>location via 3D<br>camera<br>3. Align torso/heart model<br>4. Load ECG Data<br>5. Analyze | Basic Steps to Mapping:<br>1. CT images are<br>imported and used<br>to build 3D model of<br>the patient's heart<br>2. Capture 3D<br>geometry of<br>patient's torso<br>(from vest)<br>3. Overlay ECG<br>location during CT<br>image acquisition | The method of generating<br>the map does not impact<br>the final results. | |
| | | | 4. Align torso/heart<br>model | |
| | | | 5. Load ECG data | |
| | | | 6. Analyze | |
| | | | 7. Produce map | |
| ECG Acquisition | | Standard 12-lead surface<br>ECG output imported into<br>VIVO device | Proprietary vest with 252<br>electrodes for surface ECG<br>and recorded through<br>proprietary ECG<br>acquisition<br>hardware/firmware | VIVO uses a standard 12-<br>lead ECG and standard<br>lead placement. VIVO<br>captures the lead<br>locations relative<br>to the patient's torso<br>geometry using the Kinect |
| ECG Electrode<br>Identification/<br>Localization | | Standard 12 lead ECG<br>electrode locations acquired<br>with 3D imaging camera.<br><br>Algorithm merges the 3D<br>image of the 12 lead ECG<br>electrode locations with<br>torso. User manually<br>adjusts the electrode<br>position to the 3D image<br>for accuracy. | Custom 252 electrode<br>images acquired during CT<br>imaging.<br><br>Algorithm merges ECG<br>location with torso with a<br>segmentation process. User<br>manually adds and deletes<br>electrodes after merge. | 3D camera to obtain a 3D<br>photograph. The<br>predicate, CardioInsight<br>utilizes a 252 electrode<br>sensor-array vest to gather<br>the ECG and determine<br>the patient's torso<br>geometry. |
| Cardiac Maps<br>Provided | | Color coded map of earliest<br>activation point and<br>propagation of cardiac beat | Activation map, directional<br>activation map, phase map,<br>potential map, voltage<br>map, slew rate map,<br>propagation map | VIVO's color coded<br>activation map is provided<br>for illustrative purposes<br>only during pre-procedure<br>mapping. |
# Table 1: Technological Characteristics Comparison
{8}------------------------------------------------
{9}------------------------------------------------
K183195
{10}------------------------------------------------
## Indications for Use:
VIVO is intended for acquisition, analysis, display and storage of cardiac electrophysiological data and maps for analysis by a physician.
VIVO is intended to be used as a pre-procedure planning tool for patients with structurally normal hearts undergoing ablation treatment for idiopathic ventricular arrhythmias.
### Performance Data
Performance testing was completed on the VIVO system which verified that the device complies with the safety and specifications and performs as designed. VIVO is suitable for its intended use. Performance Testing included hardware testing, software verification and integration testing performed in compliance with FDA's Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices" and AAMI / ANSI / IEC 62304:2006, Medical Device Software -Software Life Cycle Processes, clinical testing, system verification and validation testing for functionality and performance in a simulated environment.
## Clinical Study
A prospective, non-randomized study ("VIVO Accuracy Study") was completed at 6 US centers. This clinical evaluation was developed primarily to assess VIVO's ability to accurately determine the anatomical location of a particular ventricular origin. The VIVO Accuracy Study enrolled 51 patients and analyzed data from 45 patients presenting for PVC or VT ablation with structurally normal hearts and less than 10% scar.
Approximately 47% of subjects were male, and the average age was 56.4 years. Of the 45 subjects, 44 underwent an ablation procedure for PVCs and 1 underwent an ablation procedure for ventricular tachycardia (determined day of procedure). There was no subgroup analysis conducted.
Of the 45 subjects, 20% (N=9) had previous ablations and no subjects
{11}------------------------------------------------
had a previous myocardial infarction (MI). Other arrhythmias were noted at baseline in 53.33% (24), and 15.56% (N=7) reported having no symptoms associated with their PVC or VT. The most common symptom was palpitations which was reported in 57.78% (N=26) of subjects.
The study results demonstrated acceptable clinical accuracy performance of VIVO. There were no adverse events. The primary endpoint assessed the accuracy of VIVO to properly identify a PVC or VT foci in the right, left, or septal region of the heart. It was determined that the VIVO localization of the PVC/VT foci agreed (was a match) with the CARTO localization in 45 of the 45 subjects. Thus, the primary endpoint had an accuracy rate of 100% (95% Cl: 93.6%, 100%), which met the pre-specified performance goal.
#### Conclusion
The data presented in this submission demonstrate that the VIVO system is substantially equivalent to the predicate device identified in intended use, device design, fundamental technology and performance.
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.