- Integration
- The FDA-cleared architecture uses DICOM data, a Windows .NET client, a Windows agent that can monitor network storage for new CT or MR datasets, and a Linux-compatible cloud contouring service. V4 can export DICOM deformable REGISTRATION and deformed DOSE objects for review in external treatment-planning and registration-QA systems. Current product-family materials also describe direct Eclipse read/write and standalone DICOM workflows.
- Deployment and data flow
- K242729 describes a Windows .NET client and local Windows agent connected to a Linux-compatible cloud automatic-contouring service. Current product-family materials also offer cloud-based or local compute resources, but the V4 summary does not establish that every current deployment option applies to this cleared version.
- Security and privacy
- Radformation's current license terms state that cloud-processing configurations transmit selected CT or MR images, structures, plan, and dose data after software anonymization, encrypt the data in transit, and delete the imaging-plan data after returning results. The customer remains responsible for preventing PHI disclosure. The reviewed public sources do not establish which current controls apply to an installed V4 environment or describe its authentication, at-rest encryption, retention logging, vulnerability, backup, and incident-response controls.
Obtain version-specific security and support evidence and validate anonymization, identity, access, encryption, logging, deletion, recovery, and breach-response behavior.
- Training and support
- Radformation's current support terms include online educational materials, videos, and a remote training session with new access. NICE states that trained professionals must always review and edit AI autocontours and maintain manual contouring skills. Local V4 training should cover model selection, contouring-guideline alignment, review and editing, unusual-anatomy failure modes, registration QA, DICOM routing, downtime, and escalation.
- Monitoring and change control
- Monitor performance by exact software and model version, anatomy, structure, scanner and protocol, patient position, contrast, unusual or postsurgical anatomy, reviewer role, edit time, unusable or missing contours, DICOM transfer failures, registration and dose-export QA, incidents, and adverse events. NICE calls for ongoing error and adverse-event reporting, while independent AutoContour studies show that geometric averages can conceal clinically important outliers and contour-definition mismatches.
Define signed acceptance thresholds and revalidation triggers for software, model, scanner, protocol, routing, or local contouring-guideline changes.
Exact cleared model expansion
K242729 adds 77 CT and 18 MR contouring models to the V3 predicate across head and neck, thorax, abdomen, and pelvis and retains user review and editing.
exact submission · checked 2026-09-02 Create an enabled-model inventory tied to the installed build, FDA labeling, local anatomy, local contour definitions, and acceptance status.
DICOM and treatment-planning integration
The exact FDA architecture supports CT and MR contouring, PET/CT registration or fusion, DICOM RTSTRUCT and REGISTRATION inputs, and RTSTRUCT, REGISTRATION, and DOSE exports. Current product-family materials describe direct Eclipse and standalone DICOM workflows.
exact submission · checked 2026-09-02 Test each scanner, TPS, service class, object mapping, frame of reference, naming rule, routing path, retry, and failure-recovery workflow.
Human review and local commissioning
The device produces initial contours for review and modification. NICE and independent studies support model-by-model commissioning, trained review, retained manual skills, and special attention to small structures, unusual anatomy, contrast, positioning, and local contouring conventions.
product family · checked 2026-09-02 Commission with representative local cases and predefine accept, edit, reject, and manual-fallback criteria for each enabled model.
Cloud imaging-data governance
Current terms describe software anonymization, encrypted transmission, processing by Radformation, return of results, and deletion of imaging-plan data, while making the customer responsible for preventing PHI disclosure.
product family · checked 2026-09-02 Confirm the terms and controls that apply to the installed V4 environment and validate DICOM private tags, burned-in annotations, logs, support access, deletion evidence, and exception handling.
Economic evaluation
The vendor uses quote-based licensing. NICE found autocontouring economics depend on technology cost, professional grade, review and edit time, and true net time saved, with published time endpoints varying substantially.
product family · checked 2026-09-02 Model costs per completed plan and measure total hands-on and elapsed time, edit burden, rejected contours, downstream rework, throughput, and avoided overtime.
Lifecycle and upgrade planning
Current support terms condition support on current releases and installed updates. V4 users should obtain explicit support status, security-update commitments, migration scope, data portability, regression requirements, and rollback terms.
product family · checked 2026-09-02 Treat migration to a later model family as a controlled clinical change rather than assuming prior acceptance transfers.