General ophthalmic imaging including retinal, corneal, and external structures of the eye.
Device Story
Phoenix ICON and Phoenix ICON GO are wide-field, high-resolution, real-time ophthalmic imaging systems. The platform uses a handheld camera (handpiece) with interchangeable LED light sources (white for external/retinal imaging, blue for fluorescein angiography). The handpiece couples to the cornea via imaging gel for retinal procedures. The system captures still images or video, which are stored on a control box (cart-based or laptop-based) for review by clinicians (physicians, nurses, ophthalmic technicians). Used in hospitals, clinics, and physician offices, the device provides visual data to assist in ophthalmic assessment and clinical decision-making. The Phoenix ICON GO offers a portable version of the cart-based system. Output is viewed by the healthcare provider to evaluate ocular structures, potentially benefiting patients through improved diagnostic visualization.
Clinical Evidence
Bench testing only. Performance demonstrated through biocompatibility (ISO 10993-1), electrical safety (IEC 60601-1, IEC 60601-1-2), light safety (ANSI Z80.36:2021), and simulated use testing comparing image clarity against the predicate device. Cleaning validation achieved >3 log reduction in active microbials.
Technological Characteristics
Electric-powered (AC/battery) ophthalmic camera using LED light sources (450-675 nm white, 450-460 nm blue). Features Sony IMX265LLR/LQR CMOS sensor, 100-degree FOV, 30 fps video. Connectivity via USB or local network. Standards: IEC 60601-1, IEC 60601-1-2, IEC 62366, ANSI Z80.36:2021, ISO 10993-1, ASTM D4169-16.
Indications for Use
Indicated for general ophthalmic imaging of retinal, corneal, and external eye structures in patients requiring ophthalmic examination.
Regulatory Classification
Identification
An ophthalmic camera is an AC-powered device intended to take photographs of the eye and the surrounding area.
Special Controls
*Classification.* Class II (special controls). The device, when it is a photorefractor or a general-use ophthalmic camera, is exempt from the premarket notification procedures in subpart E of part 807 of this chapter subject to the limitations in § 886.9.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image contains the logo of the U.S. Food and Drug Administration (FDA). The logo consists of two parts: the Department of Health & Human Services logo on the left and the FDA acronym in a blue square, followed by the words "U.S. FOOD & DRUG ADMINISTRATION" in blue text. The Department of Health & Human Services logo is a stylized representation of a human figure.
September 21, 2023
NeoLight, LLC Amy Oakes Vice President of Quality & Regulatory Affairs 6630 Owens Drive Pleasanton, California 94588
Re: K223575
Trade/Device Name: Phoenix ICON, Phoenix ICON GO Regulation Number: 21 CFR 886.1120 Regulation Name: Ophthalmic camera Regulatory Class: Class II Product Code: HKI
Dear Amy Oakes:
The Food and Drug Administration (FDA) is sending this letter to notify you of an administrative change related to your previous substantial equivalence (SE) determination letter dated September 6, 2023. Specifically, FDA is updating this SE Letter to correct typographical error in the trade name from "Pheonix" to "Phoenix", as an administrative correction.
Please note that the 510(k) submission was not re-reviewed. For questions regarding this letter please contact Elvin Ng, Office of Ophthalmic, Anesthesia, Respiratory, ENT & Dental Devices (OHT1), 240-402-4662, elvin.ng(@fda.hhs.gov.
Sincerely,
2023.09.21 Alexander Beylin -S 17:38:28 -04'00'
for Elvin Ng
Assistant Director Retina and Diagnostic Devices Team (THT1A3) Division of Ophthalmic Devices (DHT1A) Office of Ophthalmic, Anesthesia, Respiratory, ENT & Dental Devices (OHT1) Office of Product Evaluation and Quality (OPEQ) Center for Devices and Radiological Health
{1}------------------------------------------------
Image /page/1/Picture/0 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). The logo consists of two parts: the Department of Health & Human Services logo on the left and the FDA logo on the right. The FDA logo is a blue square with the letters "FDA" in white, followed by the words "U.S. FOOD & DRUG ADMINISTRATION" in blue.
September 6, 2023
NeoLight, LLC Amy Oakes Vice President of Quality & Regulatory Affairs 6630 Owens Drive Pleasanton, California 94588
Re: K223575
Trade/Device Name: Pheonix ICON, Pheonix ICON GO Regulation Number: 21 CFR 886.1120 Regulation Name: Ophthalmic Camera Regulatory Class: Class II Product Code: HKI Dated: July 26, 2023 Received: July 27, 2023
Dear Amy Oakes:
We have reviewed vour Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database located at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal
{2}------------------------------------------------
statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting of medical device-related adverse events) (21 CFR 803) for devices or postmarketing safety reporting (21 CFR 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reportingcombination-products); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR 4. Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medicaldevices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-device-advice-comprehensive-regulatoryassistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
Elvin Y. Ng -S
Elvin Ng Assistant Director DHT1A: Division of Ophthalmic Devices OHT1: Office of Ophthalmic, Anesthesia, Respiratory, ENT and Dental Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{3}------------------------------------------------
# Indications for Use
510(k) Number (if known)
K223575
Device Name Phoenix ICON Phoenix ICON GO
Indications for Use (Describe)
General ophthalmic imaging including retinal, corneal, and external structures of the eye.
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}------------------------------------------------
Image /page/4/Picture/0 description: The image shows the logo for Neolight. The logo consists of a circular graphic on the left and the word "neolight" on the right. The graphic inside the circle appears to be a stylized image of a person or animal in a curled position. The word "neolight" is written in a sans-serif font, with a small star above the "i".
# SECTION 5: 510(K) SUMMARY
As required by 21 CFR 807.92(c)
# Submitter's Name and Address: NeoLight, LLC 6630 Owen Dr
Pleasanton, CA 94588 USA
### Contact Name and Information:
Amy Oakes Vice President of Quality & Regulatory Affairs Email: amy.oakes@theneolight.com Phone: (480) 304-2165
# Date Prepared:
November 23, 2022
#### Device Information:
| Trade Name: | Phoenix ICON, Phoenix ICON GO |
|--------------------|--------------------------------|
| Device: | Camera, Ophthalmic, Ac-Powered |
| Review Panel: | Ophthalmic |
| Product Code: | HKI |
| Regulation Number: | 886.1120 |
| Regulatory Class: | 2 |
#### Predicate Device:
| 510(k) Number | 510(k) Title | Manufacturer |
|--------------------------------|--------------|-------------------------------|
| K170527 | Phoenix ICON | Phoenix Technology Group, LLC |
| Table 5.1: Predicate Device(s) | | |
# Table 5.1: Predicate Device(s)
#### Manufacturer:
NeoLight, LLC 6630 Owen Dr Pleasanton, CA 94588 USA
{5}------------------------------------------------
Image /page/5/Picture/0 description: The image contains the logo for "neolight". The logo consists of a circular icon on the left and the word "neolight" on the right. The icon shows a baby being held in a hand. The word "neolight" is written in a sans-serif font, and there is a star above the "i".
## Device Description:
The Phoenix ICON system is an updated cart based retinal imaging system covering the design changes to date on the predicate device, Phoenix ICON. The Phoenix ICON GO retinal imaging system is a portable version of the predicate device, Phoenix ICON (K170527) including the design changes in the Phoenix ICON system.
Both the Phoenix ICON and Phoenix ICON GO are wide-field, handheld, high resolution, real-time retinal imaging devices. They are intended to be used for general ophthalmic imaging including retinal, corneal, and external structures of the eye. The intended users of the Phoenix ICON and Phoenix ICON GO are clinical imaging technicians, ophthalmic technicians, nurses, and physicians. The devices may be used in hospitals, medical clinics, and physician's offices.
The Phoenix ICON platform consists of either a cart based (Phoenix ICON) or portable (Phoenix ICON GO) control box used in conjunction with a hand-held camera (Handpiece) using interchangeable LED based light sources (White and Blue light). The Phoenix ICON cart contains an AC mains power attachment, a battery module, a keyboard interface, a monitor, and a computer with Phoenix ICON software. The Phoenix ICON GO contains a portable control box with battery function and has an interface for attachment to a specified laptop computer which runs the Phoenix ICON software. Both systems may be used with a Foot Pedal, White Light Module (standard), Blue Light Module (FA) and/or Diffuser accessory.
The Phoenix ICON Handpiece contains a wide-field, high resolution camera is used in three (3) modes, External Imaging (White Light), Retinal Imaging (White Light), and Fluorescein Angiography (Blue Light). For external imaging, the Diffuser accessory is placed over the lens tip to diffuse the light and provide for images of the outer surfaces of the eye. Both Retinal Imaging and Fluorescein Angiography are performed with the glass lens of the Handpiece coupled to the cornea via an imaging gel. In these imaging methods, LED light is emitted into the eye to illuminate the retina for image capture.
Both the Phoenix ICON and Phoenix ICON GO are software-controlled systems which can capture either video or still images and store them on the control box (Cart computer or GO laptop) for later review. The Phoenix ICON system may be connected to IT networks under IT supervision.
## Indications for Use:
General ophthalmic imaging including retinal, corneal, and external structures of the eye.
## Technological Characteristics:
The Phoenix ICON and Phoenix ICON GO function on the same technological characteristics as the predicate version of the Phoenix ICON. Electric powered (AC or battery) LED light (white or blue) is directed to the object to be imaged (retina or external eye features) and returned light is captured and saved as an image for review by a trained medical practitioner.
K223575
{6}------------------------------------------------
Image /page/6/Picture/0 description: The image shows the logo for "neolight". The logo consists of a circular graphic on the left and the word "neolight" on the right. The graphic shows a stylized image of a baby in a circle. The word "neolight" is in a sans-serif font and is a light blue color, with a star above the "i".
Table 5.2 below shows the comparison of characteristics between the Predicate and Subject Devices.
| Characteristic | Predicate (K170527) | Subject<br>Phoenix ICON | Subject<br>Phoenix ICON Go | Comparison |
|-----------------------------|-----------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------|
| Features | May be used with<br>Fluorescein<br>Angiography | Models sold with or<br>without Fluorescein<br>Angiography | Models sold with or<br>without Fluorescein<br>Angiography | Identical |
| <b>Light Sources</b> | | | | |
| Source | LED | LED | LED | Identical |
| Wavelength | 450-675 nm (white)<br>450-460 nm (blue) | 450-675 nm (white)<br>450-460 nm (blue) | 450-675 nm (white)<br>450-460 nm (blue) | Identical |
| Source Power | 10 W | 10 W | 10 W | Identical |
| Maximum<br>Intensity | 19 mW/cm² (white)<br>20 mW/cm² (blue) | 12 mW/cm² (white)<br>16 mW/cm² (blue) | 12 mW/cm² (white)<br>16 mW/cm² (blue) | Reduced maximum output<br>power does not negatively<br>impact safety or efficacy |
| Intensity<br>Adjustment | 0-19 mW/cm² (white)<br>0-20 mW/cm² (blue) | 0-12 mW/cm² (white)<br>0-16 mW/cm² (blue) | 0-12 mW/cm² (white)<br>0-16 mW/cm² (blue) | Reduced maximum output<br>power does not negatively<br>impact safety or efficacy |
| Retinal<br>Irradiance* | 6.6 mW/cm² (white)<br>6.9 mW/cm² (blue) | Group 2 Instrument | Group 2 Instrument | Equivalent |
| External<br>Fixation Light | None | None | None | Identical |
| <b>Camera & Lensing</b> | | | | |
| CMOS Sensor | Sony IMX265, 1/1.8" | Sony IMX265LLR/LQR,<br>1/1.8" | Sony IMX265LLR/LQR,<br>1/1.8" | Similar |
| Field of View | 100 degrees | 100 degrees | 100 degrees | Identical |
| Resolution | 2048 x 1536 ppi | 2048 x 1544 ppi | 2048 x 1544 ppi | Similar |
| Frame Rate<br>(video) | 30 frames per second | 30 frames per second | 30 frames per second | Identical |
| Imaging Lens | Flat field external<br>camera (white only) | Flat field external<br>camera (white only) | Flat field external<br>camera (white only) | Identical |
| Filters | 500 & 515 nm edge<br>blocking (blue only) | 500 & 515 nm edge<br>blocking (blue only) | 500 & 515 nm edge<br>blocking (blue only) | Identical |
| Data Capture | Still or Video Images | Still or Video Images | Still or Video Images | Identical |
| File Format | *.TIF<br>*.JPEG<br>*.AVI<br>*.BMP | *.TIF<br>*.JPEG<br>*.AVI | *.TIF<br>*.JPEG<br>*.AVI | Removal of obsolete file<br>type does not negatively<br>impact safety or efficacy |
| Data Archive | Archive to Internal<br>Database<br>Or<br>Export to external<br>system via USB or<br>local network<br>connection | Archive to Internal<br>Database<br>Or<br>Export to external<br>system via USB or local<br>network connection | Archive to Internal<br>Database<br>Or<br>Export to external<br>system via USB or local<br>network connection | Identical |
*Predicate Test Method ISO 15004:2-2007 / Subject Test Method ANSI Z80.36:2021
Table 5.2: Specification Comparison to Predicate Device
{7}------------------------------------------------
Image /page/7/Picture/0 description: The image contains the logo for "neolight". The logo consists of a circular graphic on the left and the word "neolight" on the right. The graphic shows a stylized image of a baby being held in a hand. The word "neolight" is written in a sans-serif font, and there is a star above the "i" in "neolight".
## Function and Safety Testing:
Bench and laboratory testing was conducted to demonstrate performance (safety and effectiveness) of the Phoenix ICON Go.
| Characteristic | Standard(s) / Test Method | Results |
|-------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------|
| Biocompatibility | ISO 10993-1 in conjunction with FDA Guidance Document “Use of<br>International Standard ISO 10993-1, Biological evaluation of medical<br>devices – Part 1: Evaluation and testing within a risk management process” | Pass |
| Cleaning Validation | >3 log reduction in active microbials | Pass |
| Electrical Safety | IEC 60601-1:2005+A1 | Pass |
| | IEC 60601-1-6:2010 (3rd Ed) +A1:2013 | Pass |
| | IEC/EN 60601-1-2:2014 (4th Ed) | Pass |
| | IEC 62366:2015 | Pass |
| Visual &<br>Dimensional | Visual and Dimensional inspection to internal specifications | Pass |
| Simulated Use | Image Clarity - Comparison between subject and predicate images to<br>ensure equivalent visual quality of the captured images | Pass |
| Light Safety | ANSI Z80.36:2021 | Pass |
| Packaging<br>Validation | ASTM D4169-16 | Pass |
Table 5.3: Performance Testing
### Conclusion:
NeoLight, LLC concludes that the Phoenix ICON and Phoenix ICON GO are substantially equivalent to the predicate device described herein.
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.