Input or output interoperability
DICOM is explicitly referenced in the described input, output, or workflow.
exact submission · checked 2026-09-01The model card does not establish every supported DICOM object, transfer method, or local interface.
FDA-cleared profile
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.
Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial overview.
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
Evidence context not reviewed for this FDA record.
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.
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
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.
FDA packet input scope.
FDA packet output scope.
Exact packet boundary.
Packet testing description, not clinical-performance evidence.
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.
Packet testing description, not clinical-performance evidence.
This field has not been curated yet.
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
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Price not public here; enter your quote
Not verified: Pricing information is recorded but not verified against a resolving source.
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.
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
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)
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
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
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
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
No tests below have been performed or accepted.
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
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.
Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
DICOM is explicitly referenced in the described input, output, or workflow.
exact submission · checked 2026-09-01The model card does not establish every supported DICOM object, transfer method, or local interface.
Scanner manufacturers: All
exact submission · checked 2026-09-01Confirm currently supported software versions, protocols, and site-specific acquisition configurations.
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-09Regulatory identity
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
FDA thoracic CT scope normalized to controlled CT bucket.
FDA thoracic and lung-nodule scope.
Research record
This audit distinguishes completed source review from fields that have not yet been researched.
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
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.
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.
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.
No public price or quote for the exact K201710 configuration was established in this review.
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
7 sources - 2 history items
Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, purpose, input, output, limitations, evidenceSummary, deployment
Scope: regulatoryIdentity, modalityContext
Scope: intendedUsers, output, limitations, integration, anatomy, implementationCapabilities
Scope: evidenceDiscovery
Scope: evidenceDiscovery, studyStatus
Scope: recallDiscovery, nativeSubmissionMatching
Scope: postmarketSafety
Regulatory record
510(k)
Research record
fda record reviewed
Alternatives
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.
Infervision Medical Technology Co., Ltd.
Authorized purpose: Adjunctive pulmonary nodule detection and measurement, including temporal comparison, in chest CT screening of asymptomatic adults aged at least 55 years.
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.
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.
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 destinationPermission 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.
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