FDA-cleared profile

Oncospace

Oncospace, Inc. · Radiotherapy Planning Imaging · FDA-cleared (510(k))

Authorized purpose: Oncospace supports trained radiation therapy professionals with protocol configuration, achievable-dose prediction, planning-objective exchange, and plan review for prostate, thoracic, pancreas, and head-and-neck workflows using locked models.

Clinical role
Protocol management, achievable-dose prediction, planning-objective exchange, and plan review
Images and patients
Radiotherapy Planning Imaging · Multi-region
Key limitation
Keep in mind: Diagnosis and treatment decisions occur prior to treatment planning and do not involve Oncospace. Decisions involving Oncospace are restricted to setting of dosimetric goals for use during plan optimization and plan evaluation. Human judgement continues to be applied in accepting these goals and updating them as necessary during the iterative beam optimization process. Human judgement is also still applied as in standard practice during plan quality assessment. Oncospace also does not interface with the treatment machines. The risk to patient safety is lower than a TPS since it only informs the treatment plan, does not allow region of interest editing, does not make treatment decisions, and does not interface directly with the treatment machine or any record and verify system. In the current software release, static machine learning models are used for prostate plan predictions, and statistical/database lookup methods are used for thoracic, pancreas, and head & neck plan predictions.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, 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: Oncospace supports trained radiation therapy professionals with protocol configuration, achievable-dose prediction, planning-objective exchange, and plan review for prostate, thoracic, pancreas, and head-and-neck workflows using locked models.
  • Which images or clinical context are in scope?Modality: Radiotherapy Planning Imaging Anatomy or clinical context: Multi-region Input: DICOM RT planning data, dose prescriptions, target and organ-at-risk geometry, protocol definitions, plan parameters, and user-confirmed structure-name mappings.
  • Who uses it?Intended users: Qualified and trained radiation-therapy professionals, including radiation oncologists, medical physicists, and dosimetrists, using the system under a physician prescription.
  • What does the software produce?Output: Oncospace is used to configure and review radiotherapy treatment plans for a patient with malignant or benign disease in the prostate, thoracic, pancreas, or head & neck regions. It allows for set up of radiotherapy treatment protocols, association of a potential treatment plan with the protocol(s), submission of a dose prescription and achievable dosimetric goals to a treatment planning system, and review of the treatment plan.
  • What is its most important limitation?Key limitation: Diagnosis and treatment decisions occur prior to treatment planning and do not involve Oncospace. Decisions involving Oncospace are restricted to setting of dosimetric goals for use during plan optimization and plan evaluation. Human judgement continues to be applied in accepting these goals and updating them as necessary during the iterative beam optimization process. Human judgement is also still applied as in standard practice during plan quality assessment. Oncospace also does not interface with the treatment machines. The risk to patient safety is lower than a TPS since it only informs the treatment plan, does not allow region of interest editing, does not make treatment decisions, and does not interface directly with the treatment machine or any record and verify system. In the current software release, static machine learning models are used for prostate plan predictions, and statistical/database lookup methods are used for thoracic, pancreas, and head & neck plan predictions.

Clinical takeaway. Clinical role: Oncospace supports trained radiation therapy professionals with protocol configuration, achievable-dose prediction, planning-objective exchange, and plan review for prostate, thoracic, pancreas, and head-and-neck workflows using locked models.

Evidence takeaway. Evidence from the reviewed source record: Exact FDA summaries describe retrospective model development, internal and external testing, and clinical validation intended to preserve plan quality while reducing planning effort. A 2026 vendor-authored publication reports a larger two-institution development and validation program; its financial-support disclosure and release mapping should be considered before generalizing results.

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
Oncospace supports trained radiation therapy professionals with protocol configuration, achievable-dose prediction, planning-objective exchange, and plan review for prostate, thoracic, pancreas, and head-and-neck workflows using locked models.
  • Exact FDA submission
  • Checked 2026-09-19

