K251763 · Intuitive Surgical, Inc. · QIH · Dec 16, 2025 · Radiology
Device Facts
Record ID
K251763
Device Name
IRISeg
Applicant
Intuitive Surgical, Inc.
Product Code
QIH · Radiology
Decision Date
Dec 16, 2025
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 892.2050
Device Class
Class 2
Attributes
AI/ML, Software as a Medical Device
AI Performance
Output
Algorithm
Acceptance
Observed
Dev DS
Dev Readers
Test DS
Test Readers
Kidney parenchyma segmentation
Neural network
—
—
Clinical data processed during commercial operation of the cleared IRIS 1.0 system (K182643)
1 (US board certified radiologist)
—
—
Kidney artery segmentation
Neural network
—
—
Clinical data processed during commercial operation of the cleared IRIS 1.0 system (K182643)
1 (US board certified radiologist)
—
—
Kidney vein segmentation
Neural network
—
—
Clinical data processed during commercial operation of the cleared IRIS 1.0 system (K182643)
1 (US board certified radiologist)
—
—
Kidney collecting system segmentation
Neural network
—
—
Clinical data processed during commercial operation of the cleared IRIS 1.0 system (K182643)
1 (US board certified radiologist)
—
—
Indications for Use
IRISeg is intended for use as a software application that receives DICOM compliant MR or contrast-enhanced CT images, provides manual and machine learning-enabled tools for image analysis and segmentation, and creates an output file that can be used to render a 3D model for preoperative surgical planning and intraoperative display. The use of IRISeg may include the generation of preliminary segmentations using machine learning algorithms. IRISeg is intended for use by qualified professionals. The output file is meant for visual, non-diagnostic use and shall be reviewed by clinicians who are responsible for all final patient management decisions. The machine learning enabled kidney CT auto-segmentation tool is intended for use for adult patients with contrast-enhanced, axial kidney CT images with slice thickness 3mm or less.
Device Story
IRISeg is a standalone software application for medical image segmentation and 3D model generation. It accepts DICOM-compliant CT or MR images and NIfTI segmentation files. Users (qualified professionals) perform manual segmentation using tools like paintbrushes, erasers, and morphological operations. An integrated neural network-based ML algorithm provides auto-segmentation for four kidney structures (parenchyma, artery, vein, collecting system) from CT scans. The ML output serves as a preliminary estimate, requiring user review and manual refinement. The software produces output files for rendering 3D models used in preoperative planning and intraoperative display. Used in office settings on general-purpose computers, the device assists clinicians by providing visual anatomical representations to support surgical decision-making. It does not generate mass labels automatically. The system is non-diagnostic; clinicians retain responsibility for all patient management decisions.
Clinical Evidence
No clinical data. Performance was established via bench testing, including functional, usability, and cybersecurity verification and validation. The ML auto-segmentation algorithm performance was previously established under K242461 and remains unchanged. Testing confirmed the software meets design requirements and user needs.
Technological Characteristics
Standalone software application; runs on general-purpose computer hardware. Inputs: DICOM CT/MR, NIfTI. Outputs: 3D model files. ML algorithm: Neural network (unchanged from predicate). Manual tools: Paintbrush, eraser, connected component selection, free curve selection, morphological/mathematical operations. Cybersecurity: Security requirement, threat mitigation, vulnerability, and penetration testing per FDA guidance. Compliant with IEC 62304.
Indications for Use
Indicated for adult patients requiring preoperative surgical planning and intraoperative display via 3D models generated from contrast-enhanced, axial kidney CT images (slice thickness ≤3mm) or MR images. Intended for use by qualified professionals. Output is for visual, non-diagnostic use; clinicians responsible for final management decisions.
Regulatory Classification
Identification
A medical image management and processing system is a device that provides one or more capabilities relating to the review and digital processing of medical images for the purposes of interpretation by a trained practitioner of disease detection, diagnosis, or patient management. The software components may provide advanced or complex image processing functions for image manipulation, enhancement, or quantification that are intended for use in the interpretation and analysis of medical images. Advanced image manipulation functions may include image segmentation, multimodality image registration, or 3D visualization. Complex quantitative functions may include semi-automated measurements or time-series measurements.
Special Controls
*Classification.* Class II (special controls; voluntary standards—Digital Imaging and Communications in Medicine (DICOM) Std., Joint Photographic Experts Group (JPEG) Std., Society of Motion Picture and Television Engineers (SMPTE) Test Pattern).
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
December 16, 2025
Intuitive Surgical Inc.
% Jyh-Shyan Lin
Senior Regulatory Affairs Specialist
1266 Kifer Road
SUNNYVALE, CA 94086
Re: K251763
Trade/Device Name: IRIseg
Regulation Number: 21 CFR 892.2050
Regulation Name: Medical Image Management And Processing System
Regulatory Class: Class II
Product Code: QIH, LLZ
Dated: November 12, 2025
Received: November 13, 2025
Dear Jyh-Shyan Lin:
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 (the 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 available 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.
{1}
K251763 - Jyh-Shyan Lin
Page 2
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality System (QS) regulation (21 CFR Part 820), which includes, but is not limited to, 21 CFR 820.30, Design controls; 21 CFR 820.90, Nonconforming product; and 21 CFR 820.100, Corrective and preventive action. Please note that regardless of whether a change requires premarket review, the QS regulation requires device manufacturers to review and approve changes to device design and production (21 CFR 820.30 and 21 CFR 820.70) and document changes and approvals in the device master record (21 CFR 820.181).
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 device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-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 Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 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-devices/medical-device-safety/medical-device-reporting-mdr-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/medical-devices/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-devices/device-advice-comprehensive-regulatory-
{2}
K251763 - Jyh-Shyan Lin
Page 3
assistance/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,

Lu Jiang, Ph.D.
Assistant Director
Diagnostic X-Ray Systems Team
DHT8B: Division of Radiologic Imaging Devices and Electronic Products
OHT8: Office of Radiological Health
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
FORM FDA 3881 (8/23)
Page 1 of 1
PSC Publishing Services (301) 443-6740
EF
| DEPARTMENT OF HEALTH AND HUMAN SERVICES Food and Drug Administration Indications for Use | Form Approved: OMB No. 0910-0120 Expiration Date: 07/31/2026 See PRA Statement below. |
| --- | --- |
| 510(k) Number (if known) K251763 | |
| Device Name IRISeg | |
| Indications for Use (Describe) IRISeg is intended for use as a software application that receives DICOM compliant MR or contrast-enhanced CT images, provides manual and machine learning-enabled tools for image analysis and segmentation, and creates an output file that can be used to render a 3D model for preoperative surgical planning and intraoperative display. The use of IRISeg may include the generation of preliminary segmentations using machine learning algorithms. IRISeg is intended for use by qualified professionals. The output file is meant for visual, non-diagnostic use and shall be reviewed by clinicians who are responsible for all final patient management decisions. The machine learning enabled kidney CT auto-segmentation tool is intended for use for adult patients with contrast-enhanced, axial kidney CT images with slice thickness 3mm or less. | |
| Type of Use (Select one or both, as applicable) ☑ Prescription Use (Part 21 CFR 801 Subpart D) ☐ 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." | |
{4}
IRISeg
510(k) K251763 Summary
# K251763: 510(k) SUMMARY
This summary of 510(k) substantial equivalence information is submitted in accordance with the requirements of Safe Medical Device Act (SMDA) 1990 and 21 CFR 807.92.
# 1. SUBMITTER
510(k) Owner: Intuitive Surgical, Inc.
1266 Kifer Road
Sunnyvale, CA 94086
Contact: Jyh-Shyan (Jesse) Lin
Senior Regulatory Affairs Specialist
Phone Number: 408-523-4952
Email: jesse.lin@intusurg.com
Date Prepared: November 12, 2025
# 2. SUBJECT DEVICE INFORMATION
Manufacturer Name: Intuitive Surgical, Inc.
510(k) Number: K251763
Trade Name: IRISeg
Common Name: Automated radiological image processing software
Medical image processing software
Classification: Class II
21 CFR 892.2050
Medical image management and processing system
Primary Product Codes: QIH
Associate Product Code: LLZ
Review Panel: Radiology
# 3. PREDICATE DEVICE INFORMATION
Manufacturer Name: Intuitive Surgical, Inc.
510(k) Number: K242461, last cleared on December 10, 2024
Trade Name: IRISeg
Common Name: Automated radiological image processing software
Medical image processing software
Classification: Class II
21 CFR 892.2050
Medical image management and processing system
Primary Product Codes: QIH
Associate Product Code: LLZ
Review Panel: Radiology
No reference devices were used in this submission.
INTUITIVE
{5}
IRISeg
510(k) K251763 Summary
# 4. DEVICE DESCRIPTION
IRISeg is a standalone software application created by Intuitive Surgical for segmentation of CT and MR images and generation of output files that can be rendered as virtual 3D models of anatomical structures. IRISeg is designed to provide qualified professionals ("users") with a machine learning (ML)-based tool for auto-segmentation of kidney anatomy based on CT scans and non-ML manual tools for segmentation based on CT and MR scans.
Note that there have been no changes to existing tools or introductions of new tools between the predicate and subject devices.
# Input File
IRISeg can open and load CT or MR imaging files in DICOM (Digital Imaging and Communications in Medicine) format, and segmentation label files in NIfTI (Neuroimaging Informatics Technology Initiative) format from an accessible storage location.
# Output File
Following the use of IRISeg to segment CT or MR imaging files, the software can be used to generate an output file that can be used to render virtual segmented 3D models.
# IRISeg Manual Tools
IRISeg includes a variety of tools for users to manually edit segmentation labels, such as Paintbrush tools, Eraser tools, Connected Component Selection, Free Curve Selection, Morphological operations, Mathematical Operations.
Manual tools alone can be used to manually segment (annotate) CT and MR scans.
Manual tools can also be used to modify the output of the ML-based auto-segmentation algorithm. The ML-based auto-segmentation does not generate mass labels. Users must segment and label renal masses using manual tools.
# IRISeg ML-Based Auto-Segmentation Tool
IRISeg includes an ML-based auto-segmentation algorithm (cleared under K242461 and unchanged in the subject device) for automatic segmentation of four kidney structures from CT imaging. The auto-segmentation algorithm is a neural network based ML algorithm. It is trained on segmented kidney CT models that were sourced from clinical data processed during commercial operation of the cleared IRIS 1.0 system (K182643). Each 3D model was reviewed by one U.S board certified radiologist. The input is a CT image (series of 2D slices). The output of the model is four probability maps for kidney parenchyma, kidney artery, kidney vein, and collecting system. The probability maps are thresholded to generate binary masks for kidney parenchyma, kidney artery, kidney vein and collecting system. The ML-based auto-segmentation does not generate binary masks for kidney masses.
The algorithm output is intended as an initial estimate of the segmentation. The user must use the manual tools to update the initial algorithm output to generate the kidney CT 3D model.
The development of the IRISeg kidney CT ML-based auto-segmentation algorithm followed FDA's Good Machine Learning Practices for Medical Device Development: Guiding Principles, October 2021.
INTUITIVE
{6}
IRISeg
510(k) K251763 Summary
# 5. INTENDED USE/INDICATIONS FOR USE
IRISeg is intended for use as a software application that receives DICOM compliant MR or contrast-enhanced CT images, provides manual and machine learning-enabled tools for image analysis and segmentation, and creates an output file that can be used to render a 3D model for preoperative surgical planning and intraoperative display. The use of IRISeg may include the generation of preliminary segmentations using machine learning algorithms. IRISeg is intended for use by qualified professionals. The output file is meant for visual, non-diagnostic use and shall be reviewed by clinicians who are responsible for all final patient management decisions.
The machine learning enabled kidney CT auto-segmentation tool is intended for use for adult patients with contrast-enhanced, axial kidney CT images with slice thickness 3mm or less.
# 6. SUMMARY OF SUBSTANTIAL EQUIVALENCE
The subject device has been developed as a standalone software application by modifying the predicate device (K242461). The comparison with the predicate device is based on the intended use, indications for use, general design, technological characteristics and operational principle/workflow. A summary of the subject device compared to the predicate device is provided below.
Comparison of Indications for Use and intended Use
| Predicate Device (K242461) | Subject Device (K251763) |
| --- | --- |
| Intended to receive DICOM compliant contrast-enhanced CT images, provide manual and machine learning-enabled tools for image analysis and segmentation, and creates an output file that can be used to render a 3D model for preoperative surgical planning and intraoperative display. | SAME intended use. |
| | SIMILAR Indications for use: Added MR indication for image analysis and non-ML manual segmentation of DICOM compliant MR images. |
Comparison of Device Characteristics
| Description | Predicate Device (K242461) | Subject Device (K251763) |
| --- | --- | --- |
| Regulation Number | 21 CFR §892.2050 | 21 CFR §892.2050 |
| Classification | Class II | Class II |
| Product Code | Primary: QIH; Associate: LLZ | Primary: QIH; Associate: LLZ |
| Prescription use | Rx only | Rx only |
| Host Hardware Compatibility | General-purpose computer hardware | Same |
| Intended population | Adult patients (ML algorithm) | Same |
| Intended Users | Qualified Professionals | Same |
INTUITIVE
{7}
IRISeg
510(k) K251763 Summary
| Description | Predicate Device (K242461) | Subject Device (K251763) |
| --- | --- | --- |
| Intended Clinical Decision Support | The output file can be used to render a 3D model for preoperative surgical planning and intraoperative display. The output file is meant for visual, non-diagnostic use and shall be reviewed by clinicians who are responsible for all final patient management decisions. | Same |
| Configuration | Label names, label color parameters and label name translation for kidney CT scans | Equivalent to the predicate device
Difference: Updated label names, label color parameters and label name translation for MR scans |
| Principles of Operations / Workflow | Manual segmentation alone
Auto-segmentation followed by manual segmentation. | Equivalent to the predicate device
Difference: Manual segmentation only for MR scans |
| User interface / Environment | Graphical user interface design.
Office setting (Segmentation Software Application running on a general-purpose computer) | Same |
| Supported Input | DICOM-Compliant CT scans (Axial views, contrast enhanced) | Equivalent to the predicate device
Difference: addition of DICOM compliant MR scans |
| Supported Output | Segmentation files that can be used to render a 3D model for preoperative surgical planning and intraoperative display | Same |
| Supported Segmentation Structures | Kidney CT structures:
• ML auto-segmentation - Parenchyma, Artery, Vein and Collecting System
• Manual segmentation - Parenchyma, Artery, Vein, Collecting System and Mass | Same: Kidney CT structures (Manual and ML auto-segmentation)
Difference (MR structures for manual segmentation):
- Kidney MR structures
- Prostate MR structures
- Rectal MR structures |
INTUITIVE
Page 4
{8}
IRISeg
510(k) K251763 Summary
| Description | Predicate Device (K242461) | Subject Device (K251763) |
| --- | --- | --- |
| ML Auto-Segmentation Structures and performance | 4 kidney CT structures: Parenchyma, Artery, Vein and Collecting System
Performance: Machine Learning Auto-Segmentation Testing of kidney CT scans. | Same
Same |
| Manual Tools and manual segmentation performance | Various segmentation and selection tools for manual segmentation.
Performance: Manual segmentation testing of kidney CT scans | Same
Same (kidney CT scans)
Equivalent manual segmentation performance for MR scans |
| 2D and 3D Visualization Features | Volume rendering, 3D model visualization, 2D slice visualization. | Same |
| Segmentation Support Features | Metadata viewing | Same |
# 7. RISK MANAGEMENT (SAFETY)
Risk is managed in compliance with ISO 14971, to identify and provide mitigation of potential hazards throughout the software development life cycle (SDLC). Risks related to IRISeg ML-based auto-segmentation algorithm is managed by following the AAMI CR34971 Guidance on the Application of ISO 14971 to Artificial Intelligence and Machine Learning. Clinical risk analysis, usability risk analysis, comparative task analysis, use-related risk analysis, Cybersecurity Risk Analysis, and Risk Assessment of off-The-Shelf Software are conducted, and the risks are mitigated throughout the SDLC.
# 8. PERFORMANCE DATA (EFFECTIVENESS)
Performance testing of the kidney ML auto-segmentation algorithm was conducted on the predicate device (cleared under K242461). The algorithm was not modified in the subject device, and therefore the performance of the ML algorithm is as effective as in the predicate device.
Final product testing have been performed in accordance with IEC 62304 Edition 1.1 2015-06 Consolidated Version. Software documentation has been provided according to FDA's Guidance, Content of Premarket Submissions for Device Software Functions" (June 14, 2023). IRISeg underwent final product testing. The software testing of the subject device included functional testing, usability testing, and cybersecurity testing. Acceptance criteria were based on the requirements and intended use of IRISeg. Test results showed that all tests met the acceptance criteria. The testing results demonstrate that IRISeg meets design specifications and user needs.
INTUITIVE
{9}
IRISeg
510(k) K251763 Summary
## Cybersecurity Testing
The cybersecurity verification and validation testing were conducted, and cybersecurity was evaluated per FDA’s Guidance “Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions” (June 27, 2025). Specifically, addressing the following cybersecurity testing areas: security requirement testing, threat mitigation testing, vulnerability testing, and penetration testing. The cybersecurity verification and validation test results demonstrate the adequacy of the implemented cybersecurity controls.
## Labeling
The device labeling contains instructions for use and any necessary cautions to ensure that the labeling differences, as compared to the predicate device, do not affect the safety and effectiveness of the subject device when used as labeled.
Labeling information including the prescription use (“Rx only”), the name and place of business of the manufacturer, device description, indications for use, directions for use, cybersecurity labeling and transparency labeling (per Transparency for Machine Learning-Enabled Medical Devices: Guiding Principles, June 2024) is provided in the subject device’s user manual. The UDI (per 21 CFR 801.50 Labeling requirements for standalone software) is provided on the software About screen.
## 9. CONCLUSION
The subject device and the predicate device are deemed to be substantially equivalent based on indications for use, general design, technological characteristics, operational principle/workflow and performance testing. The subject device raises no new questions related to safety or effectiveness, as compared to the predicate device.
INTUITIVE
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.