FDA-cleared profile

TechCare Trauma

Milvue · X-ray/Radiography · FDA-cleared (510(k))

Authorized purpose: Aids clinicians and radiologists reviewing 2D X-ray radiographs by detecting, localizing, and characterizing fractures across the FDA-listed appendicular, hip/pelvis, clavicle, and thorax/rib examinations, and by detecting elbow joint effusion on lateral elbow or forearm views in children/adolescents and adults; results are not standalone clinical decisions.

Clinical role
Detection, localization, or diagnostic support as a non-standalone concurrent aid.
Images and patients
X-ray/Radiography · MSK
Key limitation
Keep in mind: Clinical users retain primary diagnostic and management responsibility. The FDA packet defines DOUBT and YES operating points, returns NOT PROCESSED when all images are outside the indication, and does not establish local PACS compatibility, commercial security, price, or service commitments.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, 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: Aids clinicians and radiologists reviewing 2D X-ray radiographs by detecting, localizing, and characterizing fractures across the FDA-listed appendicular, hip/pelvis, clavicle, and thorax/rib examinations, and by detecting elbow joint effusion on lateral elbow or forearm views in children/adolescents and adults; results are not standalone clinical decisions.
  • Which images or clinical context are in scope?Modality: X-ray/Radiography Anatomy or clinical context: MSK Input: 2D X-ray radiographs received from DICOM sources; the FDA table supports specified frontal, lateral, oblique, lateral-elbow, ribs-series, and related views for the listed anatomy and age groups.
  • Who uses it?Intended users: Clinicians authorized to diagnose fractures and/or elbow joint effusions, including primary care, emergency, urgent care, orthopedic clinicians, and radiologists.
  • What does the software produce?Output: For each processed image, TechCare Trauma reports YES, DOUBT, or NO for each supported finding and can draw solid-line or dotted-line bounding boxes. It also creates a study-level summary image with SUSPECTED, DOUBT, NOT SUSPECTED, or NOT PROCESSED assessment and can return a DICOM Structured Report when configured.
  • What is its most important limitation?Key limitation: Clinical users retain primary diagnostic and management responsibility. The FDA packet defines DOUBT and YES operating points, returns NOT PROCESSED when all images are outside the indication, and does not establish local PACS compatibility, commercial security, price, or service commitments.

Clinical takeaway. Clinical role: Aids clinicians and radiologists reviewing 2D X-ray radiographs by detecting, localizing, and characterizing fractures across the FDA-listed appendicular, hip/pelvis, clavicle, and thorax/rib examinations, and by detecting elbow joint effusion on lateral elbow or forearm views in children/adolescents and adults; results are not standalone clinical decisions.

Evidence takeaway. Evidence from the reviewed source record: FDA standalone image-level testing used 4,109 adult fracture images, 2,872 pediatric fracture images, 280 adult elbow-joint-effusion images, and 483 pediatric elbow-joint-effusion images. The FDA MRMC study used four external US datasets totaling 769 cases and compared aided with unaided readers.

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
Aids clinicians and radiologists reviewing 2D X-ray radiographs by detecting, localizing, and characterizing fractures across the FDA-listed appendicular, hip/pelvis, clavicle, and thorax/rib examinations, and by detecting elbow joint effusion on lateral elbow or forearm views in children/adolescents and adults; results are not standalone clinical decisions.
  • Exact FDA submission
  • Checked 2026-09-07
Workflow role
Detection, localization, or diagnostic support as a non-standalone concurrent aid.
  • Exact FDA submission
  • Checked 2026-09-07
Required input
2D X-ray radiographs received from DICOM sources; the FDA table supports specified frontal, lateral, oblique, lateral-elbow, ribs-series, and related views for the listed anatomy and age groups.
  • Exact FDA submission
  • Checked 2026-09-07
Output and clinician action
For each processed image, TechCare Trauma reports YES, DOUBT, or NO for each supported finding and can draw solid-line or dotted-line bounding boxes. It also creates a study-level summary image with SUSPECTED, DOUBT, NOT SUSPECTED, or NOT PROCESSED assessment and can return a DICOM Structured Report when configured.
  • Exact FDA submission
  • Checked 2026-09-07

The packet describes newly generated DICOM series associated with the original study; the output is an aid to clinical review.

Care setting
Primary care, emergency medicine, urgent care, specialty care, and radiology review settings; fracture results cover neonates/infants, children/adolescents, and adults, while elbow-effusion results cover children/adolescents and adults.
  • Exact FDA submission
  • Checked 2026-09-07
Intended users
Clinicians authorized to diagnose fractures and/or elbow joint effusions, including primary care, emergency, urgent care, orthopedic clinicians, and radiologists.
  • Exact FDA submission
  • Checked 2026-09-07
