Improved response rate for 'Fluid Bolus Suggested' prompts compared to the predicate device.
Archived dataset from US IDE Study G170204: 1229 data points from 307 patients across 9 independent U.S. sites.
—
—
—
Indications for Use
The Edwards Lifesciences Acumen Assisted Fluid Management (AFM) Software Feature provides the clinician with physiological insight into a patient's estimated response to fluid therapy and the associated hemodynamics. The Acumen AFM Software Feature is intended for use in surgical patients ≥18 years of age, that require advanced hemodynamic monitoring. The Acumen AFM Software Feature offers suggestions regarding the patient's physiological condition and estimated response to fluid therapy. Acumen AFM fluid administration suggestions are offered to the clinician; the decision to administer a fluid bolus is made by the clinician, based upon review of the patient's hemodynamics. No therapeutic decisions should be made based solely on the Assisted Fluid Management suggestions.
Device Story
Acumen AFM Software Feature provides clinicians with fluid responsiveness insights. Input: real-time patient hemodynamic data. Operation: core AFM algorithm generates fluid bolus suggestions; new AFM Prompt Reclassifier (PR) algorithm analyzes current hemodynamics to confirm or reclassify original prompts (e.g., 'Test Bolus' to 'Fluid Bolus'). Output: visual prompts on monitoring platform. Context: used in surgical settings by clinicians to assist in fluid management decisions. Benefit: improves response rate of fluid bolus suggestions, optimizing hemodynamic management. Clinicians review output alongside patient hemodynamics; no therapeutic decisions made solely on software suggestions.
Clinical Evidence
Bench testing only. Algorithm performance validated using an archived dataset from US IDE Study G170204 (1,229 data points from 307 patients across 9 sites). Comparison of the core AFM algorithm with and without the new AFM Prompt Reclassifier (PR) algorithm demonstrated an improved response rate for 'Fluid Bolus Suggested' prompts, meeting predefined acceptance criteria. Software verification and validation performed per ANSI/AAMI/IEC 62304 and relevant FDA guidance.
Technological Characteristics
Software-based feature; core AFM algorithm combined with new AFM Prompt Reclassifier (PR) algorithm. Operates on Hemo Sphere Advanced Monitoring Platform. Complies with ANSI/AAMI/IEC 62304 software life cycle processes. No hardware modifications.
Indications for Use
Indicated for surgical patients ≥18 years of age requiring advanced hemodynamic monitoring to provide physiological insight into fluid therapy response.
Regulatory Classification
Identification
The adjunctive open loop fluid therapy recommender is a prescription device that uses software algorithms to analyze cardiovascular vital signs and predict a patient's estimated response to fluid therapy. The device is intended for adjunctive use with other physical vital sign parameters and patient information and is not intended to independently direct therapy.
Special Controls
In combination with the general controls of the FD&C Act, the adjunctive open loop fluid therapy recommender is subject to the following special controls:
*Classification.* Class II (special controls). The special controls for this device are:(1) Clinical performance testing under anticipated conditions of use must fulfill the following:
(i) A summary of the clinical performance testing must include the relevant patient demographics, and any statistical techniques used for analyzing the data;
(ii) Subjects must be representative of the intended use population for the device. Any selection criteria or sample limitations must be fully described and justified;
(iii) Testing must demonstrate the recommendation consistency using the expected range of data sources and data quality encountered in the intended patients, users, and environments; and
(iv) Testing must evaluate the relationship between algorithm recommendations, therapeutic actions, and predicted physiological event or status.
(2) A software description and the results of verification and validation testing based on a comprehensive hazard analysis and risk assessment must be provided, including:
(i) A full characterization of the software technical parameters, including algorithms;
(ii) A description of the expected recommendation, accounting for differences in patient condition and environment;
(iii) A description of all mitigations for user error or failure of any subsystem components (including signal detection, signal analysis, data display, and storage) that affect the device's recommendations;
(iv) A characterization of algorithm sensitivity to variations in user inputs;
(v) A characterization of sensor accuracy and performance;
(vi) A description of sensor data quality control measures; and
(vii) Safeguards to reduce the possibility of fluid overload.
(3) A scientific justification for the validity of the algorithm(s) must be provided. This justification must include non-clinical verification and validation of the algorithm calculations and clinical validation using an independent data set.
(4) A human factors and usability engineering assessment must be provided.
(5) Labeling must include:
(i) A description of what the device measures, how the device decides to issue recommendations, and the expected range of frequency of recommendations, while accounting for differences in patient condition and environment;
(ii) Detailed information regarding limitations of the device's algorithm, and key assumptions made when the device issues a recommendation;
(iii) Warnings identifying sensor acquisition factors that may impact measurement results;
(iv) Warnings identifying user errors that affect the device's recommendations;
(v) Detailed information regarding the expected impact of user input errors on the device recommendations;
(vi) Guidance for interpretation of the device's recommendations, including a description that the recommendation is adjunctive to other physical vital sign parameters and patient information;
(vii) Description of the impact of the compatible sensor(s) on the device's performance;
(viii) The expected performance of the device for all intended patients, users, and environments;
(ix) Relevant characteristics of the patients studied in the clinical validation (such as age, gender, race or ethnicity, and patient condition) and a summary of validation results; and
(x) Description of the software safeguards that are in place to prevent fluid overload, and description of any limitation of the software safeguards.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). On the left is the Department of Health & Human Services logo. To the right of that is the FDA logo, which is a blue square with the letters "FDA" in white. To the right of the blue square is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
August 2, 2024
Edwards Lifesciences, LLC Kshama Pai Manager, Regulatory Affairs One Edwards Way Irvine. California 92614
Re: K233984
Trade/Device Name: Acumen Assisted Fluid Management (AFM) Software Feature Regulation Number: 21 CFR 870.5600 Regulation Name: Adjunctive Open Loop Fluid Therapy Recommender Regulatory Class: Class II Product Code: OMS Dated: July 3, 2024 Received: July 3, 2024
Dear Kshama Pai:
We have reviewed your section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (the Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device"
{1}------------------------------------------------
(https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality System (QS) regulation (21 CFR Part 820), which includes, but is not limited to, 21 CFR 820.30. Design controls; 21 CFR 820.90. Nonconforming product; and 21 CFR 820.100, Corrective and preventive action. Please note that regardless of whether a change requires premarket review. the OS regulation requires device manufacturers to review and approve changes to device design and production (21 CFR 820.30 and 21 CFR 820.70) and document changes and approvals in the device master record (21 CFR 820.181).
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting of medical device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reportingcombination-products); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about 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.
Aneesh S. Deoras -S
for
LCDR Stephen Browning Assistant Director Division of Cardiac Electrophysiology, Diagnostics, and Monitoring Devices Office of Cardiovascular Devices Office of Product Evaluation and Quality
{2}------------------------------------------------
Enclosure
{3}------------------------------------------------
#### Indications for Use
Submission Number (if known)
K233984
Device Name
Acumen Assisted Fluid Management (AFM) Software Feature
Indications for Use (Describe)
The Edwards Lifesciences Acumen Assisted Fluid Management (AFM) Software Feature provides the clinician with physiological insight into a patient's estimated response to fluid therapy and the associated hemodynamics. The Acumen AFM Software Feature is intended for use in surgical patients ≥18 years of age, that require advanced hemodynamic monitoring. The Acumen AFM Software Feature offers suggestions regarding the patient's physiological condition and estimated response to fluid therapy. Acumen AFM fluid administration suggestions are offered to the clinician; the decision to administer a fluid bolus is made by the clinician, based upon review of the patient's hemodynamics. No therapeutic decisions should be made based solely on the Assisted Fluid Management suggestions.
Type of Use (Select one or both, as applicable)
> Prescription Use (Part 21 CFR 801 Subpart D)
Over-The-Counter Use (21 CFR 801 Subpart C)
#### CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
#### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff(@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{4}------------------------------------------------
| 510(k) #: | K233984 | 510(k) Summary | Prepared on: 2024-07-02 |
|-----------|---------|----------------|-------------------------|
|-----------|---------|----------------|-------------------------|
| Contact Details | 21 CFR 807.92(a)(1) |
|-----------------|---------------------|
|-----------------|---------------------|
| Applicant Name | Edwards Lifesciences, LLC |
|-----------------------------|-----------------------------------------------|
| Applicant Address | One Edwards Way Irvine CA 92614 United States |
| Applicant Contact Telephone | 9492504457 |
| Applicant Contact | Ms. Kshama Pai |
| Applicant Contact Email | kshama_pai@edwards.com |
| Device Name | 21 CFR 807.92(a)(2) |
|-------------|---------------------|
|-------------|---------------------|
| Device Trade Name | Acumen Assisted Fluid Management (AFM) Software Feature |
|---------------------|---------------------------------------------------------|
| Common Name | Adjunctive open loop fluid therapy recommender |
| Classification Name | Adjunctive Open Loop Fluid Therapy Recommender |
| Regulation Number | 870.5600 |
| Product Code | QMS |
| Legally Marketed Predicate Devices | 21 CFR 807.92(a)(3) |
|------------------------------------|---------------------|
|------------------------------------|---------------------|
| Predicate # | Predicate Trade Name (Primary Predicate is listed first) | Product Code |
|-------------|-----------------------------------------------------------------------------------------------------|--------------|
| K223865 | Acumen Assisted Fluid Management (AFM) Software Feature on Hemo Sphere Advanced Monitoring Platform | QMS |
| Device Description Summary | 21 CFR 807.92(a)(4) |
|----------------------------|---------------------|
|----------------------------|---------------------|
### Device Description Summary
The Acumen AFM Software Feature (core AFM algorithm + AFM Graphical User Interface) was originally granted in De Novo, DEN190029, on November 13, 2020, to inform clinicians about a patient's fluid responsiveness. The performance of the AFM Software Feature in predicting a patient's fluid responsiveness is measured using response rate and is calculated by reporting the percentage of followed AFM recommendations ("Fluid Bolus Suggested" and "Test Bolus Suggested" prompts) that have the desired change in stroke volume (SV), divided by the total number of AFM recommendations.
With this submission, Edwards is seeking clearance for the AFM Prompt Reclassifier algorithm (AFM PR algorithm) to the Acumen AFM Software Feature. The AFM Prompt Reclassifier algorithm is intended to be used in conjunction with the core AFM algorithm to re-assess the fluid bolus recommendations provided by the core AFM alqorithm. It analyzes the patient's current hemodynamics for either confirming (corroborating) the original prompt or reclassifying the prompts (i.e., reclassify a "Test Bolus Suggested" prompt to a "Fluid Bolus Suggested" prompt or vice versa). In doing so, it acts as a secondary check for the fluid bolus prompts such that a greater number of the "Fluid Bolus Suggested" prompts lead to the desired change in stroke volume. Through refined prompt adjustments informed by real-time hemodynamic data, the AFM PR algorithm aims to improve patient responsiveness, thereby optimizing the impact of the AFM Software Feature on patient hemodynamics.
### Intended Use/Indications for Use
21 CFR 807.92(a)(5)
{5}------------------------------------------------
The Edwards Lifesciences Acumen Assisted Fluid Management (AFM) Software Feature provides the clinician with physiological insight into a patient's estimated response to fluid therapy and the associated hemodynamics. The Acumen AFM Software is intended for use in surgical patients ≥18 years of age, that require advanced hemodynamic monitoring. The Acumen AFM Software Feature offers suggestions regarding the patient's physiological condition and estimated response to fluid therapy. Acumen AFM fluid administration suggestions are offered to the clinician; the decision to administer a fluid bolus is made by the clinician, based upon review of the patient's hemodynamics. No therapeutic decisions should be made based solely on the Assisted Fluid Management suggestions.
## Indications for Use Comparison
#### 21 CFR 807.92(a)(5)
The subject and predicate device (most recently cleared in K223865 on June 09, 2023) have the same intended use and indications for use.
# Technological Comparison
## 21 CFR 807.92(a)(6)
The subject and predicate device have the following similarities:
• The subject and predicate devices utilize the same predictive core AFM algorithm and the same fundamental technology) to obtain AFM output fluid bolus prompts.
• The functionality and use of the AFM Software Feature remains unchanged. No new output prompts or suggestions are generated and hence, the modifications made to the AFM Software Feature do not constitute a new intended use.
· The timing, volume, and number of fluid bolus prompts of the AFM Software Feature remain equivalent between the subject and predicate device.
• The sensitivity, specificity, positive value and negative predictive value remain the same between the subject device and predicate device.
The following key difference exists between the subject and predicate devices:
· The subject device utilizes an additional algorithm with the cleared core AFM algorithm, which leads to an improved response rate of the "Fluid Bolus Suggested" prompts (i.e., greater number of these prompts lead to desired changes in patient's stroke volume).
#### Non-Clinical and/or Clinical Tests Summary & Conclusions 21 CFR 807.92(b)
Software verfication and validation activities were performed in accordance with ANSI/AAM/IEC 62304, Medical Device Software -Software Life Cycle Processes, FDA's Guidance on Content of Premarket Submissions for Software in Medical Devices (issued June 14, 2023), General Principles of Software Validation (issued January 11, 2002), and Applying Human Factors and Usability Engineering to Medical Devices (issued February 3, 2016), as well as the specified in De Novo Grant, DEN190029.
Algorithm performance was analyzed on the archived dataset from the US IDE Study, G170204. This dataset consisted of 1229 data points from 307 patients from 9 independent U.S. sites. The validation was to demonstrate the impact on the response rate of the AFM Software Feature's fluid bolus prompts due to the addition of AFM Prompt Reclassifier algorithm. The resulting rates for the AFM PR algorithm and predicate/cleared core AFM algorithm were compared and demonstrated an improvement in response rate for "Fluid Bolus Suggested" prompts, thus demonstrating that the AFM PR algorithm met the predefined acceptance criteria. The results demonstrate that the differences in the fluid bolus suggestions introduced by the AFM PR algorithm do not raise any concerns of safety and effectiveness for the cleared AFM Software feature. These non-clinical design control activities form the basis for the substantial equivalence between the predicate/ existing AFM Software feature.
The results of these performance testing activities demonstrate that the specified design requirements were met, and that the modifications in scope of this submission do not adversely and effectiveness of the AFM Software Feature. Based on the information presented within this 510(k) and the testing performed, the AFM Software Feature with subject modifications for introduction of AFM PR algorithm is substantially equivalent to the predicate AFM Software Feature (last cleared in K223865 on June 09, 2023).
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.