Authorized purpose: Computer-assisted detection and diagnosis to assist radiologists and emergency physicians in detecting fractures on specified adult musculoskeletal radiographs; indicated for adults at least 22 years old.
Clinical role
Aided fracture detection and localization during radiograph review, integrated with a PACS workflow; Rayvolve does not operate autonomously and the physician remains responsible for interpretation.
Keep in mind: Rayvolve is an aided-diagnosis device and does not operate autonomously or replace medical doctors. The labeled population is adults at least 22 years old and the labeled input is limited to the listed musculoskeletal anatomic regions, radiographic views, and DICOM radiographs. Results require radiologist or emergency-physician review and are not established for other populations, regions, views, or workflows.
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: Computer-assisted detection and diagnosis to assist radiologists and emergency physicians in detecting fractures on specified adult musculoskeletal radiographs; indicated for adults at least 22 years old.
Which images or clinical context are in scope?Modality: X-ray/Radiography Anatomy or clinical context: Musculoskeletal system: ankle, clavicle, elbow, forearm, hip, humerus, knee, pelvis, shoulder, tibia/fibula, wrist, hand, and foot Input: DICOM radiographs from adults at least 22 years old, limited to the FDA-listed anatomic regions and views: ankle, clavicle, elbow, forearm, hip, humerus, knee, pelvis, shoulder, tibia/fibula, wrist, hand, and foot, with frontal, lateral, oblique, frog-leg-lateral, or axillary views as specified.
Who uses it?Intended users: Radiologists and emergency physicians
What does the software produce?Output: A prediction of the potential presence or absence of fracture with localized image annotations or bounding-box information for fracture review in the PACS workflow; the original image remains available for physician interpretation.
What is its most important limitation?Key limitation: Rayvolve is an aided-diagnosis device and does not operate autonomously or replace medical doctors. The labeled population is adults at least 22 years old and the labeled input is limited to the listed musculoskeletal anatomic regions, radiographic views, and DICOM radiographs. Results require radiologist or emergency-physician review and are not established for other populations, regions, views, or workflows.
Clinical takeaway. Clinical role: Computer-assisted detection and diagnosis to assist radiologists and emergency physicians in detecting fractures on specified adult musculoskeletal radiographs; indicated for adults at least 22 years old.
Evidence takeaway. Evidence from the reviewed source record: FDA standalone testing evaluated 2,626 radiographs from 851 patients at four US sites across all indicated study types and views. Standalone sensitivity was 0.98763 (95% Wilson CI 0.97559-0.99421), specificity was 0.88558 (0.87119-0.89882), and ROC AUC was 0.98607 (95% bootstrap CI 0.98104-0.99058). The MRMC reader study used 24 clinical readers and 186 cases; reader AUC improved from 0.84602 unaided to 0.89327 aided, reader sensitivity from 0.86561 to 0.9554, and reader specificity from 0.82645 to 0.83116. The reader endpoints are separate from the standalone model results.
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
Computer-assisted detection and diagnosis to assist radiologists and emergency physicians in detecting fractures on specified adult musculoskeletal radiographs; indicated for adults at least 22 years old.
Aided fracture detection and localization during radiograph review, integrated with a PACS workflow; Rayvolve does not operate autonomously and the physician remains responsible for interpretation.
DICOM radiographs from adults at least 22 years old, limited to the FDA-listed anatomic regions and views: ankle, clavicle, elbow, forearm, hip, humerus, knee, pelvis, shoulder, tibia/fibula, wrist, hand, and foot, with frontal, lateral, oblique, frog-leg-lateral, or axillary views as specified.
A prediction of the potential presence or absence of fracture with localized image annotations or bounding-box information for fracture review in the PACS workflow; the original image remains available for physician interpretation.
Rayvolve is an aided-diagnosis device and does not operate autonomously or replace medical doctors. The labeled population is adults at least 22 years old and the labeled input is limited to the listed musculoskeletal anatomic regions, radiographic views, and DICOM radiographs. Results require radiologist or emergency-physician review and are not established for other populations, regions, views, or workflows.
FDA standalone testing evaluated 2,626 radiographs from 851 patients at four US sites across all indicated study types and views. Standalone sensitivity was 0.98763 (95% Wilson CI 0.97559-0.99421), specificity was 0.88558 (0.87119-0.89882), and ROC AUC was 0.98607 (95% bootstrap CI 0.98104-0.99058). The MRMC reader study used 24 clinical readers and 186 cases; reader AUC improved from 0.84602 unaided to 0.89327 aided, reader sensitivity from 0.86561 to 0.9554, and reader specificity from 0.82645 to 0.83116. The reader endpoints are separate from the standalone model results.
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 testing evaluated 2,626 radiographs from 851 patients at four US sites across all indicated study types and views. Standalone sensitivity was 0.98763 (95% Wilson CI 0.97559-0.99421), specificity was 0.88558 (0.87119-0.89882), and ROC AUC was 0.98607 (95% bootstrap CI 0.98104-0.99058). The MRMC reader study used 24 clinical readers and 186 cases; reader AUC improved from 0.84602 unaided to 0.89327 aided, reader sensitivity from 0.86561 to 0.9554, and reader specificity from 0.82645 to 0.83116. The reader endpoints are separate from the standalone model results.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
Rayvolve regulatory performance study summary
DesignStand-alone performance and reader study (ACR AI Central category)
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K220164
Samplen=851
Sites4
IndependenceIndependence not established
K220164
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
The exact-identifier FDA recall query returned no native recall record for K220164. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
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: DICOM radiographs from adults at least 22 years old, limited to the FDA-listed anatomic regions and views: ankle, clavicle, elbow, forearm, hip, humerus, knee, pelvis, shoulder, tibia/fibula, wrist, hand, and foot, with frontal, lateral, oblique, frog-leg-lateral, or axillary views as specified.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Rayvolve is described as standalone software intended to work with PACS servers; when remotely connected to a medical-center PACS it directly interacts with DICOM files to output fracture predictions. The comparison describes secure local DICOM processing and delivery with PACS image annotations that can be toggled, but no specific interface version or current local compatibility is established.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact FDA decision document was reviewed on 2026-11-14 and does not state where the subject device's software runs or how it is hosted. Confirm the deployment model, hosting, data flow, and current commercial configuration with the vendor.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-11-14 ·
Returned objects
Source context, not route validation: A prediction of the potential presence or absence of fracture with localized image annotations or bounding-box information for fracture review in the PACS workflow; the original image remains available for physician interpretation.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: A prediction of the potential presence or absence of fracture with localized image annotations or bounding-box information for fracture review in the PACS workflow; the original image remains available for physician interpretation.
Scope: Exact FDA submission.
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.
Rayvolve is described as standalone software intended to work with PACS servers; when remotely connected to a medical-center PACS it directly interacts with DICOM files to output fracture predictions. The comparison describes secure local DICOM processing and delivery with PACS image annotations that can be toggled, but no specific interface version or current local compatibility is established.
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-20Last searched
26Fields reviewed
9Source classes checked
9Screened PubMed leads
1Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 9 PubMed and 1 ClinicalTrials.gov candidate records. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 9 PubMed and 1 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, fda device recall, 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-08 - Exact FDA submission
No public price or quote for the exact K220164 configuration was established in this review.
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-09-08 - Exact FDA submission
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
Deployment: Not publicly available - checked 2026-11-14 - Exact FDA submission
The exact FDA decision document was reviewed on 2026-11-14 and does not state where the subject device's software runs or how it is hosted. Confirm the deployment model, hosting, data flow, and current commercial configuration with the vendor.
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-08 - Exact FDA submission
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-08 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-08 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
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
Authorized purpose: qXR-Detect is an adult chest-radiograph concurrent reading aid that identifies, highlights and categorizes suspicious regions of interest across lung, pleura, mediastinum/hila/heart, bone, hardware and other categories; trained clinicians remain responsible for primary interpretation.
Modality
X-ray/Radiography
Anatomy
Chest/Lung; pleura, mediastinum/hila/heart, bone, hardware and other chest-radiograph regions
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 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.
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.