Limitations
Clinical users retain primary diagnostic and management responsibility. The FDA packet defines DOUBT and YES operating points, returns NOT PROCESSED when all images are outside the indication, and does not establish local PACS compatibility, commercial security, price, or service commitments.
  • Exact FDA submission
  • Checked 2026-09-07
Evidence summary
FDA standalone image-level testing used 4,109 adult fracture images, 2,872 pediatric fracture images, 280 adult elbow-joint-effusion images, and 483 pediatric elbow-joint-effusion images. The FDA MRMC study used four external US datasets totaling 769 cases and compared aided with unaided readers.
  • Exact FDA submission
  • Checked 2026-09-07

The FDA packet reports separate populations and endpoints; these figures are not a pooled performance estimate.

Evidence

Performance evidence

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
FDA standalone image-level testing used 4,109 adult fracture images, 2,872 pediatric fracture images, 280 adult elbow-joint-effusion images, and 483 pediatric elbow-joint-effusion images. The FDA MRMC study used four external US datasets totaling 769 cases and compared aided with unaided readers.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-07

The FDA packet reports separate populations and endpoints; these figures are not a pooled performance estimate.

Reported sensitivity
FDA MRMC aided-reader sensitivity increases were reported as +21.8% for adult fracture, +12.7% for adult elbow-joint effusion, +19.9% for pediatric fracture, and +18.2% for pediatric elbow-joint effusion.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-07

These are reported aided-versus-unaided percentage increases, not standalone sensitivities; the structured metrics retain endpoint and population context.

Reported specificity
FDA MRMC aided-reader specificity changes were reported as +1.47% for adult fracture, +1.08% for adult elbow-joint effusion, 0% for pediatric fracture, and +1.43% for pediatric elbow-joint effusion.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-07

These are reported aided-versus-unaided percentage changes, not standalone specificities.

Standalone fracture ROC-AUC

0.962 ROC-AUC

  • EndpointImage-level fracture detection
  • PopulationUS adults, 4,109 radiographs
  • Tested versionTechCare Trauma (K242171)

Standalone fracture ROC-AUC

0.962 ROC-AUC

  • EndpointImage-level fracture detection
  • PopulationUS pediatric patients, 2,872 radiographs
  • Tested versionTechCare Trauma (K242171)

Standalone elbow-joint-effusion ROC-AUC

0.965 ROC-AUC

  • EndpointImage-level elbow-joint-effusion detection
  • PopulationUS adults, 280 radiographs
  • Tested versionTechCare Trauma (K242171)

Standalone elbow-joint-effusion ROC-AUC

0.976 ROC-AUC

  • EndpointImage-level elbow-joint-effusion detection
  • PopulationUS pediatric patients, 483 radiographs
  • Tested versionTechCare Trauma (K242171)

Aided-reader ROC-AUC

0.955 ROC-AUC

  • EndpointCase-level adult fracture detection with TechCare Trauma assistance
  • PopulationMRMC US adult fracture dataset, 304 cases
  • Tested versionTechCare Trauma (K242171)

Aided-reader ROC-AUC

0.931 ROC-AUC

  • EndpointCase-level pediatric fracture detection with TechCare Trauma assistance
  • PopulationMRMC US pediatric fracture dataset, 256 cases
  • Tested versionTechCare Trauma (K242171)

TechCare Trauma standalone image-level performance testing

  • DesignStandalone performance testing
  • PopulationUS adult and pediatric radiographs for fracture and elbow-joint-effusion detection
  • Scopeexact submission
  • Tested versionTechCare Trauma (K242171)
  • Samplen=7744
  • IndependenceIndependence not established

K242171

Four separately analyzed datasets; the sampleSize is their sum and is not a pooled performance population.

TechCare Trauma MRMC aided-reader study

  • DesignFully crossed multiple-reader, multiple-case retrospective reader study
  • PopulationExternal multicenter anonymized US adult and pediatric radiographs for fracture and elbow-joint-effusion detection
  • Scopeexact submission
  • Tested versionTechCare Trauma (K242171)
  • Samplen=769
  • IndependenceIndependence not established

K242171

Four datasets totaling 769 cases; readers interpreted with and without assistance, with ABR-certified radiologist consensus reference standards.

TechCare Trauma 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 K242171
  • Samplen=6981
  • IndependenceIndependence not established

K242171

Baseline ACR summary retained; FDA packet details above control endpoint and population interpretation.

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 & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not verified: Pricing information is recorded but not verified against a resolving source.

Reimbursement

No product-specific code

NICE HTG739 conditionally recommends TechCare Alert for NHS use during a two-year evidence-generation period, subject to evidence-generation agreements and appropriate regulatory and DTAC approval; this is not a reimbursement determination.

