Authorized purpose: AutoContour Model RADAC V5 assists radiation treatment planners with contouring and reviewing structures in medical images for radiation therapy treatment planning. It produces initial machine-learning contours for user review and modification; it does not independently approve a contour or treatment plan.
Clinical role
Receives CT or MR image sets, generates initial structure contours, supports manual or automatic rigid registration and automatic deformable registration, presents contours for review and editing, and exports DICOM RTSTRUCT, REGISTRATION, and DOSE objects to the treatment-planning workflow.
Images and patients
Radiotherapy Planning Imaging · Multi-region
Key limitation
Keep in mind: Every generated contour and registration must be reviewed and edited as needed before planning use. FDA performance is model- and structure-specific: aggregate DSC and reviewer averages do not remove weak outliers, and several structure-level lower confidence bounds fall below the nominal size-category threshold. The summary describes training anatomy from adult male and female patients while its comparison table says any patient type with relevant scan data; pediatric, postsurgical, unusual-anatomy, positioning, contrast, and local-guideline performance therefore require local validation. Current vendor claims for CBCT and other v2.7 functions should not be assumed to be within this exact clearance unless confirmed against the applicable labeling.
Clinical detailsPurpose, workflow fit, evidence, and safety record
Workflow navigation pilot
Workflow role has not yet been reviewed for this navigation pilot.
A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources
What does this software do?Authorized purpose: AutoContour Model RADAC V5 assists radiation treatment planners with contouring and reviewing structures in medical images for radiation therapy treatment planning. It produces initial machine-learning contours for user review and modification; it does not independently approve a contour or treatment plan.
Which images or clinical context are in scope?Modality: Radiotherapy Planning Imaging Anatomy or clinical context: Multi-region Input: DICOM CT or MR images for contouring or registration and fusion; PET/CT for registration or fusion only; and DICOM RTSTRUCT and REGISTRATION objects as supported inputs.
Who uses it?Intended users: Radiation treatment planners who are qualified to select, review, edit, and export contours. Procurement and governance should include radiation oncologists, dosimetrists, medical physicists, radiation therapists, and clinical IT according to local role assignments.
What does the software produce?Output: User-reviewed and editable contours plus DICOM RTSTRUCT, REGISTRATION, and DOSE files for downstream review in a treatment-planning or independent registration-QA system. The FDA summary states that the device has no built-in reporting.
What is its most important limitation?Key limitation: Every generated contour and registration must be reviewed and edited as needed before planning use. FDA performance is model- and structure-specific: aggregate DSC and reviewer averages do not remove weak outliers, and several structure-level lower confidence bounds fall below the nominal size-category threshold. The summary describes training anatomy from adult male and female patients while its comparison table says any patient type with relevant scan data; pediatric, postsurgical, unusual-anatomy, positioning, contrast, and local-guideline performance therefore require local validation. Current vendor claims for CBCT and other v2.7 functions should not be assumed to be within this exact clearance unless confirmed against the applicable labeling.
Clinical takeaway. Clinical role: AutoContour Model RADAC V5 assists radiation treatment planners with contouring and reviewing structures in medical images for radiation therapy treatment planning. It produces initial machine-learning contours for user review and modification; it does not independently approve a contour or treatment plan.
Evidence takeaway. Evidence from the reviewed source record: V5 has an exact FDA technical-validation package and independent product-family evidence from earlier versions. The evidence supports assisted contour generation with mandatory review; it does not establish autonomous use, universal generalizability, reduced toxicity, improved tumor control, or other patient outcomes.
Evidence context
Evidence context not reviewed for this FDA record.
Public-label constraints
Label constraints have not been reviewed for this exact FDA record. Unknown is not all ages or evidence of unsuitability.
Public-label constraints, not patient-level eligibility or a medical recommendation. Training and evaluation populations are separate. Read the original labeling and confirm the exact release and protocol.
Purpose
AutoContour Model RADAC V5 assists radiation treatment planners with contouring and reviewing structures in medical images for radiation therapy treatment planning. It produces initial machine-learning contours for user review and modification; it does not independently approve a contour or treatment plan.
Exact FDA submission
Checked 2026-09-04
Added in P2 round17 from the exact FDA decision material; later product-family claims remain separate.
Receives CT or MR image sets, generates initial structure contours, supports manual or automatic rigid registration and automatic deformable registration, presents contours for review and editing, and exports DICOM RTSTRUCT, REGISTRATION, and DOSE objects to the treatment-planning workflow.
DICOM CT or MR images for contouring or registration and fusion; PET/CT for registration or fusion only; and DICOM RTSTRUCT and REGISTRATION objects as supported inputs.
User-reviewed and editable contours plus DICOM RTSTRUCT, REGISTRATION, and DOSE files for downstream review in a treatment-planning or independent registration-QA system. The FDA summary states that the device has no built-in reporting.
Radiation treatment planners who are qualified to select, review, edit, and export contours. Procurement and governance should include radiation oncologists, dosimetrists, medical physicists, radiation therapists, and clinical IT according to local role assignments.
Every generated contour and registration must be reviewed and edited as needed before planning use. FDA performance is model- and structure-specific: aggregate DSC and reviewer averages do not remove weak outliers, and several structure-level lower confidence bounds fall below the nominal size-category threshold. The summary describes training anatomy from adult male and female patients while its comparison table says any patient type with relevant scan data; pediatric, postsurgical, unusual-anatomy, positioning, contrast, and local-guideline performance therefore require local validation. Current vendor claims for CBCT and other v2.7 functions should not be assumed to be within this exact clearance unless confirmed against the applicable labeling.
V5 has an exact FDA technical-validation package and independent product-family evidence from earlier versions. The evidence supports assisted contour generation with mandatory review; it does not establish autonomous use, universal generalizability, reduced toxicity, improved tumor control, or other patient outcomes.
Metrics are shown only when they are tied to a source, endpoint, population, and tested product version. Candidate literature without exact product and version linkage is not shown as product evidence.
Evidence summary
V5 has an exact FDA technical-validation package and independent product-family evidence from earlier versions. The evidence supports assisted contour generation with mandatory review; it does not establish autonomous use, universal generalizability, reduced toxicity, improved tumor control, or other patient outcomes.
Sensitivity is not an applicable endpoint for this contour-generation device. Review the structure-specific DSC, distance, clinician-review, and local edit-burden evidence instead.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-02
Specificity is not an applicable endpoint for this contour-generation device. Review the structure-specific DSC, distance, clinician-review, and local edit-burden evidence instead.
FDA-listed CT contouring models
420 models
EndpointCT-based machine-learning contouring models listed for RADAC V5
PopulationHead and neck, thorax, abdomen, and pelvis structures in the K260509 comparison table
Tested versionAutoContour Model RADAC V5 cleared in K260509
K260509 AutoContour Model RADAC V5 verification and validation
DesignManufacturer nonclinical validation using held-out training-test partitions, external CT and MR datasets, size-stratified DSC criteria, clinical-expert Likert review, and existing-model regression tests
PopulationCT and MR structures across head and neck, thorax, abdomen, and pelvis, with data from several institutions and countries
Scopeexact submission
Tested versionAutoContour Model RADAC V5; regression tables identify AutoContour v2.7
IndependenceSponsor or vendor study
K260509
The FDA summary reports favorable category averages but also structure-level variability, one external MR structure below its DSC criterion, and no patient-outcome study.
A clinical evaluation of the performance of five commercial artificial intelligence contouring systems for radiotherapy
DesignIndependent single-center multi-vendor benchmark against manually drawn expert contours with geometric metrics and correction-time measurement
Population80 patients: 20 breast, 20 head and neck, 20 lung, and 20 prostate; 45 structures
Scopeproduct family
Tested versionAutoContour v1.0.25.0 tested in April 2022
Samplen=80
Sites1
IndependenceIndependent study
PMID 37601695
The authors reported no commercial or financial conflicts and acknowledged vendor support and guidance. Timing estimates used a three-patient subset and cannot be transferred to V5 or another site.
Evaluation of multiple-vendor AI autocontouring solutions
DesignIndependent single-center blinded physician review and geometric comparison of three commercial CT autocontouring systems against approved physician contours
PopulationSixteen organs, ten patients per organ, 47 distinct patients, and at least three physician reviewers per contour
Scopeproduct family
Tested versionAutoContour v2.2.8
Samplen=47
Sites1
IndependenceIndependent study
PMID 38822385
The study found generally comparable performance but documented poor results with unusual anatomy and local contour-definition differences. It informed implementation across five facilities, but it did not test V5.
Evaluation and failure analysis of four commercial deep learning-based autosegmentation software for abdominal organs at risk
DesignIndependent retrospective multi-vendor geometric evaluation with explicit outlier and failure-mode analysis
Population111 abdominal cases evaluating liver, stomach, and kidney contours
Scopeproduct family
Tested versionAutoContour v1.7.11
Samplen=111
Sites1
IndependenceIndependent study
PMID 39946266
Radformation outliers included liver spill into heart or stomach, incomplete stomach contours with barium, and kidney differences driven by whether the renal pelvis was included. The authors reported no conflicts.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The 2026-09-02 openFDA device-recall snapshot contained no record matched to K260509 by exact submission identifier.
Public source
Exact FDA submission
Checked 2026-09-02
A zero-result exact-identifier search does not prove that no recall, correction, MAUDE report, or other safety signal exists under a model, catalog, software-version, or product-family identifier. Maintain ongoing FDA and vendor surveillance.
Pricing is recorded, but no exact-product procurement price with a stated offer scope is published in the reviewed sources.
Public pricing
No public list price for AutoContour Model RADAC V5 was found on the reviewed product page. Radformation's license agreement places fees in a customer quote, treats pricing as confidential, and allows additional charges for special support. A quote should separate license basis, delivery-system count, implementation, local or cloud compute, storage and network needs, training, support, upgrades, and renewal terms.
No separate named-product Medicare payment for AutoContour was identified in the reviewed CMS Radiation Oncology Model material. Economic value should be evaluated within the radiation-therapy planning service line using net staff time saved after review and editing, implementation and recurring costs, throughput effects, rework, and downstream plan-quality measures.
IT implementationDeployment, interfaces, data handling, and support
System and version relationships
Match the AI release, system build, configuration and region. Source documentation does not establish acceptance of an installed system.
No specific system/version pairing has completed review for this FDA record. A broad DICOM or product-family statement does not establish a named viewer build's support.
Public source context, not tested interoperability. Each hop needs its own release/configuration evidence. Missing or unavailable routes are not documented incompatibility. All local tests are planned, not passed; no installed-system acceptance is recorded.
Acquisition/source → routing → AI processing → returned objects → viewer/worklist/report → support owner
No specific route context has been source-reviewed for this record. Obtain both endpoint builds and documents; this is not a finding of incompatibility.
Acquisition/source
Source context, not route validation: DICOM CT or MR images for contouring or registration and fusion; PET/CT for registration or fusion only; and DICOM RTSTRUCT and REGISTRATION objects as supported inputs.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: 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.
Scope: Exact product version.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: 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.
Scope: Exact product version.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: User-reviewed and editable contours plus DICOM RTSTRUCT, REGISTRATION, and DOSE files for downstream review in a treatment-planning or independent registration-QA system. The FDA summary states that the device has no built-in reporting.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: User-reviewed and editable contours plus DICOM RTSTRUCT, REGISTRATION, and DOSE files for downstream review in a treatment-planning or independent registration-QA system. The FDA summary states that the device has no built-in reporting.
Scope: Exact FDA submission.
Confirm the named viewer/worklist/report build, display behavior and report transfer. Output support alone does not establish this endpoint. The displayed source describes output, not validated end-to-end delivery.
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
Planned local route tests
No tests below have been performed or accepted.
Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
Updates and rollback (planned). Define version change control, revalidation triggers, stop-use criteria and a tested rollback route.
Local implementation checklist
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Sources & review detailsFDA identity, research record, source ledger, and history
Regulatory identity
FDA record and catalog context
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
This audit distinguishes completed source review from fields that have not yet been researched.
Human reviewedStatus
2026-09-04Last searched
26Fields reviewed
14Source classes checked
20Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
Twenty PubMed records were screened. PMID 38822385 concerns AutoContour v2.2.8 rather than RADAC V5/K260509, and the other records do not establish exact release linkage. No evidence was promoted, and all 20 candidates remain quarantined. The current discovery snapshot contains 20 PubMed and 0 ClinicalTrials.gov candidate records; its dated, count-matched human screening remains current. Unlinked candidates remain quarantined. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads were screened against the exact product and tested version. Unlinked records remain quarantined.
Source classes: fda ai list, fda decision summary, vendor product page, vendor legal documentation, peer reviewed publication, health technology guidance, trial registry, reimbursement policy, fda device recall, fda decision material, literature index, pubmed, clinical trials, openfda device recall
Field review details
Recorded state, verification date, notes and sources for fields without a publishable value. Conflicting records stay explicitly unsettled here; no plain settled value is shown for them.
Authorized purpose: The EMLA family delivers external-beam radiation therapy for adult and pediatric patients with benign, malignant, or metastatic disease. Authorized techniques vary by model: Synergy and Harmony include conventional and fractionated delivery; Infinity and Harmony Pro add SBRT/SABR; Versa HD and Evo also support SRS and specified functional disorders.
Authorized purpose: ART-Plan+ assists trained radiation-therapy professionals with multimodal image review, registration, contouring, and the release-specific planning functions described in K253091. This release combined Annotate, prostate SmartPlan, and AdaptBox for supported head-and-neck, breast or thorax, and male-pelvis offline adaptive workflows, and added structures without changing the core indication.
Authorized purpose: Oncospace supports trained radiation therapy professionals with protocol configuration, machine-learning achievable-dose prediction, planning-objective exchange, and plan review across head-and-neck, thoracic, abdominal, and pelvic workflows using locked models.
Authorized purpose: RayStation and RayPlan releases covered by K240398 are configurable radiotherapy and medical-oncology software that proposes or supports treatment plans from user inputs, with authorized users required to review and approve plans before treatment.
Copy this public context and add the field, proposed wording and original source before sending. Nothing here is submitted automatically. Form-specific prefill has not been verified.
Permission to display a submission is not evidence verification. A submission enters editorial review; it does not approve a public change. Form availability, data entry, receipt, review and publication are separate steps. Data entry and receipt remain unverified.
Accepted repository change history
No entry has been added to this scoped change history for this record. This is not proof that the record never changed.