Workflow role
Medical-image viewing, processing, segmentation, measurement, registration, communication, or planning support within the exact labeled scope.
exact submission · checked 2026-09-04 Submission-anchored workflow summary, not a local acceptance or deployment result.
Input
DICOM or other medical-image data from the exact labeled modalities, scanners, and user workflow.
exact submission · checked 2026-09-04 Exact supported inputs and protocol limits must be confirmed from the complete labeling.
Output
Images, measurements, segmentations, models, reports, or planning information for professional review.
exact submission · checked 2026-09-04 Output review, editing, approval, export, and downstream use remain release- and site-specific.
Deployment evidence
Exact deployment topology and operational boundaries remain unestablished.
exact submission · checked 2026-09-04 Confirm hosting, PHI flow, retention, access, updates, downtime, and support obligations before procurement or clinical use.
Integration evidence
The exact FDA material describes processing of medical-image data and DICOM-supported modules; local image import, export, treatment-planning connection, identity, and display require confirmation.
exact submission · checked 2026-09-04 Validate the local workflow against the exact release and enabled options.
Vendor family context
Current vendor material is product-family context for K223106 only; exact release, enabled options, deployment, security, interoperability, pricing, and local workflow require confirmation.
product family · checked 2026-09-04 Vendor material is not exact-release evidence unless that linkage is separately proven.
Release and scope verification
Map installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K223106 before acceptance.
exact submission · checked 2026-09-04 Later product-family features are not evidence that this cleared release includes them.
Deployment boundary
The exact public deployment topology remains incomplete; establish hosting responsibility, data flow, availability, upgrade, service, and downtime boundaries locally.
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 material describes DICOM transfer to and from PACS or storage, image viewing and processing, co-registration, segmentation, and 3D DICOM output.
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 exact supported applications, modalities, anatomy, protocols, options, and review path are submission-specific; outputs require professional review and do not establish a general product-wide sensitivity or specificity.
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 K223106 by exact hardware, software, model, 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.