ME-APDS (Magentig Eye's Automatic Polyp Detection System) is intended to be used by endoscopists as an adjunct to the common video colonoscopy procedure (screening and surveillance), aiming to assist the endoscopist in identifying lesions during colonoscopy procedure by highlighting regions with visual characteristics consistent with different types of mucosal abnormalities that appear in the colonoscopy video during the procedure. Highlighted regions can be independently assessed by the endoscopist and appropriate action taken according to standard clinical practice. ME-APDS is trained to process video images which may contain regions consistent with polyps. ME-APDS is limited for use with standard white-light endoscopy imaging only. ME-APDS is intended to be used as an adjunct to endoscopy procedures and is not intended to replace histopathological sampling as means of diagnosis.
Device Story
ME-APDS is a computer-aided detection (CADe) system for real-time polyp identification during colonoscopy. It acquires digital video output from an endoscopy camera; processes frames using deep machine learning algorithms to detect mucosal abnormalities; and overlays visual highlights on a separate display. Used in clinical settings by endoscopists; the system provides real-time visual cues to assist in lesion detection. It does not perform diagnosis or replace clinical judgment; endoscopists independently assess highlighted regions to determine appropriate clinical action. The device benefits patients by potentially increasing polyp detection rates during screening and surveillance procedures.
Clinical Evidence
No new clinical study was conducted; clinical validation relies on data from the predicate device (K223473). Standalone performance testing was conducted on 212 colonoscopy videos containing 702 polyps. Results showed a polyp-wise recall (PRecall1) of 99.7% for histology-verified polyps and 97.9% overall. Median coverage of histology-verified polyps was 81.7%. Marker annotation latency was 133 msec (FHD) and 157 msec (4K).
Technological Characteristics
CADe engine for real-time video frame processing. Compatible with standard white-light endoscopy. Hardware/software modifications from predicate; AI algorithm remains identical. Electrical safety per IEC 60601-1 Ed 3.2; EMC per IEC 60601-1-2:2014/AMD 1:2021 and TR 60601-4-2.
Indications for Use
Indicated for use by endoscopists as an adjunct to screening and surveillance video colonoscopy procedures to assist in identifying mucosal abnormalities (polyps) in patients. Limited to standard white-light endoscopy imaging. Not for diagnosis or replacement of histopathological sampling.
Regulatory Classification
Identification
A gastrointestinal lesion software detection system is a computer-assisted detection device used in conjunction with endoscopy for the detection of abnormal lesions in the gastrointestinal tract. This device with advanced software algorithms brings attention to images to aid in the detection of lesions. The device may contain hardware to support interfacing with an endoscope.
Special Controls
In combination with the general controls of the FD&C Act, the gastrointestinal lesion software detection system is subject to the following special controls:
*Classification.* Class II (special controls). The special controls for this device are:(1) Clinical performance testing must demonstrate that the device performs as intended under anticipated conditions of use, including detection of gastrointestinal lesions and evaluation of all adverse events.
(2) Non-clinical performance testing must demonstrate that the device performs as intended under anticipated conditions of use. Testing must include:
(i) Standalone algorithm performance testing;
(ii) Pixel-level comparison of degradation of image quality due to the device;
(iii) Assessment of video delay due to marker annotation; and
(iv) Assessment of real-time endoscopic video delay due to the device.
(3) Usability assessment must demonstrate that the intended user(s) can safely and correctly use the device.
(4) Performance data must demonstrate electromagnetic compatibility and electrical safety, mechanical safety, and thermal safety testing for any hardware components of the device.
(5) Software verification, validation, and hazard analysis must be provided. Software description must include a detailed, technical description including the impact of any software and hardware on the device's functions, the associated capabilities and limitations of each part, the associated inputs and outputs, mapping of the software architecture, and a description of the video signal pipeline.
(6) Labeling must include:
(i) Instructions for use, including a detailed description of the device and compatibility information;
(ii) Warnings to avoid overreliance on the device, that the device is not intended to be used for diagnosis or characterization of lesions, and that the device does not replace clinical decision making;
(iii) A summary of the clinical performance testing conducted with the device, including detailed definitions of the study endpoints and statistical confidence intervals; and
(iv) A summary of the standalone performance testing and associated statistical analysis.
Predicate Devices
Magentiq Eye's Automatic Polyp Detection System (K223473)
Submission Summary (Full Text)
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). On the left is the Department of Health & Human Services logo. To the right of that is the FDA logo, which is a blue square with the letters "FDA" in white. To the right of the blue square is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
January 24, 2025
Magentiq Eye LTD % John J. Smith Partner Hogan Lovells US LLP Columbia Square 555 13th Street, NW Washington, District of Columbia 20004
Re: K244023
Trade/Device Name: MAGENTIQ-COLO (ME-APDS) Regulation Number: 21 CFR 876.1520 Regulation Name: Gastrointestinal Lesion Software Detection System Regulatory Class: Class II Product Code: QNP Dated: December 27, 2024 Received: December 27, 2024
Dear John J. Smith:
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}------------------------------------------------
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 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-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 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-device-advicecomprehensive-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-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-regulatory
{2}------------------------------------------------
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,
# Shanil P. Haugen -S
Shanil P. Haugen, Ph.D. Assistant Director DHT3A: Division of Renal, Gastrointestinal, Obesity, and Transplant Devices OHT3: Office of Gastrorenal, ObGyn, General Hospital, and Urology Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{3}------------------------------------------------
# Indications for Use
Submission Number (if known)
K244023
Device Name
MAGENTIQ-COLO (ME-APDS)
# Indications for Use (Describe)
ME-APDS (Magentig Eye's Automatic Polyp Detection System) is intended to be used by endoscopists as an adjunct to the common video colonoscopy procedure (screening and surveillance), aiming to assist the endoscopist in identifying lesions during colonoscopy procedure by highlighting reqions with visual characteristics consistent with different types of mucosal abnormalities that appear in the colonoscopy video during the procedure. Highlighted regions can be independently assessed by the endoscopist and appropriate action taken according to standard clinical practice.
ME-APDS is trained to process video images which may contain regions consistent with polyps.
ME-APDS is limited for use with standard white-light endoscopy imaging only.
ME-APDS is intended to be used as an adjunct to endoscopy procedures and is not intended to replace histopathological sampling as means of diagnosis.
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}------------------------------------------------
# 510(k) Summary Magentig Eye's MAGENTIQ-COLO
# Submitter:
Magentiq Eye Ltd. 6 Ben-Gurion Blvd.. Haifa, 3541416, Israel
Phone: +972 (77) 2018838
Contact Person: Dr. Dror Zur
Date Prepared: January 14th, 2025
Name of Device: Magentiq Eye's Automatic Polyp Detection System (ME-APDS™)
Trade Name: MAGENTIQ-COLO™
Common or Usual Name: Computer aided detection software for colorectal polyps
Classification Name: Gastrointestinal Lesion Software Detection System
Regulatory Class: II
Product Code: QNP
Predicate Device: Magentiq Eye's Automatic Polyp Detection System (K223473)
# Device Description:
ME-APDS™MAGENTIQ-COLO is intended to be used as an adjunct to the common video colonoscopy procedure. The system application aims to assist the endoscopist in identifying lesions, such as polyps, during the colonoscopy procedures in real time. The device is not intended to be used for diagnosis or characterization of lesions, and does not replace clinical decision making.
The system acquires the digital video output signal from the local endoscopy camera and processes the video frames. It runs deep machine learning and additional supporting algorithms in real time on the video frames in order to detect and identify regions having characteristics consistent with different types of mucosal abnormalities such as polyps. The output video with the detected lesions is presented on a separate screen, highlighting the suspicious areas on the original video. The user can also take snapshots of the videos, with and without the highlighting of the suspicious areas, record videos and view in full screen mode.
# Intended Use / Indications for Use:
ME-APDS™ (Magentiq Eye's Automatic Polyp Detection System) is intended to be used by endoscopists as an adjunct to the common video colonoscopy procedure (screening and surveillance),
{5}------------------------------------------------
aiming to assist the endoscopist in identifying lesions during colonoscopy procedure by highlighting regions with visual characteristics consistent with different types of mucosal abnormalities that appear in the colonoscopy video during the procedure. Highlighted regions can be independently assessed by the endoscopist and appropriate action taken according to standard clinical practice.
ME-APDS™ is trained to process video images which may contain regions consistent with polyps.
ME-APDS™ is limited for use with standard white-light endoscopy imaging only.
ME-APDS™ intended to be used as an adjunct to endoscopy procedures and is not intended to replace histopathological sampling as means of diagnosis.
# Summary of Technological Characteristics:
Computer-Aided Polyp Detection (CADe) engine is the technological principle for both the subject and predicate devices. The major roles of CADe engine during colonoscopy is to process a video frame and to indicate the presence and location of detected lesions (such as polyps) in real time during colonoscopy procedure in order to improve mucosal lesion rates, thus improving the performance of the endoscopist.
The proposed device is a modification to the company cleared device. The proposed device labeling has been updated to identify an additional compatible endoscopy systems, and the system includes modifications to the devices hardware and software. The Al algorithm remains identical to the predicate device.
# Performance Data:
# Non-Clinical Testing:
The non-clinical performance studies of the subject device included:
- . Pixel-level comparison of degradation of image quality
- . Software validation
- EMC testing in accordance with the requirements of IEC 60601-1-2:2014 [Including AMD . 1:2021] and TR 60601-4-2 Edition 1.0 2016-05
- . Electrical safety testing in accordance with IEC 60601-1 Edition 3.2 2020-08 CONSOLIDATED VERSION
In all instances, the ME-APDS functioned as intended and all tests' results observed were as expected.
# Assessment of Marker Annotation Delay:
Marker annotation delay was assessed for all polyps from the standalone performance testing dataset. The marker annotation latency's median, calculated over all the polyps, is 133 msec for FHD and 157 msec for 4K.
{6}------------------------------------------------
# Standalone Performance Testing:
The algorithm was tested offline on 212 unique full colonoscopy videos, containing 702 polyps. 16 videos contained no polyps. Of the 702 polyps, 586 were small (s≤5mm), 93 have medium size (5mm<s<10mm), and 23 were large (s≥10mm). 344 polyps had histology findings where 277 were found to be adenoma polyps. Polyps evaluated varied by subject sex (270 Male, 170 Female, 262 Unknown), age (60 under 50 years, 133 50-60 years, 256 older than 60 years, 253 unknown), race (343 Caucasian, 6 African American, 353 Unknown).
ME-APDS recall and false positive performance was evaluated. In addition, the number of False Positives Per Full Video (procedure) rate was assessed. Polyp-wise Recall was defined as the number of polyps detected, each for a set number consecutive frames, out of the total number of polyps in the testing dataset, Polyp-wise Recall was evaluated a 1, 3, 5 and 7 consecutive frames as Precall1, Precall3, Precall5, and Precall7, respectively. The system detects 99.7% (PRecall1 to PRecall7) of polyps verified by histology and 97.9% to 90.6% (PRecall1 to PRecall7) of the polyps when polyps without histology verification were included, showing the ability of the system to adequately aid in the detection of polyps when working with the MAGENTIQ-COLO. The median of the coverage of polyps with histology was high (81.7%). The False Positives Per Frame (FPPF) threshold of 0.0333 was achieved.
Results on polyps that were reported in the procedure report, classified according to polyps with histology and without.
| | FRecall | CI | MPC | PRecall1 | CI | PRecall3 | CI | PRecall5 | CI | PRecall7 | CI |
|----------------------|---------|---------------------|-------|----------|---------------------|----------|---------------------|----------|---------------------|----------|---------------------|
| With<br>Histology | 76.0% | [73.13%,<br>78.8%] | 81.7% | 99.7% | [99.12%,<br>100.0%] | 99.7% | [99.09%,<br>100.0%] | 99.7% | [99.1%,<br>100.0%] | 99.7% | [99.11%,<br>100.0%] |
| Without<br>Histology | 76.3% | [70.39%,<br>81.24%] | 83.4% | 100% | [100.0%,<br>100.0%] | 100% | [100.0%,<br>100.0%] | 100% | [100.0%,<br>100.0%] | 100% | [100.0%,<br>100.0%] |
#### Reported Results on Polyps with Histology and Without
# Results on the Entire Testing Dataset
| FRecall | CI | MPC | PRecall1 | CI | PRecall3 | CI | PRecall5 | CI | PRecall7 | CI |
|---------|---------------------|-----|----------|---------------------|----------|---------------------|----------|---------------------|----------|---------------------|
| 73.1% | [70.56%,<br>75.75%] | 72% | 97.9% | [96.63%,<br>98.94%] | 95.3% | [93.39%,<br>96.96%] | 93.2% | [91.01%,<br>95.15%] | 90.6% | [88.19%,<br>92.91%] |
The testing results were observed to be as expected and support that the device has similar performance to the predicate device.
# Clinical Study:
The clinical validation used to support the device colon polyp detection functions of the ME-APDS/MAGENTIQ-COLO™ was conducted in K223473.
{7}------------------------------------------------
# Conclusions:
The modified ME-APDS/MAGENTIQ-COLO™ is as safe and effective as the company's prior cleared ME-APDS. The modified ME-APDS has the same intended uses and indications, similar technological characteristics, and principles of operation as its predicate device. The minor differences do not alter the intended use and raise no new issues of safety or effectiveness. Performance data demonstrate that the modified ME-APDS is as safe and effective as the cleared ME-APDS. Thus, the modified ME-APDS /MAGENTIQ-COLO™ is 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.