Authorized purpose: Provides semi-automatic measurement of pulmonary-nodule size in adult thoracic CT.
Clinical role
Used with a standard PACS: the user indicates a solid pulmonary nodule's location, AI algorithms automatically measure its long and short axis diameters, and a trained radiologist reviews and can edit the measurements on the DICOM image.
Images and patients
CT/CTA · Chest/Lung
Key limitation
Keep in mind: Measurement aid only, not a substitute for full evaluation or diagnosis; does not alter the original image and is limited to solid nodules.
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: Provides semi-automatic measurement of pulmonary-nodule size in adult thoracic CT.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Chest/Lung Input: DICOM thoracic CT plus radiologist-indicated nodule location.
Who uses it?Intended users: Trained radiologists.
What does the software produce?Output: Long- and short-axis axial diameter measurements displayed for review and editing on the DICOM image.
What is its most important limitation?Key limitation: Measurement aid only, not a substitute for full evaluation or diagnosis; does not alter the original image and is limited to solid nodules.
Clinical takeaway. Clinical role: Provides semi-automatic measurement of pulmonary-nodule size in adult thoracic CT.
Evidence takeaway. Evidence from the reviewed source record: Retrospective multicenter study across three manufacturers, seven scanner models, and 11 sites included 209 nodules and reported normalized long-axis error 0.113 and short-axis error 0.131.
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
Provides semi-automatic measurement of pulmonary-nodule size in adult thoracic CT.
Exact FDA submission
Checked 2026-09-15
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
Used with a standard PACS: the user indicates a solid pulmonary nodule's location, AI algorithms automatically measure its long and short axis diameters, and a trained radiologist reviews and can edit the measurements on the DICOM image.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The system then returns the measurements for the long and short axis diameters for review by a trained radiologist." … "NinesMeasure is designed to be used with a standard PACS, where the user can indicate a location of the pulmonary nodule to measure, and then review and edit the measurements on the DICOM image.". Read from the exact FDA decision document on 2026-11-14.
Retrospective multicenter study across three manufacturers, seven scanner models, and 11 sites included 209 nodules and reported normalized long-axis error 0.113 and short-axis error 0.131.
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
Retrospective multicenter study across three manufacturers, seven scanner models, and 11 sites included 209 nodules and reported normalized long-axis error 0.113 and short-axis error 0.131.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
NinesMeasure regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K202990
Samplen=209
IndependenceIndependence not established
K202990
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 K202990. 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 thoracic CT plus radiologist-indicated nodule location.
Scope: Exact FDA submission. FDA packet input scope.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact-submission ACR model card explicitly references DICOM and PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Scope: Exact FDA submission. Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
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 ·
Returned objects
Source context, not route validation: Long- and short-axis axial diameter measurements displayed for review and editing on the DICOM image.
Scope: Exact FDA submission. FDA packet output scope.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Long- and short-axis axial diameter measurements displayed for review and editing on the DICOM image.
Scope: Exact FDA submission. FDA packet output scope.
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-submission ACR model card explicitly references DICOM and PACS in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Exact FDA submission
Checked 2026-09-01
Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
ACR AI Central provides an exact-submission model card for NinesMeasure; 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
25Fields 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, 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 K202990 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.
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-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.
eyonis LCS is a concurrent-reading aid for radiologists that detects, localizes, and characterizes 4-30 mm solid and part-solid pulmonary nodules on low-dose chest CT images for high-risk lung cancer screening patients; it provides nodule measurements and malignancy scores and does not replace physician judgment.
Authorized purpose: Quantitative support for thoracic CT interpretation and treatment planning, including emphysema burden, airway/lung segmentation, endobronchial valve assessment and estimated chronic perfusion defect.
Authorized purpose: Adjunctive pulmonary nodule detection and measurement, including temporal comparison, in chest CT screening of asymptomatic adults aged at least 55 years.
The Thirona LungQ software provides reproducible CT values for pulmonary tissue which is essential for providing quantitative support for diagnosis and follow up examination. The LungQ software can be used to support physician in the diagnosis and documentation of pulmonary tissues images (e.g. abnormalities) from CT thoracic datasets. Three-D segmentation and isolation of sub-compartments, volumetric analysis, density evaluations, fissure evaluation, and reporting tools are provided.
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.