Clinical-use display mirrors the exact FDA-supported purpose reconciled from the decision-summary packet.

Workflow role
Protocol management, achievable-dose prediction, planning-objective exchange, and plan review
  • Exact FDA submission
  • Checked 2026-09-03
Required input
DICOM RT planning data, dose prescriptions, target and organ-at-risk geometry, protocol definitions, plan parameters, and user-confirmed structure-name mappings.
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Output and clinician action
Oncospace is used to configure and review radiotherapy treatment plans for a patient with malignant or benign disease in the prostate, thoracic, pancreas, or head & neck regions. It allows for set up of radiotherapy treatment protocols, association of a potential treatment plan with the protocol(s), submission of a dose prescription and achievable dosimetric goals to a treatment planning system, and review of the treatment plan.
  • Exact FDA submission
  • Checked 2026-09-19

The exact indication states protocol setup, plan association, dose-prescription and dosimetric-goal submission, and plan review; it does not state the current protocol-scorecard output wording.

Care setting
Radiation-therapy departments in hospitals, clinics, and other qualified treatment-planning facilities.
  • Exact FDA submission
  • Checked 2026-09-03
Intended users
Qualified and trained radiation-therapy professionals, including radiation oncologists, medical physicists, and dosimetrists, using the system under a physician prescription.
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Limitations
Diagnosis and treatment decisions occur prior to treatment planning and do not involve Oncospace. Decisions involving Oncospace are restricted to setting of dosimetric goals for use during plan optimization and plan evaluation. Human judgement continues to be applied in accepting these goals and updating them as necessary during the iterative beam optimization process. Human judgement is also still applied as in standard practice during plan quality assessment. Oncospace also does not interface with the treatment machines. The risk to patient safety is lower than a TPS since it only informs the treatment plan, does not allow region of interest editing, does not make treatment decisions, and does not interface directly with the treatment machine or any record and verify system. In the current software release, static machine learning models are used for prostate plan predictions, and statistical/database lookup methods are used for thoracic, pancreas, and head & neck plan predictions.
  • Exact FDA submission
  • Checked 2026-09-19

The replacement uses only the packet’s direct decision, human-judgment, control, interface, locked-model, and release-specific prediction statements.

Evidence summary
Exact FDA summaries describe retrospective model development, internal and external testing, and clinical validation intended to preserve plan quality while reducing planning effort. A 2026 vendor-authored publication reports a larger two-institution development and validation program; its financial-support disclosure and release mapping should be considered before generalizing results.
  • Exact FDA submission
  • Checked 2026-09-03

Evidence

Performance evidence

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
Exact FDA summaries describe retrospective model development, internal and external testing, and clinical validation intended to preserve plan quality while reducing planning effort. A 2026 vendor-authored publication reports a larger two-institution development and validation program; its financial-support disclosure and release mapping should be considered before generalizing results.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-03
Reported sensitivity
Not applicable
  • Not applicable
  • Not applicable
  • Checked 2026-09-03

Sensitivity is not an applicable primary endpoint for this radiation-planning software. Review structure-, model-, workflow-, and release-specific geometric, clinical-review, dosimetric, and edit-burden evidence instead.

Reported specificity
Not applicable
  • Not applicable
  • Not applicable
  • Checked 2026-09-03

Specificity is not an applicable primary endpoint for this radiation-planning software. Review structure-, model-, workflow-, and release-specific geometric, clinical-review, dosimetric, and edit-burden evidence instead.

Retrospective development and validation plans

5334 plans

  • EndpointPhoton-beam plans used across model development and validation
  • PopulationTwo-institution multi-region cohort
  • Tested versionOncospace Predictive Planning product family

Development institutions

2 institutions

  • EndpointInstitutions contributing retrospective plans
  • PopulationMulti-region photon treatment plans
  • Tested versionOncospace Predictive Planning product family

