FDA-cleared profile

A View LCS

Coreline Soft Co., Ltd. · CT/CTA · FDA-cleared (510(k))

Reviews, analyzes, and reports thoracic CT images to characterize lung nodules across single or follow-up studies.

Clinical role
Software for reviewing, analyzing and reporting thoracic CT nodules in single or serial studies: semi-automatic nodule segmentation and measurement, automatic detection via integration with 3rd party CAD, and PDF reports saved or sent in DICOM.
Images and patients
CT/CTA · Chest/Lung
Key limitation
The packet does not establish all-scanner support or a current deployment model.

Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial overview.

Report a correction
Clinical details Purpose, 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

  • Imaging and anatomyCT/CTA · Chest/Lung
  • Workflow roleSoftware for reviewing, analyzing and reporting thoracic CT nodules in single or serial studies: semi-automatic nodule segmentation and measurement, automatic detection via integration with 3rd party CAD, and PDF reports saved or sent in DICOM.
  • Required inputThoracic CT studies in DICOM format.
  • Output and human actionNodule type and location, size, volume, HU, mass, VDT, Lung-RADS, PANCAN, CAC/LAA, follow-up matching, CAD integration, and reports.

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
Reviews, analyzes, and reports thoracic CT images to characterize lung nodules across single or follow-up studies.
  • Exact FDA submission
  • Checked 2026-09-15

Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.

Workflow role
Software for reviewing, analyzing and reporting thoracic CT nodules in single or serial studies: semi-automatic nodule segmentation and measurement, automatic detection via integration with 3rd party CAD, and PDF reports saved or sent in DICOM.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "AVIEW LCS is intended for the review and analysis and reporting of thoracic CT images for the purpose of characterizing nodules in the lung in a single study, or over the time course of several thoracic studies." … "Provides following features as semi-automatic nodule measurement (segmentation), maximal plane measure, 3D measure and volumetric measures, automatic nodules detection by integration with 3rd party CAD.". Read from the exact FDA decision document on 2026-11-14.

Required input
Thoracic CT studies in DICOM format.
  • Exact FDA submission
  • Checked 2026-09-15

FDA packet input scope.

Output and clinician action
Nodule type and location, size, volume, HU, mass, VDT, Lung-RADS, PANCAN, CAC/LAA, follow-up matching, CAD integration, and reports.
  • Exact FDA submission
  • Checked 2026-09-15

FDA packet output scope.

Limitations
The packet does not establish all-scanner support or a current deployment model.
  • Exact FDA submission
  • Checked 2026-09-15

Exact packet boundary.

Evidence summary
No clinical study or testing was required; support is nonclinical verification, validation, DICOM, integration, and performance testing.
  • Exact FDA submission
  • Checked 2026-09-15

Packet testing description, not clinical-performance evidence.

Evidence

Performance evidence

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
No clinical study or testing was required; support is nonclinical verification, validation, DICOM, integration, and performance testing.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-15

Packet testing description, not clinical-performance evidence.

Reported sensitivity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

Reported specificity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.

Safety and lifecycle

Postmarket record

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 K201710. 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.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-09
Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not verified: Pricing information is recorded but not verified against a resolving source.

Reimbursement

IT implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. Acquisition/source

    Source context, not route validation: Thoracic CT studies in DICOM format.

    Scope: Exact FDA submission. FDA packet input scope.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-15 · FDA K201710: A View LCS

  2. Routing

    Source context, not route validation: The exact-submission ACR model card explicitly references DICOM 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.

    Field checked 2026-09-01 · AVIEW LCS model card (K201710)

  3. AI processing

    Source context, not route validation: The exact FDA package describes a thin client service that supports mobile viewing through iOS and Android devices, and lists a thin client server compatibility test report. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "Support mobile view through various mobile device served by Ios and Android." … "AVIEW LCS Thin Client Server Compatibility Test Report". 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.

    Field checked 2026-11-14 · FDA K201710: A View LCS

  4. Returned objects

    Source context, not route validation: Nodule type and location, size, volume, HU, mass, VDT, Lung-RADS, PANCAN, CAC/LAA, follow-up matching, CAD integration, and reports.

    Scope: Exact FDA submission. FDA packet output scope.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-15 · FDA K201710: A View LCS

  5. Viewer/worklist/report

    Unresolved route: Nodule type and location, size, volume, HU, mass, VDT, Lung-RADS, PANCAN, CAC/LAA, follow-up matching, CAD integration, and reports.

    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.

    Field checked 2026-09-15 · FDA K201710: A View LCS

  6. Support owner

    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.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. 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.

