K230144 · Denti.Ai Technology, Inc. · MYN · Oct 6, 2023 · Radiology
Device Facts
Record ID
K230144
Device Name
Denti.AI Detect
Applicant
Denti.Ai Technology, Inc.
Product Code
MYN · Radiology
Decision Date
Oct 6, 2023
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 892.2070
Device Class
Class 2
Attributes
AI/ML, Software as a Medical Device
AI Performance
Output
Algorithm
Acceptance
Observed
Dev DS
Dev Readers
Test DS
Test Readers
Caries and periapical radiolucency detection
—
wAFROC AUC > 0.6
wAFROC AUC 0.737 (95% CI: 0.713, 0.761)
—
—
Stand-alone study: 709 images from 6 US sites
3 (dentists)
Mesial and distal bone level measurements
—
—
Bitewing CEJ-Bone MAE 0.513 mm; Periapical CEJ-Bone MAE 0.572 mm; Extraoral CEJ-Bone-Root MAE 4.7%
—
—
Stand-alone study: 193 images from 9 US sites
3 (dentists)
Caries and periapical radiolucency detection (reader improvement)
—
—
Aided wAFROC 0.809 vs Unaided wAFROC 0.784 (p=0.029)
—
—
MRMC study: 154 images from 5 US sites
24 (dental professionals)
Indications for Use
Denti.AI Detect is a Computer-Assisted Detection (CADe) software device intended to be used by dental professionals, comprising dentists and dental specialists, while reading extraoral and intraoral 2D dental radiographs. The device aims to assist in detecting and highlighting uncategorized regions of interest (ROIs) within the teeth area, which include caries and periapical radiolucency, as a second reader. The device is also intended to aid in the measurements of mesial and distal bone levels associated with each tooth. The device is aimed to be used with images from the patients of 22 years age and older without remaining primary dentition. The device is not intended to replace a complete clinician's review or clinical judgment that considers other relevant information from the image or patient history.
Device Story
Denti.AI Detect is a cloud-based CADe software for dental professionals; inputs include 2D intraoral (bitewing, periapical) and extraoral (panoramic) radiographs. The device processes images to detect and highlight regions of interest (caries, periapical radiolucency) and performs automated measurements of mesial and distal bone levels. Output is presented to the clinician as a second reader to support diagnostic review. The device does not replace clinical judgment; it aids in identifying findings and quantifying bone levels to assist in patient evaluation and decision-making. Benefits include improved detection performance and standardized measurement of bone levels.
Clinical Evidence
Bench testing: 709 images for caries/radiolucency (wAFROC AUC 0.737, 95% CI 0.713-0.761); 193 images for bone measurements (sensitivity 91.6-98.2%, specificity 84.3-93%, MAE 0.513-0.735 mm). Clinical MRMC study: 24 dental professionals, 154 images. Aided vs. unaided read showed statistically significant improvement (aided wAFROC 0.809 vs. unaided 0.784, p=0.029).
Technological Characteristics
Cloud-based software; no physical components. Supports DICOM, JPEG, TIFF, PNG, BMP, etc. Uses automated image analysis algorithms for detection and measurement. No patient-contacting materials. Software level of concern: Moderate.
Indications for Use
Indicated for dental professionals (dentists/specialists) to assist in detecting caries and periapical radiolucency and measuring mesial/distal bone levels on 2D dental radiographs (extraoral/intraoral). Patient population: adults 22+ years old with permanent dentition. Not for use on primary dentition.
Regulatory Classification
Identification
Medical image analyzers, including computer-assisted/aided detection (CADe) devices for mammography breast cancer, ultrasound breast lesions, radiograph lung nodules, and radiograph dental caries detection, is a prescription device that is intended to identify, mark, highlight, or in any other manner direct the clinicians' attention to portions of a radiology image that may reveal abnormalities during interpretation of patient radiology images by the clinicians. This device incorporates pattern recognition and data analysis capabilities and operates on previously acquired medical images. This device is not intended to replace the review by a qualified radiologist, and is not intended to be used for triage, or to recommend diagnosis.
Special Controls
*Classification.* Class II (special controls). The special controls for this device are:(1) Design verification and validation must include:
(i) A detailed description of the image analysis algorithms including a description of the algorithm inputs and outputs, each major component or block, and algorithm limitations.
(ii) A detailed description of pre-specified performance testing methods and dataset(s) used to assess whether the device will improve reader performance as intended and to characterize the standalone device performance. Performance testing includes one or more standalone tests, side-by-side comparisons, or a reader study, as applicable.
(iii) Results from performance testing that demonstrate that the device improves reader performance in the intended use population when used in accordance with the instructions for use. The performance assessment must be based on appropriate diagnostic accuracy measures (
*e.g.,* receiver operator characteristic plot, sensitivity, specificity, predictive value, and diagnostic likelihood ratio). The test dataset must contain a sufficient number of cases from important cohorts (*e.g.,* subsets defined by clinically relevant confounders, effect modifiers, concomitant diseases, and subsets defined by image acquisition characteristics) such that the performance estimates and confidence intervals of the device for these individual subsets can be characterized for the intended use population and imaging equipment.(iv) Appropriate software documentation (
*e.g.,* device hazard analysis; software requirements specification document; software design specification document; traceability analysis; description of verification and validation activities including system level test protocol, pass/fail criteria, and results; and cybersecurity).(2) Labeling must include the following:
(i) A detailed description of the patient population for which the device is indicated for use.
(ii) A detailed description of the intended reading protocol.
(iii) A detailed description of the intended user and user training that addresses appropriate reading protocols for the device.
(iv) A detailed description of the device inputs and outputs.
(v) A detailed description of compatible imaging hardware and imaging protocols.
(vi) Discussion of warnings, precautions, and limitations must include situations in which the device may fail or may not operate at its expected performance level (
*e.g.,* poor image quality or for certain subpopulations), as applicable.(vii) Device operating instructions.
(viii) A detailed summary of the performance testing, including: test methods, dataset characteristics, results, and a summary of sub-analyses on case distributions stratified by relevant confounders, such as lesion and organ characteristics, disease stages, and imaging equipment.
{0}------------------------------------------------
October 6, 2023
Image /page/0/Picture/1 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). On the left is the Department of Health & Human Services logo. To the right of that is a blue square with the letters "FDA" in white. To the right of the blue square is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
Denti.AI Technology, Inc. % Donna-Bea Tillman Senior Consultant Biologics Consulting 100 Daingerfield Road, Suite 400 ALEXANDRIA, VA 22314
Re: K230144
Trade/Device Name: Denti.AI Detect Regulation Number: 21 CFR 892.2070 Regulation Name: Medical Image Analyzer Regulatory Class: Class II Product Code: MYN Dated: September 6, 2023 Received: September 6, 2023
Dear Donna-Bea Tillman:
We have reviewed your section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (the Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (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).
{1}------------------------------------------------
Your device is also subject to, among other requirements, the Quality System (QS) regulation (21 CFR Part 820), which includes, but is not limited to, 21 CFR 820.30, Design controls; 21 CFR 820.90, Nonconforming product; and 21 CFR 820.100, Corrective and preventive action. Please note that regardless of whether a change requires premarket review, the QS regulation requires device manufacturers to review and approve changes to device design and production (21 CFR 820.30 and 21 CFR 820.70) and document changes and approvals in the device master record (21 CFR 820.181).
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting of medical device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reportingcombination-products); good manufacturing practice requirements as set forth in the quality systems (QS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about mediation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medicaldevices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-device-advice-comprehensive-regulatoryassistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
Lu Jiang
Lu Jiang, Ph.D. Assistant Director DHT8B: Division of Radiologic Imaging Devices and Electronic Products OHT8: Office of Radiological Health Office of Product Evaluation and Quality Center for Devices and Radiological Health
{2}------------------------------------------------
## Indications for Use
510(k) Number (if known) K230144
Device Name Denti.AI Detect
### Indications for Use (Describe)
Denti. Al Detect is a Computer-Assisted Detection (CADe) software device intended to be used by dental professionals. comprising dentists and dental specialists, while reading extraoral and intraoral 2D dental radiographs. The device aims to assist in detecting and highlighting uncategorized regions of interest (ROIs) within the teeth area, which include cares and periapical radiolucency, as a second reader. The device is also intended to aid in the measurements of mesial and distal bone levels associated with each tooth.
The device is aimed to be used with images from the patients of 22 years age and older without remaining primary dentition. The device is not intended to replace a complete clinical judgment that considers other relevant information from the image or patient history.
| Type of Use (Select one or both, as applicable) |
|-------------------------------------------------|
|-------------------------------------------------|
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}------------------------------------------------
In accordance with 21 CFR 807.87(h) and 21 CFR 807.92 the 510(k) Summary for the Denti.AI Detect is provided below.
#### 1. SUBMITTER
| Applicant: | Denti.AI Technology Inc.<br>99 Yorkville Ave, Suite 214<br>Toronto, Ontario, Canada M5R3K5 |
|--------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Contact/Submission<br>Correspondent: | Donna-Bea Tillman, Ph.D.<br>Biologics Consulting Group<br>100 Daingerfield Road, Suite 400<br>Alexandria, VA 22314<br>(410) 531-6542<br>dtillman@biologicsconsulting.com |
| Date Prepared: | October 5, 2023 |
#### 2. DEVICE
| Device Trade Name: | Denti.AI Detect |
|--------------------------|---------------------------------------------------|
| Device Common Name: | Medical Image Analyzer |
| Primary Classification | |
| Classification Name | 892.2070 Medical Image Analyzer |
| Regulatory Class: | II |
| Product Code: | MYN |
| Secondary Classification | |
| Classification Name | 892.2050 Picture Archive and Communication System |
| Regulatory Class: | II |
| Product Code: | LLZ |
### 3. PREDICATE DEVICE
| Primary Predicate: | Pearl Second Opinion (K210365) |
|----------------------|---------------------------------|
| Secondary Predicate: | Overjet Dental Assist (K210187) |
{4}------------------------------------------------
#### DEVICE DESCRIPTION 4.
Denti.AI Detect is a prescription use Computer-Assisted Detection (CADe) device aimed to assist dentists and dental specialists in detecting and highlighting regions of interest (ROIs) within the teeth area, which include caries and periapical radiolucency. The device is also intended to aid in the measurements of medial and distal bone levels associated with each tooth.
### ട. INTENDED USE/INDICATIONS FOR USE
Denti.AI Detect is a Computer-Assisted Detection (CADe) software device intended to be used by dental professionals, comprising dentists and dental specialists, while reading extraoral and intraoral 2D dental radiographs.
The device aims to assist in detecting and highlighting uncategorized regions of interest (ROIs) within the teeth area, which include caries and periapical radiolucency, as a second reader. The device is also intended to aid in the measurements of mesial and distal bone levels associated with each tooth.
The device is aimed to be used with images from the patients of 22 years age and older without remaining primary dentition. The device is not intended to replace a complete clinician's review or clinical judgment that considers other relevant information from the image or patient history.
### 6. SUBSTANTIAL EQUIVALENCE
## Comparison of Intended Use/Indications for Use
Both the subject device and the primary predicate device are Computer-Assisted Detection software devices intended to be used by dental professional as a second reader to identify and mark dental findings in 2D dental radiograph. While the supported age range for the subject Denti.AI device is more limited than that of the Pearl predicate (22 years and older versus 12 years and older), both devices are only intended to be used on permanent teeth. The types of findings detected by the subject device are slightly different from those detected by the predicate device, but the intended use of both is the same, namely to detect findings of interest.
The intended use of the subject device for measuring mesial and distal bone level is the same as that of the Overjet secondary predicate device. Both devices are intended to be used to support dental professionals in conjunction with a full patient evaluation. The slight differences in features do not change the intended use of the device which is to provide measurements to trained dental professionals.
# Technological Comparisons
Table 1 compares the key technological feature of the subject devices to the predicate devices: Pearl Second Opinion (K210365) and Overjet Dental Assist (K210187).
{5}------------------------------------------------
| | Subject Device | Primary Predicate<br>Device | Secondary Predicate<br>Device |
|-------------------------------------|-----------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------|
| 510(k) Number | K230144 | K210365 | K210187 |
| Applicant | Denti.AI | Pearl | Overjet |
| Device Name | Detect | Second Opinion | Dental Assist |
| Classification<br>Regulation | 892.2070 Medical Image<br>Analyzer<br>892.2050 Picture Archive<br>and Communication<br>System | 892.2070 Medical Image<br>Analyzer | 892.2050 Picture Archive<br>and Communication<br>System |
| Product Code | MYN<br>LLZ | MYN | LLZ |
| Prescription<br>Use | Yes | Yes | Yes |
| Intended Users | Dentists and Dental<br>Specialists | Dental health<br>professionals | Trained professionals<br>including, but not limited<br>to, dentists and dental<br>hygienists |
| Patient<br>Population | Adults 22 years of age<br>and older with permanent<br>dentition | Patients 12 years and<br>older with permanent<br>teeth | Adults 22 years of age and<br>older |
| Platform | Cloud-based | Windows 7 | Cloud-based |
| Imaging<br>Modality | Intraoral (bitewing,<br>periapical)<br>Extraoral (panoramic) | Intraoral (bitewing,<br>periapical) | Intraoral (bitewing,<br>periapical) |
| Supported File<br>formats | jpeg, jpg, tiff, tif, png,<br>bmp, DICOM | RVG, DICOM, JPEG,<br>TIFF, and PNG and<br>converts to JPEG | jpg, png, jfif, eop, etp, jif |
| Detection<br>Findings | Caries and Periapical<br>radiolucency | Caries, Discrepancy at<br>the margin of an existing<br>restoration, Calculus,<br>Periapical radiolucency,<br>Crown (metal, including<br>zirconia & non-metal),<br>Filling (metal & non-<br>metal), Root canal,<br>Bridge and Implants. | N/A |
| Reader<br>Workflow for<br>Detection | Second Reader | Second Reader | N/A |
| | Subject Device | Primary Predicate<br>Device | Secondary Predicate<br>Device |
| Measurements | Mesial and distal bone<br>levels associated with<br>each tooth | N/A | Mesial and distal bone<br>levels associated with each<br>tooth |
Table 1: Technological Comparison
{6}------------------------------------------------
### 7. PERFORMANCE DATA
# Biocompatibility Testing
There are no direct or indirect patient-contacting components of the subject device. Therefore, patient contact information is not needed for this device.
# Electrical safety and electromagnetic compatibility (EMC)
Not applicable. The subject device is a software-only device. It contains no electric components, generates no electrical emissions, and uses no electrical energy of any type.
# Software Verification and Validation Testing
Software verification and validation testing were conducted, and documentation was provided as recommended by FDA's Guidance for Industry and FDA Staff. "Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices." The software for this device was considered as a Moderate Level of Concern as a malfunction of, or a latent design flaw in, the Software Device could lead to an erroneous diagnosis or a delay in delivery of appropriate medical care that could lead to Minor Injury. Verification of the software was conducted to ensure that the product works as designed. Validation was conducted to validate the design and performance of the product.
# Bench Testing
Stand-alone studies were conducted to assess the performance of the Denti. Al Detect system for 1) detecting suspicious ROIs (caries and periapical radiolucencies); and 2) making measurements of distal and mesial bone levels associated with each tooth on a range of intraoral and extraoral radiographs.
The caries and periapical radiolucency study included 709 images obtained from 6 sites in the US. Study subjects aged in range from 22 to 92 and were roughly split between males and females. Ground truthing was performed by three independent dentists with the consensus rule applied to establish final reference standard. The primary endpoint for the study was to show that the lower bound of the 95% CI of the across-category wAFROC AUC exceeds the predefined threshold of 0.6. The study met its primary endpoint with an across-category wAFRPOC AUC of 0.737 and a 95% CI of (0.713. 0.761).
The bone measurement study included 193 images obtained from 9 sites in the US. Study subjects aged in range from 22 to 88 and were roughly split between males and females. Ground
{7}------------------------------------------------
truthing was performed by three independent dentists with majority rule applied to establish final reference standard. The primary study endpoints and results are shown in Table 2.
| Endpoint | Results (95% CI) |
|------------------------------------------|-------------------------------|
| Bitewing: CEJ-Bone: Sensitivity | 98.1% (96%, 99.5%) |
| Bitewing: CEJ-Bone: Specificity | 93% (88.7%, 96.7%) |
| Bitewing: CEJ-Bone: MAE | 0.513 mm (0.444 mm, 0.593 mm) |
| Bitewing: CEJ-Bone/CEJ-Root Ratio: MAE | 3.8% (3.3%, 4.4%) |
| Periapical: CEJ-Bone: Sensitivity | 98.2% (96.2%, 99.7%) |
| Periapical: CEJ-Bone: Specificity | 88.5% (82.8%, 93.4%) |
| Periapical: CEJ-Bone: MAE | 0.572 mm (0.497 mm, 0.653 mm) |
| Periapical: CEJ-Root: Sensitivity | 96.9% (94.2%, 99%) |
| Periapical: CEJ-Root: Specificity | 92.2% (87.9%, 96%) |
| Periapical: CEJ-Root: MAE | 0.735 mm (0.612 mm, 0.868 mm) |
| Periapical: CEJ-Bone/CEJ-Root Ratio: MAE | 4.3% (3.7%, 4.9%) |
| Extraoral: CEJ-Bone-Root: Sensitivity | 91.6% (89.6%, 93.6%) |
| Extraoral: CEJ-Bone-Root: Specificity | 84.3% (70.8%, 95.8%) |
| Extraoral: CEJ-Bone/CEJ-Root Ratio: MAE | 4.7% (4%, 5.5%) |
Table 2: Primary Study Endpoints and Results
All of the Acceptance Criteria were met with the exception of the CEJ-Bone Specificity on Periapical images, where the lower CI bound was slightly less than the Acceptance Criterion.
## Animal Testing
Not applicable. Animal studies are not necessary to establish the substantial equivalence of this device.
# Clinical Data
A fully crossed Multi-Reader Multi-Case (MRMC) study was conducted to evaluate the Denti.AI Detect device's effect on dental professionals' performance in detecting periapical radiolucencies and caries on a range of intraoral and extraoral radiographs. A total of 154 images taken from 5 sites located across the US were included in the study enrolled 24 dental professionals who were asked to evaluate each of the images under two conditions: an unaided read followed by a computer-aided read. The results demonstrated a statistically significant improvement in across-category reader performance when assisted by Denti.AI Detect as compared to when unassisted (aided wAFROC 0.809, unaided wAFROC 0.784, difference 0.025, p-value 0.029).
### CONCLUSION 8.
Denti.AI Detect has the same intended use as the predicate devices: to detect findings of interest and provide measurements on dental X-rays for use by trained dental professionals. While there are some small differences in technological characteristics between the subject device and the predicate devices, these differences do not raise different questions of safety and effectiveness. The results of the stand-alone and reader studies demonstrate that the performance of Denti.AI
{8}------------------------------------------------
Detect is equivalent to that of the predicate devices, and Denti.AI has demonstrated that the device complies with applicable Special Controls for Medical Image Analyzers. Therefore, Denti.AI Detect can be found substantially equivalent to the predicate devices.
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.