K202284 FDA performance package for Oncospace

  • DesignManufacturer retrospective model development, internal or external performance testing, and clinical plan-quality validation
  • PopulationRelease-specific retrospective radiation plans and supported disease-site models described in the FDA summary
  • Scopeexact submission
  • Tested versionInitial Oncospace release cleared in K202284
  • IndependenceSponsor or vendor study

K202284

Manufacturer evidence submitted for substantial equivalence. The initial release supported protocol configuration, plan-quality prediction, and plan review for prostate, thoracic, pancreas, and head-and-neck disease using locked models and retrospective validation.

Development and clinical validation of Oncospace Predictive Planning

  • DesignRetrospective development, internal testing, and clinical validation of protocol-agnostic dose-volume prediction models
  • Population5,334 photon-beam plans across head and neck, thoracic, abdominal, and pelvic regions
  • Scopeproduct family
  • Tested versionOncospace Predictive Planning product family; exact release mapping was not established for every submission
  • Samplen=5334
  • Sites2
  • IndependenceSponsor or vendor study

PMID 42382856

Authors were affiliated with Oncospace and the publication reports company and grant support; treat it as vendor-involved product-family evidence.

Safety and lifecycle

Postmarket record

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 K202284 by exact submission identifier.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-03

A zero-result exact-identifier search does not prove that no recall, correction, adverse-event report, or product-family safety signal exists. Maintain ongoing FDA and vendor surveillance.

Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

Reimbursement

Reimbursement
No separate named-product Medicare payment was identified in the reviewed CMS Radiation Oncology Model material. Evaluate the product within the radiation-therapy planning service line using net staff time after review, plan quality, rework, throughput, implementation cost, and recurring cost.
  • Service-level, not product-specific
  • Checked 2026-09-03

No product-specific code

No separate named-product payment identified in reviewed CMS material

Centers for Medicare & Medicaid Services · United States

Build a local total-cost and value model; do not infer reimbursement from FDA clearance.

IT implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. Acquisition/source

    Source context, not route validation: DICOM RT planning data, dose prescriptions, target and organ-at-risk geometry, protocol definitions, plan parameters, and user-confirmed structure-name mappings.

    Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-19 · FDA K202284: Oncospace

  2. Routing

    Source context, not route validation: DICOM-RT compliant browser-based workflow with treatment-planning-system scripts used to transmit DICOM files and plan parameters; exact supported TPS versions and scripting permissions require local verification.

    Scope: Exact FDA submission.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-09-03 · FDA K202284: Oncospace · Oncospace product and implementation frequently asked questions

  3. AI processing

    Source context, not route validation: FDA summaries describe a Windows-server and web-browser architecture, including cloud Windows servers and client machines. The current vendor FAQ describes enterprise identity integration; confirm tenancy, data residency, availability, backups, and interface ownership.

    Scope: Exact FDA submission.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-09-03 · FDA K202284: Oncospace · Oncospace product and implementation frequently asked questions

  4. Returned objects

    Source context, not route validation: Oncospace is used to configure and review radiotherapy treatment plans for a patient with malignant or benign disease in the prostate, thoracic, pancreas, or head & neck regions. It allows for set up of radiotherapy treatment protocols, association of a potential treatment plan with the protocol(s), submission of a dose prescription and achievable dosimetric goals to a treatment planning system, and review of the treatment plan.

    Scope: Exact FDA submission. The exact indication states protocol setup, plan association, dose-prescription and dosimetric-goal submission, and plan review; it does not state the current protocol-scorecard output wording.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-19 · FDA K202284: Oncospace

  5. Viewer/worklist/report

    Unresolved route: Oncospace is used to configure and review radiotherapy treatment plans for a patient with malignant or benign disease in the prostate, thoracic, pancreas, or head & neck regions. It allows for set up of radiotherapy treatment protocols, association of a potential treatment plan with the protocol(s), submission of a dose prescription and achievable dosimetric goals to a treatment planning system, and review of the treatment plan.

    Scope: Exact FDA submission. The exact indication states protocol setup, plan association, dose-prescription and dosimetric-goal submission, and plan review; it does not state the current protocol-scorecard output wording.

    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.

    Field checked 2026-09-19 · FDA K202284: Oncospace

  6. Support owner

    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.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. 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.

