VELMENI for DENTISTS (V4D)
K250753Velmeni Inc. · cleared 2025-09-02 · product code MYN · Radiology
Premarket evidence — what FDA accepted
Device typesamd
source quote (p.5)
“V4D software medical device comprises of the following key components:”
AlgorithmMachine Learning (ML) Engine delivers V4D's core ML capabilities through the radiograph type classifier, condition detection module, tooth numbering module, and merging module. The device contains models trained for detecting predetermined conditions (caries and fillings/restorations, fixed prostheses, and implants).
source quote (p.5)
“Machine Learning (ML) Engine delivers V4D's core ML capabilities through the radiograph type classifier, condition detection module, tooth numbering module, and merging module. This submission provided a set of PCCPs that Velmeni will follow to validate the standalone updates to the identified Machine Learning Software Device functions (ML-DSF) of the device, namely the Condition Detection Modules for each radiograph type (bitewing, periapical, and panoramic) that contains the models trained for detecting predetermined conditions (caries and fillings/restorations, fixed prostheses, and implants).”
Adaptive (vs locked)Yes
source quote (p.6)
“The PCCPs include key components (data management, retraining, performance evaluation, update procedures, and impact assessments) that describe the plan for developing, validating, and implementing the modifications using post-market and real-world data to reduce false positives and negatives. The predefined performance and validation requirements must be met prior to the manual update of the device. Re-training will be triggered if performance or data drift metrics are observed.”
PCCPYes
source quote (p.2)
“FDA's substantial equivalence determination also included the review and clearance of your Predetermined Change Control Plan (PCCP).”
Cybersecurity addressedYes
source quote (p.9)
“Velmeni maintains adherence to FDA guidance, Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions, throughout the course of model modifications under the authorized PCCP.”
Validation studies (0)
FDA source did not describe a validation study.
Reported performance (0 observations)
FDA source did not state a quantitative performance metric — non-reporting is itself the signal.
Each value carries its own analysis unit and task — never compare or pool across devices. Source: 510(k) summary PDF.
Predicate network
Postmarket — what happened after clearance
0
recalls in product code, 24mo
0
MAUDE reports in code, 12mo
-100%
vs code's own 3-yr baseline
0
drift signals on this device
Recall and MAUDE counts are product-code-level (reports aren't reliably attributable to one device). Signals are descriptive observables with sources — never a judgment that the device is unsafe or drifting. Snapshot 2026-07-08.
Reimbursement — how devices like this got paid
Not yet tracked — no payment pathway indexed for this clearance (the reimbursement corpus is a growing seed set).