Authorized purpose: Tracks, assesses, and characterizes incidentally detected pulmonary nodules, with a CADx function for pulmonologists and radiologists.
Clinical role
CADx for radiologists and pulmonologists: an AI algorithm computes an LCP-CNN score for a user-selected lung CT region, displayed against a histogram of known-ground-truth cases; other users, without the score, view images, track patients and organize nodule clinics.
Images and patients
CT/CTA · Chest/Lung
Key limitation
Keep in mind: For incidental solid or semi-solid nodules 5-30 mm in patients age 35 or older; not screening, pure GGO, calcified nodules, more than five nodules, or specified acquisition and history exclusions.
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: Tracks, assesses, and characterizes incidentally detected pulmonary nodules, with a CADx function for pulmonologists and radiologists.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Chest/Lung Input: User-selected regions of interest from lung CT through DICOM/PACS.
Who uses it?Intended users: Pulmonologists and radiologists for CADx; clinicians, nurses, nurse practitioners, and navigators for management functions without the score.
What does the software produce?Output: An LCP-CNN integer score from 1 to 10 with histogram context; it is not a malignancy probability.
What is its most important limitation?Key limitation: For incidental solid or semi-solid nodules 5-30 mm in patients age 35 or older; not screening, pure GGO, calcified nodules, more than five nodules, or specified acquisition and history exclusions.
Clinical takeaway. Clinical role: Tracks, assesses, and characterizes incidentally detected pulmonary nodules, with a CADx function for pulmonologists and radiologists.
Evidence takeaway. Evidence from the reviewed source record: Standalone LCP-CNN AUC was 0.867; MRMC study used 300 subjects, 12 readers, and 9 hospitals and reported mean reader AUC improvement of 6.85 points.
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
Tracks, assesses, and characterizes incidentally detected pulmonary nodules, with a CADx function for pulmonologists and radiologists.
Exact FDA submission
Checked 2026-09-15
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
CADx for radiologists and pulmonologists: an AI algorithm computes an LCP-CNN score for a user-selected lung CT region, displayed against a histogram of known-ground-truth cases; other users, without the score, view images, track patients and organize nodule clinics.
Exact FDA submission
Checked 2026-11-14
Packet wording: "VNC includes a computer-aided diagnosis (CADx) function, available only to pulmonologists and radiologists. This automatically analyzes user-selected regions of interest (ROI) within lung CT data" … "an artificial intelligence algorithm calculates a single value, the LCP-CNN score, which is displayed to the user. The LCP-CNN score is analyzed relative to LCP-CNN scores generated on a database of cases with known ground-truth using a histogram display format.". Read from the exact FDA decision document on 2026-11-14.
Used in hospitals to support nodule clinics; the LCP-CNN score is for incidentally detected solid and semi-solid nodules 5-30mm in patients aged 35 years or above, not lung cancer screening.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Virtual Nodule Clinic is intended for use in hospitals to support these clinics." … "VNC’s LCP-CNN score is indicated for the evaluation of incidentally detected solid and semi-solid pulmonary nodules of diameter 5-30mm in patients aged 35 years or above.". Read from the exact FDA decision document on 2026-11-14.
For incidental solid or semi-solid nodules 5-30 mm in patients age 35 or older; not screening, pure GGO, calcified nodules, more than five nodules, or specified acquisition and history exclusions.
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
Standalone LCP-CNN AUC was 0.867; MRMC study used 300 subjects, 12 readers, and 9 hospitals and reported mean reader AUC improvement of 6.85 points.
Values reported in the exact-submission materials. Consult the linked source for endpoint, threshold, population, and confidence interval before comparison.
Values reported in the exact-submission materials. Consult the linked source for endpoint, threshold, population, and confidence interval before comparison.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
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 K202300. 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: User-selected regions of interest from lung CT through DICOM/PACS.
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 FDA package describes Virtual Nodule Clinic connecting to a DICOM-compatible PACS, querying and pulling images into a local PACS proxy, and to a RIS or reporting system for clinical reports, with read-only access that does not push data back. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "a DICOM-compatible Picture Archiving and Communication System (PACS) for accessing images and to the Radiology Information System (RIS) or reporting system for accessing the clinical reports." … "DICOM data is pulled from the hospital’s PACS and copied locally in a PACS proxy. VNC can query the hospital PACS for a patient’s images". 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 Virtual Nodule Clinic as a web application deployed on a virtual server within a hospital datacenter and accessed via web browser, with the LCP-CNN module deployed on a GPU-equipped server on hospital premises or in the cloud. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "A web application deployed on a virtual server within a hospital datacenter;" … "The LCP-CNN module deployed on a GPU-equipped server on hospital premises or in the cloud.". 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.
Unresolved route: An LCP-CNN integer score from 1 to 10 with histogram context; it is not a malignancy probability.
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 FDA package describes Virtual Nodule Clinic as a web application deployed on a virtual server within a hospital datacenter and accessed via web browser, with the LCP-CNN module deployed on a GPU-equipped server on hospital premises or in the cloud. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "A web application deployed on a virtual server within a hospital datacenter;" … "The LCP-CNN module deployed on a GPU-equipped server on hospital premises or in the cloud.". 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 Virtual Nodule Clinic connecting to a DICOM-compatible PACS, querying and pulling images into a local PACS proxy, and to a RIS or reporting system for clinical reports, with read-only access that does not push data back. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "a DICOM-compatible Picture Archiving and Communication System (PACS) for accessing images and to the Radiology Information System (RIS) or reporting system for accessing the clinical reports." … "DICOM data is pulled from the hospital’s PACS and copied locally in a PACS proxy. VNC can query the hospital PACS for a patient’s images". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
ACR AI Central provides an exact-submission model card for Optellum Virtual Nodule Clinic, Optellum software, Optellum platform; 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
27Fields 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 K202300 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.
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: Adjunctive pulmonary nodule detection and measurement, including temporal comparison, in chest CT screening of asymptomatic adults aged at least 55 years.
Authorized purpose: Assist radiologists in detecting solid and subsolid pulmonary nodules during review of multivendor multi-detector CT examinations of the chest; the device is an adjunctive first- or second-reader tool.
Authorized purpose: Adjunctive detection of 3-20 mm pulmonary nodules in chest CT examinations for asymptomatic populations, including second-reader use.
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.