K160218 · St Jude Medical · DQK · Dec 13, 2016 · Cardiovascular
Device Facts
Record ID
K160218
Device Name
AutoMark Module
Applicant
St Jude Medical
Product Code
DQK · Cardiovascular
Decision Date
Dec 13, 2016
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.1425
Device Class
Class 2
Indications for Use
The EnSite™ Velocity™ Cardiac Mapping System is a suggested Diagnostic tool in patients for whom electrophysiology studies are indicated. When used with EnSite™ Array Catheter, the EnSite™ Velocity™ Cardiac Mapping System is intended to be used in the right atrium of patients with complex arrhythmias that may be difficult to identify using conventional mapping system alone. OR When used with the EnSite™ Velocity™ Surface Electrode Kit, the EnSite™ Velocity™ Cardiac Mapping System is intended to display the position of conventional electrophysiology (EP) catheters in the heart. When used with compatible hardware, the AutoMark Module is intended to automatically catalog and display various parameters associated with RF information on the 3D model in real-time.
Device Story
EnSite Velocity Cardiac Mapping System is a diagnostic tool for electrophysiology (EP) studies. It uses electrode catheters introduced into the heart to record electrical activity. The system consists of a display workstation (DWS) and an amplifier subsystem. The amplifier collects electrical signals from catheters and surface electrodes, converts them to digital format, and transmits them to the DWS via fiber optic/Ethernet. The DWS displays cardiac electrical activity as waveform traces and dynamic 3D isopotential maps of the cardiac chamber. The AutoMark Module is an optional software add-on that automatically catalogs and displays RF ablation parameters on the 3D model in real-time based on user-defined criteria. Used in EP laboratories by physicians to identify arrhythmias and guide ablation procedures. The system aids clinical decision-making by providing real-time visualization of catheter position and cardiac electrical activity, potentially improving the accuracy and efficiency of complex arrhythmia identification and treatment.
Clinical Evidence
No clinical data. Bench testing only. Software verification and validation activities were performed to ensure the AutoMark Module meets performance specifications and does not affect device safety or effectiveness. Risk management and cybersecurity assessments were conducted.
Technological Characteristics
System comprises a display workstation and amplifier subsystem. Connectivity via fiber optic/Ethernet. Software-based mapping and signal processing. AutoMark Module is an optional software feature for real-time RF parameter cataloging and display. Conforms to IEC 62304 for software life cycle processes.
Indications for Use
Indicated for patients undergoing electrophysiology studies. Specifically, the EnSite Array Catheter is indicated for patients with complex arrhythmias in the right atrium. The EnSite Velocity Surface Electrode Kit is indicated for displaying the position of conventional EP catheters in the heart.
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
EnSite™ Velocity™ Cardiac Mapping System (K141050)
EnSite™ Velocity™ Cardiac Mapping System v5.0.1 with AutoMap Module v1.0.1 (K160187)
EnSite Precision™ Cardiac Mapping System v2.0.1 (K160210)
Submission Summary (Full Text)
{0}------------------------------------------------
Image /page/0/Picture/1 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo consists of a stylized depiction of a bird or eagle in flight, composed of three overlapping profiles facing to the right. The words "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" are arranged in a circular fashion around the bird symbol.
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-0002
December 13, 2016
St. Jude Medical Melissa Frank Senior Regulatory Affairs Specialist One St. Jude Medical Drive St. Paul, Minnesota 55117
Re: K160218
Trade/Device Name: EnSite Velocity Cardiac Mapping System v5.0.1 with AutoMark Module v1.0.1 Regulation Number: 21 CFR 870.1425 Regulation Name: Programmable Diagnostic Computer Regulatory Class: Class II Product Code: DQK Dated: September 20, 2016 Received: September 21, 2016
Dear Melissa Frank:
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 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 (reporting of medical devicerelated adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in
{1}------------------------------------------------
the quality systems (OS) 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.
Mule Jellm
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) K160218
Device Name
EnSite™ Velocity™ Cardiac Mapping System v5.0.1 with AutoMark Module v1.0.1
Indications for Use (Describe)
Device Name: EnSite™ Velocity™ Cardiac Mapping System v5.0.1
Indications for Use:
The EnSite™ Velocity™ Cardiac Mapping System is a suggested Diagnostic tool in patients for whom electrophysiology studies are indicated.
When used with EnSite™ Array Catheter, the EnSite™ Velocity™ Cardiac Mapping System is intended to be used in the right atrium of patients with complex arrhythmias that may be difficult to identify using conventional mapping system alone.
OR
When used with the EnSite™ Velocity™ Surface Electrode Kit, the EnSite™ Velocity™ Cardiac Mapping System is intended to display the position of conventional electrophysiology (EP) catheters in the heart
Device Name: AutoMark Module v1.0.1
Indications for Use:
When used with compatible hardware, the AutoMark Module is intended to automatically catalog and display various parameters associated with RF information on the 3D model in real-time.
Type of Use (Select one or both, as applicable)
| <span style="font-size: 10px;"> <svg height="10" width="10"> <rect height="10" style="fill:lightgrey;stroke-width:1;stroke:rgb(0,0,0)" width="10"></rect> <line style="stroke:rgb(0,0,0);stroke-width:2" x1="0" x2="10" y1="0" y2="10"></line> <line style="stroke:rgb(0,0,0);stroke-width:2" x1="0" x2="10" y1="10" y2="0"></line> </svg> </span> Prescription Use (Part 21 CFR 801 Subpart D) |
|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| <span style="font-size: 10px;"> <svg height="10" width="10"> <rect height="10" style="fill:white;stroke-width:1;stroke:rgb(0,0,0)" width="10"></rect> </svg> </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}------------------------------------------------
# 510KSUMMARY
| 510(k) Number | K160218 |
|------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Date Prepared | October 18, 2016 |
| Submitter Information | |
| Manufacturer<br>Name/Address | St. Jude Medical<br>One St. Jude Medical Drive<br>St. Paul, MN 55117 |
| Contact Person | Melissa Frank<br>Sr. Regulatory Affairs Specialist<br>Phone (651) 756-2954<br>Mfrank02@sjm.com |
| Device Information | |
| Trade Name | EnSite™ Velocity™ Cardiac Mapping System v5.0.1 with AutoMark Module v1.0.1 |
| Common Name | Programmable Diagnostic Computer |
| Class | II |
| Classification Name | 870.1425, computer, diagnostic, programmable |
| Product Code | DQK |
| Predicate Device | EnSite™ Velocity™ Cardiac Mapping System (K141050) |
| Secondary Predicates | WorkMate Claris™ System (K151911) |
| Reference Devices | EnSite™ Velocity™ Cardiac Mapping System v5.0.1 with AutoMap Module v1.0.1<br>(K160187)<br>EnSite Precision™ Cardiac Mapping System v2.0.1 (K160210) |
| Base System Device<br>Description: | The EnSite™ Velocity™ Cardiac Mapping System with software version 5.0.1 is a<br>catheter navigation and mapping system capable of displaying the three-dimensional<br>(3D) position of conventional electrophysiology catheters, as well as displaying<br>cardiac electrical activity as waveform traces and as dynamic 3-D isopotential maps<br>of the cardiac chamber. The contoured surfaces of these three-dimensional maps are<br>based on the anatomy of the patient's own cardiac chamber.<br><br>The EnSite Velocity™ Cardiac Mapping System, Model EE3000 consists of a<br>display workstation subsystem (DWS) and an Amplifier subsystem. The EnSite<br>Amplifier collects the data from the patient connections and sends them to the DWS<br>Workstation. The Amplifier connects to the DWS through a fiber optic cable and a<br>media converter to convert the optical signals to digital signals. The EnSite™<br>Velocity™ DWS software displays the cardiac signal data received from the |
{4}------------------------------------------------
Amplifier on the workstation monitors and stores it for later retrieval.
### Display Work Station (DWS) Subsystem
- DWS The DWS houses the system software and connects all the components . together.
- . Monitors - Two monitors display patient information. One monitor is positioned near the workstation and keyboard for system operation, and the physician places the second monitor near the patient table for use.
- . Isolation transformer - All system components on the DWS connect to line power through a medical-grade isolation transformer.
- . Printer - Allows for printing study data
### Amplifier Subsystem
- Amplifier contains electronic circuitry and firmware responsible for collecting . and transmitting the electrical signal data of the patient to the DWS software application via fiber Ethernet. The Amplifier converts these signals to a digital format and sends them to the workstation for processing.
- NavLink Connects surface electrodes and the system reference surface . electrode to the Amplifier.
- ArrayLink Connects the EnSite Array Multi-electrode Diagnostic Catheter to . the Amplifier. It also has a connection for an auxiliary unipolar reference electrode.
- . CathLink - Connects the diagnostic catheters to the Amplifier
- . GenConnect - Connects the ablation catheter and dispersive surface electrodes to the Amplifier.
- . RecordConnect - The RecordConnect allows simultaneous connection for catheters and surface ECG to a recording system and to the Amplifier.
- . ECG cable - The ECG cable connects standard ECG electrodes to the Amplifier.
The EnSite™ Velocity™ Cardiac Mapping System is used as a diagnostic tool in electrophysiology (EP) Studies. An EP study involves the introduction of one or more electrode catheters into the heart to record its electrical activity. These catheters
{5}------------------------------------------------
| | connect to the EnSite™ Velocity™ Cardiac Mapping System through specialized |
|--------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | catheter input modules (CIMs). The EnSite™ Velocity™ Cardiac Mapping System |
| | v5.0.1 is designed for use in the EP laboratory in conjunction with other equipment |
| | as described in the labeling. |
| Expansion Module<br>Device Description: | The AutoMark Module is an optional add-on module to the EnSite™ Velocity™<br>System v5.0.1. The software module allows the user to set criteria for ablation-<br>related parameters and the software automatically displays the lesion marks on the<br>EnSite Velocity model during RF ablation when the user set criteria are met. The<br>color, size, and ranges of the AutoMark are defined by the user. |
| Secondary Predicate<br>Device Descriptions | The following secondary predicate devices are provided to ensure that all features of<br>the proposed AutoMark Module are demonstrated to be substantially equivalent to<br>features of currently cleared medical devices |
| | |
| | WorkMate Claris System |
| | The WorkMate Claris™ System is a fully computerized system for capturing and |
| | measuring physiological data in the clinical electrophysiology (EP) laboratory. It |
| | provides digital signal acquisition and display of those electrical signals on high |
| | resolution monitors. |
| | |
| | The WorkMate Claris System is connected to electrophysiology catheters that are |
| | guided into various locations within the heart, and to surface electrocardiogram |
| | (ECG) cables. Intracardiac and ECG signals are then acquired from electrodes on the |
| | indwelling catheters and ECG leads connected to the amplifier, which amplifies and |
| | conditions the signals before they are received by the WorkMate Claris System |
| | computer for display, measurement and storage. |
| | |
| | During the procedure, cardiac signals are acquired and an automated software |
| | waveform detector (trigger) performs online recognition of cardiac activation on |
| | preselected leads. Temporal interval measurements are computed on a beat-by-beat |
| | basis on multiple channels and dynamically posted on the Real Time display. |
| | Intervals are calculated between waveforms from the same source on a specific |
| | channel (intra-channel measurements) and from multi-source signals across two or |
| | more channels (inter-channel measurements). |
| | |
| | Signals are also presented on a review monitor for measurement and analysis. |
| | Continuous capture of the digitized signals can be invoked, and the user can also |
| | retrieve and display earlier passages of the current study without interruption of the |
| | real-time display. The system can also acquire, display and record data from other |
| | interfaced devices in use during the procedure, such as imaging devices and ablation |
| | generators. |
| Base System | Device Name: EnSite™ Velocity™ Cardiac Mapping System v5.0.1 |
| Indications for Use | The EnSite Velocity Cardiac Mapping System is a suggested Diagnostic tool in |
| | patients for whom electrophysiology studies are indicated. |
| | |
| | When used with EnSite Array Catheter, the EnSite System is intended to be used in |
| | the right atrium of patients with complex arrhythmias that may be difficult to identify |
| | using conventional mapping system alone. |
| | OR |
| | When used with the EnSite Velocity Surface Electrode Kit, the EnSite System is |
| | intended to display the position of conventional electrophysiology (EP) catheters in |
| | the heart |
| Expansion Module | Device Name: AutoMark Module v1.0.1 |
| Indications for Use | When used with compatible hardware, the AutoMark Module is intended to |
| | automatically catalog and display various parameters associated with RF information |
| | on the 3D model in real-time. |
| Submission History | No prior submissions have been made to FDA for the device subject of this |
| | submission. |
| Predicate Comparison | |
| Comparison | The AutoMark module was developed to provide additional functionality to the |
| | predicate devices in allowing the user to set parameters and the software |
| | automatically displays the lesion marks on the EnSite Velocity model during RF |
| | ablation. The proposed AutoMark Module has the same intended use and |
| | fundamental scientific technology as the predicate devices, EnSite™ Velocity™ |
| | Cardiac Mapping System v4.0.2 and WorkMate Claris™ System |
| Non-Clinical Testing<br>Summary | Design verification activities for functional testing were performed with their<br>respective acceptance criteria to ensure that the software modifications do not affect |
| | the safety or effectiveness of the device. All testing performed met the established<br>performance specifications. |
| | <b>Testing</b> |
| | The AutoMark software module was developed and tested in accordance with the<br>following industry guidance documents and standards: |
| | FDA Reviewers and Compliance on Off-the-Shelf Software used in Medical<br>Devices and IEC 62304 OTS classification Guidance for the Content of Premarket Submissions for Software Contained<br>in Medical Devices IEC 62304:2006 Medical Device Software - Software Life Cycle Processes Content of Premarket Submissions for Management of Cybersecurity in<br>Medical Devices: Guidance for Industry and Food and Drug Administration<br>Staff |
| | Software Documentation for a Major Level of Concern software per FDA's Guidance<br>Document "Guidance for the Content of Premarket Submissions for Software<br>Contained in Medical Devices" is included as part of this submission. |
| | The changes to the optional AutoMark software module were evaluated through<br>software verification and validation to show that the software is acceptable for use<br>and meets the requirements. |
| | <b>Risk Management</b> |
| | The changes to the AutoMark software were evaluated through review of risk<br>management to ensure no new hazards have been introduced by this change. The risk<br>analysis was completed and risk controls were implemented to mitigate identified<br>hazards. |
| | The AutoMark software module conforms to the Cybersecurity requirements through<br>the cybersecurity risk management process comprised of a risk assessment, risk<br>control, and maintenance of cybersecurity activities. |
| Statement of | The technological characteristics for the device are the same as the predicate devices. |
{6}------------------------------------------------
{7}------------------------------------------------
{8}------------------------------------------------
| Equivalence: | Based on this and the data provided in this pre-market notification, the subject device and predicate devices have been shown to be substantially equivalent. |
|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
|--------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------|
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.