- Integration
- The FDA package describes DICOM 3.0 storage, transfer, query, and display for CT studies.
This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
- Deployment and data flow
- The FDA package describes on-premises, cloud, mobile, and Chrome access options; the current configured topology and service boundary remain unverified.
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.
- Security and privacy
- Not established in reviewed sources
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.
- Training and support
- 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.
- Monitoring and change control
- Monitor K214036 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: The labeled use is for adults and supported thoracic or cardiac CT; scan kernel, protocol, device, image quality, and downstream clinical-review limits apply.
Monitoring guidance is buyer-facing implementation guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.
Release and scope verification
Map installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K214036 before acceptance.
exact submission · checked 2026-09-04 Later product-family features are not evidence that this cleared release includes them.
Deployment boundary
The FDA package describes on-premises, cloud, mobile, and Chrome access options; the current configured topology and service boundary remain unverified.
exact submission · checked 2026-09-04 FDA-described deployment boundaries do not establish current hosting contracts, security controls, uptime, or local qualification.
Interoperability acceptance
The FDA package describes DICOM 3.0 storage, transfer, query, and display for CT studies.
exact submission · checked 2026-09-04 Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.
Clinical acceptance
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. The labeled use is for adults and supported thoracic or cardiac CT; scan kernel, protocol, device, image quality, and downstream clinical-review limits apply.
exact submission · checked 2026-09-04 Define stop-use, escalation, rollback, and revalidation triggers before production use.
Economic evaluation
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.
Lifecycle monitoring
Monitor K214036 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: The labeled use is for adults and supported thoracic or cardiac CT; scan kernel, protocol, device, image quality, and downstream clinical-review limits apply.
exact submission · checked 2026-09-04 Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. thoracic CT analysis software limits remain submission-specific.