Open the printable evaluation checklist

Deployment
The exact FDA package describes a thin client service that supports mobile viewing through iOS and Android devices, and lists a thin client server compatibility test report. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Support mobile view through various mobile device served by Ios and Android." … "AVIEW LCS Thin Client Server Compatibility Test Report". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The exact-submission ACR model card explicitly references DICOM 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.

Input or output interoperability

DICOM is explicitly referenced in the described input, output, or workflow.

exact submission · checked 2026-09-01

The model card does not establish every supported DICOM object, transfer method, or local interface.

Supported acquisition environment

Scanner manufacturers: All

exact submission · checked 2026-09-01

Confirm currently supported software versions, protocols, and site-specific acquisition configurations.

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for A View LCS; FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-09
Sources & review details FDA 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.

FDA submission
K201710
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-15

FDA thoracic CT scope normalized to controlled CT bucket.

Anatomy
Chest/Lung
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-15

FDA thoracic and lung-nodule scope.

Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2020-10-16
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Exact FDA record reviewedStatus
2026-09-15Last searched
22Fields reviewed
10Source classes checked
0Awaiting review PubMed leads
0Awaiting review trial leads
0Unreviewed FDA recall leads

Exact-submission ACR model-card fields were normalized under the current provenance rules; vendor and independent-study confirmation remain distinct. Exact FDA decision-summary packet reviewed on 2026-09-15. Applied FDA-supported reader facts: purpose, modality, anatomy, input, output, limitations, evidenceSummary. Facts marked unknown in the FDA packet retain any prior non-FDA source without reclassification. Candidate literature and postmarket candidates remain in their existing review state. Automated exact-name discovery found 0 PubMed and 0 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.

Candidate leads remain unpublished until a human confirms the exact product and tested version.

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.

  • Care setting: 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 a care setting or patient population for the subject device. Confirm intended sites and patients with the vendor and local policy.

  • Intended users: Withdrawn - checked 2026-09-15 - Exact FDA submission

    Previous value withdrawn: The exact FDA decision-summary packet reviewed on 2026-09-15 does not establish this claim; the packet does not name a specific user class.

  • Public pricing: Not verified - checked 2026-09-09 - Exact FDA submission

    No public price or quote for the exact K201710 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.

7 sources - 2 history items

Source ledger

  1. FDA K201710: A View LCS

    U.S. Food and Drug Administration - Published 2020-10-16 - Accessed 2026-09-09

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, purpose, input, output, limitations, evidenceSummary, deployment

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. AVIEW LCS model card (K201710)

    American College of Radiology - Published 2026-08-17 - Accessed 2026-09-01

    Scope: intendedUsers, output, limitations, integration, anatomy, implementationCapabilities

  4. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  6. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  7. openFDA exact recall query for K201710

    U.S. Food and Drug Administration - Accessed 2026-09-09

    Scope: postmarketSafety

Research history

  1. K201710 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

Alternatives

Related tools to compare

FDA-cleared K251474

Median LCS (internal name) / eyonis LCS (trade name) (1.0)

Median Technologies

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.

Modality
CT/CTA
Anatomy
Chest/Lung
Decision
2026-02-06
FDA-cleared K242919

V5med Lung AI

V5med Inc.

Authorized purpose: V5med Lung AI provides concurrent-read adjunctive notification of suspected pulmonary nodules on chest CT; it does not replace radiologist judgment, diagnostic processes, or review of original CT series.

Modality
CT/CTA
Anatomy
Chest/Lung
Decision
2025-03-27
FDA-cleared K231157

syngo.CT Lung CAD (Version VD30)

Siemens Healthcare GmbH

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.

Modality
CT/CTA
Anatomy
Chest/Lung
Decision
2023-07-19

Correct this exact record

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.

Open existing correction destination

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.

Correction policy and limits · Public repository change history