NICE guidance for the NHS in England · England · Effective 2025-01-14

NICE's exploratory model uses GBP 1 per scan and says actual software, implementation, and postmarket costs are uncertain. This is not a vendor quote or US coverage evidence.

IT implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. Acquisition/source

    Source context, not route validation: 2D X-ray radiographs received from DICOM sources; the FDA table supports specified frontal, lateral, oblique, lateral-elbow, ribs-series, and related views for the listed anatomy and age groups.

    Scope: Exact FDA submission.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-07 · FDA 510(k) K242171: TechCare Trauma

  2. Routing

    Source context, not route validation: The FDA packet describes automatic receipt from DICOM sources and return of newly generated result series to specified DICOM destinations, including PACS, VNA, storage platforms, and compatible DICOM viewers; optional DICOM SR can list finding status and area.

    Scope: Exact FDA submission. Specific interface versions, routing rules, viewer behavior, and local compatibility remain acceptance-test items.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-09-07 · FDA 510(k) K242171: TechCare Trauma

  3. AI processing

    Source context, not route validation: On-premises or cloud deployment connected to multiple DICOM sources and destinations.

    Scope: Exact FDA submission. This FDA-described deployment boundary does not establish current hosting region, retention, security controls, uptime, or contract terms.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-09-07 · FDA 510(k) K242171: TechCare Trauma

  4. Returned objects

    Source context, not route validation: For each processed image, TechCare Trauma reports YES, DOUBT, or NO for each supported finding and can draw solid-line or dotted-line bounding boxes. It also creates a study-level summary image with SUSPECTED, DOUBT, NOT SUSPECTED, or NOT PROCESSED assessment and can return a DICOM Structured Report when configured.

    Scope: Exact FDA submission. The packet describes newly generated DICOM series associated with the original study; the output is an aid to clinical review.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-07 · FDA 510(k) K242171: TechCare Trauma

  5. Viewer/worklist/report

    Unresolved route: For each processed image, TechCare Trauma reports YES, DOUBT, or NO for each supported finding and can draw solid-line or dotted-line bounding boxes. It also creates a study-level summary image with SUSPECTED, DOUBT, NOT SUSPECTED, or NOT PROCESSED assessment and can return a DICOM Structured Report when configured.

    Scope: Exact FDA submission. The packet describes newly generated DICOM series associated with the original study; the output is an aid to clinical review.

    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.

    Field checked 2026-09-07 · FDA 510(k) K242171: TechCare Trauma

  6. Support owner

    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.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. 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.

Open the printable evaluation checklist

Deployment
On-premises or cloud deployment connected to multiple DICOM sources and destinations.
  • Exact FDA submission
  • Checked 2026-09-07

This FDA-described deployment boundary does not establish current hosting region, retention, security controls, uptime, or contract terms.

Integration
The FDA packet describes automatic receipt from DICOM sources and return of newly generated result series to specified DICOM destinations, including PACS, VNA, storage platforms, and compatible DICOM viewers; optional DICOM SR can list finding status and area.
  • Exact FDA submission
  • Checked 2026-09-07

Specific interface versions, routing rules, viewer behavior, and local compatibility remain acceptance-test items.

DICOM source and automatic processing

The FDA packet says TechCare Trauma relies on DICOM sources and automatically receives and processes images after network integration without manual intervention.

exact submission · checked 2026-09-07

Validate routing, identifiers, supported views, failure handling, and local compatibility before use.

DICOM result delivery

The packet describes delivery of summary and annotated DICOM series to specified DICOM destinations, including PACS, VNA, storage platforms, and radiological equipment; compatible DICOM viewers can display the results.

exact submission · checked 2026-09-07

Deployment options

The cleared device can be deployed on-premises or in the cloud and connected to multiple DICOM sources and destinations.

exact submission · checked 2026-09-07

Current hosting, PHI flow, retention, and operational service terms are not established.

Current family workflow

Milvue describes the current TechCare Alert configuration as analyzing incoming radiographs, returning localized findings and confidence scores in under 30 seconds, and prioritizing critical cases in the RIS/PACS worklist; its page identifies the US configuration as TechCare Trauma.

product family · checked 2026-09-07

Current family/configuration description, not proof of every feature in the K242171 release.

NICE evidence-generation controls

NICE HTG739 conditionally recommends TechCare Alert for use in NHS urgent care while evidence is generated and calls for local disagreement protocols plus monitoring of accuracy, software failures, downstream referrals, treatment changes, implementation cost, subgroups, and postmarket surveillance.

product family · checked 2026-09-08

