FDA-cleared profile

qXR-Detect

Qure.Ai Technologies · X-ray/Radiography · FDA-cleared (510(k))

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.

Clinical role
Highlights regions of interest after or alongside image review as an adjunct; it is not a primary interpretation tool.
Images and patients
X-ray/Radiography · Chest/Lung; pleura, mediastinum/hila/heart, bone, hardware and other chest-radiograph regions
Key limitation
Keep in mind: Concurrent-reading adjunct for adult chest radiographs only; it does not replace the trained clinician's primary image interpretation. PCCP authorization does not establish performance of every later model update.

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: 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.
  • Which images or clinical context are in scope?Modality: X-ray/Radiography Anatomy or clinical context: Chest/Lung; pleura, mediastinum/hila/heart, bone, hardware and other chest-radiograph regions Input: DICOM adult chest X-ray images sent through the qXR client software.
  • Who uses it?Intended users: Trained emergency-room physicians, family-medicine practitioners and radiologists.
  • What does the software produce?Output: Highlighted and categorized suspicious regions of interest returned to the client and available to PACS or other receiving systems.
  • What is its most important limitation?Key limitation: Concurrent-reading adjunct for adult chest radiographs only; it does not replace the trained clinician's primary image interpretation. PCCP authorization does not establish performance of every later model update.

Clinical takeaway. Clinical role: 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.

Evidence takeaway. Evidence from the reviewed source record: The manufacturer MRMC study included 301 cases and 18 readers. It evaluated aided versus unaided reader performance for the study's composite chest-radiograph endpoint.

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
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.
  • Exact FDA submission
  • Checked 2026-09-06
Workflow role
Highlights regions of interest after or alongside image review as an adjunct; it is not a primary interpretation tool.
  • Exact FDA submission
  • Checked 2026-09-06
Required input
DICOM adult chest X-ray images sent through the qXR client software.
  • Exact FDA submission
  • Checked 2026-09-06
Output and clinician action
Highlighted and categorized suspicious regions of interest returned to the client and available to PACS or other receiving systems.
  • Exact FDA submission
  • Checked 2026-09-06
Care setting
Adults undergoing chest radiography; the FDA summary identifies emergency, family-medicine and radiology users.
  • Exact FDA submission
  • Checked 2026-09-06
Intended users
Trained emergency-room physicians, family-medicine practitioners and radiologists.
  • Exact FDA submission
  • Checked 2026-09-06
Limitations
Concurrent-reading adjunct for adult chest radiographs only; it does not replace the trained clinician's primary image interpretation. PCCP authorization does not establish performance of every later model update.
  • Exact FDA submission
  • Checked 2026-09-06
Evidence summary
The manufacturer MRMC study included 301 cases and 18 readers. It evaluated aided versus unaided reader performance for the study's composite chest-radiograph endpoint.
  • Exact FDA submission
  • Checked 2026-09-06

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
The manufacturer MRMC study included 301 cases and 18 readers. It evaluated aided versus unaided reader performance for the study's composite chest-radiograph endpoint.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-06
Reported sensitivity
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-06

The reviewed summary reports category and composite performance, but a single general diagnostic sensitivity is not appropriate for this multi-finding CADe device.

Reported specificity
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-06

The reviewed summary does not establish one general diagnostic specificity across the heterogeneous finding categories.

Aided weighted AFROC

0.7505 weighted AFROC

  • EndpointReader performance with qXR-Detect assistance in the MRMC study
  • Population301 adult chest-radiograph cases interpreted by 18 readers
  • Tested versionqXR-Detect CADe

Aided versus unaided weighted AFROC improvement

0.0611 weighted AFROC difference

  • EndpointDifference between aided 0.7505 and unaided 0.6894 reader performance
  • Population301 adult chest-radiograph cases interpreted by 18 readers
  • Tested versionqXR-Detect CADe

K251934 qXR-Detect multi-reader multi-case study

  • DesignManufacturer multi-reader multi-case study comparing aided and unaided interpretation
  • Population301 adult chest-radiograph cases interpreted by 18 readers
  • Scopeexact submission
  • Tested versionqXR-Detect CADe
  • Samplen=301
  • IndependenceSponsor or vendor study

K251934

