Authorized purpose: Assists dentists in detecting caries, fillings/restorations, fixed prostheses, and implants on digital bitewing, periapical, and panoramic radiographs of permanent teeth in patients aged 15 years and older; final diagnoses and treatment plans remain the dentist's responsibility.
Clinical role
Concurrent-read computer-assisted detection software that assists dentists in detecting caries, fillings/restorations, fixed prostheses and implants on dental radiographs as additional information; it does not replace the dentist's examination, and final diagnoses and treatment plans remain the dentist's responsibility.
Images and patients
X-ray/Radiography · Dental/Maxillofacial
Key limitation
Keep in mind: This device is not intended as a replacement for a complete examination by the dentist or their clinical judgment that considers other relevant information from the image, patient history, or actual in vivo clinical assessment. Final diagnoses and patient treatment plans are the responsibility of the dentist.
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: Assists dentists in detecting caries, fillings/restorations, fixed prostheses, and implants on digital bitewing, periapical, and panoramic radiographs of permanent teeth in patients aged 15 years and older; final diagnoses and treatment plans remain the dentist's responsibility.
Which images or clinical context are in scope?Modality: X-ray/Radiography Anatomy or clinical context: Dental/Maxillofacial Input: XRAY images or data. Inclusion criteria: Digital bitewing, periapical, and panoramic radiographs of permanent teeth in patients 15 years of age or older
Who uses it?Intended users: Dentists
What does the software produce?Output: The ML Engine delivers V4D's core ML capabilities through the radiograph type classifier, condition detection module, tooth numbering module, and merging module. The AI-Worker accepts radiograph analysis requests from Backend API via the Queue, passes gray scale radiographs to the ML Engine in the supported extensions (jpeg and png), and returns the ML analysis results to the Backend API.
What is its most important limitation?Key limitation: This device is not intended as a replacement for a complete examination by the dentist or their clinical judgment that considers other relevant information from the image, patient history, or actual in vivo clinical assessment. Final diagnoses and patient treatment plans are the responsibility of the dentist.
Clinical takeaway. Clinical role: Assists dentists in detecting caries, fillings/restorations, fixed prostheses, and implants on digital bitewing, periapical, and panoramic radiographs of permanent teeth in patients aged 15 years and older; final diagnoses and treatment plans remain the dentist's responsibility.
Evidence takeaway. Evidence from the reviewed source record: The proposed device remains unchanged from the predicate Velmeni for Dentists cleared under K240003, hence, no additional software testing was conducted. The intended use of both the predicate device and the proposed device is identical. The existing data from the previous testing remains applicable.
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
Assists dentists in detecting caries, fillings/restorations, fixed prostheses, and implants on digital bitewing, periapical, and panoramic radiographs of permanent teeth in patients aged 15 years and older; final diagnoses and treatment plans remain the dentist's responsibility.
Exact FDA submission
Checked 2026-09-19
Clinical-use display mirrors the exact FDA-supported purpose reconciled from the decision-summary packet.
Concurrent-read computer-assisted detection software that assists dentists in detecting caries, fillings/restorations, fixed prostheses and implants on dental radiographs as additional information; it does not replace the dentist's examination, and final diagnoses and treatment plans remain the dentist's responsibility.
Exact FDA submission
Checked 2026-11-14
Packet wording: "VELMENI for DENTISTS (V4D) is a concurrent-read, computer-assisted detection software intended to assist dentists in the clinical detection of dental caries, fillings/restorations, fixed prostheses, and implants" … "This device provides additional information for dentists in examining radiographs of patients’ teeth. This device is not intended as a replacement for a complete examination by the dentist". Read from the exact FDA decision document on 2026-11-14.
XRAY images or data. Inclusion criteria: Digital bitewing, periapical, and panoramic radiographs of permanent teeth in patients 15 years of age or older
Exact FDA submission
Checked 2026-09-19
Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.
The ML Engine delivers V4D's core ML capabilities through the radiograph type classifier, condition detection module, tooth numbering module, and merging module. The AI-Worker accepts radiograph analysis requests from Backend API via the Queue, passes gray scale radiographs to the ML Engine in the supported extensions (jpeg and png), and returns the ML analysis results to the Backend API.
Exact FDA submission
Checked 2026-09-19
The exact device description supports the ML capabilities and returned analysis results, but it does not state the current overlay/localization wording.
This device is not intended as a replacement for a complete examination by the dentist or their clinical judgment that considers other relevant information from the image, patient history, or actual in vivo clinical assessment. Final diagnoses and patient treatment plans are the responsibility of the dentist.
Exact FDA submission
Checked 2026-09-19
The exact indications for use provide the clinician-review and final-responsibility boundary; commercial deployment and pricing are not stated in the packet.
The proposed device remains unchanged from the predicate Velmeni for Dentists cleared under K240003, hence, no additional software testing was conducted. The intended use of both the predicate device and the proposed device is identical. The existing data from the previous testing remains applicable.
Exact FDA submission
Checked 2026-09-19
The exact performance section states the software-testing and existing-data boundary for the proposed device.
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.
Evidence summary
The proposed device remains unchanged from the predicate Velmeni for Dentists cleared under K240003, hence, no additional software testing was conducted. The intended use of both the predicate device and the proposed device is identical. The existing data from the previous testing remains applicable.
FDA source
Exact FDA submission
Checked 2026-09-19
The exact performance section states the software-testing and existing-data boundary for the proposed device.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Safety and lifecycle
Postmarket record
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: XRAY images or data. Inclusion criteria: Digital bitewing, periapical, and panoramic radiographs of permanent teeth in patients 15 years of age or older
Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes VELMENI BRIDGE, a non-medical interface available with V4D that acts as a conduit enabling data and information exchange between the device's Backend API and third-party software such as patient management or imaging software. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "The following non-medical interfaces are also available with VELMENI for DENTISTS (V4D):" … "VELMENI BRIDGE (VB) acts as a conduit enabling data and information exchange between Backend API and third-party software like Patient Management or Imaging Software". 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 V4D components including a web application interface that is the user's point of interaction, a backend API, and an AI-Worker that takes analysis requests via a queue and passes radiographs to the ML Engine. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "Web Application Interface delivers front-end capabilities and is the point of interaction between the device and the user." … "Backend API allows interaction between all the components, as defined in this section, in order to fulfill the user's requests on the web application interface.". 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 ML Engine delivers V4D's core ML capabilities through the radiograph type classifier, condition detection module, tooth numbering module, and merging module. The AI-Worker accepts radiograph analysis requests from Backend API via the Queue, passes gray scale radiographs to the ML Engine in the supported extensions (jpeg and png), and returns the ML analysis results to the Backend API.
Scope: Exact FDA submission. The exact device description supports the ML capabilities and returned analysis results, but it does not state the current overlay/localization wording.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: The ML Engine delivers V4D's core ML capabilities through the radiograph type classifier, condition detection module, tooth numbering module, and merging module. The AI-Worker accepts radiograph analysis requests from Backend API via the Queue, passes gray scale radiographs to the ML Engine in the supported extensions (jpeg and png), and returns the ML analysis results to the Backend API.
Scope: Exact FDA submission. The exact device description supports the ML capabilities and returned analysis results, but it does not state the current overlay/localization wording.
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 V4D components including a web application interface that is the user's point of interaction, a backend API, and an AI-Worker that takes analysis requests via a queue and passes radiographs to the ML Engine. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Web Application Interface delivers front-end capabilities and is the point of interaction between the device and the user." … "Backend API allows interaction between all the components, as defined in this section, in order to fulfill the user's requests on the web application interface.". 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 VELMENI BRIDGE, a non-medical interface available with V4D that acts as a conduit enabling data and information exchange between the device's Backend API and third-party software such as patient management or imaging software. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The following non-medical interfaces are also available with VELMENI for DENTISTS (V4D):" … "VELMENI BRIDGE (VB) acts as a conduit enabling data and information exchange between Backend API and third-party software like Patient Management or Imaging Software". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The official 2D product page identifies panoramic, bitewing, and periapical X-rays as supported inputs and describes near-real-time analysis in seconds.
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.
Exact FDA record reviewedStatus
2026-09-19Last searched
26Fields reviewed
11Source 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, fda decision summary packet, 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: 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.
Authorized purpose: Acts as a CADe second reader to detect and segment caries on periapical radiographs of permanent teeth in patients aged 12 years and older; clinicians review the contours and percentage analysis in context.
Authorized purpose: Aids dentists reviewing bitewing and periapical radiographs of permanent teeth by detecting/segmenting caries and periapical radiolucencies, identifying restorations and dental anatomy, and measuring mesial/distal bone levels; it does not replace dentist review.
Authorized purpose: Aids dental professionals in detecting caries on digital bitewing and periapical radiographs from patients aged 4 years and older with primary, permanent, or mixed dentition; polygon overlays require clinical review.
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.