DS Core Detect is a concurrent read, computer assisted detection software intended to aid the dentist in the incidental detection of permanent teeth that may be associated with periapical radiolucencies in CBCT images. The device is not intended as a replacement for a complete dentist’s review or a replacement of their clinical judgment. The device is to be used by licensed dentists. The device is designed for patients who already have CBCT data obtained for other reasons. DS Core Detect does not generate X-ray images and does not provide an indication for taking such images. The device is intended for adults aged 22 years and older with permanent teeth.
Device Story
Cloud-based SaMD; utilizes ML-enabled CADe to analyze existing CBCT images for periapical radiolucency (PARL). Input: CBCT data acquired for other clinical reasons. Processing: identifies teeth potentially associated with PARL; generates a list of flagged teeth and a visual PARL 'map'. Output: displayed within dental image viewer for practitioner review. Workflow: dentist reviews findings; retains full autonomy to confirm or reject device-flagged teeth. Clinical impact: aids incidental detection of PARL; supports diagnostic decision-making; does not replace standard of care or clinical judgment. Used in dental clinics by licensed dentists.
Clinical Evidence
Performance validated via standalone study (n=306 CBCTs) and MRMC reader study (n=11 U.S. dentists). Standalone sensitivity: 0.78 (High) / 0.66 (Standard); specificity: 0.93 (High) / 0.97 (Standard). MRMC study showed significant improvement in AUC (0.415 unaided vs 0.639 aided; difference 0.224, 95% CI 0.124-0.324) and sensitivity (0.421 unaided vs 0.649 aided; difference 0.227, 95% CI 0.124-0.330) with minimal impact on specificity.
Technological Characteristics
Cloud-based SaMD; ML-enabled CADe algorithm. Input: 3D CBCT images. Output: list of teeth with potential PARL and visual PARL map. Operates on existing CBCT data; no X-ray generation. Designed for adult patients (22+) with permanent teeth. Software-based analysis.
Indications for Use
Indicated for licensed dentists to aid in incidental detection of permanent teeth associated with periapical radiolucencies (PARL) in adult patients (aged 22+) using existing CBCT data. Not for use as a replacement for clinical judgment or standard of care diagnosis.
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}
FDA U.S. FOOD & DRUG ADMINISTRATION
January 7, 2026
Dentsply Sirona Inc
% Deepthi Paknikar
Senior Manager, Regulatory Affairs
221 West Philadelphia St.
YORK, PA 17401
Re: K253009
Trade/Device Name: DS Core Detect
Regulation Number: 21 CFR 892.2070
Regulation Name: Medical Image Analyzer
Regulatory Class: Class II
Product Code: MYN
Dated: December 5, 2025
Received: December 5, 2025
Dear Deepthi Paknikar:
We have reviewed your section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (the Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K253009 - Deepthi Paknikar
Page 2
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality 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 (reporting of medical device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-products); good manufacturing practice requirements as set forth in the quality 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.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-
{2}
K253009 - Deepthi Paknikar
Page 3
assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,

Lu Jiang, Ph.D.
Assistant Director
Diagnostic X-Ray Systems Team
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
Enclosure
{3}
FORM FDA 3881 (8/23)
Page 1 of 1
PSC Publishing Services (301) 443-6740
EF
| DEPARTMENT OF HEALTH AND HUMAN SERVICES Food and Drug Administration Indications for Use | Form Approved: OMB No. 0910-0120 Expiration Date: 07/31/2026 See PRA Statement below. |
| --- | --- |
| 510(k) Number (if known) K253009 | |
| Device Name DS Core Detect | |
| Indications for Use (Describe) DS Core Detect is a concurrent read, computer assisted detection software intended to aid the dentist in the incidental detection of permanent teeth that may be associated with periapical radiolucencies in CBCT images. The device is not intended as a replacement for a complete dentist’s review or a replacement of their clinical judgment. The device is to be used by licensed dentists. The device is designed for patients who already have CBCT data obtained for other reasons. DS Core Detect does not generate X-ray images and does not provide an indication for taking such images. The device is intended for adults aged 22 years and older with permanent teeth. | |
| Type of Use (Select one or both, as applicable) ☑ 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.” | |
{4}
Page 1 of 4
510(k) Summary
510(k) #: K253009
Applicant Name: Dentsply Sirona Inc
Applicant Address: 221 West Philadelphia St. York PA 17401 United States
Applicant Contact Telephone: 630-201-1612
Applicant Contact: Dr. Deepthi Paknikar
Applicant Contact Email: Deepthi.Paknikar@dentsplysirona.com
Device Trade Name: DS Core Detect
Common Name: Medical image analyzer
Classification Name: Medical Image Analyzer
Regulation Number: 21 CFR 892.2070
Product Code(s): MYN
Predicate Device: Videa Dental Assist (K232384)
Common Name: Medical image analyzer
Classification Name: Medical Image Analyzer
Regulation Number: 21 CFR 892.2070
Product Code(s): MYN
Device Description Summary
The DS Core Detect device is a cloud-based SaMD that is a Computer Aided Detection "CADe" Machine Learning "ML" enabled device for the aid in incidental detection of permanent teeth that may have periapical radiolucency "PARL" on a CBCT image. The device is designed for patients who already have CBCT data obtained from a CBCT imaging system for other reasons. DS Core Detect does not generate X-ray images and does not provide an indication for taking such images.
The device itself is accessed by the dental practitioner through their dental image viewer. From within the dental viewer the user can view the CBCT with results from the subject device. The device will provide a list of teeth that may potentially have PARL and a corresponding PARL "map" to visualize where the PARL is detected. The user has completely autonomy to confirm or reject a tooth that is flagged by the device as potentially PARL positive.
The intended users of the device are trained and licensed dentists. The intended patient population for the device is adult patients with permanent teeth at least age 22.
Intended Use/Indications for Use
DS Core Detect is a concurrent read, computer assisted detection software intended to aid the dentist in the incidental detection of permanent teeth that may be associated with periapical radiolucencies in CBCT images. The device is not intended as a replacement for a complete dentist's review or a replacement of their clinical judgment. The device is to be used by licensed dentists. The device is designed for patients who already have CBCT data obtained for other
{5}
reasons. DS Core Detect does not generate X-ray images and does not provide an indication for taking such images.
The device is intended for adults aged 22 years and older with permanent teeth.
## Indications for Use Comparison
The minor differences in indications for use between the subject and predicate do not constitute a new intended use. Both devices are diagnostic aids for detection of PARL. The primary predicate device provides PARL findings for 2D periapical images whereas the subject device detects PARL positive teeth on a CBCT image. The predicate is indicated for bitewing, periapical, and panoramic radiographs and detects multiple pathologies, restorations, and normal anatomy, whereas the subject device is indicated only for incidental detection of PARL on CBCT. The subject device is also specific with regards to being used with CBCTs that have already been taken for other reasons, for aiding with incidental detection of PARL only. Both devices are SaMD and AI/ML enabled. Both devices are diagnostic aids only, not a replacement for standard of care diagnosis.
## Technological Comparison
The main technological difference is that the predicate device provides PARL detection, as well as multiple other detections (anatomy, caries, etc.) for 2D dental radiographs, whereas the subject device provides PARL detection on 3D CBCT images. The predicate device spans a large age range and permanent and primary teeth findings, whereas the subject device is limited to permanent teeth for patients 22 and older. The subject device input is CBCT's taken for other reasons for the incidental detection of PARL, whereas the predicate device has 2D bitewing, periapical, and panoramic images as the input. The subject device will provide a list of teeth that may potentially have PARL which the user must confirm or reject and a corresponding PARL "map" to visualize where the PARL is detected. The predicate device outputs a set of bounding boxes for each finding, including PARL. The minor difference in technological characteristics do not raise a concern of substantial equivalence as demonstrated by the performance testing of the subject device.
## Non-Clinical and/or Clinical Tests Summary & Conclusions
The DS Core Detect device underwent comprehensive performance testing including standalone testing and a Multi-Reader Multi-Case Reader Study (MRMC). Software verification and validation testing was completed per applicable standards and agency guidance.
DS Core Detect indications detections in two operating points: Standard sensitivity and High sensitivity, whereby sensitivity describes the portion of detected teeth with evidence of periapical radiolucency. The standalone study assessed the performance of the device compared to a consensus ground truth. The MRMC study evaluated reader performance with and without the assistance of the device, in a fully crossed study design.
Depending on the operating point, these teeth are detected with the following standalone study accuracy with 95% CI's:
{6}
1. Sensitivity: High sensitivity 0.78 [0.74; 0.81], Standard sensitivity 0.66 [0.62; 0.70]
2. Specificity: High sensitivity 0.93 [0.92; 0.94], Standard sensitivity 0.97 [0.97; 0.98]
Standalone Study Subgroup performance testing subjects included patients 22 and older from various clinical sites across the U.S., with permanent teeth, with CBCT images. Subgroup reporting included lesion size, age, device, gender, and endodontic treatment status, with results as follows:
| Operating point | Group | | \( Sensitivity^1 \) | 95% confi-dence interval | \( Specificity^1 \) | 95% confi-dence interval |
| --- | --- | --- | --- | --- | --- | --- |
| High sensitivity | Lesion | >8 mm3 | 0.82 | [0.79; 0.86] | 0.93 | [0.92; 0.94] |
| | | ≤ 8 mm3 | 0.65 | [0.59; 0.71] | 0.93 | [0.92; 0.94] |
| | Age | >52 years | 0.76 | [0.71; 0.80] | 0.95 | [0.94; 0.96] |
| | | ≤ 52 years | 0.8 | [0.75; 0.84] | 0.92 | [0.91; 0.93] |
| | Device | Orthophos S/SL | 0.76 | [0.72; 0.81] | 0.93 | [0.91; 0.94] |
| | | Axeos | 0.80 | [0.75;0.84] | 0.94 | [0.91; 0.94] |
| | Gender | Male | 0.78 | [0.73;0.83] | 0.93 | [0.92; 0.95] |
| | | Female | 0.79 | [0.74; 0.85] | 0.93 | [0.91; 0.95] |
| | Endodontic treatment | Tooth treated | 0.82 | [0.78; 0.86] | 0.82 | [0.77; 0.87] |
| | | Tooth un-treated | 0.72 | [0.67; 0.78] | 0.94 | [0.93; 0.95] |
| Standard sensitivity | Lesion | >8 mm3 | 0.73 | [0.68; 0.77] | 0.97 | [0.97; 0.98] |
| | | ≤ 8 mm3 | 0.50 | [0.43; 0.57] | 0.97 | [0.97; 0.98] |
| | Age | >52 years | 0.64 | [0.58; 0.70] | 0.98 | [0.97; 0.98] |
| | | ≤ 52 years | 0.68 | [0.62; 0.74] | 0.97 | [0.96; 0.98] |
| | Device | Orthophos S/SL | 0.64 | [0.58; 0.69] | 0.97 | [0.96; 0.98] |
| | | Axeos | 0.70 | [0.64; 0.76] | 0.98 | [0.97; 0.98] |
| | Gender | Male | 0.67 | [0.60; 0.73] | 0.97 | [0.96; 0.98] |
| | | Female | 0.70 | [0.64; 0.76] | 0.97 | [0.96; 0.98] |
| | Endodontic treatment | Tooth treated | 0.75 | [0.70; 0.80] | 0.90 | [0.86; 0.94] |
| | | Tooth un-treated | 0.56 | [0.50; 0.62] | 0.98 | [0.97; 0.98] |
| 1 Result of a representative standalone study with 306 CBCTs | | | | | | |
The MRMC Tooth Level AUC results are as follows:
| Number of U.S. readers = 11 | Unaided | Aided | Difference |
| --- | --- | --- | --- |
| | OR Model-Based AUC Estimates (95% CIs) | | |
| | 0.415 (0.279, 0.550) | 0.639 (0.529, 0.749) | 0.224 (0.124, 0.324) |
| | Tooth Level Sensitivity (95% CIs) | | |
| | 0.421 (0.281, 0.562) | 0.649 (0.535, 0.763) | 0.227 (0.124, 0.330) |
| | Tooth Level Specificity (95% CIs) | | |
| | 0.962 (0.928, 0.995) | 0.946 (0.915, 0.976) | -0.016 (-0.034, 0.002) |
{7}
Page 4 of 4
# Conclusion
The standalone and MRMC study results collectively demonstrate that the device is as safe, as effective, and performs as well as or better than the legally marketed 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.