- Integration
- The FDA-cleared architecture uses DICOM 3.0 data over TCP/IP, 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. Current AutoContour v2.7 materials also describe direct Eclipse read/write through ESAPI and standalone DICOM workflows; each interface and object type needs site acceptance testing.
FDA source Exact product version Checked 2026-09-02
- Deployment and data flow
- K260509 describes a Windows client and local Windows agent connected to a Linux-compatible cloud automatic-contouring service. Current v2.7 marketing also offers cloud-based or local compute resources, but the selected commercial architecture, capacity, network path, and support boundary must be confirmed in the quote and deployment design.
FDA source Exact product version Checked 2026-09-02
- 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 terms place responsibility on the customer to prevent PHI disclosure. Public materials reviewed do not establish the exact V5 authentication, at-rest encryption, retention logging, vulnerability, backup, or incident-response controls for a proposed deployment.
Vendor supplied Product family Checked 2026-09-02
Obtain a current security package and contract exhibits, validate anonymization with representative DICOM objects, and document identity, access, encryption, logging, retention, subprocessor, recovery, and breach-response controls.
- 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 training should therefore cover model selection, contouring-guideline alignment, review and editing, unusual-anatomy failure modes, registration QA, DICOM routing, downtime, and escalation.
Vendor supplied Product family Checked 2026-09-02
- 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 contouring-guideline mismatches.
Public source Product family Checked 2026-09-02
Define signed acceptance thresholds and a revalidation trigger for model, software, scanner, protocol, routing, or local contouring-guideline changes.
Exact cleared model scope
K260509 lists 420 CT-based and 62 MR-based contouring models for head and neck, thorax, abdomen, and pelvis. The current product page advertises 480 models across CT, MR, and CBCT; those counts and modality categories are not interchangeable.
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 over TCP/IP. Current v2.7 materials add direct Eclipse and standalone DICOM workflow descriptions.
exact product version · 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 Validate the behavior technically and contractually, including 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 monitoring
Current support terms condition support on current releases and installed updates, while NICE calls for ongoing error and adverse-event reporting. Monitoring must remain version-, model-, and anatomy-specific.
product family · checked 2026-09-02 Use controlled update review, regression cases, release acceptance, incident trending, recall surveillance, downtime drills, and rollback criteria.