K254265 · Videomed Srl ( a Baxter Healthcare Corp company) · LLZ · May 27, 2026 · Radiology
Device Facts
Record ID
K254265
Device Name
Helion Viewer Suite
Applicant
Videomed Srl ( a Baxter Healthcare Corp company)
Product Code
LLZ · Radiology
Decision Date
May 27, 2026
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 892.2050
Device Class
Class 2
Attributes
Software as a Medical Device
Indications for Use
Helion Viewer Suite is a software device for displaying DICOM data and medical images. It includes functions for image review, image manipulation, annotations, and 3D visualization (Multiplanar reconstructions and 3D volume rendering). Helion Viewer Suite is not intended for primary image diagnosis or review of mammography images. Helion Viewer Suite is not intended as the primary source for identification of surgical structures. Helion Viewer Suite is not intended for performing any measurements for diagnostic, treatment, or therapy, but only for reference purposes
Device Story
Helion Viewer Suite is a client-server software for displaying/annotating 2D radiological images and 3D visualizations (MPR, volume rendering). It consists of two modules: 'Fluid Touchless' for OR use via gesture-controlled monitors, and 'Anywhere Streaming' for pre/post-surgery review on Windows PCs. Inputs are DICOM-compliant images. The device transforms these into visual outputs for healthcare professionals to facilitate collaboration and reference. It does not perform diagnostic measurements; output is for reference only. It benefits patients by enabling surgical teams to access and manipulate imaging data in the OR and clinical settings, supporting workflow efficiency.
Clinical Evidence
Bench testing only. Verification and validation activities assessed distance, angle, Cobb angle, area, and HU value annotations using standardized phantom datasets and synthetic images. Distance measurements verified to ±0.1 cm; angles to ±1 degree; area to ±1%; HU values to ±1 unit. All functions met predefined acceptance criteria.
Technological Characteristics
Client-server software; DICOM-compliant. Interaction via mouse/keyboard (Windows) or gesture recognition sensor (OR). Standards: ISO 14971 (Risk Management), IEC 62366-1 (Usability), IEC 62304 (Software Lifecycle), NEMA PS 3.1-3.20 (DICOM).
Indications for Use
Indicated for display of DICOM data and medical images for reference purposes. Intended for use by trained healthcare professionals (surgeons/surgical teams) for non-diagnostic image review, manipulation, annotation, and 3D visualization. Contraindicated for primary image diagnosis, review of mammography images, primary identification of surgical structures, or diagnostic/therapeutic measurements.
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}
FDA U.S. FOOD & DRUG ADMINISTRATION
May 27, 2026
Videomed Srl (a Baxter Healthcare Corp company)
Dania Di Pietro Paolo
Sr. Specialist, Regulatory Affairs
Via Cesare Battisti N. 31/C
Limena (Pd), 35010
Italy
Re: K254265
Trade/Device Name: Helion Viewer Suite
Regulation Number: 21 CFR 892.2050
Regulation Name: Medical Image Management And Processing System
Regulatory Class: Class II
Product Code: LLZ
Dated: [NOTE: Use date of most recent supplement]
Received: April 27, 2026
Dear Dania Di Pietro Paolo:
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.
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K254265 - Dania Di Pietro Paolo
Page 2
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" (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 Management System Regulation (QMSR) (21 CFR Part 820), which includes, but is not limited to, ISO 13485 clause 7.3 (Design controls), ISO 13485 clause 8.3 (Nonconforming product), ISO 13485 clause 8.5.2 (Corrective action), and ISO 13485 clause 8.5.3 (Preventative action). Please note that regardless of whether a change requires premarket review, the QMSR requires device manufacturers to review and approve changes to device design and production (ISO 13485 clause 7.3 and ISO 13485 clause 7.5) and document changes and approvals in the Medical Device File (ISO 13485 clause 4.2.3).
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-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-reporting-combination-products); good manufacturing practice requirements as set forth in the Quality Management System Regulation (QMSR) (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.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
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-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/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-devices/device-advice-comprehensive-regulatory-
{2}
K254265 - Dania Di Pietro Paolo
Page 3
assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
Jessica Lamb, Ph.D.
Assistant Director
Imaging Software Team
DHT8B: Division of Radiological Imaging Devices and Electronic Products
OHT8: Office of Radiological Health
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
| Indications for Use | | |
| --- | --- | --- |
| Please type in the marketing application/submission number, if it is known. This textbox will be left blank for original applications/submissions. | K254265 | ? |
| Please provide the device trade name(s). | | ? |
| Helion Viewer Suite | | |
| Please provide your Indications for Use below. | | ? |
| Helion Viewer Suite is a software device for displaying DICOM data and medical images. It includes functions for image review, image manipulation, annotations, and 3D visualization (Multiplanar reconstructions and 3D volume rendering). Helion Viewer Suite is not intended for primary image diagnosis or review of mammography images. Helion Viewer Suite is not intended as the primary source for identification of surgical structures. Helion Viewer Suite is not intended for performing any measurements for diagnostic, treatment, or therapy, but only for reference purposes | | |
| Please select the types of uses (select one or both, as applicable). | ☑ Prescription Use (21 CFR 801 Subpart D) ☐ Over-The-Counter Use (21 CFR 801 Subpart C) | |
{4}
Baxter
K254265
# Section 10.2 510(k) Summary
April 22, 2026
## OWNER:
Videomed S.r.l (a subsidiary of Baxter Healthcare Corporation)
Interporto Centro Ingrosso 81
Pordenone, IT 33170
Italy (EU)
## CONTACT PERSON:
Dania Di Pietro Paolo
Sr Regulatory Specialist
Videomed S.r.l (a subsidiary of Baxter Healthcare Corporation)
Interporto Centro Ingrosso 81
Pordenone, IT 33170
Italy (EU)
Telephone: +49 (0) 15161725291
## IDENTIFICATION OF THE DEVICE:
Trade/Device Name: Helion Viewer Suite
Common Name: DICOM Viewer
Classification Panel: Picture archiving and communications system (21 CFR 892.2050)
Regulation Number: 21 CFR 892.2050
Regulation Name: Picture Archiving And Communications System
Regulatory Class: Class II
Product Code: LLZ
Table 1. Proposed Model number and Version Helion Viewer Suite
| Model Number | Version Number | Name |
| --- | --- | --- |
| 116002 | 1.0 | Helion Viewer Suite |
{5}
Baxter
# Predicate Device
Table 2. Predicate Device
| Device | Company | Predicate 510(k) | Clearance Date |
| --- | --- | --- | --- |
| Viewer | Brainlab AG | K191014 | January 23, 2020 |
# DESCRIPTION OF THE DEVICE
Helion Viewer Suite is a client-server application software for displaying and annotating 2D radiological images and 3D visualizations (Multi Planar Reconstruction MPR, 3D volume rendering). Helion Viewer Suite enables mobile and shared sessions for collaboration between healthcare professionals.
Helion Viewer Suite consists of two primary modules which also can be used independently.
- The Helion Fluid Touchless module supports the DICOM image viewer in the operating room using a touchless gesture-controlled monitor which is used throughout the surgery. The module is accessed on a Computer utilizing an external monitor.
- The Helion Anywhere Streaming module provides options for visualization of DICOM images exclusively before and after surgery. The module can be used on a Windows computer with monitor, mouse, and keyboard.
The software manages data and images acquired from DICOM compliant imaging systems.
# Indications For Use
Helion Viewer Suite is a software device for displaying DICOM data and medical images.
It includes functions for image review, image manipulation, annotations, and 3D visualization (Multiplanar reconstructions and 3D volume rendering).
The Helion Viewer Suite is not intended for primary image diagnosis or review of mammography images.
The Helion Viewer Suite is not intended as the primary source for identification of surgical structures.
Helion Viewer Suite is not intended for performing any measurements for diagnostic, treatment, or therapy, but only for reference purposes.
# Contraindications:
The Helion Viewer Suite is not intended for primary image diagnosis or review of mammography images.
The Helion Viewer Suite is not intended as the primary source for identification of surgical structures.
Helion Viewer Suite is not intended for performing any measurements for diagnostic, treatment, or therapy, but only for reference purposes.
{6}
Baxter
Device Comparison and Substantial Equivalence
| Features | Predicate Device Cleared under K191014 | Proposed Device Helion Viewer Suite | Assessment of Differences |
| --- | --- | --- | --- |
| Intended Use | Viewer is a software device for display of medical images and other healthcare data. It includes functions for image review, image manipulation, basic measurements and 3D visualization (Multiplanar reconstructions and 3D volume rendering). | Helion Viewer Suite is a software for visualizing DICOM image data for investigation of the anatomy, for reference purposes. | The intended use of Helion Viewer Suite is more general than that of the predicate device, but the indications for use (see row below) remain the same. The proposed device IFU does not constitute a new Intended Use from the predicate device as both the predicate and the proposed devices are intended to review DICOM data for not diagnostic use. The use environment and use conditions are the same as the predicate device for which it is intended to be used. |
| Indications for Use | Viewer is a software device for display of medical images and other healthcare data. It includes functions for image review, image manipulation, basic measurements and 3D visualization (Multiplanar reconstructions and 3D volume rendering). It is not intended for primary image diagnosis or the review of mammographic images. | Helion Viewer Suite is a software device for displaying DICOM data and medical images. It includes functions for image review, image manipulation, annotations, and 3D visualization (Multiplanar reconstructions and 3D volume rendering). The Helion Viewer Suite is not intended for primary image diagnosis or review of mammography images. The Helion Viewer Suite is not intended as the primary source for identification of surgical structures. | The measurement functionality of the proposed device is included in the word “annotations”. The proposed device has a limited scope in comparison to the predicate device, but the limitation in scope does not affect the intended use. |
{7}
Baxter
| | | Helion Viewer Suite is not intended for performing any measurements for diagnostic, treatment, or therapy, but only for reference purposes. | In summary, no safety or effectiveness concerns were identified for the proposed device. |
| --- | --- | --- | --- |
| Primary operating functions | Non-diagnostic viewing of medical images and other healthcare data in DICOM format. | Non-diagnostic viewing of medical images and other healthcare data in DICOM format. | Same |
| Intended Users | The device is generally used by medical professionals such as doctors, their assistants or nursing staff which are in need of displaying medical (DICOM) images and other healthcare data for non-diagnostic purposes. | The device is used by trained healthcare professionals such as surgeons or surgical teams responsible for displaying medical (DICOM) images and other healthcare data for non-diagnostic purposes. | Same |
| Patient population | The device is software which allows viewing of DICOM data. Hence there is no specific patient population. | The device is software which allows viewing of DICOM data. Hence there is no specific patient population. | Same |
| Operating principles | - On desktop PCs the interaction with the software is mainly performed with mouse and/or keyboard. - On touch screen PCs and on mobile devices the software is mainly used with a touch screen interface. - On Mixed Reality glasses the interaction is performed with a dedicated pointing device. | -On Windows PCs interaction with the software is mainly performed with mouse and/or keyboard. -On touch screen PCs interaction is intended to be performed with mouse and/or keyboard. - In the OR, the interaction is performed with a gesture recognition by means of a off the shelf sensor device. | The predicate device can be used also on touch screen PCs and on mobile devices with a touch screen interface. The system's limitation to specific platforms and the different interaction in the operating theater do not impact the safety and effectiveness of the device, and therefore, does not pose a risk to patients or users. This is because the device is intended for non-diagnostic purposes, and its functionality is not dependent on the underlying platform. |
{8}
Baxter
| Sterile | N/A; software | N/A; software | N/A; software |
| --- | --- | --- | --- |
| Non-Pyrogenic | N/A; software | N/A; software | N/A; software |
{9}
Baxter
# DISCUSSION OF NONCLINICAL TESTS:
Non-Clinical testing of Helion Viewer Suite has been performed against requirements for performance and safety, and to provide objective evidence that the device's intended use is met.
Non-Clinical testing was conducted on the Helion Viewer Suite software system to evaluate the functional performance of the device. Testing involved system level tests, performance tests and safety testing based on hazard analysis. Cybersecurity issues have been addressed.
Detailed summary information regarding the performance testing is supplied in following sections
- Performance Testing: Bench Testing
- Software Documentation: Software Verification and Validation Testing within the eSTAR submission documentation.
Specifically, non-clinical performance testing was performed to verify the accuracy of measurement and annotation functions used for reference purposes. Verification and validation activities assessed distance, angle and Cobb angle, area, point, circle, and ellipse measurements using standardized phantom datasets and controlled synthetic test images with known reference values. Distance measurements were verified within a tolerance of ±0.1 cm; angle and Cobb angle measurements within ±1 degree; area measurements for circles and ellipses within ±1%; and point, circle, and ellipse HU value annotations within ±1 unit.
All measurement functions met predefined acceptance criteria and demonstrated repeatable performance, with no failures or deviations identified that would impact safety or effectiveness.
In addition to the verification and validation testing activities executed by Videomed srl to establish the performance and functionality of the Helion Viewer Suite, several standards were utilized to verify safety and efficacy of the device:
General Use Standards:
ISO 14971 – Medical Devices – Application of Risk Management to Medical Devices
IEC 62366-1 – Medical devices – Part 1: Application of usability engineering to medical devices
IEC 62304 – Medical device software – Software life cycle processes
ISO 15223-1 Medical devices – Symbols to be used with information to be supplied by the manufacturer – Part 1: General requirements
NEMA PS 3.1 - 3.20 2024e: Digital Imaging and Communications in Medicine (DICOM) Set
Baxter/Videomed Srl referred as well to the following guidance documents:
{10}
Baxter
Guidance for Industry: Content of Premarket Submissions for Device Software Functions
Guidance for Industry: General Principles of Software Validation; Final Guidance for Industry and FDA Staff
Guidance for Industry – Applying Human Factors and Usability Engineering to Optimize Medical Device Design
Guidance for Industry– Cybersecurity for Networked Medical Devices Containing Off-the-Shelf (OTS) Software
Guidance for Industry- Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions
Guidance for Industry- Postmarket Management of Cybersecurity in Medical Devices
Guidance for Industry- Off the Shelf Software Use in Medical Devices
## CONCLUSION:
The Helion Viewer Suite has been verified and validated against design input requirements, user needs and intended uses. The non-clinical data demonstrate that the subject device raises no new questions concerning safety and effectiveness, is substantially equivalent, and performs comparably to the predicate device that is currently marketed for the same intended use.
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.