K171463 · Fujifilm Medical Systems U.S.A, Inc. · LLZ · Sep 29, 2017 · Radiology
Device Facts
Record ID
K171463
Device Name
ASPIRE Bellus II
Applicant
Fujifilm Medical Systems U.S.A, Inc.
Product Code
LLZ · Radiology
Decision Date
Sep 29, 2017
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 892.2050
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
ASPIRE Bellus II is medical imaging software that is intended to provide trained medical imaging professionals, including Physicians and Radiologists, with tools to aid them in reading, interpreting, reporting. This product accepts DICOM compliant medical images acquired from a variety of imaging devices including, MG, CT, PT, MR, CR, DX, and US, etc. This product also provides general 2D/3D viewing and general image processing, measurements, annotations, reporting, printing, storing, and general image administration tools, etc. This product does not accept lossy compressed mammographic images, which should not be used for primary diagnostic interpretation. Display monitors connected to this product for diagnostic interpretation of mammographic images must be approved for use in digital mammography. All images sent to or imported into this product must conform to regulatory requirements. Image quality must conform to applicable quality guidelines.
Device Story
ASPIRE Bellus II is medical imaging software for viewing, processing, and interpreting DICOM-compliant images (MG, CT, PT, MR, CR, DX, US). Operates as a client-side viewer receiving data from acquisition systems or PACS via network. Provides 2D/3D visualization, measurements, annotations, and reporting tools. Used by physicians and radiologists in clinical settings to facilitate diagnostic interpretation. Output displayed on monitors; assists clinicians in clinical decision-making by providing enhanced visualization and workflow tools. Benefits include efficient image review and reporting.
Clinical Evidence
No clinical data. Bench testing only. Verification and validation included software unit testing, integration testing, and system-level testing to confirm functionality and performance against requirements.
Technological Characteristics
Software-only PACS; platform-independent browser-based UI. Supports DICOM (PS 3.1-3.18). Connectivity via network to imaging modalities and PACS. Security via Windows Authentication. Developed per IEC 62304 and ISO 14971. Programming languages: C++, C#, HTML, JavaScript.
Indications for Use
Indicated for trained medical imaging professionals, including Physicians and Radiologists, to aid in reading, interpreting, and reporting medical images. Supports MG, CT, PT, MR, CR, DX, and US modalities. Contraindicated for use with lossy compressed mammographic images for primary diagnostic interpretation.
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/2 description: The image shows the logo for the United States Department of Health and Human Services. The logo consists of a circular seal with the text "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" arranged around the perimeter. Inside the circle is a stylized image of three human profiles facing to the right, stacked on top of each other.
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-0002
FUJIFILM Medical Systems U.S.A., Inc. Jyh-Shyan Lin Senior Manager, Regulatory, Ouality and Clinical Affairs 419 West Avenue Stamford, Connecticut 06902
September 29, 2017
Re: K171463
Trade/Device Name: ASPIRE Bellus II Regulation Number: 21 CFR 892.2050 Regulation Name: Picture Archiving And Communications System Regulatory Class: Class II Product Code: LLZ Dated: August 25, 2017 Received: August 28, 2017
Dear Jyh-Shyan Lin:
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. 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 801); medical device reporting (reporting of medical device
{1}------------------------------------------------
related adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please contact the Division of Industry and Consumer Education (DICE) at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm. 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
http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm for the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
You may obtain other general information on your responsibilities under the Act from the Division of Industry and Consumer Education (DICE) at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm.
Sincerely,
Michael D. O'Hara For
Robert A. Ochs, Ph.D Director Division of Radiological Health Office of In Vitro Diagnostics and Radiological Health Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
## Indications for Use
510(k) Number (if known) K171463
Device Name ASPIRE Bellus II
#### Indications for Use (Describe)
ASPIRE Bellus II is medical imaging software that is intended to provide trained medical imaging professionals, including Physicians and Radiologists, with tools to aid them in reading, interpreting, This product accepts DICOM compliant medical images acquired from a variety of imaging devices including, MG, CT, PT, MR, CR, DX, and US, etc. This product also provides general 2D/3D viewing and general image processing, measurements, annotations, reporting, printing, storing, and general image administration tools, etc.
This product does not accept lossy compressed mammographic images, which should not be used for primary diagnostic interpretation. Display monitors connected to this produt for diagnostic interpretation of mammographic images must be approved for use in digital mammography. All images sent to or imported into this product must conform to regulatory requirements. Image quality must conform to applicable quality guidelines.
| Type of Use (Select one or both, as applicable) | |
|--------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------|
| <div> <span> <span style="font-size:16px">✖</span> Prescription Use (Part 21 CFR 801 Subpart D) </span> </div> | <div> <span> <span style="font-size:16px">☐</span> Over-The-Counter Use (21 CFR 801 Subpart C) </span> </div> |
### 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
| Date Prepared: | August 25, 2017 |
|-----------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Submitter's Information: | FUJIFILM Medical Systems U.S.A., Inc.<br>419 West Avenue<br>Stamford, Connecticut 06902<br>Telephone: (301) 251-1092<br>Fax: (203) 602-3785<br>Contact: Jyh-Shyan Lin |
| Device Trade Name: | ASPIRE Bellus II |
| Device Common Names: | Picture Archiving and Communications System (PACS) |
| Device Clasification Name: | System, Image Processing, Radiological |
| Product Code: | LLZ |
| Regulation Number: | 21 CFR 892.2050 |
| Device Class: | Class II |
| Panel: | Radiology |
| Primary Predicate Device: | Synapse PACS 5.1.0 (K160108)<br>FUJIFILM Medical Systems U.S.A., Inc. |
| Reference Predicate Device: | Senolris (K160937)<br>GE Healthcare |
{4}------------------------------------------------
## 1 . Description of the Device
ASPIRE Bellus II is medical application software with speedy image display and intelligent functions by image processing technologies. This application can support user to efficiently perform interpretation of examination images and make a diagnosis using various modality images and generate Mammography reports for diagnostic/screening purposes. ASPIRE Bellus II can receive various diagnostic images directly from image acquisition systems or PACS via network using DICOM protocol. Images are displayed on viewer monitors for doctors' review.
### 2. Indications for Use
ASPIRE Bellus II is medical imaging software that is intended to provide trained medical imaging professionals, including Physicians and Radiologists, with tools to aid them in reading, interpreting, reporting. This product accepts DICOM compliant medical images acquired from a variety of imaging devices including, MG, CT, PT, MR, CR, DX, and US, etc. This product also provides general 2D/3D viewing and general image processing, measurements, annotations, reporting, printing, storing, and general image administration tools, etc.
This product does not accept lossy compressed mammographic images, which should not be used for primary diagnostic interpretation. Display monitors connected to this product for diagnostic interpretation of mammographic images must be approved for use in digital mammography. All images sent to or imported into this product must conform to regulatory requirements. Image quality must conform to applicable quality guidelines.
### 3. Substantial Equivalence Comparison
ASPIRE Bellus II has the same intended use, similar labeling, and clinical application tools as those of the cleared primary predicate devices Synapse PACS 5.1.0 (K160108). The device features and technical characteristics comparison with predicates is shown as Table 1. Device Features and Technical Characteristics Comparison Matrix, and Table 2. Device Features and Technical Characteristics Comparison Matrix for displaying Mammography Tomosynthesis images.
| Device Parameters | ASPIRE Bellus II<br>(This submission) | Synapse PACS 5.1.0<br>(K160108)<br>(Primary predicate) |
|-------------------------------------------------------------------------------|--------------------------------------------------------------|---------------------------------------------------------|
| Product availability | Provided as Software only | Provided as Software only |
| Operating Systems | Windows 7 Professional SP1<br>(64bit)/Windows 8.1/Windows 10 | Windows<br>XP/Vista/Windows7/Windo<br>ws8.1 |
| Device Parameters | ASPIRE Bellus II<br>(This submission) | Synapse PACS 5.1.0<br>(K160108)<br>(Primary predicate) |
| Web Browser | Internet Explorer Version: 11 | Internet Explorer Version:<br>10 or 11 or Google Chrome |
| Database and file access<br>method | Web based (http(s)) | Web based (http(s)) |
| Display of Digital Mammography<br>Images | Yes | Yes |
| Process of Digital<br>Mammography (Non-Processed<br>or For Process) Images | Yes | Yes |
| On-demand access to database<br>and images | Yes | Yes |
| Viewing study lists | Yes | Yes |
| Decompression for compressed<br>images before display | Yes | Yes |
| Display images | Yes | Yes |
| Viewing report | Yes | Yes |
| Hanging Protocol | Yes | Yes |
| Spine labeling | Yes | Yes |
| Reference line display | Yes | Yes |
| Key images identification | Yes | Yes |
| Link multiple series | Yes | Yes |
| Measurement Tools | Yes | Yes |
| Annotation Tools | Yes | Yes |
| Standard Image Manipulation<br>Tools (Window width/level,<br>Zoom, Pan, etc.) | Yes | Yes |
| FCR IPSS for Fuji-CR-images | Yes | Yes |
| CT IPSS for CT images | Yes | Yes |
| Orthogonal and Oblique Multi<br>Planar Reconstruction (MPR) | Yes | Yes |
| Maximum, Average, and<br>Minimum Intensity Projection<br>(MIP, MPVR, MinIP) | Yes | Yes |
| Independent Window/Level of<br>upper and lower images in | Yes | Yes |
| Device Parameters | ASPIRE Bellus II<br>(This submission) | Synapse PACS 5.1.0<br>(K160108)<br>(Primary predicate) |
| Fusion Study | | |
| Save Window/Level Preferences | Yes | Yes |
| Multi-Modal Fusion to include<br>MR/PET/NM/and CT | Yes | Yes |
| Compare Current Study to<br>previous study in Fusion View | Yes | Yes |
| Compare Current Study to Prior<br>Study in Compare Mode | Yes | Yes |
| Image and Data Processing | Client side (Image Viewer) | Server side |
| Technology Platform (Client) | Platform Independent (Browser<br>based UI) | Platform Independent<br>(Browser based UI) |
| Technology Platform (Server) | Windows 7 Professional SP1<br>(64bit)/Windows 10 Pro (64bit) | Window server |
| System Security | Windows Authentication | Windows Authentication |
| Programming Language(s)<br>(Synapse Client) | C++, C#,<br>HTML, JavaScript | Javascript (TypeScript),<br>HTML5, CSS |
### Table 1. Device Features and Technical Characteristics Comparison Matrix
{5}------------------------------------------------
{6}------------------------------------------------
# Table 2. Device Features and Technical Characteristics Comparison Matrix for functions for displaying Mammography Tomosynthesis images
| Device Parameters | ASPIRE Bellus II<br>(This submission) | Senolris<br>(K160937)<br>(Reference predicate) |
|------------------------------------------------------------------------------------------|---------------------------------------|------------------------------------------------|
| Support Multi-vendor Digital<br>Breast Tomography | Yes | Yes |
| Drive multi-modality<br>workflow from the PACS<br>study list, including<br>tomosynthesis | Yes | Yes |
| The ability to include<br>tomosynthesis images in the<br>hanging protocol | Yes | Yes |
| The display of synthetized<br>2D image | Yes | Yes |
{7}------------------------------------------------
### 4. Safety Information
ASPIRE Bellus II introduces no new safety or efficacy issues other than those already indentified with the predicate device. The Risk Management and the results of the Hazard Analysis combined with the appropriate preventive measures taken indicate that the device is of moderate concern as per the May 11, 2005 issue of the "Guidance for the Content of Premarket Submission for Software Contained in Medical Devices." The ASPIRE Bellus II labeling contains instructions for use and necessary cautions, warnings and notes to provide the safe and effective use of the device.
### 5. Testing and Performance Information
### Nonclinical testing result:
The purpose of Software Development Process for ASPIRE Bellus II is to carry out the activities relating to the establishment of the software development plan (or plans) for definitely conducting software requirement analysis, architectural design, the detailed design, unit implementation and verification, software integration testing, software system test, software release, software maintenance. The main activities in software development process are described as follows.
- Software development plan ●
- Update of software development plan ●
- Software requirements analysis ●
- Software Architectural Design
- Software Detailed Design ●
- Software Unit Implementation and Verification .
- . Software Integration and Integration Testing
- Software System Testing .
- . Software Release
### Clinical tests:
The subject of this 510(k) notification, ASPIRE Bellus II did not require clinical studies to support safety and effectiveness of the software.
### Verification and Validation:
Software verification and validation have been performed by the following testing activities as defined in the procedure.
- . Unit test: Code verification has covered unit level verification activities and no independent unit testing was planned.
{8}------------------------------------------------
- Integration test: According to the procedure, no specific integration test was planned, but ● the test cases for integration were included in the initial part of system test including system software build process, which integrates all software modules, and testing using the build results.
- . System test: System test has been executed throughout the design verification phase and design validation phase.
### Cybersecurity:
The confidentiality, integrity and availability are maintained by ASPIRE Bellus II in accordance with Section 6 of the Content of Premarket Submissions for Management of Cybersecurity in Medical Devices; Guidance for Industry and Food and Drug Administration Staff (October 2, 2014).
ASPIRE Bellus II is connected through DICOM standard to medical devices such as CT, MR, CR, US, NM, PT, XA, etc. and to a PACS system storing data generated by these medical devices, and it retrieves image data via network communication based on the DICOM standard. Therefore ASPIRE Bellus II assure an adequate degree of protection for cybersecurity.
### Performance standards:
- . Digital Imaging and Communications in Medicine (DICOM) Set (PS 3.1 - 3.18).
- Medical device software Software life cycle processes (IEC 62304 First edition 2006-05). .
- Medical devices Application of risk management to medical devices (14971 Second . Edition 2007-03-01).
## 6. Conclusion
Performance tests were conducted to test the functionality of the subject device, ASPIRE Bellus II. Results of all conducted testing were acceptable in supporting the claim of substantial equivalence.
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.