Authorized purpose: AVIEW provides CT values for pulmonary tissue from thoracic and cardiac CT datasets and supports quantitative diagnosis, follow-up evaluation, and documentation through lung, lobe, airway, and cardiac segmentation, inspiration-expiration registration, air-trapping analysis, volumetric and density evaluation, nodule characterization, and reporting.
Clinical role
CT segmentation, quantitative tissue and nodule analysis, registration, reporting, and image-management support.
Images and patients
CT/CTA · Lungs, lobes, airways, pulmonary nodules, and cardiac anatomy
Key limitation
Keep in mind: Exact feature, anatomy, scan protocol, patient, reconstruction, and deployment limits are release-specific; quantitative outputs require physician review and do not replace the complete CT interpretation.
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: AVIEW provides CT values for pulmonary tissue from thoracic and cardiac CT datasets and supports quantitative diagnosis, follow-up evaluation, and documentation through lung, lobe, airway, and cardiac segmentation, inspiration-expiration registration, air-trapping analysis, volumetric and density evaluation, nodule characterization, and reporting.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Lungs, lobes, airways, pulmonary nodules, and cardiac anatomy Input: Thoracic and cardiac CT datasets received through DICOM 3.0 and supported study inputs.
Who uses it?Intended users: Trained radiologists and qualified physicians.
What does the software produce?Output: Lung, lobe, airway, cardiac, nodule, calcium, and related segmentations; measurements; quantitative values; reports; and DICOM or PDF results.
What is its most important limitation?Key limitation: Exact feature, anatomy, scan protocol, patient, reconstruction, and deployment limits are release-specific; quantitative outputs require physician review and do not replace the complete CT interpretation.
Clinical takeaway. Clinical role: AVIEW provides CT values for pulmonary tissue from thoracic and cardiac CT datasets and supports quantitative diagnosis, follow-up evaluation, and documentation through lung, lobe, airway, and cardiac segmentation, inspiration-expiration registration, air-trapping analysis, volumetric and density evaluation, nodule characterization, and reporting.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports only non-clinical software verification and validation, including performance tests of auto lung and lobe segmentation, airway segmentation, nodule matching, VDT and Lung RADS calculation, and CAC performance; the device passed all tests based on pre-determined Pass/Fail criteria. It states no clinical testing was required because the indications for use are equivalent to the predicate device. Results are as reported in the FDA submission, not independent validation.
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
AVIEW provides CT values for pulmonary tissue from thoracic and cardiac CT datasets and supports quantitative diagnosis, follow-up evaluation, and documentation through lung, lobe, airway, and cardiac segmentation, inspiration-expiration registration, air-trapping analysis, volumetric and density evaluation, nodule characterization, and reporting.
Exact feature, anatomy, scan protocol, patient, reconstruction, and deployment limits are release-specific; quantitative outputs require physician review and do not replace the complete CT interpretation.
The exact FDA document reports only non-clinical software verification and validation, including performance tests of auto lung and lobe segmentation, airway segmentation, nodule matching, VDT and Lung RADS calculation, and CAC performance; the device passed all tests based on pre-determined Pass/Fail criteria. It states no clinical testing was required because the indications for use are equivalent to the predicate device. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Additionally, there was no clinical testing required to support the medical device as the indications for use is equivalent to the predicate device. The substantial equivalence of the device is supported by the non-clinical testing" … "Verification, validation and testing activities were conducted to establish the performance, functionality and reliability characteristics of the modified devices. The device passed all of the tests based on pre-determined Pass/Fail criteria.". Read from the exact FDA decision document on 2026-11-14.
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
The exact FDA document reports only non-clinical software verification and validation, including performance tests of auto lung and lobe segmentation, airway segmentation, nodule matching, VDT and Lung RADS calculation, and CAC performance; the device passed all tests based on pre-determined Pass/Fail criteria. It states no clinical testing was required because the indications for use are equivalent to the predicate device. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Additionally, there was no clinical testing required to support the medical device as the indications for use is equivalent to the predicate device. The substantial equivalence of the device is supported by the non-clinical testing" … "Verification, validation and testing activities were conducted to establish the performance, functionality and reliability characteristics of the modified devices. The device passed all of the tests based on pre-determined Pass/Fail criteria.". Read from the exact FDA decision document on 2026-11-14.
Sensitivity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, study design, and source if separately verified.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-04
Specificity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, study design, and source if separately verified.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K200714 FDA evidence package for AVIEW
DesignFDA 510(k) software verification, validation, and substantial-equivalence evidence for CT image analysis applications.
PopulationLungs, lobes, airways, pulmonary nodules, and cardiac anatomy
Scopeexact submission
Tested versionAVIEW 2.0 configuration described in K200714
IndependenceSponsor or vendor study
K200714
The FDA summary states that no clinical study was required before release because the indications were equivalent to the predicate; testing was verification and validation against predetermined pass/fail criteria.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The 2026-09-02 openFDA device-recall snapshot contained no record matched to K200714 by exact native submission identifier. This does not exclude product-family, later-version, or adverse-event information.
Public source
Exact FDA submission
Checked 2026-09-04
Exact-identifier review does not prove absence of all product-family safety signals.
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging or clinical service line and verify payer, site-of-service, coding, and coverage assumptions independently.
No separate named-product payment identified in reviewed public material
Centers for Medicare & Medicaid Services · United States
This is not a product-specific reimbursement determination. Build a local total-cost and value model and verify payer, site-of-service, coding, and coverage assumptions independently.
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: Thoracic and cardiac CT datasets received through DICOM 3.0 and supported study inputs.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA package describes DICOM 3.0 input, image reading and manipulation, storage, transfer, PDF reports, DICOM result files, on-premise or cloud dataset access, mobile devices, and a Chrome browser.
Scope: Exact FDA submission. This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The FDA package describes AVIEW use on premise and in a cloud environment with access from mobile devices and a Chrome browser; current hosting, contracts, availability, security, and site configuration remain unverified.
Scope: Exact FDA submission. This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Lung, lobe, airway, cardiac, nodule, calcium, and related segmentations; measurements; quantitative values; reports; and DICOM or PDF results.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Lung, lobe, airway, cardiac, nodule, calcium, and related segmentations; measurements; quantitative values; reports; and DICOM or PDF results.
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 FDA package describes AVIEW use on premise and in a cloud environment with access from mobile devices and a Chrome browser; current hosting, contracts, availability, security, and site configuration remain unverified.
Exact FDA submission
Checked 2026-09-04
This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.
The FDA package describes DICOM 3.0 input, image reading and manipulation, storage, transfer, PDF reports, DICOM result files, on-premise or cloud dataset access, mobile devices, and a Chrome browser.
Exact FDA submission
Checked 2026-09-04
This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
Only trained radiologists and qualified physicians should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor K200714 by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: Exact feature, anatomy, scan protocol, patient, reconstruction, and deployment limits are release-specific; quantitative outputs require physician review and do not replace the complete CT interpretation.
Exact FDA submission
Checked 2026-09-04
This is buyer-facing monitoring guidance derived from the exact cleared or authorized scope; it is not a claim that the FDA package provides a live monitoring service.
The FDA package describes AVIEW use on premise and in a cloud environment with access from mobile devices and a Chrome browser; current hosting, contracts, availability, security, and site configuration remain unverified.
exact submission · checked 2026-09-04
FDA-described deployment boundaries do not establish current hosting contracts, security controls, uptime, or local qualification.
The FDA package describes DICOM 3.0 input, image reading and manipulation, storage, transfer, PDF reports, DICOM result files, on-premise or cloud dataset access, mobile devices, and a Chrome browser.
exact submission · checked 2026-09-04
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.
Use a signed local test set for the supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. Exact feature, anatomy, scan protocol, patient, reconstruction, and deployment limits are release-specific; quantitative outputs require physician review and do not replace the complete CT interpretation.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs.
product family · checked 2026-09-04
No exact-product price was found in the reviewed public material; productivity or value claims require local evidence.
Monitor K200714 by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: Exact feature, anatomy, scan protocol, patient, reconstruction, and deployment limits are release-specific; quantitative outputs require physician review and do not replace the complete CT interpretation.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. thoracic and cardiac CT analysis software limits remain submission-specific.
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.
Human reviewedStatus
2026-09-04Last searched
26Fields reviewed
12Source classes checked
20Screened PubMed leads
4Screened trial leads
0Unreviewed FDA recall leads
Twenty PubMed records and four trial records were screened. Exact Coreline records identify AVIEW versions 1.1.42.92, 2.5, 1.1.39.14, or another build rather than AVIEW 2.0 in K200714; remaining records are unrelated AView names or lack exact version linkage, so all 24 are quarantined. The current discovery snapshot contains 20 PubMed and 4 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 decision material, fda pma record, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, 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 publicly available - checked 2026-09-04 - Exact FDA submission
No public list price for the exact cleared or authorized configuration was found. Obtain a written quote separating hardware or license basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.
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
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 publicly available - checked 2026-09-04 - Exact FDA submission
Public materials reviewed for this exact release do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.
Authorized purpose: AVIEW provides quantitative CT analysis of pulmonary and cardiac anatomy, including lung, lobe, airway, fissure, nodule, coronary calcium, and related measurements and reports to support physician review in adults.
Modality
CT/CTA
Anatomy
Lungs, lobes, airways, fissures, heart, coronary arteries, and pulmonary nodules
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: AI-CVD provides automated quantitative CT-derived anatomical and density measurements for clinician review, including calcium scores, cardiac and vascular measurements, lung and liver density, bone mineral density, and muscle/fat composition; it is opportunistic decision support, not diagnostic interpretation or risk prediction.
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.