Authorized purpose: Analyzes bitewing, periapical, and panoramic intraoral radiographs from patients aged 3 years and older to identify and localize specified suspected dental findings, historical treatments, and normal anatomy; diagnostic use remains with trained dental professionals.
Clinical role
Computer-assisted detection device that returns bounding boxes or segmentation outlines for suspect dental findings, historical treatments and normal anatomy on radiographs; for suspect findings it is an adjunct tool that should not replace a dentist's review.
Images and patients
X-ray/Radiography · Dental/Maxillofacial
Key limitation
Keep in mind: The outputs are suspected findings and normal-anatomy or historical-treatment annotations for clinician review; the FDA indication does not make the software a stand-alone diagnosis or treatment planner.
Clinical detailsPurpose, workflow fit, evidence, and safety record
Workflow navigation pilot
Workflow role has not yet been reviewed for this navigation pilot.
A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources
What does this software do?Authorized purpose: Analyzes bitewing, periapical, and panoramic intraoral radiographs from patients aged 3 years and older to identify and localize specified suspected dental findings, historical treatments, and normal anatomy; diagnostic use remains with trained dental professionals.
Which images or clinical context are in scope?Modality: X-ray/Radiography Anatomy or clinical context: Dental/Maxillofacial Input: Bitewing, periapical and panoramic radiographs from patients aged 3 years or older with primary, mixed and/or permanent dentition, with patient scope depending on the indication; panoramic radiographs are used only for historical treatment and normal anatomy indications.
Who uses it?Intended users: Trained dental professionals including dentists and dental hygienists. Only dentists performing diagnostic activities shall use the suspect dental finding indications.
What does the software produce?Output: The device outputs a binary indication to identify the presence or absence of findings for each indication. If findings are present, the device outputs the number of findings by finding type and the coordinates of bounding boxes and/or segmentation outlines for each finding. If no findings are present, the device outputs a clear indication that there are no findings identified for each indication. For caries and calculus, a segmentation (isocontour) view is available as an alternative to bounding boxes. For caries and periapical radiolucency, a second operating point (high sensitivity vs. high specificity) is available as a user toggle. Normal tooth anatomy segmentations (enamel, pulp, crown dentin, root dentin) can be toggled on and off.
What is its most important limitation?Key limitation: The outputs are suspected findings and normal-anatomy or historical-treatment annotations for clinician review; the FDA indication does not make the software a stand-alone diagnosis or treatment planner.
Clinical takeaway. Clinical role: Analyzes bitewing, periapical, and panoramic intraoral radiographs from patients aged 3 years and older to identify and localize specified suspected dental findings, historical treatments, and normal anatomy; diagnostic use remains with trained dental professionals.
Evidence takeaway. Evidence from the reviewed source record: Study type: Both. Cases: 1445. Sites: 35. Reader-study cases: 378. Readers: 20
Evidence context
Evidence context not reviewed for this FDA record.
Public-label constraints
Label constraints have not been reviewed for this exact FDA record. Unknown is not all ages or evidence of unsuitability.
Public-label constraints, not patient-level eligibility or a medical recommendation. Training and evaluation populations are separate. Read the original labeling and confirm the exact release and protocol.
Purpose
Analyzes bitewing, periapical, and panoramic intraoral radiographs from patients aged 3 years and older to identify and localize specified suspected dental findings, historical treatments, and normal anatomy; diagnostic use remains with trained dental professionals.
Exact FDA submission
Checked 2026-09-06
Exact clinical-use normalization from the FDA packet; this text is also the locked corrections value.
Computer-assisted detection device that returns bounding boxes or segmentation outlines for suspect dental findings, historical treatments and normal anatomy on radiographs; for suspect findings it is an adjunct tool that should not replace a dentist's review.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Videa Dental AI is a computer-assisted detection (CADe) device that analyzes intraoral radiographs to identify and localize the following features." … "the device returns a set of bounding boxes and/or segmentation outlines depending on the indication representing the suspect dental finding, historical treatment or normal anatomy detected.". Read from the exact FDA decision document on 2026-11-14.
Bitewing, periapical and panoramic radiographs from patients aged 3 years or older with primary, mixed and/or permanent dentition, with patient scope depending on the indication; panoramic radiographs are used only for historical treatment and normal anatomy indications.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Videa Dental AI is indicated for the review of bitewing, periapical, and panoramic radiographs acquired from patients aged 3 years or older." … "Depending on the specific VDA indication for use, the intended patients of Videa Dental AI are patients 3 years of age and older above with primary, mixed and/or permanent dentition". Read from the exact FDA decision document on 2026-11-14.
The device outputs a binary indication to identify the presence or absence of findings for each indication. If findings are present, the device outputs the number of findings by finding type and the coordinates of bounding boxes and/or segmentation outlines for each finding. If no findings are present, the device outputs a clear indication that there are no findings identified for each indication. For caries and calculus, a segmentation (isocontour) view is available as an alternative to bounding boxes. For caries and periapical radiolucency, a second operating point (high sensitivity vs. high specificity) is available as a user toggle. Normal tooth anatomy segmentations (enamel, pulp, crown dentin, root dentin) can be toggled on and off.
Exact FDA submission
Checked 2026-09-01
Clinical output reported in the exact-submission ACR model card.
Trained dental professionals including dentists and dental hygienists. Only dentists performing diagnostic activities shall use the suspect dental finding indications.
Exact FDA submission
Checked 2026-09-01
Intended-user text reported in the exact-submission ACR model card.
The outputs are suspected findings and normal-anatomy or historical-treatment annotations for clinician review; the FDA indication does not make the software a stand-alone diagnosis or treatment planner.
Exact FDA submission
Checked 2026-09-06
Exact-product limitations and clinician-review boundary from the FDA packet.
Metrics are shown only when they are tied to a source, endpoint, population, and tested product version. Candidate literature without exact product and version linkage is not shown as product evidence.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Videa Dental AI regulatory performance study summary
DesignStand-alone performance and reader study (ACR AI Central category)
PopulationAdult and Pediatric
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K251002
Samplen=1445
Sites35
IndependenceIndependence not established
K251002
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No native submission-identifier match was found in the checked openFDA radiology recall snapshot. Product-name, manufacturer, and adverse-event searches remain necessary; this does not establish that no recall or safety report exists.
Pricing & contractsPublic price, contract terms, and reimbursement
CMS states that Original Medicare does not pay for care, treatment, filling, removal or replacement of teeth or the structures directly supporting them (Social Security Act 1862(a)(12), 42 CFR 411.15(i)), except for inpatient hospital services and dental services that are integral to certain Medicare-covered medical services. This product's FDA-cleared use is analysis of dental radiographs, which falls in routine dental care, so no separate Medicare payment is expected outside those exceptions. Dental plan, CDT coding and private payer treatment of AI radiograph analysis were not reviewed, and no price or payment amount was established.
Original Medicare dental-service exclusion applies to routine dental care; dental plan and private payer treatment not reviewed
Medicare (Original Medicare, CMS) · United States
Service-level exclusion from the CMS dental coverage page; it does not address this product by name and does not establish coverage or payment by dental plans or other payers.
IT implementationDeployment, interfaces, data handling, and support
System and version relationships
Match the AI release, system build, configuration and region. Source documentation does not establish acceptance of an installed system.
No specific system/version pairing has completed review for this FDA record. A broad DICOM or product-family statement does not establish a named viewer build's support.
Public source context, not tested interoperability. Each hop needs its own release/configuration evidence. Missing or unavailable routes are not documented incompatibility. All local tests are planned, not passed; no installed-system acceptance is recorded.
Acquisition/source → routing → AI processing → returned objects → viewer/worklist/report → support owner
No specific route context has been source-reviewed for this record. Obtain both endpoint builds and documents; this is not a finding of incompatibility.
Acquisition/source
Source context, not route validation: Bitewing, periapical and panoramic radiographs from patients aged 3 years or older with primary, mixed and/or permanent dentition, with patient scope depending on the indication; panoramic radiographs are used only for historical treatment and normal anatomy indications.
Scope: Exact FDA submission. Packet wording: "Videa Dental AI is indicated for the review of bitewing, periapical, and panoramic radiographs acquired from patients aged 3 years or older." … "Depending on the specific VDA indication for use, the intended patients of Videa Dental AI are patients 3 years of age and older above with primary, mixed and/or permanent dentition". Read from the exact FDA decision document on 2026-11-14.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes a service available via an API that is accessed through the dental practitioner's image viewer, from which users upload radiographs and review results, including finding counts and bounding box or segmentation outline coordinates. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "device itself is available as a service via an API (Application Programming Interface) behind a firewalled network." … "VDA is accessed by the dental practitioner through their dental image viewer. From within the dental viewer the user can upload a radiograph to VDA and then review the results.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The exact FDA package describes Videa Dental AI as cloud-based software available as a service via an API (Application Programming Interface) behind a firewalled network. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "Videa Dental AI (VDA) software is a cloud-based AI-powered medical device for the automatic" … "device itself is available as a service via an API (Application Programming Interface) behind a firewalled network.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: The device outputs a binary indication to identify the presence or absence of findings for each indication. If findings are present, the device outputs the number of findings by finding type and the coordinates of bounding boxes and/or segmentation outlines for each finding. If no findings are present, the device outputs a clear indication that there are no findings identified for each indication. For caries and calculus, a segmentation (isocontour) view is available as an alternative to bounding boxes. For caries and periapical radiolucency, a second operating point (high sensitivity vs. high specificity) is available as a user toggle. Normal tooth anatomy segmentations (enamel, pulp, crown dentin, root dentin) can be toggled on and off.
Scope: Exact FDA submission. Clinical output reported in the exact-submission ACR model card.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: The device outputs a binary indication to identify the presence or absence of findings for each indication. If findings are present, the device outputs the number of findings by finding type and the coordinates of bounding boxes and/or segmentation outlines for each finding. If no findings are present, the device outputs a clear indication that there are no findings identified for each indication. For caries and calculus, a segmentation (isocontour) view is available as an alternative to bounding boxes. For caries and periapical radiolucency, a second operating point (high sensitivity vs. high specificity) is available as a user toggle. Normal tooth anatomy segmentations (enamel, pulp, crown dentin, root dentin) can be toggled on and off.
Scope: Exact FDA submission. Clinical output reported in the exact-submission ACR model card.
Confirm the named viewer/worklist/report build, display behavior and report transfer. Output support alone does not establish this endpoint. The displayed source describes output, not validated end-to-end delivery.
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
Planned local route tests
No tests below have been performed or accepted.
Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
Updates and rollback (planned). Define version change control, revalidation triggers, stop-use criteria and a tested rollback route.
Local implementation checklist
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
The exact FDA package describes Videa Dental AI as cloud-based software available as a service via an API (Application Programming Interface) behind a firewalled network. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Videa Dental AI (VDA) software is a cloud-based AI-powered medical device for the automatic" … "device itself is available as a service via an API (Application Programming Interface) behind a firewalled network.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The exact FDA package describes a service available via an API that is accessed through the dental practitioner's image viewer, from which users upload radiographs and review results, including finding counts and bounding box or segmentation outline coordinates. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "device itself is available as a service via an API (Application Programming Interface) behind a firewalled network." … "VDA is accessed by the dental practitioner through their dental image viewer. From within the dental viewer the user can upload a radiograph to VDA and then review the results.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Sources & review detailsFDA identity, research record, source ledger, and history
Regulatory identity
FDA record and catalog context
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
This audit distinguishes completed source review from fields that have not yet been researched.
Human reviewedStatus
2026-09-07Last searched
26Fields reviewed
10Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
Stored exact-submission candidate metadata had zero PubMed and ClinicalTrials.gov identifiers; this metadata screening is not a full paper or registry-record review. The current discovery snapshot contains 0 PubMed and 0 ClinicalTrials.gov candidate records; its dated, count-matched human screening remains current. Unlinked candidates remain quarantined. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads were screened against the exact product and tested version. Unlinked records remain quarantined.
Source classes: fda ai list, fda decision summary, acr ai central product, vendor product page, literature index, trial registry, payer policy, pubmed, clinical trials, openfda device recall
Field review details
Recorded state, verification date, notes and sources for fields without a publishable value. Conflicting records stay explicitly unsettled here; no plain settled value is shown for them.
Public pricing: Not publicly available - checked 2026-09-06 - Exact FDA submission
Official non-FDA product sources were reviewed for buyer and workflow context, but no exact-submission amount, currency, unit, term, or implementation fee was displayed. A vendor quote remains required.
Pricing model: Not yet reviewed
Setup and integration fees: Not yet reviewed
Recurring fees: Not yet reviewed
Minimum commitment: Not yet reviewed
Contract duration: Not yet reviewed
Renewal terms: Not yet reviewed
Cancellation terms: Not yet reviewed
Support and service terms: Not yet reviewed
Trial or pilot terms: Not yet reviewed
Data hosting location: Not yet reviewed
Data retention: Not yet reviewed
Documented data use: Not yet reviewed
Hardware requirements: Not yet reviewed
Network requirements: Not yet reviewed
Identity and access: Not yet reviewed
Security: Not verified - checked 2026-08-13 - Exact FDA submission
FDA authorization does not establish the current commercial security posture. Request data-flow diagrams, hosting and retention details, access controls, audit logging, attestations, and incident-response documentation.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-08-13 - Exact FDA submission
Training, onboarding, competency, and support commitments are commercial implementation details that require current vendor documentation.
Monitoring: Not verified - checked 2026-08-13 - Exact FDA submission
Local acceptance testing, production monitoring, drift review, update control, and incident escalation require a current vendor and site-specific governance plan.
Authorized purpose: Second Opinion CC assists dental health professionals as a second reader for caries on bitewing and periapical radiographs of permanent teeth in patients 19 years or older, displaying editable polygonal contours for clinician review; it does not replace a complete dentist review or clinical judgment.
Authorized purpose: Analyzes two-dimensional bitewing and periapical radiographs of permanent teeth in patients aged 15 and older to identify and localize caries, calculus, periapical radiolucency, root canal filling deficiency, discrepancy at an existing restoration margin, and bone loss; also supports alveolar bone-level measurement and restoration/dental-anatomy segmentation as an adjunct to dentist review.
Authorized purpose: Provides automated concurrent-read detection and segmentation of caries on bitewing radiographs in patients 18 and older, adding information for the dentist while requiring complete dentist review and judgment.
Copy this public context and add the field, proposed wording and original source before sending. Nothing here is submitted automatically. Form-specific prefill has not been verified.
Permission to display a submission is not evidence verification. A submission enters editorial review; it does not approve a public change. Form availability, data entry, receipt, review and publication are separate steps. Data entry and receipt remain unverified.
Accepted repository change history
No entry has been added to this scoped change history for this record. This is not proof that the record never changed.