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: Adult thoracic and cardiac CT datasets, including supported sharp-to-soft kernel and single or serial lung-nodule studies.
Scope: Exact FDA submission. Prior source-backed dossier value: Supported medical images, DICOM metadata, patient and protocol information, and release-specific user inputs.
Confirm scanner/model, protocol, series completeness and both software builds.
Field checked 2026-09-04 · FDA 510(k) decision material K243689: AVIEW
Routing
Source context, not route validation: The FDA indication describes CT data storage, transfer, inquiry, and display in on-premises or cloud environments; validate the exact DICOM, identity, routing, archive, and deployment contract locally.
Scope: Exact FDA submission. The exact FDA material describes this input or interface boundary; local interoperability acceptance remains necessary. This is the interface boundary described in the exact FDA decision material; 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.
Field checked 2026-09-04 · FDA 510(k) decision material K243689: AVIEW
AI processing
Source context, not route validation: The FDA indication describes on-premises and cloud environments; hosting region, availability, security, retention, and contract responsibilities are not established by that indication.
Scope: Exact FDA submission. The exact FDA material describes this release-level deployment boundary; hosting, contracts, security, availability, and site configuration remain separate evidence. This is the release-level boundary described in the exact FDA decision material; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 · FDA 510(k) decision material K243689: AVIEW
Returned objects
Source context, not route validation: Lung, lobe, airway, fissure, and cardiac segmentations; density, size, volume, mass, volume-doubling-time, Lung-RADS, and Agatston, volume, or mass scores; reports and displays.
Scope: Exact FDA submission. Prior source-backed dossier value: Images, segmentations, measurements, models, calculations, overlays, or reports that require professional review.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Field checked 2026-09-04 · FDA 510(k) decision material K243689: AVIEW
Viewer/worklist/report
Unresolved route: Lung, lobe, airway, fissure, and cardiac segmentations; density, size, volume, mass, volume-doubling-time, Lung-RADS, and Agatston, volume, or mass scores; reports and displays.
Scope: Exact FDA submission. Prior source-backed dossier value: Images, segmentations, measurements, models, calculations, overlays, or reports that require professional review.
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-04 · FDA 510(k) decision material K243689: AVIEW
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.
No tests below have been performed or accepted.