English NHS health-technology guidance; not exact K242171 pricing, reimbursement, or US adoption evidence.

Sources & review details FDA 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.

FDA submission
K242171
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
X-ray/Radiography
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-07

Normalized from the exact FDA packet's 2D X-ray radiograph indication.

Anatomy
MSK
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-07

Controlled anatomy normalization for the FDA-listed appendicular, hip/pelvis, clavicle, and thorax/rib fracture scope plus elbow/forearm effusion.

Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2025-01-17
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Human reviewedStatus
2026-09-07Last searched
29Fields 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 was metadata screening, 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, health technology guidance, literature index, trial registry, 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 verified - checked 2026-09-07 - Exact FDA submission

    No current exact-product price or contract terms were established from the reviewed public sources.

  • 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
  • Reimbursement: Not publicly available - checked 2026-10-26 - Exact FDA submission

    Bounded web search on 2026-10-26 (query: "Milvue reimbursement CPT"; top results reviewed) found no vendor or payer page stating coding, coverage or payment for this product. No result was a vendor or payer page naming this product with coding or payment; any results were general billing guidance. This records what was found, not that none exists.

  • 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-09-07 - Exact FDA submission

    The reviewed product page uses protected-data language but does not establish the exact deployment's security architecture, retention, access control, audit, or incident-response terms.

  • Installation timeline: Not yet reviewed
  • Training: Not verified - checked 2026-09-07 - Exact FDA submission

    User training, onboarding, competency, and support commitments were not established for the exact commercial configuration.

  • Monitoring: Not verified - checked 2026-09-07 - Exact FDA submission

    Local acceptance testing, production monitoring, drift review, update control, and incident escalation remain to be qualified.

9 sources - 3 history items

Source ledger

  1. K242171 FDA decision source

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, purpose, modality, anatomy

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. TechCare Trauma model card (K242171)

    American College of Radiology - Published 2026-08-17 - Accessed 2026-09-01

    Scope: purpose, modality, intendedUsers, careSetting, output, evidenceSummary, anatomy, evidenceStudies

  4. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  6. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  7. FDA 510(k) K242171: TechCare Trauma

    U.S. Food and Drug Administration - Published 2025-01-17 - Accessed 2026-09-07

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation

  8. TechCare Alert fracture detection and workflow

    Milvue - Accessed 2026-09-08

    Scope: productFamily, clinicalWorkflow, DICOM, RIS, PACS, implementationCapabilities

  9. NICE HTG739: AI technologies to help detect fractures on X-rays in urgent care

    National Institute for Health and Care Excellence - Published 2025-01-14 - Accessed 2026-09-08

    Scope: conditionalAdoption, economics, evidenceGaps, implementationCapabilities

Research history

  1. K242171 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    human reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K240845

Rayvolve

AZmed SAS

Authorized purpose: Assists radiologists and emergency physicians in detecting fractures on DICOM musculoskeletal radiographs for adults and children aged 2 years or older, limited to the FDA-listed anatomic areas and standard views (ankle, clavicle, elbow, forearm, hip, humerus, knee, pelvis, shoulder, tibia/fibula, wrist, hand, and foot); it is an aided-diagnosis device and does not operate autonomously.

Modality
X-ray/Radiography
Anatomy
MSK
Decision
2024-07-17
FDA-cleared K193417

FractureDetect (FX)

Imagen Technologies, Inc.

Authorized purpose: Assists clinicians in detecting fractures during review of adult musculoskeletal radiographs.

Modality
X-ray/Radiography
Anatomy
MSK
Decision
2020-07-30
FDA-cleared K251408

OsteoSight™ Hip (v1)

Naitive Technologies Ltd

Authorized purpose: Opportunistically analyzes standard AP hip or pelvis radiographs in patients aged 50 years and older and issues a report when the estimated femoral-neck BMD is below a preset threshold to prompt clinical bone-health assessment; absence of a report does not rule out low BMD.

Modality
X-ray/Radiography
Anatomy
MSK
Decision
2025-09-02
FDA-cleared K252953

Velmeni for Dentists (V4D) Endo-Perio

Velmeni, Inc.

Authorized purpose: Concurrent-read CADe to assist dentists in detecting specified tooth and jaw anatomy, bone-level landmarks, and root-canal-treated teeth in digital radiographs of permanent teeth in patients 15 years or older.

Modality
X-ray/Radiography
Anatomy
Permanent teeth and jaw/maxillofacial anatomy, including enamel, dentine, pulp, root, mental foramen, inferior alveolar canal, maxillary sinus, cementoenamel junction, crestal bone, and root-canal-treated teeth
Decision
2026-05-11

Correct this exact record

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.

Open existing correction destination

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.

Correction policy and limits · Public repository change history