FDA-cleared profile

RayStation 12A

RaySearch Laboratories AB (publ) · Radiotherapy Planning Imaging · FDA-cleared (510(k))

Authorized purpose: RayStation 12A is configurable software for radiation therapy and medical oncology that proposes treatment plans from user input. Authorized users may use reviewed and approved plans to support treatment administration; the system includes image handling, contouring, treatment planning and optimization, dose calculation and evaluation, machine commissioning, treatment interfaces, and machine-learning segmentation or planning functions.

Clinical role
Imports patient imaging, supports registration and contouring, builds and optimizes treatment plans, calculates and evaluates dose, supports machine modeling and selected treatment interfaces, and exports reviewed and approved DICOM RT objects for downstream clinical use.
Images and patients
Radiotherapy Planning Imaging · Multi-region
Key limitation
Keep in mind: The systems are not intended for long term storage of images or other patient data.

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: RayStation 12A is configurable software for radiation therapy and medical oncology that proposes treatment plans from user input. Authorized users may use reviewed and approved plans to support treatment administration; the system includes image handling, contouring, treatment planning and optimization, dose calculation and evaluation, machine commissioning, treatment interfaces, and machine-learning segmentation or planning functions.
  • Which images or clinical context are in scope?Modality: Radiotherapy Planning Imaging Anatomy or clinical context: Multi-region Input: CT, PET, and MR images transferred through DICOM; patient geometry and structures; treatment-machine and beam-model data; prescriptions, clinical goals, optimization objectives, and other user-entered planning parameters.
  • Who uses it?Intended users: Authorized intended users who review and approve proposed treatment plans before treatment use.
  • What does the software produce?Output: Proposed and approved treatment plans, dose distributions, structures, images, reports, machine and setup parameters, and DICOM RT exports for authorized review and downstream treatment workflows.
  • What is its most important limitation?Key limitation: The systems are not intended for long term storage of images or other patient data.

Clinical takeaway. Clinical role: RayStation 12A is configurable software for radiation therapy and medical oncology that proposes treatment plans from user input. Authorized users may use reviewed and approved plans to support treatment administration; the system includes image handling, contouring, treatment planning and optimization, dose calculation and evaluation, machine commissioning, treatment interfaces, and machine-learning segmentation or planning functions.

Evidence takeaway. Evidence from the reviewed source record: The exact-version evidence is strongest for technical validation and comparative plan quality, not patient outcomes. FDA-reviewed manufacturer tests covered dose-engine and treatment-technique changes, while an independent 59-plan comparison evaluated RayStation 12A CyberKnife plans. Additional independent product-family commissioning data support local QA design but cannot be assumed to represent 12A without version confirmation.

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
RayStation 12A is configurable software for radiation therapy and medical oncology that proposes treatment plans from user input. Authorized users may use reviewed and approved plans to support treatment administration; the system includes image handling, contouring, treatment planning and optimization, dose calculation and evaluation, machine commissioning, treatment interfaces, and machine-learning segmentation or planning functions.
  • Exact FDA submission
  • Checked 2026-09-19

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

Workflow role
Imports patient imaging, supports registration and contouring, builds and optimizes treatment plans, calculates and evaluates dose, supports machine modeling and selected treatment interfaces, and exports reviewed and approved DICOM RT objects for downstream clinical use.
  • Exact FDA submission
  • Checked 2026-09-02
Required input
CT, PET, and MR images transferred through DICOM; patient geometry and structures; treatment-machine and beam-model data; prescriptions, clinical goals, optimization objectives, and other user-entered planning parameters.
  • 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
Proposed and approved treatment plans, dose distributions, structures, images, reports, machine and setup parameters, and DICOM RT exports for authorized review and downstream treatment workflows.
  • Exact FDA submission
  • Checked 2026-09-19

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

Care setting
Professional radiation oncology and medical oncology environments performing treatment planning, machine commissioning, plan review, and approved-plan transfer or treatment-management workflows.
  • Exact FDA submission
  • Checked 2026-09-02
Intended users
Authorized intended users who review and approve proposed treatment plans before treatment use.
  • Exact FDA submission
  • Checked 2026-09-19

