Automatic Anatomy Recognition (AAR) is a software-only medical device intended for use by technicians and trained physicians to derive contours of anatomical structures from computed tomography studies for input to a radiation treatment planning system. It is only intended to work for anatomical structures in the head & neck and thoracic body regions. It is not for use on patients below 18 years of age and it relies on third party treatment planning systems to display and edit the contours.
Device Story
AAR is a cloud-based, software-only medical device for radiation therapy planning. It accepts non-contrast CT images as input; automatically processes images to derive contours of anatomical structures (organs at risk) in head, neck, and thoracic regions using deep learning algorithms; and outputs contours for use in third-party radiation treatment planning systems. Used by technicians and physicians in clinical settings. AAR operates independently of treatment delivery modality (photons, protons) or intent (curative, palliative). It provides automated segmentation without human intervention; clinicians review and edit output contours within external treatment planning software. Benefits include standardized, automated anatomical identification to support radiation treatment planning workflows.
Clinical Evidence
No clinical data. Bench testing only. Performance evaluated using segmentation accuracy tests comparing automated contours to ground truth via DICE similarity coefficients and mean 95% Hausdorff Distance (HD) calculations. Software verification and validation performed per IEC 62304.
Technological Characteristics
Software-only; cloud-deployed; Linux-based. Deep learning algorithm for automated anatomical segmentation. Compatible with DICOM 3.0 compliant non-contrast CT images and third-party treatment planning systems. No hardware, sterilization, or biocompatibility requirements.
Indications for Use
Indicated for adults (18+ years) undergoing radiation therapy requiring identification of organs at risk (OAR) in head, neck, and thoracic regions using non-contrast CT studies. Contraindicated for patients under 18 years of age.
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/10 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). The logo consists of two parts: a seal on the left and the FDA acronym with the full name of the agency on the right. The seal features an eagle with its wings spread, surrounded by text that reads "DEPARTMENT OF HEALTH & HUMAN SERVICES-USA". The right side of the logo displays the acronym "FDA" in blue, followed by the words "U.S. FOOD & DRUG ADMINISTRATION" in a larger, bolder font, also in blue.
Quantitative Radiology Solutions, LLC % Mary Vater 510(k) Consultant Medical Device Academy 345 Lincoln Hill Rd. SHREWSBURY, VT 05738
Re: K203610
Trade/Device Name: Automatic Anatomy Recognition (AAR) Regulation Number: 21 CFR 892.2050 Regulation Name: Picture Archiving And Communications System Regulatory Class: Class II Product Code: QKB Dated: March 22, 2021 Received: March 23, 2021
Dear Mary Vater:
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 requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part
April 20, 2021
{1}------------------------------------------------
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 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,
For
Thalia T. Mills, Ph.D. Director Division of Radiological Health OHT7: Office of In Vitro Diagnostics and Radiological Health Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
## Indications for Use
510(k) Number (if known) K203610
Device Name Automatic Anatomy Recognition System
#### Indications for Use (Describe)
Automatic Anatomy Recognition (AAR) is a software-only medical device intended for use by technicians and trained physicians to derive contours of anatomical structures from computed tomography studies for input to a radiation treatment planning system. It is only intended to work for anatomical structures in the head & neck and thoracic body regions. It is not for use on patients below 18 years of age and it relies on third party treatment planning systems to display and edit the contours.
| Type of Use (Select one or both, as applicable) | | | |
|-------------------------------------------------|---------------------------------------------|--|--|
| X 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
This summary of 510(k) safety and effectiveness information is submitted in accordance with the requirements of 21 CFR §807.92:
1. SUBMITTER Quantitative Radiology Solutions, LLC 3675 Market Street, Suite 200 Philadelphia, PA 19104 | USA Tel: +1.973.590.8574
Contact Person: Steve Owens Date Prepared: December 9, 2020
| II. DEVICE | |
|------------------------------|---------------------------------------------|
| Name of Device: | Automatic Anatomy Recognition |
| Classification Name: | Picture Archiving And Communications System |
| Regulation: | 21 CFR §892.2050 |
| Regulatory Class: | Class II |
| Product Classification Code: | QKB |
Ⅲ. PREDICATE DEVICE
| Predicate Manufacturer: | Xiamen Manteia Technology LTD. |
|-------------------------|--------------------------------|
| Predicate Trade Name: | AccuContour™ |
| Predicate 510(k): | K191928 |
No reference devices were used in this submission.
#### IV. DEVICE DESCRIPTION
...
Automatic Anatomy Recognition product for radiation therapy planning (AAR) is a software-only medical device and is deployed on a cloud-based platform. AAR is intended to be used on adults undergoing treatment that requires the identification of anatomical structures in the body considered to be "organs at risk" (OAR). AAR is intended to be used in the head and thoracic body regions.
AAR operates independently from the treatment plan that is subsequently created based on AARgenerated contours. Therefore, AAR is agnostic to the method of radiation treatment delivery such as photons, protons, or other, to the modality of radiation treatment such as three-dimensional conformal radiation therapy (3D-CRT), intensity modulated radiation therapy (IMRT), or other, and to the intent of radiation treatment such as definitive (curative), neoadjuvant, adjuvant, or palliative.
AAR is also agnostic to the disease process being treated in the head and neck or thoracic body regions, For example, the identification of OARs is required during the treatment of head and neck cancers such as squamous cell carcinoma, brain cancer, and lymphoma. The identification of OARs is also required during the treatment of thoracic cancers such as lung cancer, breast cancer, esophageal cancer, lymphoma, and thymoma, just to name a few.
AAR automatically processes computed tomography (CT) studies and produces contours with no human intervention. AAR does not provide the capability to modify contours. If adjustments are required, they must be performed on another system.
{4}------------------------------------------------
#### V. INDICATIONS FOR USE
Automatic Anatomy Recognition (AAR) is a software-only medical device intended for use by technicians and trained physicians to derive contours of anatomical structures from computed tomography studies for input to a radiation treatment planning system. It is only intended to work for anatomical structures in the head & neck and thoracic body regions. It is not for use on patients below 18 years of age and it relies on third party treatment planning systems to display and edit the contours.
#### COMPARISON OF TECHNOLOGICAL CHARACTERISTICS WITH THE VI. PREDICATE DEVCE
The following characteristics were compared between the subject device and the predicate device in order to demonstrate substantial equivalence:
- Indications for Use The predicate and subject device have identical indications for use. .
- . Materials - The predicate and subject device are both software-only medical devices.
- Design The predicate and subject device both utilize deep learning contouring to . automatically contour the organ-at-risk for the head, neck, and thorax.
- . Energy Source - The predicate and subject device both run within the users' existing computer system.
- Other Design Features The predicate device has additional features such as patient . management, review of processed images, automatic image registration, manual contouring functionality, and segmentation in the abdomen and pelvic regions. This additional functionality is not required to achieve the intended use for the subject device.
- . Performance Testing - The predicate and subject device conducted segmentation performance tests to evaluate the automated segmentation accuracy using DICE similarity coefficients. These tests were further supported by additional tests using a mean 95% Hausdorff Distance (HD) calculation.
| Table 1: Proposed Predicate Device | | | |
|--------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | Subject Device | Proposed Predicate Device | Rationale for SE |
| Device Name | Automatic Anatomy Recognition<br>(AAR) | AccuContourTM | N/A |
| Applicant | Quantitative Radiology Solutions | Xiamen Manteia Technology LTD. | N/A |
| 510(k) Number | TBD | K191928 | N/A |
| Decision Date | TBD | 02/28/2020 | N/A |
| Regulation<br>Number | 892.2050 | 892.2050 | Same |
| Regulation Name | Picture archiving and<br>communication system | Picture archiving and communication<br>system | Same |
| Device | Radiological Image Processing<br>Software for Radiation Therapy | Radiological Image Processing<br>Software for Radiation Therapy | Same |
| Regulatory<br>Definition | To provide semi-automatic-or fully-<br>automated radiological image<br>process and analysis tools for<br>radiation therapy. Software<br>implementing artificial intelligence<br>(AI) including non-adaptive<br>machine learning algorithms trained<br>with clinical and/or artificial<br>radiological images. In these<br>devices, the algorithm training<br>images typically impact device. | To provide semi-automatic or fully-<br>automated radiological image<br>process and analysis tools for<br>radiation therapy. Software<br>implementing artificial intelligence<br>(AI) including non-adaptive machine<br>learning algorithms trained with<br>clinical and/or artificial radiological<br>images. In these devices, the<br>algorithm training images typically<br>impact device performance. AI based | Both the subject<br>device and the<br>predicate fall under<br>the regulatory<br>definition for<br>892.2050, product<br>code QKB. |
| Product Code | | | |
| | performance. AI based radiological<br>image processing software is<br>intended to be used in the workflow<br>of radiation therapy. Adaptive AI<br>algorithms are not within the scope<br>of this product code. Primary<br>radiation dose calculation or plan<br>optimization for treatment planning<br>are not within scope of the product<br>code. | radiological image processing<br>software is intended to be used in the<br>workflow of radiation therapy.<br>Adaptive AI algorithms are not<br>within the scope of this product code.<br>Primary radiation dose calculation or<br>plan optimization for treatment<br>planning are not within scope of the<br>product code. | |
| Product Code | QKB | QKB | Same |
| Classification | Class II | Class II | Same |
| 510(k) Review<br>Panel | Radiology | Radiology | Same |
| Combination<br>Product? | No | No | Same |
| Rx or OTC? | RX | RX | Same |
| Intended Use /<br>Indications for Use | Automatic Anatomy Recognition<br>(AAR) is a software-only medical<br>device intended for use by<br>technicians and trained physicians<br>to derive contours of anatomical<br>structures from computed<br>tomography studies for input to a<br>radiation treatment planning system.<br>It is only intended to work for<br>anatomical structures in the head &<br>neck and thoracic body regions. It is<br>not for use on patients below 18<br>years of age and it relies on third<br>party treatment planning systems to<br>display and edit the contours. | It is used by radiation oncology<br>department to register multimodality<br>images and segment (non-contrast)<br>CT images, to generate needed<br>information for treating planning,<br>treatment evaluation and treatment<br>adaptation. | Same |
| Image process<br>functions | 1) Deep learning contouring: it<br>can automatically contour<br>anatomical structures, including<br>head and neck, thorax (for both<br>male and female). | 1) Deep learning contouring: it can<br>automatically contour the organ-<br>at-risk, including head and neck,<br>thorax, abdomen and pelvis (for<br>both male and female);<br>2) Automatic Registration, and<br>3) Manual Contour | Same. AAR contains<br>only Deep Learning<br>contouring |
| General<br>Functionalities | Receive, add/edit/delete,<br>transmit, input/export, medical<br>images and DICOM data | Receive, add/edit/delete,<br>transmit, input/export, medical<br>images and DICOM data;Patient management;Review of processed images;Open and Save of files. | Same. AAR only<br>receives,<br>adds/edits/deletes,<br>transmits,<br>inputs/exports<br>medical images and<br>DICOM data |
| Operating Systems | Linux | Windows | QRS utilizes Linux as<br>this OS is more<br>secure as compared<br>to Windows |
| Segmentation Features | | | |
| Algorithm | Deep Learning | Deep Learning | Same |
| Compatible<br>Modality | Non-Contrast CT | Non-Contrast CT | Same |
| Compatible<br>Scanner Models | No limitation on scanner model,<br>DICOM 3.0 compliance required | No limitation on scanner model,<br>DICOM 3.0 compliance required | Same |
| Compatible<br>Treatment<br>Planning System | No limitation on TPS model,<br>DICOM 3.0 compliance required. | No limitation on TPS model, DICOM<br>3.0 compliance required. | Same |
| Contraindications | AAR is not intended for use on<br>patients below 18 years of age; | None | AAR is intended for<br>use in adults |
| Segmentation Features | | | |
| Performance<br>Testing | Segmentation Performance Test<br>Evaluated automated<br>segmentation accuracy non-<br>inferiority using DICE<br>similarity coefficients. Software Verification and<br>Validation testing | Segmentation Performance Test<br>Evaluated automated<br>segmentation accuracy non-<br>inferiority using DICE similarity<br>coefficients. Registration Performance Test | Segmentation<br>Performance Testing<br>is equivalent.<br>Registration<br>performance test is<br>N/A because the<br>subject device does<br>not do registration. |
{5}------------------------------------------------
{6}------------------------------------------------
### VII. PERFORMANCE DATA
The following performance data were provided in support of the substantial equivalence determination.
## Sterilization & Shelf-life Testing
Not Applicable (Standalone Software)
### Biocompatibility Testing
Not Applicable (Standalone Software)
### Electrical safety and electromagnetic compatibility (EMC)
Not Applicable (Passive Device)
### Software Verification and Validation Testing
Software Verification and Validation Testing included testing at the unit, integration, and system level per IEC 62304 standard.
### Mechanical and acoustic Testing
Not Applicable (Standalone Software)
## Animal Study
Animal performance testing was not required to demonstrate safety and effectiveness of the device.
### Human Clinical Performance Testing
Clinical testing was not required to demonstrate the safety and effectiveness of the device.
### VIII. CONCLUSIONS
Based on the comparison and analysis above, the proposed devices are determined to be Substantially Equivalent (SE) to the predicate devices.
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.