Open the printable evaluation checklist

Deployment
FDA summaries describe a Windows-server and web-browser architecture, including cloud Windows servers and client machines. The current vendor FAQ describes enterprise identity integration; confirm tenancy, data residency, availability, backups, and interface ownership.
  • Exact FDA submission
  • Checked 2026-09-03
Integration
DICOM-RT compliant browser-based workflow with treatment-planning-system scripts used to transmit DICOM files and plan parameters; exact supported TPS versions and scripting permissions require local verification.
  • Exact FDA submission
  • Checked 2026-09-03
Security
The current vendor FAQ states that Oncospace can use an organization's Active Directory or Azure policies for user authentication and invites deployment-specific security review. This is product-family information, not an attestation for a particular installation.
  • Product family
  • Checked 2026-09-03

Request the current security package and contract controls for the proposed deployment.

Training
Only trained and qualified radiation-therapy professionals should operate the software and review, correct, and approve its outputs. Local onboarding must include release-specific limitations, failure examples, escalation, and competency documentation.
  • Exact FDA submission
  • Checked 2026-09-03
Monitoring
Monitor prediction and plan-review performance by software and model version, disease site, protocol, target and OAR geometry, structure-name mapping, objective acceptance, optimization iterations, plan quality, overrides, transfer failures, and update. Revalidate when models, protocols, TPS versions, interfaces, or clinical policies change.
  • Exact FDA submission
  • Checked 2026-09-03

Release and scope verification

The initial release supported protocol configuration, plan-quality prediction, and plan review for prostate, thoracic, pancreas, and head-and-neck disease using locked models and retrospective validation. Procurement should map the installed build, modules, models, anatomies, inputs, and outputs to K202284 before acceptance.

exact submission · checked 2026-09-03

Later product-family features are not evidence that an earlier cleared release includes them.

Interoperability acceptance

DICOM-RT compliant browser-based workflow with treatment-planning-system scripts used to transmit DICOM files and plan parameters; exact supported TPS versions and scripting permissions require local verification.

exact submission · checked 2026-09-03

Test representative imports, exports, identifiers, orientation, geometry, structure names, units, failure handling, and round trips in the local environment.

Clinical acceptance

Use a signed local test set spanning supported anatomies, scanners, protocols, unusual or postsurgical anatomy, and small or complex structures. Measure edit burden, rejection, downstream plan effects, and reviewer agreement rather than relying only on average overlap metrics.

product family · checked 2026-09-03

Define stop-use, escalation, rollback, and revalidation triggers before production use.

Economic evaluation

Model total annual and per-plan cost against hands-on and elapsed time after review, correction, failed transfers, rework, support, upgrades, downtime, and any effect on plan quality or throughput.

product family · checked 2026-09-03

Vendor time-saving results are scenario inputs, not guaranteed local savings.

Lifecycle monitoring

Monitor prediction and plan-review performance by software and model version, disease site, protocol, target and OAR geometry, structure-name mapping, objective acceptance, optimization iterations, plan quality, overrides, transfer failures, and update. Revalidate when models, protocols, TPS versions, interfaces, or clinical policies change.

product family · checked 2026-09-03

Trend failures and edits by exact software version, model, anatomy, scanner, protocol, and site.

Sources & review details FDA 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.

FDA submission
K202284
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Radiotherapy Planning Imaging
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Anatomy
Multi-region
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.

Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2021-03-12
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Exact FDA record reviewedStatus
2026-09-20Last searched
27Fields reviewed
13Source classes checked
4Screened PubMed leads
1Screened trial leads
0Unreviewed FDA recall leads

