FDA-cleared profile

Rayvolve

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

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.
Images and patients
X-ray/Radiography · Musculoskeletal system: ankle, clavicle, elbow, forearm, hip, humerus, knee, pelvis, shoulder, tibia/fibula, wrist, hand, and foot
Key limitation
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.

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: 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.
  • Exact FDA submission
  • Checked 2026-09-08
Workflow 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.
  • Exact FDA submission
  • Checked 2026-09-08
Required 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.
  • Exact FDA submission
  • Checked 2026-09-08
Output and clinician action
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.
  • Exact FDA submission
  • Checked 2026-09-08
Care setting
Musculoskeletal radiograph review in a medical imaging/PACS workflow; the FDA packet does not establish a specific commercial facility type.
  • Exact FDA submission
  • Checked 2026-09-08
Intended users
Radiologists and emergency physicians
  • Exact FDA submission
  • Checked 2026-09-08
Limitations
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.
  • Exact FDA submission
  • Checked 2026-09-08
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.
  • Exact FDA submission
  • Checked 2026-09-08

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 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.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Reported sensitivity
Overall standalone: 98.763% (95% Wilson CI 97.559%-99.421%).
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08

FDA K220164 reports ROC AUC 0.98607 separately; reader-aided results are not standalone device endpoints.

Reported specificity
Overall standalone: 88.558% (95% Wilson CI 87.119%-89.882%).
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08

FDA K220164 reports ROC AUC 0.98607 separately; reader-aided results are not standalone device endpoints.

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.

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
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.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-08
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

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: 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.

    Field checked 2026-09-08 · FDA K220164: Rayvolve

  2. Routing

    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.

    Field checked 2026-09-08 · FDA K220164: Rayvolve

  3. AI processing

    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 ·

  4. 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.

    Field checked 2026-09-08 · FDA K220164: Rayvolve

  5. Viewer/worklist/report

    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.

    Field checked 2026-09-08 · FDA K220164: Rayvolve

  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

Integration
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.
  • Exact FDA submission
  • Checked 2026-09-08

Supported acquisition environment

Scanner manufacturers: All

exact submission · checked 2026-09-01

Confirm currently supported software versions, protocols, and site-specific acquisition configurations.

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for Rayvolve; FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-08
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
K220164
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
X-ray/Radiography
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Anatomy
Musculoskeletal system: ankle, clavicle, elbow, forearm, hip, humerus, knee, pelvis, shoulder, tibia/fibula, wrist, hand, and foot
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-08
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2022-06-02
  • 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.

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.

7 sources - 3 history items

Source ledger

  1. FDA K220164: Rayvolve

    U.S. Food and Drug Administration - Published 2022-06-02 - Accessed 2026-09-08

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

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. Rayvolve model card (K220164)

    American College of Radiology - Published 2026-06-26 - Accessed 2026-09-01

    Scope: intendedUsers, careSetting, output, limitations, reportedSensitivity, reportedSpecificity, evidenceSummary, anatomy, evidenceStudies, implementationCapabilities

  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. openFDA exact recall query for K220164

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

    Scope: postmarketSafety

Research history

  1. K220164 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

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
FDA-cleared K251934

qXR-Detect

Qure.Ai Technologies

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
Decision
2026-01-16
FDA-cleared K242437

Smile Dx®

Cube Click, Inc.

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.

Modality
X-ray/Radiography
Anatomy
Dental/Maxillofacial
Decision
2025-05-14
FDA-cleared K242171

TechCare Trauma

Milvue

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.

Modality
X-ray/Radiography
Anatomy
MSK
Decision
2025-01-17

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