Authorized purpose: Provide quantitative support for physician diagnosis, follow-up examination, and documentation of pulmonary-tissue images or abnormalities from CT thoracic datasets.
Clinical role
Command-line post-processing and quantitative-analysis aid; it supplies segmentation, volume/density/fissure measurements, and reports and has no graphical user interface.
Images and patients
CT/CTA · Thorax and lungs, including left and right lungs, lobes, pulmonary tissue, and fissures.
Key limitation
Keep in mind: The software is command-line and has no graphical user interface; the comparison table states that users cannot manually edit the segmentation. The reported equivalence criteria were volume difference <=10%, LAA-950HU agreement limits -1% to 1%, LAA-910HU limits -10% to 10%, and 15th-percentile limits -10 HU to 10 HU. The packet does not establish a disease-classification sensitivity or specificity endpoint.
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: Provide quantitative support for physician diagnosis, follow-up examination, and documentation of pulmonary-tissue images or abnormalities from CT thoracic datasets.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Thorax and lungs, including left and right lungs, lobes, pulmonary tissue, and fissures. Input: DICOM CT thoracic datasets that may contain pulmonary abnormalities.
Who uses it?Intended users: Physicians; the FDA packet does not further specify user credentials.
What does the software produce?Output: Three-dimensional segmentation and isolation of the left and right lungs and lobes; lung/lobar volume, density-range and 15th-percentile measurements; fissure evaluation; and a report.
What is its most important limitation?Key limitation: The software is command-line and has no graphical user interface; the comparison table states that users cannot manually edit the segmentation. The reported equivalence criteria were volume difference <=10%, LAA-950HU agreement limits -1% to 1%, LAA-910HU limits -10% to 10%, and 15th-percentile limits -10 HU to 10 HU. The packet does not establish a disease-classification sensitivity or specificity endpoint.
Clinical takeaway. Clinical role: Provide quantitative support for physician diagnosis, follow-up examination, and documentation of pulmonary-tissue images or abnormalities from CT thoracic datasets.
Evidence takeaway. Evidence from the reviewed source record: FDA K173821 compared LungQ 1.1.0 with VIDA PW2 on 250 randomly selected COPDGene CT scans spanning subjects with and without COPD and multiple disease stages. Lung/lobar volume and density outputs were assessed against prespecified equivalence limits. A separate fissure study used 55 scans from a five-site multicenter study in Germany, the Netherlands, and Sweden and compared voxel-wise fissure completeness with a manual reference; mean Az was 0.95 for LungQ 1.1.0 versus 0.76 for the previously published version (p<0.001). Az is an AUC endpoint, not sensitivity or specificity.
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
Provide quantitative support for physician diagnosis, follow-up examination, and documentation of pulmonary-tissue images or abnormalities from CT thoracic datasets.
Command-line post-processing and quantitative-analysis aid; it supplies segmentation, volume/density/fissure measurements, and reports and has no graphical user interface.
Three-dimensional segmentation and isolation of the left and right lungs and lobes; lung/lobar volume, density-range and 15th-percentile measurements; fissure evaluation; and a report.
The software is command-line and has no graphical user interface; the comparison table states that users cannot manually edit the segmentation. The reported equivalence criteria were volume difference <=10%, LAA-950HU agreement limits -1% to 1%, LAA-910HU limits -10% to 10%, and 15th-percentile limits -10 HU to 10 HU. The packet does not establish a disease-classification sensitivity or specificity endpoint.
FDA K173821 compared LungQ 1.1.0 with VIDA PW2 on 250 randomly selected COPDGene CT scans spanning subjects with and without COPD and multiple disease stages. Lung/lobar volume and density outputs were assessed against prespecified equivalence limits. A separate fissure study used 55 scans from a five-site multicenter study in Germany, the Netherlands, and Sweden and compared voxel-wise fissure completeness with a manual reference; mean Az was 0.95 for LungQ 1.1.0 versus 0.76 for the previously published version (p<0.001). Az is an AUC endpoint, not sensitivity or specificity.
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 K173821 compared LungQ 1.1.0 with VIDA PW2 on 250 randomly selected COPDGene CT scans spanning subjects with and without COPD and multiple disease stages. Lung/lobar volume and density outputs were assessed against prespecified equivalence limits. A separate fissure study used 55 scans from a five-site multicenter study in Germany, the Netherlands, and Sweden and compared voxel-wise fissure completeness with a manual reference; mean Az was 0.95 for LungQ 1.1.0 versus 0.76 for the previously published version (p<0.001). Az is an AUC endpoint, not sensitivity or specificity.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
LungQ 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 K173821
Samplen=250
IndependenceIndependence not established
K173821
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 K173821. 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 CT thoracic datasets that may contain pulmonary abnormalities.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: DICOM loading and command-line/Image Analysis Service processing are described; the packet does not name a PACS, RIS, EHR, routing interface, or current deployment topology.
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 LungQ as stand-alone command-line software that must be run from a command-line interpreter and does not have a graphical user interface. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "LungQ is stand- alone command-line software which must be run from a command-line interpreter and does not have a graphical user interface.". 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: Three-dimensional segmentation and isolation of the left and right lungs and lobes; lung/lobar volume, density-range and 15th-percentile measurements; fissure evaluation; and a report.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Three-dimensional segmentation and isolation of the left and right lungs and lobes; lung/lobar volume, density-range and 15th-percentile measurements; fissure evaluation; and a report.
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 LungQ as stand-alone command-line software that must be run from a command-line interpreter and does not have a graphical user interface. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "LungQ is stand- alone command-line software which must be run from a command-line interpreter and does not have a graphical user interface.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
DICOM loading and command-line/Image Analysis Service processing are described; the packet does not name a PACS, RIS, EHR, routing interface, or current deployment topology.
ACR AI Central provides an exact-submission model card for LungQ Software; FDA labeling remains controlling for clinical use, limitations, and performance.
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
23Fields reviewed
9Source classes checked
7Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 7 PubMed and 0 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 7 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, 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 K173821 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
Security: Not verified - checked 2026-09-09 - 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-09 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-09 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: Auto-Seg and Spine Auto-Seg accept spine and pelvis CT images and provide three-dimensional segmentation and labels to support spine-surgery planning and assessment by spine surgeons.
Authorized purpose: Acorn 3D Software and Acorn 3DP Model process CT, synthetic CT, and CT angiography for segmentation, visualization, measurement, treatment planning, and three-dimensional printing, including adult and pediatric spine trajectory planning.
Modality
CT/CTA
Anatomy
Spine; craniomaxillofacial; musculoskeletal anatomy; and patient-specific printed models
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.