RayStation 8.1, marketed as RayStation 8B, is configurable radiation therapy treatment-planning and analysis software. It imports patient images, supports contouring, image fusion, dose calculation, optimization and plan evaluation, and exports approved treatment plans with dose, structure, and image data for treatment.
Clinical role
Treatment-planning workstation used after image acquisition to create and review patient geometry, optimize beams, calculate dose, inspect two- and three-dimensional dose displays and dose-volume histograms, approve a plan, and export approved treatment objects.
Images and patients
Radiotherapy Planning Imaging · Multi-region
Key limitation
A proposed plan must be reviewed and approved by authorized, clinically qualified users before treatment. The clearance establishes substantial equivalence and manufacturer verification and validation, not independent proof of patient outcomes or suitability for a site's machines, protocols, interfaces, and commissioned beam models.
Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial overview.
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
Imaging and anatomyRadiotherapy Planning Imaging · Multi-region
Workflow roleTreatment-planning workstation used after image acquisition to create and review patient geometry, optimize beams, calculate dose, inspect two- and three-dimensional dose displays and dose-volume histograms, approve a plan, and export approved treatment objects.
Required inputPatient CT data and, where used, registered PET or MR images; user-defined regions of interest, treatment-machine data, prescription and optimization objectives, and other planning parameters.
Output and human actionReviewed treatment plans, calculated dose distributions, structures, images, setup parameters, two- and three-dimensional plan displays, and dose-volume histograms; approved DICOM treatment objects can be exported for downstream use.
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 8.1, marketed as RayStation 8B, is configurable radiation therapy treatment-planning and analysis software. It imports patient images, supports contouring, image fusion, dose calculation, optimization and plan evaluation, and exports approved treatment plans with dose, structure, and image data for treatment.
Treatment-planning workstation used after image acquisition to create and review patient geometry, optimize beams, calculate dose, inspect two- and three-dimensional dose displays and dose-volume histograms, approve a plan, and export approved treatment objects.
Patient CT data and, where used, registered PET or MR images; user-defined regions of interest, treatment-machine data, prescription and optimization objectives, and other planning parameters.
Reviewed treatment plans, calculated dose distributions, structures, images, setup parameters, two- and three-dimensional plan displays, and dose-volume histograms; approved DICOM treatment objects can be exported for downstream use.
A proposed plan must be reviewed and approved by authorized, clinically qualified users before treatment. The clearance establishes substantial equivalence and manufacturer verification and validation, not independent proof of patient outcomes or suitability for a site's machines, protocols, interfaces, and commissioned beam models.
Manufacturer nonclinical verification and validation supported the 510(k). An independent hospital study found generally close agreement between measured data and RayStation's VMC++ electron Monte Carlo calculations, but did not report the software version and did not assess clinical 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
Manufacturer nonclinical verification and validation supported the 510(k). An independent hospital study found generally close agreement between measured data and RayStation's VMC++ electron Monte Carlo calculations, but did not report the software version and did not assess clinical outcomes.
Evaluation of the RayStation electron Monte Carlo dose calculation algorithm
DesignIndependent single-center dosimetric validation against measured percentage-depth-dose, profile, heterogeneity, oblique-incidence, and output-factor data
PopulationVarian TrueBeam electron beams from 6 to 18 MeV in water-tank and clinically relevant phantom geometries
Scopeproduct family
Tested versionRayStation VMC++ electron Monte Carlo; software release not reported
Samplen=170
Sites1
IndependenceIndependent study
PMID 31629601
The publication reports no conflict of interest. Product-family evidence is not proof of equivalence to the exact 8B build, local beam model, machine, or protocol.
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-2488-2025 includes RayStation 8B 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-1186-2025 includes RayStation 8B 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-1743-2024 affects RayStation 8B builds 8.1.0.47, 8.1.1.8, and 8.1.2.5 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 8B. 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 recall Z-2426-2020 includes RayStation 8B and concerns treatment-record handling with RayCare PACS and RayTreat, including manual-import propagation and display of planned versus delivered gantry angles. FDA lists the recall as open and classified. FDA recall Z-2346-2020 affected RayStation 8B because a pencil-beam or line-scanning dose-calculation error could locally underestimate expected dose. FDA lists the recall as terminated. FDA recall Z-2347-2020 affected RayStation 8B SP1 because a pencil-beam or line-scanning dose-calculation error could locally underestimate expected dose. FDA lists the recall as terminated. FDA recall Z-2348-2020 affected RayStation 8B SP2 because a pencil-beam or line-scanning dose-calculation error could locally underestimate expected dose. FDA lists the recall as terminated. FDA recall Z-1598-2020 includes RayStation 8.1 and concerns Siemens Virtual Wedge fields whose opening could exceed the treatment-machine vendor recommendation, potentially producing a high-dose plateau. FDA lists the recall as open and classified. FDA recall Z-1464-2020 affected RayStation or RayPlan 8B build 8.1.0.47 because tabletop positions could propagate incorrectly when pitch or roll correction was applied. FDA lists the recall as terminated. FDA recall Z-1465-2020 affected RayStation or RayPlan 8B SP1 build 8.1.1.8 because tabletop positions could propagate incorrectly when pitch or roll correction was applied. FDA lists the recall as terminated. FDA recall Z-1466-2020 affected RayStation or RayPlan 8B SP2 build 8.1.2.5 because tabletop positions could propagate incorrectly when pitch or roll correction was applied. FDA lists the recall as terminated. FDA recall Z-0866-2020 includes RayStation 8.1 and addresses three issues involving ROI mapping geometry, Elekta guard-leaf interoperability, and source-to-surface-distance handling. FDA lists the recall as terminated. FDA recall Z-0736-2020 includes RayStation 8.1 because editing a static arc beam could reset monitor units to the default 200 MU, requiring dose recalculation before approval or export. FDA lists the recall as terminated.
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.
The FDA record names RayStation 8B versions 8.1.0.47, 8.1.1.8, and 8.1.2.5. Sites should verify installed versions and the vendor correction or re-export workaround.
RayStation 8B is explicitly included. Sites should verify material-assignment review controls and whether the affected material remains available in the installed release.
Exact RayStation 8B match. The FDA action described Monte Carlo or geometry-related workarounds; verify correction status and local particle-planning exposure.
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 RayStation 8B was found. A 2025 vendor announcement reports a RMB 51 million RayStation order including a service contract for a Chinese carbon-ion center; this is a product-family, bundled institutional benchmark and is not an 8B list price or a transferable quote.
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 a carbon-ion center. It is not a RayStation 8B list price, excludes unknown allocation across licenses and services, and should not be transferred to another institution or configuration.
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.
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: Patient CT data and, where used, registered PET or MR images; user-defined regions of interest, treatment-machine data, prescription and optimization objectives, and other planning parameters.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA summary describes DICOM import of CT images, multimodality registration with PET and MR, interfacing with a treatment console, and DICOM export of approved plans, dose, structures, and images to a DICOM server.
Scope: Exact FDA submission. Confirm exact supported DICOM services, treatment-machine interfaces, transfer checks, interface ownership, and installed service-pack compatibility during local validation.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: Software treatment-planning system deployed in the radiation oncology technical environment and connected to imaging, DICOM storage, and treatment-delivery workflows configured by the institution.
Scope: Exact FDA submission. The reviewed FDA summary does not specify a transferable hardware, server, database, virtualization, or high-availability architecture for every 8B installation.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Reviewed treatment plans, calculated dose distributions, structures, images, setup parameters, two- and three-dimensional plan displays, and dose-volume histograms; approved DICOM treatment objects can be exported for downstream use.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Reviewed treatment plans, calculated dose distributions, structures, images, setup parameters, two- and three-dimensional plan displays, and dose-volume histograms; approved DICOM treatment objects can be exported for downstream use.
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.
Software treatment-planning system deployed in the radiation oncology technical environment and connected to imaging, DICOM storage, and treatment-delivery workflows configured by the institution.
Exact FDA submission
Checked 2026-09-02
The reviewed FDA summary does not specify a transferable hardware, server, database, virtualization, or high-availability architecture for every 8B installation.
The FDA summary describes DICOM import of CT images, multimodality registration with PET and MR, interfacing with a treatment console, and DICOM export of approved plans, dose, structures, and images to a DICOM server.
Exact FDA submission
Checked 2026-09-02
Confirm exact supported DICOM services, treatment-machine interfaces, transfer checks, interface ownership, and installed service-pack compatibility during local validation.
The FDA summary describes contouring, image fusion, collapsed-cone dose calculation, four-dimensional compatibility, optimization, dose tracking and adaptation, deformable registration, machine-learning planning, and machine-learning segmentation.
exact submission · checked 2026-09-02
License, commissioning, validation, user privileges, and clinical scope should be mapped function by function; inclusion in the clearance summary does not mean every site has every option enabled.
RaySearch continues to market RayStation as a configurable treatment-planning platform spanning multiple treatment techniques and machine ecosystems.
product family · checked 2026-09-02
Current product-family features, hardware requirements, cybersecurity controls, and commercial terms must not be assumed to apply to an installed 8B release.
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
22Fields reviewed
10Source classes checked
20Awaiting review PubMed leads
5Awaiting review trial leads
0Unreviewed FDA recall leads
Recovered from the prior exact-submission extraction and normalized under the current provenance rules. The exact FDA summary, current vendor product context, peer-reviewed product-family dosimetry evidence, public pricing observation, CMS payment context, and every exact-identifier FDA recall candidate were manually reviewed. Security and operational-monitoring details remain explicitly unresolved for the exact 8B release rather than being inferred from later documentation. Automated exact-name discovery found 20 PubMed and 5 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. 32 FDA recall candidates were manually reviewed: 14 published and 18 rejected as a neighboring or otherwise inapplicable version. Native FDA recall identifiers produced 32 postmarket candidate records; 32 have been reviewed (14 published, 18 rejected) and 0 remain unreviewed.
Candidate leads remain unpublished until a human confirms the exact product and tested version.
Source classes: fda ai list, fda decision summary, peer reviewed publication, vendor product page, vendor pricing observation, reimbursement policy, fda device recall, 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
Security: Not publicly available - checked 2026-09-02 - Exact product version
No exact RayStation 8B cybersecurity architecture or supported-platform security guide was established from the reviewed public sources. Obtain the version-specific security, patching, identity, encryption, audit, remote-access, backup, and vulnerability-management documentation.
Installation timeline: Not yet reviewed
Monitoring: Not publicly available - checked 2026-09-02 - Exact product version
The reviewed public sources do not define an exact 8B operational monitoring program. Require local dose-calculation commissioning, end-to-end testing, DICOM transfer checks, machine and beam-model change control, backup testing, service-pack regression testing, incident review, and recall surveillance.
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.
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.
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.