The exact packet states that proposed plans are reviewed and approved by authorized intended users; it does not define the current role, qualification, or training wording.

Limitations
The systems are not intended for long term storage of images or other patient data.
  • Exact FDA submission
  • Checked 2026-09-19

The exact packet states the storage boundary; the current acceptance, commissioning, lesion-detection, dose-check, export, and machine-learning limitations are not stated in this packet.

Evidence summary
The exact-version evidence is strongest for technical validation and comparative plan quality, not patient outcomes. FDA-reviewed manufacturer tests covered dose-engine and treatment-technique changes, while an independent 59-plan comparison evaluated RayStation 12A CyberKnife plans. Additional independent product-family commissioning data support local QA design but cannot be assumed to represent 12A without version confirmation.
  • Exact product version
  • Checked 2026-09-02

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
The exact-version evidence is strongest for technical validation and comparative plan quality, not patient outcomes. FDA-reviewed manufacturer tests covered dose-engine and treatment-technique changes, while an independent 59-plan comparison evaluated RayStation 12A CyberKnife plans. Additional independent product-family commissioning data support local QA design but cannot be assumed to represent 12A without version confirmation.
  • Public source
  • Exact product version
  • Checked 2026-09-02
Reported sensitivity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

Reported specificity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

Electron dose-engine gamma failure acceptance limit

2 % of evaluated data points upper bound

  • EndpointData points failing a 2% / 2 mm gamma comparison against the prior RayStation electron Monte Carlo implementation
  • PopulationManufacturer electron dose-engine validation cases described in the K222312 summary
  • Tested versionRayStation 12A electron Monte Carlo dose engine cleared in K222312

Maximum averaged central-axis dose difference

0.8 %

  • EndpointMaximum averaged difference between measured and calculated absolute central-axis dose across tested collimators and algorithms
  • PopulationCyberKnife M6 fixed, Iris, and multileaf collimator beam-model commissioning and validation
  • Tested versionRayStation CyberKnife module; software release not reported

Mean patient-specific QA gamma pass rate

98 % of points

  • EndpointMean proportion of points meeting 3% / 1 mm gamma criteria
  • PopulationPatient-specific QA plans across commissioned CyberKnife M6 collimator and dose-algorithm models
  • Tested versionRayStation CyberKnife module; software release not reported

K222312 RayStation 12A nonclinical verification and validation

  • DesignManufacturer software verification and validation with water-tank, phantom, prior-engine, published-reference, competing-system, and independent Monte Carlo comparisons across changed treatment-planning functions
  • PopulationOcular planning, electron dose calculation, brachytherapy TG-43, automated field-in-field, Flexitron support, and other software changes; no patient cohort reported
  • Scopeexact submission
  • Tested versionRayStation 12A cleared in K222312
  • IndependenceSponsor or vendor study

K222312

FDA found the verification and validation adequate for substantial equivalence. The summary does not establish patient outcomes.

Dosimetric comparison of M6 CyberKnife plans optimized with Precision and RayStation 12A treatment planning systems

  • DesignIndependent single-center paired dosimetric comparison in which each case was planned with RayStation 12A and Precision
  • Population59 paired CyberKnife M6 plans: 39 brain-metastasis plans and 20 vertebral-metastasis plans
  • Scopeexact product version
  • Tested versionRayStation 12A CyberKnife module
  • Samplen=59
  • Sites1
  • IndependenceIndependent study

PMID 39698880

Target coverage was equivalent for brain cases and worse for vertebral cases; organ-at-risk sparing improved, conformity was lower, and optimization took longer. The authors reported no conflicts of interest.

Commissioning and validation of RayStation treatment planning system for CyberKnife M6

  • DesignIndependent single-center beam-model commissioning and phantom validation of collapsed-cone and Monte Carlo calculations for fixed, Iris, and multileaf collimators
  • PopulationCyberKnife M6 water-tank, homogeneous and heterogeneous phantom, irregular-field, off-axis, and patient-specific QA measurements
  • Scopeproduct family
  • Tested versionRayStation CyberKnife module; software release not reported
  • Sites1
  • IndependenceIndependent study

PMID 35856911

