K223091 · Olea Medical · LLZ · Jun 9, 2023 · Radiology
Device Facts
Record ID
K223091
Device Name
CT Perfusion V1.0
Applicant
Olea Medical
Product Code
LLZ · Radiology
Decision Date
Jun 9, 2023
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 892.2050
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
CT Perfusion V1.0 is an automatic calculation tool indicated for use in radiology. The device is an image processing software allowing computation of parametric maps from CT Perfusion data and extraction of volumes of interest based on numerical thresholds applied to the aforementioned maps. Computation of mismatch between extracted volumes is automatically provided. The device is intended to be used by trained professionals with medical imaging education including but not limited to, physicians and medical technicians in the imaging assessment workflow by extraction and communication of metrics from CT Perfusion dataset. The results of CT Perfusion V1.0 are intended to be used in conjunction with other patient information and, based on professional judgment, to assist the clinician in the medical imaging assessment. Trained professionals are responsible for viewing the full set of native images per the standard of care. The device does not alter the original image. CT Perfusion V1.0 is not intended to be used as a standalone diagnostic device and shall not be used to take decisions with diagnosis or therapeutic purposes. Patient management decisions should not solely be based on CT Perfusion V1.0 results. CT Perfusion V1.0 can be integrated and deployed through technical platforms, responsible for transferring, storing, converting formats, notifying of detected image variations and display DICOM of imaging data.
Device Story
CT Perfusion V1.0 is an image processing software module (docker) deployed on a technical platform (Medical Image Communications Device). It processes dynamic CT perfusion sequences acquired after iodine contrast agent injection. The device automatically identifies relevant series via DICOM tags, computes qualitative/quantitative parametric maps (e.g., CBF, CBV, MTT, TTP, Delay, tMIP), performs volume segmentation based on user-configurable numerical thresholds, and calculates mismatch metrics (volume, ratio, relative mismatch). The device lacks a native interface; it relies on the host technical platform for input reception, output visualization, and DICOM display. Results assist clinicians in imaging assessment; however, clinicians must review native images per standard of care. The device does not alter original images and is not for standalone diagnosis. It benefits patients by providing automated, reproducible perfusion metrics to support clinical judgment.
Clinical Evidence
Bench testing only. Clinical image comparison study compared CT Perfusion V1.0 against Olea Sphere V3.0. Results showed identical parametric map values (voxel-by-voxel difference = 0; Pearson/Spearman correlation = 1) and identical segmentation volumes (Mean DICE index = 1).
Technological Characteristics
Software-only image processing application (docker). Deterministic, non-AI algorithms. Operates on Medical Image Communications Device (MICD) platforms. Inputs/outputs via DICOM. Supports automated volume segmentation based on configurable numerical thresholds. No native interface; relies on host platform for visualization.
Indications for Use
Indicated for use in radiology by trained professionals (physicians, medical technicians) to assist in imaging assessment by extracting and communicating metrics from CT Perfusion datasets. Not for standalone diagnosis or therapeutic decision-making.
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}------------------------------------------------
Image /page/0/Picture/0 description: The image contains 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.
Olea Medical % John J. Smith Partner Hogan Lovells US LLP Columbia Square 555 Thirteenth Street. NW WASHINGTON DC 20004
Re: K223091
June 9, 2023
Trade/Device Name: CT Perfusion V1.0 Regulation Number: 21 CFR 892.2050 Regulation Name: Medical image management and processing system Regulatory Class: Class II Product Code: LLZ Dated: May 16, 2023 Received: May 16, 2023
Dear John 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 (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 statutes and regulations administered by other Federal agencies. You must comply with all the Act's
{1}------------------------------------------------
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 (OS) 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 mediation-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,
Jessica Lamb
Jessica Lamb, Ph.D. Assistant Director Imaging Software Team DHT8B: Division of Imaging Devices and Electronic Products OHT8: Office of Radiological Health Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
| 510(k) Number (if known) | K223091 |
|--------------------------|---------|
| Device Name | |
#### CT Perfusion V1.0
CT Perfusion V1.0 is an automatic calculation tool in radiology. The device is an image processing software allowing computation of parametric maps from CT Perfusion of volumes of interest based on numerical thresholds applied to the aforementioned maps. Computation of mismatch between extracted volumes is automatically provided.
The device is intended to be used by trained with medical imaging education including but not limited to, physicians and medical technicians in the imaging assessment workflow by extraction and communication of metrics from CT Perfusion dataset.
The results of CT Perfusion V1.0 are intended to be used in conjunction and, based on professional judgment, to assist the clinician in the medical imaging assessment. Trained professionals are responsible for viewing the full set of native images per the standard of care.
The device does not alter the original image. CT Perfusion V1.0 is not intended to be used as a standalone diagnostic device and shall not be used to take decisions with diagnosis or therapeutic purposes. Patient management decisions should not solely be based on CT Perfusion V1.0 results.
CT Perfusion V1.0 can be integrated and deployed through technical platforms, responsible for transfering formats, notifying of detected image variations and display DICOM of imaging data.
| 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
{3}------------------------------------------------
#### 510(K) SUMMARY l.
The Company's 510(k) Summary is provided on the following pages.
{4}------------------------------------------------
# 510(k) SUMMARY
### Olea Medical's CT Perfusion V1.0
#### Submitter
K223091
Olea Medical 93 avenue des Sorbiers, ZI ATHELIA IV 13600, La Ciotat France Phone: +33 4 42 71 24 20 Facsimile: +33 4 42 71 24 27 Contact Person: Nathalie Palumbo
Date Prepared: September 30, 2022
Name of Device: CT Perfusion V1.0
Common or Usual Name: Picture archiving and communication system (PACS)
Regulation Name: Medical Image Management and Processing System
Regulatory Class: 21 CFR 892.2050
Product Code: LLZ
Predicate Device: Olea Sphere V3.0 (K152602)
- Manufacturer: Olea Medical .
- Regulation Number: 21 CFR 892.2050
- Product Code: LLZ
{5}------------------------------------------------
#### Intended Use / Indications for Use
CT Perfusion V1.0 is an automatic calculation tool indicated for use in radiology. The device is an image processing software allowing computation of parametric maps from CT Perfusion data and extraction of volumes of interest based on numerical thresholds applied to the aforementioned maps. Computation of mismatch between extracted volumes is automatically provided.
The device is intended to be used by trained professionals with medical imaging education including but not limited to, physicians and medical technicians in the imaging assessment workflow by extraction and communication of metrics from CT Perfusion dataset.
The results of CT Perfusion V1.0 are intended to be used in conjunction with other patient information and, based on professional judgment, to assist the clinician in the medical imaging assessment. Trained professionals are responsible for viewing the full set of native images per the standard of care.
The device does not alter the original image. CT Perfusion V1.0 is not intended to be used as a standalone diagnostic device and shall not be used to take decisions with diagnosis or therapeutic purposes. Patient management decisions should not solely be based on CT Perfusion V1.0 results.
CT Perfusion V1.0 can be integrated and deployed through technical platforms, responsible for transferring, storing, converting formats, notifying of detected image variations and display DICOM of imaqing data.
#### Device Description
#### Introduction
The CT perfusion V1.0 application can be used to automatically compute qualitative as well as quantitative perfusion maps based on the dynamic (first-pass) effect of a contrast agent (CA). The perfusion application assumes that the input data describes a well-defined and transient signal response following rapid administration of a contrast agent.
Olea Medical proposes CT Perfusion V1.0 as an image processing application, Picture Archiving Communications System (PACS) software module that is intended for use in a technical environment, which incorporates a Medical Image Communications Device (MICD) (21 CFR 892.2020) as its technical platform.
## CT Perfusion V1.0 interaction with the technical platform
For optimal performance, the docker needs a technical base (MICD). The technical platform allows the docker to:
- . receive the inputs;
- provide the outputs; .
- visualize the outputs as the docker has no interface. .
The technical base can support several applications encapsuled in a docker such as CT Perfusion V1.0.
{6}------------------------------------------------
## Principles of operation and technological characteristics of CT Perfusion V1.0
CT Perfusion V1.0 image processing application is designed as a docker installed on a technical platform, a Medical Image Communications Device.
Image /page/6/Figure/2 description: The image shows a diagram of the CT Perfusion V1.0 application. The input to the application is CT Perfusion data. The application processes the data and generates parametric maps, volume 1 and volume 2 segmentation, and mismatch computation. The output of the application is the processed data.
Figure 1: CT Perfusion V1.0 inputs/outputs
CT Perfusion V1.0 is a docker totally independent from the technical platform in which it is integrated:
- Input DICOM images are received by the technical platform; ●
- Relevant series are automatically identified among the images received in the platform by ● reading the relevant DICOM tags and are provided to the application;
- . The arrival of identified series will launch CT Perfusion V1.0;
- The CT Perfusion V1.0 processes the identified series;
- . The generated results are automatically pushed to the technical platform;
- . The results can be visualized with any DICOM viewer comprising but not limited to the technical platform or exported to a dedicated file location.
The CT Perfusion V1.0 application takes as input a full CT perfusion (CTP) sequence acquired following the injection of an iodine contrast agent.
By processing these input image series, the application provides the following outputs:
- . Parametric maps.
- Volume 1 and volume 2 segmentation in DICOM format. Fusion of segmented Volume 1 and 2 and CTP map could be provided in PNG and DICOM secondary captures.
- . Mismatch computation:
- Mismatch volume = Volume 2-Volume 1
- Mismatch ratio = Volume 2/Volume 1 O
- Relative Mismatch = (Volume 2-Volume 1)/Volume 2*100. O
CT Perfusion V1.0 does not contain any Al-based algorithms. All calculations are based on deterministic algorithms.
The CT Perfusion V1.0 offers automatic volume seqmentations based on a set of maps and thresholds. The user is able to tune/adjust these thresholds and the maps associated to thresholds in the configuration files.
{7}------------------------------------------------
### Substantial Equivalence
The following Predicate Device Comparison Table provides a summary of the comparison between the CT Perfusion V1.0 and its predicate device.
| CT Perfusion V1.0 | Olea Sphere® V3.0 (K152602) |
|-----------------------------------------------------------------|-----------------------------|
| Parametric maps computation | YES |
| Hypoperfused areas segmentations on maps<br>(e.g : CBF and TTP) | YES |
| Mismatch computation | YES |
To explain that the subject device and the predicate device are comparable, it is important to point out that CT Perfusion V1.0 represents a subset of functionality of Olea Sphere V3.0. Comparative performance testing was conducted using the comparable Perfusion module in Olea Sphere V3.0.
Both CT Perfusion V1.0 and Olea Sphere® V3.0 are user-defined software analysis tools used for the analysis of CT studies.
Both devices are intended for use in hospitals and imaging centers. Importantly, neither software product is used for diagnosis. Patient management decisions should not be based solely on the results of either software. Therefore, the intended use of the software is the same.
Both the CT Perfusion V1.0 and Olea Sphere V3.0 have similar technological characteristics as they both:
- . provide processing capabilities for the analysis of CT series;
- are designed to be able to process CT series; .
- . are able to provide same outputs;
- are able to automatically compute the mismatch between extracted volumes.
CT Perfusion V1.0 and Olea Sphere V3.0 have essentially equivalent features. The only difference is that Olea Sphere V3.0 is equipped with a visualization interface whereas CT Perfusion V1.0 needs to communicate with a technical platform to visualize the outputs.
This minor difference does not impact the intended use of the device or raise different questions of safety and efficacy.
#### Performance Data
Olea Medical has conducted extensive validation testing of the CT Perfusion V1.0. Internal verification and validation testing confirm that the product specifications are met and supports substantial equivalence of the intended use and technological characteristics to the predicate device.
CT Perfusion V1.0 has been validated to ensure that the system as a whole provides all the capabilities necessary to operate according to its intended use and in a manner substantially equivalent to the predicate device.
The following performance evaluations were conducted:
- Product risk assessment;
- Software modules verification tests; ●
- Software validation test; ●
- Clinical image comparison study. ●
{8}------------------------------------------------
Based on the performance as documented in the clinical image comparison study, the CT Perfusion V1.0 has a safety and effectiveness profile that is similar to the predicate device. Indeed:
- . Parametric maps result comparison: All parametric maps (CBF, CBV, MTT, TTP, Delay, tMIP) computed with CT Perfusion V1.0 and Olea Sphere® V3.0 predicate device were identical: value differences voxel-by-voxel were equal to zero; Pearson and Spearman correlation coefficients were equal to 1.
- . Volumes result comparison: Mean DICE index (similarity coefficient) was equal to 1 between CT Perfusion V1.0 and Olea Sphere® V3.0 predicate device segmentations. It could be concluded that volume shape and position were identical. For all cases, no difference was found as the volumes derived from both thresholds were similar between CT Perfusion V1.0 and Olea Sphere® V3.0 predicate device.
#### Conclusions
CT Perfusion V1.0 is substantially equivalent to the predicate device, Olea Sphere® V3.0. The CT Perfusion V1.0 has the same intended use and similar indications for use, technological characteristics, and principles of operation as its predicate device.
In addition, the minor technological differences between the CT Perfusion V1.0 and its predicate devices raise no new questions of safety or effectiveness. Performance data demonstrate that the CT Perfusion V1.0 is as safe and effective as the Olea Sphere® V3.0. Thus, the CT Perfusion V1.0 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.