Authorized purpose: Automated measurement of cardiac diameter, thoracic diameter, and the cardiothoracic ratio (CTR) on posterior-anterior chest X-rays to aid physicians or licensed practitioners; not a stand-alone decision tool.
Clinical role
Automated post-processing measurement and structured-report support for CD, TD, and CTR with clinician assessment.
Images and patients
X-ray/Radiography · Heart and thoracic cavity
Key limitation
Keep in mind: The device aids the intended users and is not intended to be used on a stand-alone basis or to preclude clinical assessment of CTR cases; the FDA indication is limited to adults aged 22 years and older and PA-view chest X-rays.
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: Automated measurement of cardiac diameter, thoracic diameter, and the cardiothoracic ratio (CTR) on posterior-anterior chest X-rays to aid physicians or licensed practitioners; not a stand-alone decision tool.
Which images or clinical context are in scope?Modality: X-ray/Radiography Anatomy or clinical context: Heart and thoracic cavity Input: DICOM chest X-ray images in posterior-anterior (PA) view from adults aged 22 years and older.
Who uses it?Intended users: Physicians or licensed practitioners in healthcare institutions.
What does the software produce?Output: Cardiac diameter, thoracic diameter, and CTR with annotation lines indicating the measured heart and thoracic-cavity diameters; a DICOM Structured Report for PACS-based mode and a downloadable PDF for web-based mode.
What is its most important limitation?Key limitation: The device aids the intended users and is not intended to be used on a stand-alone basis or to preclude clinical assessment of CTR cases; the FDA indication is limited to adults aged 22 years and older and PA-view chest X-rays.
Clinical takeaway. Clinical role: Automated measurement of cardiac diameter, thoracic diameter, and the cardiothoracic ratio (CTR) on posterior-anterior chest X-rays to aid physicians or licensed practitioners; not a stand-alone decision tool.
Evidence takeaway. Evidence from the reviewed source record: FDA packet: clinical testing used 435 PA-view scans, with ground truth established by three ABR thoracic radiologists with at least 10 years of experience. RMSE was 7.55 mm (95% CI 6.96-8.38) for cardiac diameter, 5.43 mm (4.94-6.09) for thoracic diameter, and 0.03 (0.02-0.03) for CTR; MAE/SD was 5.66/5.0 mm, 4.04/3.63 mm, and 0.02/0.02 for those measures. No sensitivity, specificity, or AUC was reported.
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
Automated measurement of cardiac diameter, thoracic diameter, and the cardiothoracic ratio (CTR) on posterior-anterior chest X-rays to aid physicians or licensed practitioners; not a stand-alone decision tool.
Cardiac diameter, thoracic diameter, and CTR with annotation lines indicating the measured heart and thoracic-cavity diameters; a DICOM Structured Report for PACS-based mode and a downloadable PDF for web-based mode.
The device aids the intended users and is not intended to be used on a stand-alone basis or to preclude clinical assessment of CTR cases; the FDA indication is limited to adults aged 22 years and older and PA-view chest X-rays.
FDA packet: clinical testing used 435 PA-view scans, with ground truth established by three ABR thoracic radiologists with at least 10 years of experience. RMSE was 7.55 mm (95% CI 6.96-8.38) for cardiac diameter, 5.43 mm (4.94-6.09) for thoracic diameter, and 0.03 (0.02-0.03) for CTR; MAE/SD was 5.66/5.0 mm, 4.04/3.63 mm, and 0.02/0.02 for those measures. No sensitivity, specificity, or AUC was reported.
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 packet: clinical testing used 435 PA-view scans, with ground truth established by three ABR thoracic radiologists with at least 10 years of experience. RMSE was 7.55 mm (95% CI 6.96-8.38) for cardiac diameter, 5.43 mm (4.94-6.09) for thoracic diameter, and 0.03 (0.02-0.03) for CTR; MAE/SD was 5.66/5.0 mm, 4.04/3.63 mm, and 0.02/0.02 for those measures. No sensitivity, specificity, or AUC was reported.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
qXR-CTR regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested version1.0
IndependenceIndependence not established
K231149
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 K231149. 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 chest X-ray images in posterior-anterior (PA) view from adults aged 22 years and older.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA packet describes DICOM input and a PACS-based DICOM Structured Report path, with a PDF report in web-based mode; it does not establish other interface standards or universal local compatibility.
Scope: Exact FDA submission.
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-CTR as a non-invasive software medical device designed to be installed on a computer with specific system requirements. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "The qXR-CTR is a non-invasive software medical device designed to be installed on the computer with specific system requirements.". 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: Cardiac diameter, thoracic diameter, and CTR with annotation lines indicating the measured heart and thoracic-cavity diameters; a DICOM Structured Report for PACS-based mode and a downloadable PDF for web-based mode.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Cardiac diameter, thoracic diameter, and CTR with annotation lines indicating the measured heart and thoracic-cavity diameters; a DICOM Structured Report for PACS-based mode and a downloadable PDF for web-based mode.
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.
The exact FDA package describes qXR-CTR as a non-invasive software medical device designed to be installed on a computer with specific system requirements. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The qXR-CTR is a non-invasive software medical device designed to be installed on the computer with specific system requirements.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The FDA packet describes DICOM input and a PACS-based DICOM Structured Report path, with a PDF report in web-based mode; it does not establish other interface standards or universal local compatibility.
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
10Source 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, 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 K231149 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: Quantified results from X-ray angiographic images of the coronary arteries to support clinical decisions about diagnosis or treatment evaluation in adult patients with coronary artery disease; results are not the sole basis for diagnosis.
Authorized purpose: Automatic cardiothoracic-ratio assessment on PA chest X-ray images for adults 20-80 years old in healthcare institutions; results support clinician assessment and are not for standalone clinical decision-making.
Modality
X-ray/Radiography
Anatomy
Heart and thoracic cavity for cardiothoracic-ratio measurement
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: View and quantify bone age from 2D posteroanterior left-hand radiographs to aid pediatric radiologists assessing patients aged 2-18 years.
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.