Most measured-versus-calculated differences were within plus or minus 1%, with a 3.2% maximum at 19.5 cm depth. One author held an unrelated Accuray grant.

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
FDA recall Z-1105-2026 affects RayStation 12A and its first two service packs because calculated dose might not invalidate after geometry or material changes to certain empty, bolus, fixation, or support ROIs. FDA lists the recall as open and classified. FDA recall Z-2493-2025 includes RayStation 12A and its first two service packs. DICOM objects exported through the RayGateway interface to Accuray iDMS were not guaranteed to receive unique SOP Instance and Series Instance UIDs. FDA lists the recall as open and classified. FDA recall Z-1191-2025 includes RayStation 12A and its first two service packs. It concerns inconsistent interpretation of density uncertainty in robust optimization, robust evaluation, and perturbed-dose calculations for proton and light-ion plans using an HU-to-mass-density calibration curve. FDA lists the recall as open and classified. FDA recall Z-1750-2024 affects RayStation 12A builds 13.0.0.1547, 13.1.0.144, and 13.1.1.89 because the reported source-to-surface distance could be too high. FDA lists the recall as open and classified. FDA recall Z-1482-2024 includes RayStation 12A. It addresses a use error in which elemental silicon could be selected instead of silicone gel polymer as an implant material override, with potentially greater consequence for ion-beam planning. FDA lists the recall as open and classified.
  • FDA source
  • Exact product version
  • Checked 2026-09-04

Each published event was manually matched to the exact FDA submission and affected product or version; a recall does not establish an AI-algorithm defect or current site exposure unless the event states that scope.

recall: Z-1105-2026

Open, Classified

2026-01-16

The FDA record names RayStation 12A builds 13.0.0.1547, 13.1.0.144, and 13.1.1.89. Verify installed build, correction status, and the vendor workaround.

recall: Z-2493-2025

Open, Classified

2025-09-02

The FDA record names all three 12A builds. Sites should verify installed versions and the vendor correction or re-export workaround.

recall: Z-1191-2025

Open, Classified

2025-02-19

The FDA record explicitly names the RayStation 12A builds. Applicability depends on particle planning and the installed CT calibration approach.

recall: Z-1750-2024

Open, Classified

2024-05-01

Exact 12A build match. The FDA action directs users to verify critical SSD values with the Measure Tool and follow the vendor correction.

recall: Z-1482-2024

Open, Classified

2024-04-05

RayStation 12A is explicitly included. Sites should verify material-assignment review controls and whether the affected material remains available in the installed release.

Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Pricing is recorded, but no exact-product procurement price with a stated offer scope is published in the reviewed sources.

Public pricing
No public price for the exact RayStation 12A configuration was found. A 2025 vendor announcement reports a RMB 51 million RayStation order including a service contract for a Chinese carbon-ion center; it is a bundled product-family benchmark, not a 12A list price or a transferable quote.
  • Product family
  • Checked 2026-09-02

Pricing context

These observations are not an exact-product procurement quotation. They are family, vendor, patient-charge, reimbursement, model, or unscoped records and are not comparable across dates, bundles, currencies, or units.

CNY 51000000

Price observation, scope not stated · total order including service contract · China

Observed 2025-03-04

Vendor-announced product-family order for an advanced carbon-ion, proton, and photon center. It is not a RayStation 12A list price, excludes unknown allocation across licenses and services, and should not be transferred to another institution or configuration.

Reimbursement

Reimbursement
CMS describes payment for professional and technical radiation therapy services, not a separate payment assigned to named treatment-planning software. The reviewed source does not support treating RayStation as independently reimbursed; local payer, contract, and service-line analysis remains necessary.
  • Service-level, not product-specific
  • Checked 2026-09-02

No product-specific code

No separate named-product payment identified in the reviewed CMS Radiation Oncology Model page

Medicare · United States

