Standalone fracture ROC-AUC
0.962 ROC-AUC
- EndpointImage-level fracture detection
- PopulationUS adults, 4,109 radiographs
- Tested versionTechCare Trauma (K242171)
FDA-cleared profile
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.
Overview status: Source-reviewed overview
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
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 not reviewed for this FDA record.
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.
The packet describes newly generated DICOM series associated with the original study; the output is an aid to clinical review.
The FDA packet reports separate populations and endpoints; these figures are not a pooled performance estimate.
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.
The FDA packet reports separate populations and endpoints; these figures are not a pooled performance estimate.
These are reported aided-versus-unaided percentage increases, not standalone sensitivities; the structured metrics retain endpoint and population context.
These are reported aided-versus-unaided percentage changes, not standalone specificities.
0.962 ROC-AUC
0.962 ROC-AUC
0.965 ROC-AUC
0.976 ROC-AUC
0.955 ROC-AUC
0.931 ROC-AUC
K242171
Four separately analyzed datasets; the sampleSize is their sum and is not a pooled performance population.
K242171
Four datasets totaling 769 cases; readers interpreted with and without assistance, with ABR-certified radiologist consensus reference standards.
K242171
Baseline ACR summary retained; FDA packet details above control endpoint and population interpretation.
Safety and lifecycle
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
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.
Price not public here; enter your quote
Not verified: Pricing information is recorded but not verified against a resolving source.
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-14NICE'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.
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.
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
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
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
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
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
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
No tests below have been performed or accepted.
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
This FDA-described deployment boundary does not establish current hosting region, retention, security controls, uptime, or contract terms.
Specific interface versions, routing rules, viewer behavior, and local compatibility remain acceptance-test items.
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-07Validate routing, identifiers, supported views, failure handling, and local compatibility before use.
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-07The cleared device can be deployed on-premises or in the cloud and connected to multiple DICOM sources and destinations.
exact submission · checked 2026-09-07Current hosting, PHI flow, retention, and operational service terms are not established.
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-07Current family/configuration description, not proof of every feature in the K242171 release.
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-08English NHS health-technology guidance; not exact K242171 pricing, reimbursement, or US adoption evidence.
Regulatory identity
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
Normalized from the exact FDA packet's 2D X-ray radiograph indication.
Controlled anatomy normalization for the FDA-listed appendicular, hip/pelvis, clavicle, and thorax/rib fracture scope plus elbow/forearm effusion.
Research record
This audit distinguishes completed source review from fields that have not yet been researched.
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
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.
No current exact-product price or contract terms were established from the reviewed public sources.
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.
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.
User training, onboarding, competency, and support commitments were not established for the exact commercial configuration.
Local acceptance testing, production monitoring, drift review, update control, and incident escalation remain to be qualified.
9 sources - 3 history items
Scope: regulatoryIdentity, purpose, modality, anatomy
Scope: regulatoryIdentity, modalityContext
Scope: purpose, modality, intendedUsers, careSetting, output, evidenceSummary, anatomy, evidenceStudies
Scope: evidenceDiscovery
Scope: evidenceDiscovery, studyStatus
Scope: recallDiscovery, nativeSubmissionMatching
Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation
Scope: productFamily, clinicalWorkflow, DICOM, RIS, PACS, implementationCapabilities
Scope: conditionalAdoption, economics, evidenceGaps, implementationCapabilities
Regulatory record
510(k)
Research record
human reviewed
Editorial review
Source-reviewed editorial overlay
Alternatives
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.
Imagen Technologies, Inc.
Authorized purpose: Assists clinicians in detecting fractures during review of adult musculoskeletal radiographs.
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.
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.
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 destinationPermission 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.
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