The VISIONAIR™ system is a software application intended to be used with third-party endoscopic systems in the measurement of the nasal respiratory airway. The VISIONAIR™ system measures the nasal respiratory airway from the endoscopic images taken in the region of the internal nasal valve (INV) and nasal cavum (NC).
Device Story
VISIONAIR is a software application for Windows-based smart devices (tablets/laptops) that interfaces with third-party endoscopic systems to analyze nasal respiratory airway anatomy. It captures endoscopic video/images via HDMI/USB ports. An AI algorithm processes these images to segment and measure the cross-sectional area of the internal nasal valve and nasal cavum. The system provides a GUI for data entry, image viewing, and report generation (quantitative/qualitative). Data is stored locally or in a cloud server (REAI module) with encryption managed by a physical USB key. Used by clinicians pre-, during, or post-procedure to assess nasal airway structure. The output assists clinicians in evaluating nasal respiratory airway size and structure, potentially aiding in clinical decision-making regarding nasal decongestion or airway obstruction.
Clinical Evidence
Bench testing only. No clinical trials. Performance validated via: 1) System-level, interface, and connectivity testing; 2) Patient database encryption/decryption verification; 3) Endoscopic display and report generation testing; 4) Segmentation accuracy: VISIONAIR AI-segmented endoscopic images compared against cross-sectional areas from CT scans; 5) Segmentation accuracy: VISIONAIR AI-segmented images compared against manual segmentations by experienced clinicians.
Technological Characteristics
Windows-based software application; Python 3.6. Interfaces with third-party endoscopes via HDMI/USB. Uses light reflection technology for image acquisition. Employs AI-based segmentation algorithm. Data security via encrypted USB key and cloud-based REAI module. Non-sterile. Standalone software on provided smart device hardware.
Indications for Use
Indicated for use with third-party endoscopic systems to measure the nasal respiratory airway, specifically the internal nasal valve and nasal cavum, in patients undergoing nasal airway assessment.
Regulatory Classification
Identification
A rhinoanemometer is a device used to quantify the amount of nasal congestion by measuring the airflow through, and differential pressure across, a patient's nasal passages.
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image contains the logo of the U.S. Food and Drug Administration (FDA). On the left, there is a symbol representing the Department of Health & Human Services - USA. To the right of this symbol, there is a blue square with the letters "FDA" in white. Next to the blue square, the words "U.S. FOOD & DRUG ADMINISTRATION" are written in blue.
October 5, 2022
PacificMD Biotech Llc % David Locke Regulatory Consultant Canyon Labs 6217 South Bringhurst Blvd, Suite 600 Bluffdale, Utah 84065
Re: K221892
Trade/Device Name: VISIONAIR Regulation Number: 21 CFR 868.1800 Regulation Name: Rhinoanemometer Regulatory Class: Class II Product Code: BXQ, EOB Dated: September 3, 2022 Received: September 7, 2022
Dear David Locke:
We have reviewed your Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database located at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration. listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's
{1}------------------------------------------------
requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting of medical device-related adverse events) (21 CFR 803) for devices or postmarketing safety reporting (21 CFR 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reportingcombination-products); good manufacturing practice requirements as set forth in the quality systems (OS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about mediation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medicaldevices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-device-advice-comprehensive-regulatoryassistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
for Shu-Chen Peng, Ph.D. Assistant Director DHT1B: Division of Dental and ENT Devices OHT1: Office of Ophthalmic, Anesthesia, Respiratory, ENT and Dental Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
# Indications for Use
510(k) Number (if known) K221892
Device Name VISIONAIR™
#### Indications for Use (Describe)
The VISIONAIR™ system is a software application intended to be used with third-party endoscopic systems in the measurement of the nasal respiratory airway. The VISIONAIR™ system measures the nasal respiratory airway from the endoscopic images taken in the region of the internal nasal valve (INV) and nasal cavum (NC).
| Type of Use (Select one or both, as applicable) | |
|------------------------------------------------------------|-----------------------------------------------------------|
| <span></span> Prescription Use (Part 21 CFR 801 Subpart D) | <span></span> Over-The-Counter Use (21 CFR 801 Subpart C) |
#### CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
#### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff(@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
# 510(K) SUMMARY
# [807.92(a)(1)] Submitter Information
| Applicant: | PacificMD Biotech<br>3195 Saint Rose Pkwy<br>Suite 210<br>Henderson, NV, 89052<br>Tel.: 201-819-8685<br>Fax: 702-780-6912 |
|-----------------|-----------------------------------------------------------------------------------------------------------------------------------------------------|
| Contact Person: | David Locke<br>Regulatory Consultant<br>Canyon Labs<br>16217 South Bringhurst Blvd.,<br>Suite 600 Bluffdale, UT 84065<br>David.locke@canyonlabs.com |
| Authored by: | David Locke<br>Regulatory Consultant<br>Canyon Labs<br>Phone: 419-233-2611 |
| Date Summary | October 4, 2022 |
|--------------|-----------------|
| Prepared: | |
## [807.92(a)(2)] Name of Device
| Device Trade Name: | VISIONAIR™ |
|------------------------|-----------------------------------------------------|
| Device Common Name: | VISIONAIR™ |
| Classification Name: | Rhinoanemometer (Measurement of Nasal Decongestion) |
| Regulation Number: | 868.1800 |
| Device Classification: | Class II |
| Product Code: | BXQ |
| Secondary Code: | EOB |
| Primary Review Panel: | Anesthesia |
{4}------------------------------------------------
## [807.92(a)(3)] Legally Marketed Devices
| Primary Predicate<br>Device: | Eccovision™ System (K170071) |
|------------------------------|---------------------------------------------|
| Reference Device: | Smith & Nephew Image Video System (K970247) |
## [807.92(a)(4)] Device Description
Device Description: The VISIONAIR™ software can be utilized to automatically measure the cross-section area of the Internal Nasal Valve (INV) and Nasal Cavum (NV) and measure the nasal respiratory airway in this region of the anatomy. The VISIONAIR™ system consists of the following components: - The VISIONAIR™ algorithm which performs the Internal Nasal Valve and Nasal Cavum cross-section area segmentations. - The VISIONAIR™ Graphical User Interface (GUI) used for data entry, view the endoscopic image from third party endoscopes and display the data analysis to the user. - A smart device such as tablet or laptop which runs on Windows 10 or a later operating system with the VISIONAIR™ application installed. - A cloud service that runs in the background and can be activated by the user when a particular dataset for a case is desired to securely and anonymously be stored to the Cloud Server (REAI). - USB memory used to encrypt and anonymize the patient information, whether the data is stored locally or to the cloud, and stores the credits needed to activate the VISIONAIR™ software for each case. The VISIONAIR™ application interfaces with third-party endoscopic systems via the ports located on the smart device. The smart device ports enable the third-party systems endoscopic video display to be streamed on the VISIONAIR™ application endoscopic video display. In this 510(k) submission, a FDAcleared endoscope (K970247) was selected as the reference device to support the scientific methodology. The VISIONAIR™ application automatically analyzes the endoscopic images using its trained AI algorithm to measure the nasal valve and nasal cavum surface areas. The VISIONAIR™ application also provides a database file system to manage the data and interface securely and anonymously with the cloud server via the REAl module.
{5}------------------------------------------------
The USB KEY adds another level of security for the data management file system by allowing the user to physically have possession of the database encryption kev all the time.
In addition, the segmented cross-section areas by the VISIONAIR™ application, of the internal nasal valve and nasal cavum on the endoscopic images are captured on a report which consists of quantitative and qualitative information related to the assessment of the nasal respiratory airway.
The VISIONAIR™ application manages the data by creating for each patient a directory with a unique encrypted ID where the patient endoscopic anatomical images and videos are stored anonymously. The smart device and USB KEY both consist of encryption keys which are used to translate unique IDs to patient information and vice versa. The database, whether stored locally on the smart device, or to the cloud via the REA1 module, never stores any of the patient's information without encrypting them. The only patient information captured during the procedure, which is encrypted using the VISIONAIR™ application, are the patient's name, patient Date of Birth (DOB) and optionally their ethnicity, which is used to compare the measured results of the patient against the normative published data of the nasal respiratory airway and apex angle measurements.
#### [807.92(a)(5)] Intended Use and Predicate Device Comparison
Indications for Use: The VISIONAIR™ system is a software application intended to be used with third-party endoscopic systems in the measurement of the nasal respiratory airway. The VISIONAIR™ system measures the nasal respiratory airway from the endoscopic images taken in the region of the internal nasal valve (INV) and nasal cavum (NC).
### [807.92(a)(6)] Technical Characteristics
System Characteristics: The VISIONAIR™ application comes installed into a windowsbased operating system smart device. The HDMI and USB ports of the smart device can be utilized to connect the external third-party endoscopic system to the VISIONAIR™ application. The user can use the HDMI, DISPLAY or DVI output port from the third-party endoscopic system, to connect it to the USB port of the smart device. A standard adapter to convert the output of the endoscopic system to the USB port may be utilized and is provided with the smart device.
{6}------------------------------------------------
| | The smart device which comes with the VISIONAIR™ software installed is programmed with an encryption key to encode and anonymize the data acquired. In addition, a separate USB KEY is provided which adds a second layer of encryption for the database. The USB KEY is plugged into the smart device prior to starting the VISIONAIR™ application otherwise the data will remain on its encryption and anonymized state, resulting on the VISIONAIR™ application not being able to read the data. |
|-----------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | Once, the smart device, the third-party endoscopic system and the USB KEY are connected, the user is ready to start the VISIONAIR™ application. The VISIONAIR™ application can be used pre-, during, or post- procedure to measure the cross section of the internal nasal valve and nasal cavum to measure the nasal respiratory airway. In addition, the application will store the data locally or to the cloud, depending on the clinician's preference in a secure manner so the clinician can access them at any time by using the dedicated smart device and the USB KEY. |
| | Prior to each use of the VISIONAIR™ application, credits are required for the VISIONAIR™ application to be used for image analysis and processing. A USB TOKEN can be plugged into the smart device and used until the credits are fully used. |
| Non-clinical<br>Performance Data: | The VISIONAIR™ system was tested to ensure that it functions in accordance with the device design specifications related to substantial equivalence in terms of device safety and effectiveness. The following nonclinical tests were performed: |
| 1. | System Level Test: Confirmation of system components such as Windows OS, processor, RAM requirements, ports, wireless connectivity, and other items required to operate the VISIONAIR™ application. |
|----|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 2. | System Interface and Connectivity Test: Confirmation of the VISIONAIR™ application to the USB device containing the cloud key and application credits and system connections to other devices. |
| 3. | VISIONAIR™ Application Test: VISIONAIR™ connectivity to external endoscopes, cloud server, successful launch, and other interaction tests of the VISIONAIR™ application. |
| 4. | Patient Database Verification Test: Confirmation of the data stored, anatomical marking, and successful encryption/decryption of the database verification. |
| 5. | Endoscopic Display Test: Endoscopic view verification of the image capture, video recording and other functions. |
| 6. | Nasal respiratory airway Analysis Test: VISIONAIR™ AI application confirmation of successful segmentation of the Internal Nasal Valve and Nasal Cavum. This test also |
{7}------------------------------------------------
verifies the ability of manipulating images, loading new images, removing unwanted images and other functions related to the analysis phase.
- 7. Report Generation Test: Confirmation of successful report generation in pdf, csv, and other formats.
- 8. User Validation Test: Validation of the entire VISIONAIR™ system by the clinicians. This test includes successful verification of all the features of the VISIONAIR™ application which the user will have access and visibility.
- 9. CT vs Segmentation Accuracy Test: Comparison of endoscopic image cross-sectional areas which were segmented by the VISIONAIR™ application vs. the crosssectional areas of the same anatomical regions marked on the CT scans.
- 10. VISIONAIR™ AI Segmentation Accuracy Test: Comparison of segmented endoscopic images by the VISIONAIR™ application vs. segmented endoscopic images by experienced clinicians.
{8}------------------------------------------------
# Substantial Equivalence Table
| Attribute | Primary Predicate<br>Device (K170071):<br>Eccovision™ | Subject Device:<br>VISIONAIR™ | Substantial Equivalence<br>Rationale |
|-------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 510(k) number | K170071 | K221892 | N/A |
| Manufacturer | Sleep Group<br>Solutions | PacificMD Biotech | N/A |
| Trade Name | Eccovision™ | VISIONAIR™ | N/A |
| Common Name | Eccovision™ | VISIONAIR™ | N/A |
| Class | II | II | Same |
| Classification<br>Product Code | BXQ | BXQ<br>EOB | Same |
| Subsequent<br>Product Code | 868.1800 | 868.1800 | Same |
| Sterilization | Non-sterile | Non-sterile | Same |
| Packaging | Provided non-sterile | Provided non-sterile | Same |
| Single Patient Use | No | No | Same |
| Indications for Use | The Eccovision™ is<br>intended to measure the<br>upper respiratory airway<br>by acoustic reflection. | The VISIONAIR™<br>system is a software<br>application intended to be<br>used with third-party<br>endoscopic systems in the<br>measurement of the nasal<br>respiratory airway. The<br>VISIONAIR™ system<br>measures the nasal<br>respiratory airway from<br>the endoscopic images<br>taken in the region of the<br>internal nasal valve (INV)<br>and nasal cavum (NC). | The IFU and Indications<br>of the subject<br>VISIONAIR™ System is<br>aligned with the predicate<br>devices. The change in<br>the manner in which data<br>is captured and processed<br>does not bring about any<br>new concerns with respect<br>to substantial equivalence,<br>and the safety and<br>effectiveness of the<br>subject device is<br>supported by completed<br>device testing. |
| System Function<br>to Capture Data | Both mouthpiece or<br>nose tip via the Wave<br>Tube. | Applicable FDA<br>cleared endoscopes. | These are different but the<br>differences do not raise<br>any new concerns with<br>respect to safety and<br>effectiveness. |
| Attribute | Primary Predicate<br>Device (K170071):<br>EccovisionTM | Subject Device:<br>VISIONAIRTM | Substantial Equivalence<br>Rationale |
| Computer<br>Requirements:<br>Hardware and<br>Software<br>(Operating<br>System, device<br>application<br>software) | A customer owned<br>computer with the<br>Eccovision software<br>application loaded by<br>the customer. | Windows 10 or later<br>operating system (OS)<br>computer is provided<br>by PacificMD Biotech. | Same with the only<br>exception being system<br>version. |
| Control Unit -<br>Hardware | Provided hardware<br>which connects to the<br>computer.<br>Modified with the<br>redesign of the PCB<br>(Print Circuit Board)<br>configuration. | Windows 10 or later<br>operating system (OS)<br>computer is provided<br>with the<br>VISIONAIRTM<br>application installed<br>and tested prior to its<br>release to the market. | Same with the only<br>exception being system<br>version. |
| Electronic<br>Platform -<br>Hardware | Supporting the<br>Pharyngometer and<br>connects to the<br>Control Unit. | Endoscopic System –<br>Connects to the<br>Windows 10 computer<br>via the USB port. | These are different but the<br>differences do not raise<br>any new concerns with<br>respect to safety and<br>effectiveness. |
| Application<br>Software<br>(Language) | Windows with GUI | Windows based GUI<br>and AI written in<br>Python 3.6 language. | Same as compared to<br>applicable devices. |
{9}------------------------------------------------
{10}------------------------------------------------
| Attribute | Primary Predicate<br>Device (K170071):<br>Eccovision™ | Subject Device:<br>VISIONAIR™ | Substantial Equivalence<br>Rationale |
|------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Technological<br>Characteristics /<br>Principles of<br>Operation | The Eccovision<br>device uses acoustic<br>reflection technology<br>to accurately map the<br>size and structure of<br>the nasal airway.<br>Sound waves are sent<br>up the nasal<br>passageway and are<br>reflected back to<br>accurately map out<br>the topography of the<br>nasal airway. | The VISIONAIR™<br>system uses the<br>endoscopic image,<br>which is created from<br>light reflection<br>technology, to<br>accurately map the<br>size and structure of<br>the nasal<br>airway. Light is sent<br>up the nasal<br>passageway and<br>reflected to accurately<br>map out the<br>topography of the<br>nasal airway. Each<br>pixel brightness<br>correspondents to how<br>much light is being<br>reflected thus<br>determining the<br>proximity of the tissue<br>relative to the<br>endoscopic optics and<br>ultimately result on a<br>2-D image that maps<br>the size and structure<br>of the nasal anatomy. | The technological<br>characteristics have been<br>tested through nonclinical<br>testing and they do not<br>impact substantial<br>equivalence. Moreover,<br>the minor technological<br>differences do not raise<br>any new concerns with<br>respect to safety and<br>effectiveness. |
{11}------------------------------------------------
| Conclusion: | The VISIONAIRTM device is substantially equivalent to<br>the predicate device in indication for use, performance,<br>technology, features, principles operation and<br>components. |
|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|-------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
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.