The purpose of Visaris Avanse® is to acquire, store, communicate, display and process medical X-ray images. It offers features (e.g. window leveling, zoom, measurements, annotations etc.) routinely used by medical professionals, such as radiologists and radiographers. Visaris Avanse supports printing to DICOM compatible printers. Within a network environment Visaris Avanse may provide other modalities with a DICOM worklist and a DICOM worklist service. Images and worklists can be sent and received using the DICOM protocol. Visaris Avanse has a modular system architecture. It consists of the basic application, processing and viewing as well as a number of other modules for image and worklist management, archiving, search and display. Beside the basic functionality Visaris Avanse also provides a user interface for generator control and image acquisition of medical images DR detectors.
Device Story
Visaris Avanse is autonomous digital radiography imaging, control, and management software for PCs. It interfaces with DR flat panel detectors and X-ray generators to acquire, process, and store medical images. Features include patient entry, generator control, image acquisition, window leveling, zoom, measurements, annotations, and DICOM archiving/export. Used in clinical environments by radiologists and radiographers to manage radiology workflows. The software operates on Windows PCs; supports network integration via DICOM protocols for worklists and image communication. It aids clinical decision-making by providing diagnostic-quality images for review. Benefits include streamlined digital radiology department management and efficient image handling.
Clinical Evidence
Clinical images obtained using compatible digital panels were evaluated by a board-certified radiologist. Images were determined to be of excellent diagnostic quality. No formal clinical trial data provided; evidence based on bench testing and expert review of clinical images.
Technological Characteristics
Modular software architecture; runs on Windows XP/7/8 PCs. Interfaces: DR flat panel, X-ray generator, HTTP, DICOM (Store, Send, Print, Worklist). Supports DICOM image formats (TIFF, BMP, PNG, JPEG, RAW) and various JPEG compression methods (Lossy, Lossless, JPEG-LS, JPEG 2000). Validated for compatibility with specific X-ray generators (Sedecal, Claymount, Spellman, EMD, CPI).
Indications for Use
Indicated for medical professionals, including radiologists and radiographers, to acquire, store, communicate, display, and process medical X-ray images. Not intended for mammography.
Regulatory Classification
Identification
A stationary x-ray system is a permanently installed diagnostic system intended to generate and control x-rays for examination of various anatomical regions. This generic type of device may include signal analysis and display equipment, patient and equipment supports, component parts, and accessories.
Special Controls
*Classification.* Class II (special controls). A radiographic contrast tray or radiology diagnostic kit intended for use with a stationary x-ray system only is exempt from the premarket notification procedures in subpart E of part 807 of this chapter subject to the limitations in § 892.9.
{0}------------------------------------------------
Image /page/0/Picture/1 description: The image shows the logo for the U.S. Department of Health & Human Services. The logo consists of a circular seal with the text "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" 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
June 8, 2015
VISARIS d.o.o. Belgrade % Mr. Daniel Kamm Principal Engineer Kamm & Associates 8870 Ravello Court NAPLES FL 34114
Re: K150725
Trade/Device Name: Visaris Avanse® Regulation Number: 21 CFR 892.1680 Regulation Name: Stationary x-ray system Regulatory Class: II Product Code: KPR, LLZ Dated: May 12, 2015 Received: May 14, 2015
Dear Mr. Kamm:
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-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.
{1}------------------------------------------------
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 at its toll-free number (800) 638 2041 or (301) 796-7100 or at its Internet address
http://www.fda.gov/MedicalDevices/Resourcesfor You/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 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 yours,
Robert A Ochs
Robert Ochs. Ph.D. Acting 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) K150725
Device Name Visaris Avanse®
#### Indications for Use (Describe)
The purpose of Visaris Avanse® is to acquire, store, communicate, display and process medical X-ray images. It offers features (e.g. window leveling, zoom, measurements, annotations etc.) routinely used by medical professionals, such as radiologists and radiographers. Visaris Avanse supports printing to DICOM compatible printers. Within a network environment Visaris Avanse may provide other modalities with a DICOM worklist and a DICOM worklist service. Images and worklists can be sent and received using the DICOM protocol. Visaris Avanse has a modular system architecture. It consists of the basic application, processing and viewing as well as a number of other modules for image and worklist management, archiving, search and display. Beside the basic functionality Visaris Avanse also provides a user interface for generator control and image acquisition of medical images DR detectors.
X Prescription Use (Part 21 CFR 801 Subpart D)
Over-The-Counter Use (21 CFR 801 Subpart C)
#### CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
#### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
#### 1. Administrative Information
#### Reason for Submission:
#### 510(k) Notification for Visaris Avanse®, a new device
#### Submitter:
| Address: | VISARIS d.o.o. Belgrade<br>Batajnički drum 10 deo 1b<br>11080 Zemun<br>SERBIA |
|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Submission contact person:<br>Contact telephone:<br>Contact e-mail:<br>Date prepared:<br>Common device name:<br>Classification:<br>Regulation #s.:<br>Product codes: | Mr. Milan Ratković<br>+381 11 2017 631<br>mratkovic@visaris.com<br>May 12, 2015<br>Stationary X-Ray System (accessory)<br>Class II<br>21 CFR 892.1680 and 21 CFR 892.2050<br>KPR and LLZ |
| Substantially equivalent device: | |
| Device Name(s): | dicomPACS® 5.2 - dicomPACS DX-R® 1.6 |
| Manufacturer: | Oehm & Rehbein GmbH |
| Product Code: | LLZ |
| Regulation Number: | 21 CFR 892.2050 |
| Common Product Name: | Radiological Image Processing System |
| 510(k) Number: | K091364 |
## 2. Device description: 21 CFR 807 92 (a) (4)
Visaris Avanse® is a digital radiography imaging, control and management software (for imaging consoles) that works with DR flat panel detectors technology. Visaris Avanse® PACS provides functionality for digital radiography examinations from patient search and entry, generator control, image acquisition and processing to DICOM data archiving and export. Visaris Avanse® PACS can also include a number of Digital Radiology modules such as network DICOM archive (PACS module). DICOM modality worklist module and diagnostic workstation software to turn it into digital radiology department on a PC for small clinics. Visaris Avanse ® is autonomous software and involves no hardware. It runs under the MS Windows XP/7/8 operating system on any hardware platform meeting the minimum system requirements.
## 3. Indications for Use: 21 CFR 807 92 (a) (5)
The purpose of Visaris Avanse® is to acquire, store, communicate, display and process medical X-ray images. It offers features (e.g. window leveling, zoom, measurements, annotations etc.) routinely used by medical professionals, such as radiologists and radiographers. Visaris Avanse® supports printing to DICOM compatible printers. Within a network environment Visaris Avanse® may provide other modalities with a DICOM worklist and a DICOM worklist service. Images and worklists can be sent and received using the DICOM protocol. Visaris Avanse® has a modular
{4}------------------------------------------------
system architecture. It consists of the basic application for image acquisition, processing and viewing as well as a number of other modules for image and worklist management, archiving, search and display. Beside the basic functionality Visaris Avanse® also provides a user interface for generator control and image acquisition of medical images DR detectors. Not intended for mammography.
## 4. Technological characteristics: 21 CFR 807 92 (a) (6)
Visaris Avanse/PACS ® has a modular system architecture. It consists of the basic application for image acquisition, processing and viewing as well as a number of other modules for image and worklist management, archiving, search and display. The software has been validated for compatibility with digital panels previously cleared by FDA and has been validated for control compatibility with the following list of generators:
| Manufacturer | Product Name |
|------------------------|----------------|
| Sedecal, Spain | All models |
| Claymount, Switzerland | Clayrad Series |
| Spellman, Germany | HFe Series |
| EMD, Canada | All models |
| CPI, Canada | Indico100, CMP |
The image formats used are: DICOM, TIFF, BMP, PNG, JPEG, RAW (new)
Image Compression:
Visaris Avanse/PACS use the following compression methods within the DICOM standard:
- JPEG Baseline (Process 1): Lossy JPEG 8 Bit Image Compression .
- JPEG Extended (Process 2 & 4): Lossy JPEG 12 Bit Image Compression (Process 4 . only)
- JPEG Extended (Process 3 & 5) ●
- JPEG Spectral Selection. Non-Hierarchical (Process 6 & 8) ●
- JPEG Lossless, Non-Hierarchical (Process 14) ●
- JPEG Lossless, Non-Hierarchical, First-Order Prediction (Process 14 [Selection Value . 11)
- JPEG-LS Lossless Image Compression
- JPEG-LS Lossy (Near-Lossless) Image Compression ●
- JPEG 2000 Image Compression (Lossless Only)
- JPEG 2000 Image Compression ●
These compression methods are defined in the DICOM standard. Support of them is optional.
The modules are:
- 1. Avanse® DR image acquisition module
- 2. X-ray Generator Control Module
- 3. Minet Server internal communication module
- 4. CDViewer module
- 5. RIS Interface module
- 6. Avanse® DR service shell module
- 7. VisarisPACS database module
- 8. Worklist Server module
- 9. Dics Burn server module
{5}------------------------------------------------
10. Worklist generator module
- 11. Diagon DICOM image viewer module
The interfaces are:
- 1. DR flat panel
- 2. X-ray generator
- 3. HTTP
- 4. DICOM Store (SCP)
- 5. DICOM Send (SCU)
- 6. DCIOM Print (SCU)
- 7. Worklist Query (SCP)
#### 5. Non clinical testing
The complete Visaris Avanse® PACS system configuration has been assessed and tested at the factory and has passed all in-house criteria. The Verification and Validation plan was design to evaluate all input and output functions, and actions performed by Visaris Avanse® PACS software in each operation mode and followed the process documented in the Validation Test Plan. Validation testing indicate that as required by risk analysis, designated individuals performed all verification and validation activities and that the result demonstrated that the predetermine acceptance criteria were met. If the device is installed by Visaris, installation and integration verification tests are conduct against acceptance criteria prior to release to client.
#### 6. Clinical testing
Clinical images were obtained using each of the declared compatible digital panels. The images were evaluated by a board certified radiologist and were found to be of excellent diagnostic quality.
## 7. Substantial Equivalence Discussion
The Visaris Avanse® has the same essential indications for use as the predicate and uses the same kind of platform (Windows PC) to perform its functions. The same kind of software validation and panel testing has been performed. It is DICOM compatible like the predicate and handles jpeq images like the predicate.
| dicomPACS®5.2 and dicomPACS DX-R<br>K091364, Oehm und Rehbein GmbH<br>(Predicate Device) | VISARIS AVANSE®<br>(New Device)<br>[Equivalence Level] | Equivalence Justification |
|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Design | | |
| Overall software architecture:<br>A front-end + back-end architecture.<br>Front-end includes user interface realised<br>through „stand-alone" user applications.<br>Back-end includes image and metadata<br>databases and background services that<br>operate on them. Front and back end are<br>linked through DICOM standard protocol<br>communication. DICOM communication<br>realised trough service provider-client<br>model, back end provides the service and<br>front end is its client. | Overall software architecture:<br>A front-end + back-end architecture.<br>Front-end includes user interface realised<br>through „stand-alone" user applications.<br>Back-end includes image and metadata<br>databases and background services that<br>operate on them. Front and back end are<br>linked through DICOM standard protocol<br>communication. DICOM communication<br>realised trough service provider-client<br>model, back end provides the service and<br>front end is its client.<br>[EQUIVALENT] | None required. They are<br>EQUIVALENT. |
| dicomPACS®5.2 and dicomPACS DX-R<br>K091364, Oehm und Rehbein GmbH | VISARIS AVANSE®<br>(New Device) | Equivalence Justification |
| (Predicate Device)<br>Software architecture back end:<br>Integrated database of image, examination<br>and patient data linking acquired image files<br>on the file system (local or network storage).<br>Windows services (background processes<br>with no user interface) handle data transfer<br>to and from database and ensure database<br>integrity. | [Equivalence Level]<br>Software architecture back end<br>Integrated database of image, examination<br>and patient data linking acquired image files<br>on the file system (local or network storage).<br>Windows services (background processes<br>with no user interface) handle data transfer<br>to and from database and ensure database<br>integrity.<br>[EQUIVALENT] | None required.<br>They are<br>EQUIVALENT. |
| Software architecture front end:<br>Front end is realised throught several static<br>windows (win32) applications implementing<br>main user interface functionality including<br>image acquisition, exam scheduling and<br>image review.<br>Only one application entity active on the<br>user interface at any time.<br>Win32 applications implement<br>DICOM<br>communication clients to communicate<br>with services in the back-end and external<br>DICOM services. | Software architecture front end:<br>Front end is realised throught several static<br>windows (win32) applications implementing<br>main user interface functionality including<br>image acquisition, exam scheduling and<br>image review.<br>Only one application entity active on the<br>user interface at any time.<br>Win32 applications implement DICOM<br>communication clients to communicate<br>with services in the back-end and external<br>DICOM services.<br>Exam scheduling user interface is also<br>realised through web based interface.<br>[PRACTICALLY EQUIVALENT] | Web interface architecture<br>is used to collect user input,<br>but not process it. Main<br>processing functionality is<br>still performed in the back<br>end and the web interface<br>is implemented on a win32<br>process within a browser. |
| Communication to external components:<br>Realised through each<br>component's<br>proprietary communication protocol using<br>standard interface/data exchange protocols<br>(such as RS232 or TCP-IP). Connections to<br>components managed locally on the main<br>system PC through component proprietary<br>software (SDK) interfaces implemented in<br>dynamicly linked libratries (dlls).<br>Communication from main system software<br>realised through direct calls to exposed<br>functions of the SDK contained within the<br>dlls. Data transfer realised through common<br>memory access. | Communication to external components:<br>Realised through each<br>component's<br>proprietary communication protocol using<br>standard interface/data exchange protocols<br>(such as RS232 or TCP-IP). Connections to<br>components managed locally on the main<br>system PC through component proprietary<br>software (SDK) interfaces implemented in<br>dynamicly linked libratries (dlls).<br>Communication from main system software<br>realised through direct calls to exposed<br>functions of the SDK contained within the<br>dlls. Data transfer realised through common<br>memory access.<br>[EQUIVALENT] | None required.<br>They are<br>EQUIVALENT. |
| dicomPACS®5.2 and dicomPACS DX-R<br>K091364, Oehm und Rehbein GmbH<br>(Predicate Device) | VISARIS AVANSE®<br>(New Device)<br>[Equivalence Level] | Equivalence Justification |
| User Interface design<br>Multiple application enetites with related<br>but separate user interface to cover<br>different workflow aspects (DR/CR<br>acquisition and patient entry, database<br>search, image viewing, examination<br>scheduling).<br>User interface is graphical with clear display<br>of acquired or retreived images and system<br>information on the screen as well as data<br>entry fields.<br>Action commands are input by the user as<br>mouse clicks on command buttons, menus,<br>results lists and data entry fields.<br>Textual data input is handled through<br>keyboard/touchscreen keyboard input. | User Interface design<br>Multiple application enetites with related<br>but separate user interface to cover<br>different workflow aspects (DR/CR<br>acquisition and patient entry, database<br>search, image viewing, examination<br>scheduling).<br>User interface is graphical with clear display<br>of acquired or retreived images and system<br>information on the screen as well as data<br>entry fields.<br>Action commands are input by the user as<br>mouse clicks on command buttons, menus,<br>results lists and data entry fields.<br>Textual data input is handled through<br>keyboard/touchscreen keyboard input.<br>[EQUIVALENT] | None required. They are<br>EQUIVALENT. |
| Development Platform:<br>Main development platform Microsoft<br>Windows development platform (.NET<br>Technologies: ADO.NET Entity Framework,<br>LINQ, ADO.NET, XML, ODATA Protocol,<br>Native: ODBC, ADO, MSDASQL, Database:<br>SQL Serever Database Engine, SQL Server<br>Integration Services SSIS, SQL Server<br>Reporting Services SSRS). | Development Platform:<br>Main development platform Microsoft<br>Windows development platform (.NET<br>Technologies: ADO.NET Entity Framework,<br>LINQ, ADO.NET, XML, ODATA Protocol,<br>Native: ODBC, ADO, MSDASQL, Database:<br>SQL Serever Database Engine, SQL Server<br>Integration Services SSIS, SQL Server<br>Reporting Services SSRS). Android mobile<br>platform used for UI extension to mobile<br>devices.<br>[PRACTICALLY EQUIVALENT] | Main development platform<br>is equivalent. Android<br>platform is additionally used<br>on Visaris Avanse only to<br>collect user actions from<br>mobile devices. System<br>actions are not processed<br>on this platform, rather on<br>the same main platform as<br>predicate device.<br>Functionality verified. |
| PC Platform | PC Platform | |
| Common Personal Computer (PC) platform,<br>static or mobile (laptop, tablet). | Common Personal Computer (PC) platform,<br>static or mobile (laptop, tablet).<br>[EQUIVALENT] | None required. They are<br>EQUIVALENT. |
| Material | Material | |
| Software only product, no material<br>included. | Software only product, no material<br>included.<br>[EQUIVALENT] | None required. They are<br>EQUIVALENT. |
| Chemical Composition | Chemical Composition | |
| Software only product, no chemical<br>composition. | Software only product, no chemical<br>composition.<br>[EQUIVALENT] | None required. They are<br>EQUIVALENT. |
| Energy Source | Energy Source | |
| Software only product, no energy source<br>included. | Software only product, no energy source<br>included.<br>[EQUIVALENT] | None required. They are<br>EQUIVALENT. |
## Substantial Equivalence Table
{6}------------------------------------------------
{7}------------------------------------------------
8. Substantial Equivalence Conclusion: After analyzing software validation, risk analysis, and clinical images, it is the conclusion of VISARIS d.o.o. Belgrade Inc that the VISARIS AVANSE® is as safe and effective as the predicate device, have few technological differences, and has the same indications for use, thus rendering it substantially equivalent to the predicate device.
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.