Authorized purpose: Generate a secondary digital chest X-ray image to facilitate confirmation of breathing-tube position and the carina in adults.
Clinical role
Processes chest X-rays sent from the user's PACS and returns PDF and DICOM outputs showing breathing tube and carina position to the PACS; its image provides adjunctive information and is not a substitute for the original PA/AP image.
Images and patients
X-ray/Radiography · Chest; target structures are the breathing tube and carina
Key limitation
Keep in mind: Adjunctive only, not a substitute for the original PA/AP image, and restricted to breathing-tube confirmation in adults.
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: Generate a secondary digital chest X-ray image to facilitate confirmation of breathing-tube position and the carina in adults.
Which images or clinical context are in scope?Modality: X-ray/Radiography Anatomy or clinical context: Chest; target structures are the breathing tube and carina Input: Frontal AP or PA chest X-ray in DICOM format.
Who uses it?Intended users: Licensed physicians trained in evaluation of breathing-tube placement
What does the software produce?Output: PDF and DICOM outputs with text and labeled overlays showing the presence and localization of the breathing tube and carina.
What is its most important limitation?Key limitation: Adjunctive only, not a substitute for the original PA/AP image, and restricted to breathing-tube confirmation in adults.
Clinical takeaway. Clinical role: Generate a secondary digital chest X-ray image to facilitate confirmation of breathing-tube position and the carina in adults.
Evidence takeaway. Evidence from the reviewed source record: FDA reports standalone testing on 162 images: mean localization error 2.15 mm for carina, 1.97 mm for tube tip, and 1.98 mm for tube-tip-to-carina distance; software validation and system verification also passed.
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
Generate a secondary digital chest X-ray image to facilitate confirmation of breathing-tube position and the carina in adults.
Exact FDA submission
Checked 2026-09-19
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
Processes chest X-rays sent from the user's PACS and returns PDF and DICOM outputs showing breathing tube and carina position to the PACS; its image provides adjunctive information and is not a substitute for the original PA/AP image.
Exact FDA submission
Checked 2026-11-14
Packet wording: "X-rays are sent to qXR-BT by means of transmission functions within the user’s PACS system. Upon completion of processing, the qXR-BT device returns results to the user’s PACS" … "The qXR-BT device produces PDF and DICOM format outputs that enable users to view the position of a breathing tube and an anatomical landmark (carina).". Read from the exact FDA decision document on 2026-11-14.
Adult patients whose chest X-rays are reviewed to confirm breathing tube position; the FDA document does not specify a facility type.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The qXR-BT device is intended to generate a secondary digital chest X-ray image that facilitates confirmation of the position of a breathing tube and an anatomical landmark on adult chest". Read from the exact FDA decision document on 2026-11-14.
FDA reports standalone testing on 162 images: mean localization error 2.15 mm for carina, 1.97 mm for tube tip, and 1.98 mm for tube-tip-to-carina distance; software validation and system verification also passed.
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 reports standalone testing on 162 images: mean localization error 2.15 mm for carina, 1.97 mm for tube tip, and 1.98 mm for tube-tip-to-carina distance; software validation and system verification also passed.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
qXR-BT regulatory performance study summary
DesignStand-Alone Performance
PopulationPopulation described in the exact-submission ACR model card
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K212690
IndependenceIndependence not established
K212690
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 K212690. 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: Frontal AP or PA chest X-ray in DICOM format.
Scope: Exact FDA submission. FDA device description.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes qXR-BT receiving DICOM chest X-rays sent from the user's PACS and returning results to the user's PACS or other specified radiology software, including an additional DICOM series with labeled overlays suitable for viewing in the PACS or radiology viewer. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "X-rays are sent to qXR-BT by means of transmission functions within the user’s PACS system. Upon completion of processing, the qXR-BT device returns results to the user’s PACS or other user- specified radiology software system or database." … "The input to the qXR-BT device is a chest X-ray (AP and PA, referred to as frontal) in digital imaging and communications in medicine (DICOM) format.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The exact FDA package describes qXR-BT as standalone software deployed on-premise or on the cloud. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "Predicate Device Subject Device ClearRead+Confirm qXR-BT" … "qXR-BT is standalone software standalone software device deployed on-premise or on the that integrates with PACS cloud, that integrates with PACS or". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: PDF and DICOM outputs with text and labeled overlays showing the presence and localization of the breathing tube and carina.
Scope: Exact FDA submission. FDA device description and output-format table.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: PDF and DICOM outputs with text and labeled overlays showing the presence and localization of the breathing tube and carina.
Scope: Exact FDA submission. FDA device description and output-format table.
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.
The exact FDA package describes qXR-BT as standalone software deployed on-premise or on the cloud. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Predicate Device Subject Device ClearRead+Confirm qXR-BT" … "qXR-BT is standalone software standalone software device deployed on-premise or on the that integrates with PACS cloud, that integrates with PACS or". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The exact FDA package describes qXR-BT receiving DICOM chest X-rays sent from the user's PACS and returning results to the user's PACS or other specified radiology software, including an additional DICOM series with labeled overlays suitable for viewing in the PACS or radiology viewer. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "X-rays are sent to qXR-BT by means of transmission functions within the user’s PACS system. Upon completion of processing, the qXR-BT device returns results to the user’s PACS or other user- specified radiology software system or database." … "The input to the qXR-BT device is a chest X-ray (AP and PA, referred to as frontal) in digital imaging and communications in medicine (DICOM) format.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
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.
Qure.ai's vulnerability disclosure programme states that it covers all Qure.ai commercial products, including cloud-hosted products and Qure.ai-operated infrastructure, and commits to handling every report promptly and transparently with an acknowledgement and tracking reference within 2 business days.
Vendor-wide
Checked 2026-10-27
Vendor statement, not an attestation. The page names Qure.ai generally and does not scope these commitments to any specific product release; exact-release scope is not established. The programme is an intake and response-handling commitment; it makes no uptime, drift or continuous-monitoring claims.
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
24Fields reviewed
11Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains no PubMed or ClinicalTrials.gov candidates; no external 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, fda decision summary, acr ai central product, vendor documentation, fda device recall, literature index, trial registry, fda decision summary packet, 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-09 - Exact FDA submission
No public price or quote for the exact K212690 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-09 - 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.
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-09 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Authorized purpose: Assist trained professionals in assessing radiographic knee osteoarthritis and its sclerosis, joint-space-narrowing, and osteophyte features on standing fixed-flexion knee radiographs.
Authorized purpose: Overjet Iris is a web-based dental PACS for storing, viewing, and supporting image-quality review of two-dimensional intraoral radiographs, panoramic images, and color photographs.
Authorized purpose: Second Opinion Panoramic is an automated image-processing aid that identifies and marks regions of interest for caries, periapical radiolucency, and impacted third molars on panoramic radiographs of permanent teeth in patients aged 16 years and older.
Modality
X-ray/Radiography
Anatomy
Permanent teeth; caries, periapical radiolucency, and impacted third molars
Authorized purpose: Analyzes bitewing, periapical, and panoramic intraoral radiographs from patients aged 3 years and older to identify and localize specified suspected dental findings, historical treatments, and normal anatomy; diagnostic use remains with trained dental professionals.
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.