The refreshed discovery snapshot contains 4 PubMed and 1 ClinicalTrials.gov candidate records. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 4 PubMed and 1 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, peer reviewed publication, health technology guidance, reimbursement policy, fda device recall, fda decision summary packet, literature index, trial registry, 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.

  • Public pricing: Not publicly available - checked 2026-09-03 - Exact FDA submission

    No public list price for the exact cleared release was found. Obtain a written quote separating license basis, sites or users, enabled modules or models, implementation, interfaces, compute, storage, training, support, upgrades, renewal, and exit costs.

  • Pricing model: Not yet reviewed
  • Setup and integration fees: Not yet reviewed
  • Recurring fees: Not yet reviewed
  • Minimum commitment: Not yet reviewed
  • Contract duration: Not yet reviewed
  • Renewal terms: Not yet reviewed
  • Cancellation terms: Not yet reviewed
  • Support and service terms: Not yet reviewed
  • Trial or pilot terms: Not yet reviewed
  • Data hosting location: Not yet reviewed
  • Data retention: Not yet reviewed
  • Documented data use: Not yet reviewed
  • Hardware requirements: Not yet reviewed
  • Network requirements: Not yet reviewed
  • Identity and access: Not yet reviewed
  • Installation timeline: Not yet reviewed

9 sources - 3 history items

Source ledger

  1. FDA K202284: Oncospace

    U.S. Food and Drug Administration - Published 2021-03-12 - Accessed 2026-09-19

    Scope: purpose, modality, anatomy, intendedUsers, input, output, limitations, evidenceSummary, clinicalUse

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  4. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  5. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  6. Radiation Oncology Model

    Centers for Medicare & Medicaid Services - Accessed 2026-09-02

    Scope: reimbursement, radiationTherapyPaymentContext

  7. Artificial intelligence technologies to aid contouring for radiotherapy treatment planning

    National Institute for Health and Care Excellence - Published 2023-09-27 - Accessed 2026-09-02

    Scope: limitations, training, pricing, evidenceSummary, economics, monitoring, implementationCapabilities

  8. Oncospace product and implementation frequently asked questions

    Oncospace, Inc. - Accessed 2026-09-03

    Scope: productFamily, workflowRole, integration, deployment, security, currentCommercialContext, implementationCapabilities

  9. Development and clinical validation of a protocol-agnostic machine-learning platform for automated treatment planning

    Advances in Radiation Oncology - Published 2026-04-01 - Accessed 2026-09-03

    Scope: limitations, evidenceSummary, evidenceStudy, evidenceMetrics, economics, monitoring, implementationCapabilities

Research history

  1. K202284 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K253091

ART-Plan+ (v3.1.0)

Therapanacea Sas

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.

Modality
Radiotherapy Planning Imaging
Anatomy
Multi-region
Decision
2025-12-23
FDA-cleared K242822

ART-Plan+ (v.3.0.0)

Therapanacea SAS

Authorized purpose: ART-Plan assists trained radiation-therapy professionals with multimodal image review, registration, contouring, and the release-specific planning functions described in K242822. This release included Annotate and TumorBox contouring plus SmartPlan automatic prostate-plan generation for import into the treatment-planning system for dose calculation, review, and approval.

Modality
Radiotherapy Planning Imaging
Anatomy
Multi-region
Decision
2025-02-25
FDA-cleared K222803

Oncospace

Oncospace, Inc.

Authorized purpose: Oncospace supports trained radiation therapy professionals with protocol configuration, machine-learning achievable-dose prediction, planning-objective exchange, and plan review for prostate and head-and-neck workflows using locked models.

Modality
Radiotherapy Planning Imaging
Anatomy
Multi-region
Decision
2023-02-02
FDA-cleared K260509

AutoContour (RADAC V5)

Radformation, Inc.

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.

Modality
Radiotherapy Planning Imaging
Anatomy
Multi-region
Decision
2026-03-19

Correct this exact record

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.

Open existing correction destination

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.

Correction policy and limits · Public repository change history