This is payment context for radiation therapy services, not a comprehensive coding or coverage determination.

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: CT, PET, and MR images transferred through DICOM; patient geometry and structures; treatment-machine and beam-model data; prescriptions, clinical goals, optimization objectives, and other user-entered planning parameters.

    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 K222312: RayStation 12A

  2. Routing

    Source context, not route validation: RayStation 12A imports and exports DICOM and DICOM RT images, structures, plans, and dose objects and can exchange data with PACS, treatment delivery, and oncology workflow systems. The reviewed architecture uses patient, machine, and clinic Microsoft SQL databases.

    Scope: Exact product version. Validate every DICOM service, transfer profile, object mapping, treatment-machine interface, database dependency, and failure-recovery path in the local environment.

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

    Field checked 2026-09-02 · FDA K222312: RayStation 12A · RayStation 12A System Environment Guidelines

  3. AI processing

    Source context, not route validation: RayStation 12A supports Windows workstations connected to Microsoft SQL Server and DICOM systems, with documented desktop, centralized Citrix, shared application-server, and restricted virtual-machine patterns. The FDA summary permits standard desktop or remote virtualized use when remote behavior is verified equivalent to local use and states that RayStation is not intended for long-term image or patient-data storage.

    Scope: Exact product version.

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

    Field checked 2026-09-02 · FDA K222312: RayStation 12A · RayStation 12A System Environment Guidelines

  4. Returned objects

    Source context, not route validation: Proposed and approved treatment plans, dose distributions, structures, images, reports, machine and setup parameters, and DICOM RT exports for authorized review and downstream treatment workflows.

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

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

    Field checked 2026-09-19 · FDA K222312: RayStation 12A

  5. Viewer/worklist/report

    Unresolved route: Proposed and approved treatment plans, dose distributions, structures, images, reports, machine and setup parameters, and DICOM RT exports for authorized review and downstream treatment workflows.

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

    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 K222312: RayStation 12A

  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
RayStation 12A supports Windows workstations connected to Microsoft SQL Server and DICOM systems, with documented desktop, centralized Citrix, shared application-server, and restricted virtual-machine patterns. The FDA summary permits standard desktop or remote virtualized use when remote behavior is verified equivalent to local use and states that RayStation is not intended for long-term image or patient-data storage.
  • Exact product version
  • Checked 2026-09-02
Integration
RayStation 12A imports and exports DICOM and DICOM RT images, structures, plans, and dose objects and can exchange data with PACS, treatment delivery, and oncology workflow systems. The reviewed architecture uses patient, machine, and clinic Microsoft SQL databases.
  • Exact product version
  • Checked 2026-09-02

Validate every DICOM service, transfer profile, object mapping, treatment-machine interface, database dependency, and failure-recovery path in the local environment.

Security
The FDA summary describes licensing controls, checksums, and administrator-limited database access. RaySearch's 12A environment guide calls for role-based Active Directory groups, least privilege, encrypted SQL and backend communications, VPN or network segmentation for legacy DICOM, disk and database encryption where appropriate, encrypted backups, malware protection, account lockout, and controlled remote access.
  • Exact product version
  • Checked 2026-09-02

The environment guide warns that secure operation on Windows Server 2016 cannot be guaranteed after the end of NVIDIA R470 security support. Confirm the exact supported operating-system, GPU-driver, database, and patch matrix for the installed build.

Training
The organization is responsible for ensuring that only authorized, appropriately trained planners and other qualified users operate RayStation 12A. Training should cover the configured clinical functions, plan review, machine and beam-model commissioning, automated segmentation review, dose-check independence, export verification, and applicable warnings.
  • Exact product version
  • Checked 2026-09-02
Monitoring
RayStation 12A implementation guidance requires installation-specific acceptance and commissioning, independent dose verification, DICOM export checks, controlled software and hardware changes, database backup and maintenance, and monitoring of disk capacity, services, and processor resources. Automated-segmentation and machine-learning outputs remain subject to qualified-user review and local model commissioning.
  • Exact product version
  • Checked 2026-09-02

Local governance should also include incident review, backup-restoration tests, interface reconciliation, performance baselines, access review, vulnerability response, change control, and FDA recall surveillance.

Application and database architecture

The FDA summary describes RayStation, RayPhysics, and RayTreat applications and separate Microsoft SQL patient, machine, and clinic databases.

exact submission · checked 2026-09-02

Assign technical ownership for application servers, databases, storage, backups, treatment interfaces, and clinical configuration.

Supported deployment patterns