The study evaluates reader-aid performance for its defined composite endpoint, not autonomous interpretation or clinical outcomes.

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 publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

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 adult chest X-ray images sent through the qXR client software.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-06 · FDA 510(k) K251934: qXR-Detect

  2. Routing

    Source context, not route validation: qXR client software sends de-identified radiographs to the service through HTTPS, and results are passed to the client for transfer to PACS or another receiving system.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-06 · FDA 510(k) K251934: qXR-Detect

  3. AI processing

    Source context, not route validation: The FDA summary describes a secure cloud-server deployment with de-identified radiographs transmitted via HTTPS client software; its comparison table also describes on-premises or cloud deployment.

    Scope: Exact FDA submission. This does not establish an installed site's hosting, data-residency or security-control configuration.

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

    Field checked 2026-09-06 · FDA 510(k) K251934: qXR-Detect

  4. Returned objects

    Source context, not route validation: Highlighted and categorized suspicious regions of interest returned to the client and available to PACS or other receiving systems.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-06 · FDA 510(k) K251934: qXR-Detect

  5. Viewer/worklist/report

    Unresolved route: Highlighted and categorized suspicious regions of interest returned to the client and available to PACS or other receiving systems.

    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-06 · FDA 510(k) K251934: qXR-Detect

  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
The FDA summary describes a secure cloud-server deployment with de-identified radiographs transmitted via HTTPS client software; its comparison table also describes on-premises or cloud deployment.
  • Exact FDA submission
  • Checked 2026-09-06

This does not establish an installed site's hosting, data-residency or security-control configuration.

Integration
qXR client software sends de-identified radiographs to the service through HTTPS, and results are passed to the client for transfer to PACS or another receiving system.
  • Exact FDA submission
  • Checked 2026-09-06
Security
Qure.ai's documentation FAQ says data is sent over HTTPS (TLS 1.2 or higher), stored encrypted at rest with AES-256-GCM, backed up with restore tests twice a year, and that Qure maintains an ISO 27001 certification with periodic surveillance audits. It also says hospitals anonymize PHI before sending data. The certificate itself was not read and no date or scope is given.
  • Vendor-wide
  • Checked 2026-10-25

Vendor-wide statement, not an independent attestation. It does not establish certificate or report scope for this exact release, expiry, data location, retention, identity and access, or incident-response terms for a deployed configuration. Obtain these from the vendor.

Monitoring
Qure.ai's documentation FAQ states that data is backed up with restore tests performed twice a year.
  • Vendor-wide
  • Checked 2026-10-27

Vendor statement, not an attestation. The FAQ names Qure.ai generally and does not scope this commitment to any specific product release; exact-release scope is not established. This is an availability commitment only; the FAQ states no alerting or response-time SLAs.

Current qXR-Detect family announcement

Qure.ai's February 2026 announcement describes qXR-Detect as identifying, highlighting and categorizing positive findings on chest X-rays and identifies the device as a CADe radiography solution.

product family · checked 2026-09-06

Commercial announcement context only; exact intended use, version and performance are sourced to K251934.

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
K251934
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
X-ray/Radiography
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-06
Anatomy
Chest/Lung; pleura, mediastinum/hila/heart, bone, hardware and other chest-radiograph regions
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-06
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2026-01-16
  • 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-06Last searched
23Fields reviewed
12Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads

Stored PubMed and ClinicalTrials candidate metadata snapshots were screened; both arrays were empty. No candidate evidence was promoted. 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, acr ai central product, vendor documentation, fda decision summary, vendor product page, literature index, trial registry, stored candidate metadata, stored recall candidates, 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 publicly available - checked 2026-09-06 - Exact FDA submission

    No public exact-version price or procurement record reviewed.

  • 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: "Qure.ai qXR reimbursement CPT"; top results reviewed) found no vendor or payer page stating coding, coverage or payment for this product. This records what was found, not that none exists; eligibility depends on payer, site of service and use case.

  • 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
  • Installation timeline: Not yet reviewed
  • Training: Not verified - checked 2026-09-06 - Exact FDA submission

    Trained-user intent does not establish a verified current training program.

8 sources - 3 history items

Source ledger

  1. FDA 510(k) K251934: qXR-Detect

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

    Scope: identity, clinicalUse, modality, anatomy, implementationCapabilities, evidenceStudies

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. qXR-Detect model card (K251934)

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

    Scope: intendedUsers, careSetting, output, evidenceSummary, integration, 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. Qure.ai qXR-Detect FDA clearance announcement

    Qure.ai - Accessed 2026-09-06

    Scope: productFamily, currentCommercialContext

  8. Qure.ai Documentation: Security and Privacy FAQ

    Qure.Ai Technologies - Accessed 2026-10-25

    Scope: security

Research history

  1. K251934 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 K210666

Chest-CAD

Imagen Technologies, Inc

Authorized purpose: Concurrent CADe reading aid that identifies, categorizes, and highlights suspicious regions of interest on adult chest radiographs

Modality
X-ray/Radiography
Anatomy
Chest/thorax, with ROI categories covering cardiac, mediastinum/hila, lungs, pleura, bones, soft tissues, hardware, and other
Decision
2021-07-20
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 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