- Integration
- Containerized application with dedicated input/output channels on a compatible image-communications platform; validate DICOM series selection, vendor and protocol variation, output association, viewer display, notification, and failure handling.
Public source Exact FDA submission Checked 2026-09-03
- Deployment and data flow
- A Docker application running on Olea Platform or another compatible configurable medical image communications platform.
Public source Exact FDA submission Checked 2026-09-03
- Security and privacy
- K230552 describes an independently deployable container and platform-mediated file channels but does not establish a complete current security posture. Obtain the exact container provenance, hardening, identity, audit, encryption, update, backup, and incident-response package.
FDA source Exact FDA submission Checked 2026-09-03
Confirm the controls against the exact contracted architecture and release.
- Training and support
- Only physicians, medical technicians, and trained professionals with medical-imaging education. should operate or interpret the system. 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-03
- Monitoring and change control
- Monitor by exact hardware, software and model 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 the limits that matter for this product: The application is not a standalone diagnostic device, does not alter the original images, and cannot be the sole basis for diagnosis, therapy, or patient management. Users must review all native images.
Public source Exact FDA submission Checked 2026-09-03
Release and scope verification
Map the installed model, build, options, population, anatomy, inputs, and outputs to K230552 before acceptance.
exact submission · checked 2026-09-03 Later product-family features are not evidence that this cleared release includes them.
Interoperability acceptance
Containerized application with dedicated input/output channels on a compatible image-communications platform; validate DICOM series selection, vendor and protocol variation, output association, viewer display, notification, and failure handling.
exact submission · checked 2026-09-03 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 application is not a standalone diagnostic device, does not alter the original images, and cannot be the sole basis for diagnosis, therapy, or patient management. Users must review all native images.
exact submission · checked 2026-09-03 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-03 Vendor productivity claims are scenario inputs, not guaranteed local savings.
Lifecycle monitoring
Monitor by exact hardware, software and model 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 the limits that matter for this product: The application is not a standalone diagnostic device, does not alter the original images, and cannot be the sole basis for diagnosis, therapy, or patient management. Users must review all native images.
exact submission · checked 2026-09-03 Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.