The 12A environment guide documents local desktop, centralized Citrix, shared application-server, and restricted virtual-machine designs using Windows clients, Microsoft SQL Server, and supported NVIDIA GPUs.

exact product version · checked 2026-09-02

Size CPU, memory, GPU, storage, database, remote-display, and concurrency for the purchased modules and workload; confirm every component against the installed 12A build.

DICOM and treatment workflow

RayStation 12A imports CT, PET, and MR data and supports DICOM and DICOM RT exchange of images, structures, plans, and dose with connected clinical systems.

exact submission · checked 2026-09-02

The IFU requires verification that DICOM export completed successfully. Include object-level reconciliation and treatment-machine end-to-end tests in acceptance.

Security baseline

Role-based Active Directory groups separate administration, beam commissioning, plan approval, and machine-learning administration; the guide also describes least privilege, encrypted communications and storage, protected backups, malware controls, account lockout, VPN or segmentation for legacy DICOM, and controlled remote access.

exact product version · checked 2026-09-02

Translate vendor guidance into a site security design, access matrix, patch plan, vulnerability process, backup architecture, logging plan, and downtime procedure.

Acceptance, commissioning, and change control

The IFU requires installation-specific acceptance after relevant hardware or software changes, local commissioning of machine-learning models, qualified-user review of automated segmentations, and genuinely independent dose verification.

exact product version · checked 2026-09-02

Create signed acceptance protocols for each modality, machine, energy, technique, dose engine, model, script, interface, and report used clinically.

Operations and maintenance

The environment guide calls for database backup and reindexing and monitoring of disk capacity, services, and processor utilization.

exact product version · checked 2026-09-02

Define alert thresholds, owners, escalation, restoration tests, maintenance windows, capacity forecasts, and evidence retention.

Current product-family context

RaySearch continues to market RayStation as a configurable treatment-planning platform spanning multiple treatment techniques and machine ecosystems and maintains versioned safety and performance documentation.

product family · checked 2026-09-02

Map all current commercial claims, support terms, upgrade paths, and optional modules back to the exact licensed 12A configuration.

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
K222312
  • 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
2023-03-29
  • 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.

Human reviewedStatus
2026-09-04Last searched
24Fields reviewed
15Source classes checked
4Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads

