- Integration
- Standards-based DICOM/PACS integration was identified in the FDA submission materials; compatibility with a specific PACS, RIS, EHR, or orchestrator requires confirmation.
Public source Exact FDA submission Checked 2026-08-13
Normalized from the prior exact-submission review. Confirm interface versions and local compatibility during technical evaluation.
- Deployment and data flow
- Not established in reviewed sources
Reviewed sources checked Exact FDA submission Checked 2026-09-04
The exact installed deployment, hosting, service, and operational boundary is not established by the reviewed public FDA material.
- Security and privacy
- Not established in reviewed sources
Reviewed sources checked Exact FDA submission Checked 2026-09-04
The FDA decision material does not establish the complete security posture for the exact product and deployment. Obtain architecture, identity, audit, encryption, retention, support-access, vulnerability-management, and incident-response evidence.
- Training and support
- Only qualified ct technologists and trained interpreting or treating physicians should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
FDA source Exact FDA submission Checked 2026-09-04
- Monitoring and change control
- Monitor K241200 by exact software, hardware, 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: Use is limited by the cleared patient population, acquisition and dose protocols, contrast conditions, and trained professional interpretation; the low-dose screening option has its own labeled eligibility and protocol limits.
FDA source Exact FDA submission Checked 2026-09-04
Release and scope verification
Map the installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K241200 before acceptance.
exact submission · checked 2026-09-04 Later product-family features are not evidence that this cleared release includes them.
Interoperability acceptance
Exact public integration details remain incomplete; establish and test the supported input, output, identity, routing, archive, report, and downtime contract locally.
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 exact labeled population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. Use only the cleared populations, protocols, reconstructions, applications, and patient-size limits; local dose, image-quality, geometry, and downstream acceptance remain necessary.
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 reviewed public material; productivity or value claims require local evidence.
Lifecycle monitoring
Monitor 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.
exact submission · checked 2026-09-04 Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. No exact native-submission recall record was found in the checked snapshot; this does not exclude other product-family or later signals.
Deployment boundary
The exact installed deployment, hosting, service, security, and operational boundary remains unverified and requires site-specific confirmation.
exact submission · checked 2026-09-04 FDA-described deployment details do not establish current hosting contracts, security controls, uptime, or local qualification.