The refreshed discovery snapshot contains 4 PubMed and 0 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 0 ClinicalTrials.gov candidate records; its dated, count-matched human screening remains current. Unlinked candidates remain quarantined. 6 FDA recall candidates were manually reviewed: 5 published and 1 rejected as a neighboring or otherwise inapplicable version. Native FDA recall identifiers produced 6 postmarket candidate records; 6 have been reviewed (5 published, 1 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 instructions for use, vendor technical documentation, vendor product page, peer reviewed publication, vendor pricing observation, 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.

  • 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

18 sources - 3 history items

Source ledger

  1. FDA K222312: RayStation 12A

    U.S. Food and Drug Administration - Published 2023-03-29 - Accessed 2026-09-19

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

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. FDA recall Z-1105-2026: Brand Name: RayStation Product Name: RayStation/RayPlan Model/Catalog Number: 13.0.0.1547, 13.1.0.144, 13.1.1.89 Software Version: RayStation 12A, RayStation 12A SP1, RayStation 12A SP2 Product Description: Radiation Therapy Treatment Planning System Component: No

    U.S. Food and Drug Administration - Published 2026-01-16 - Accessed 2026-09-04

    Scope: postmarketSafety, affectedProduct, recallStatus, correctiveAction

  4. FDA recall Z-2493-2025: RayStation with the following product descriptions: 1. RayStation 12A, Software Version: 13.0.0.1547. 2. RayStation 12A Service Pack 1, Software Version: 13.1.0.144. 3. RayStation 12A Service Pack 2, Software Version: 13.1.1.89. Product Description: Radiation Therapy Treatment Planning System.

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

    Scope: postmarketSafety, affectedProduct, recallStatus, correctiveAction

  5. FDA recall Z-1191-2025: Brand Name: RayStation- Intended as a Radiation Therapy Treatment Planning System Model/Catalog Number: 13.0.0.1547, 13.1.0.144, 13.1.1.89 and 14.0.0.3338 Software Version: RayStation 12A, 12A Service Pack 1 and 2 and 2023B

    U.S. Food and Drug Administration - Published 2025-02-19 - Accessed 2026-09-04

    Scope: postmarketSafety, affectedProduct, recallStatus, correctiveAction

  6. FDA recall Z-1750-2024: RayStation 13.0.0.1547, 13.1.0.144 & 13.1.1.89. Radiation Therapy Treatment Planning System.

    U.S. Food and Drug Administration - Published 2024-05-01 - Accessed 2026-09-04

    Scope: postmarketSafety, affectedProduct, recallStatus, correctiveAction

  7. FDA recall Z-1482-2024: RayStation Software Version Numbers version numbers 8B, 9A, 9B, 10A, 10B, 11A, 11B, 12A, 12B, 2023B, 2024A including some service packs.

    U.S. Food and Drug Administration - Published 2024-04-05 - Accessed 2026-09-04

    Scope: postmarketSafety, affectedProduct, recallStatus, correctiveAction

  8. PubMed biomedical literature index

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

    Scope: evidenceDiscovery

  9. ClinicalTrials.gov study registry

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

    Scope: evidenceDiscovery, studyStatus

  10. openFDA Device Recall API

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

    Scope: recallDiscovery, nativeSubmissionMatching

  11. RayStation treatment planning system product page

    RaySearch Laboratories - Accessed 2026-09-02

    Scope: productFamily, implementationCapabilities, currentCommercialContext

  12. RayStation safety and performance information

    RaySearch Laboratories - Accessed 2026-09-02

    Scope: instructionsForUse, releaseNotes, systemEnvironmentGuidelines

  13. RayStation 12A System Environment Guidelines

    RaySearch Laboratories - Published 2022-06-23 - Accessed 2026-09-02

    Scope: deployment, integration, security, monitoring, implementationCapabilities

  14. RayStation 12A Instructions for Use

    RaySearch Laboratories - Published 2023-03-28 - Accessed 2026-09-02

    Scope: limitations, training, monitoring, implementationCapabilities

  15. Commissioning and validation of RayStation treatment planning system for CyberKnife M6

    Journal of Applied Clinical Medical Physics - Published 2022-07-20 - Accessed 2026-09-02

    Scope: evidenceSummary, evidenceStudy, evidenceMetrics, implementationCapabilities

  16. Dosimetric comparison of M6 CyberKnife plans optimized with Precision and RayStation 12A treatment planning systems

    Journal of Applied Clinical Medical Physics - Published 2024-12-19 - Accessed 2026-09-02

    Scope: evidenceSummary, evidenceStudy, evidenceMetrics

  17. Heyou Hospital selects RayStation for its carbon-ion center

    RaySearch Laboratories - Published 2025-03-04 - Accessed 2026-09-02

    Scope: pricing, economicsObservation, productFamily

  18. Radiation Oncology Model

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

    Scope: reimbursement, radiationTherapyPaymentContext

Research history

  1. K222312 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    human reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K232928

DeepContour (V1.0)

Wisdom Technologies., Inc.

Authorized purpose: DeepContour uses deep-learning CT processing to generate editable organ contours and RTSTRUCT objects for selected adult radiation-treatment planning workflows, with quantitative statistics, registration, and three-dimensional visualization; it does not contour tumors.

Modality
Radiotherapy Planning Imaging
Anatomy
Multi-region
Decision
2024-05-07
FDA-cleared K252188

EMLA (Elekta Evo); EMLA (VersaHD); EMLA (Elekta Harmony Pro); EMLA (Elekta Infintiy); EMLA (Elekta Harmony); EMLA (Elekta Synergy)

Elekta Solutions AB

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.

Modality
Radiotherapy Planning Imaging
Anatomy
Multi-region
Decision
2026-01-15
FDA-cleared K240398

RayStation 2023B, RayPlan 2023B, RayStation 2024A, RayPlan 2024A, RayStation 2024A SP3, RayPlan 2024A SP3

RaySearch Laboratories AB (PUBL)

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.

Modality
Radiotherapy Planning Imaging
Anatomy
Multi-region
Decision
2025-04-04
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

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