RaySearch Laboratories AB (publ)

Beam set delivery note issues in which there is potential data loss if the beam set delivery note is modified simultaneously and/or if a note is updated during a treatment session, the user is not notified of the change.

Potential for the invalidation for calculated radiation dose does not work as intended for certain Regions of Interest (ROIs). This issue occurs for some ROI(s) which have no contours and either have a material override defined, or are of type Bolus, Fixation, or Support. In thes…

DICOM SOP Instance UID and Series Instance UID from RayGateway, i.e. the interface to Accuray's iDMS, are not guaranteed to be unique.

Inconsistency in the use of Density uncertainty in the RayStation functions Robust optimization, Robust evaluation and Compute perturbed dose for proton and light ion treatment plans when a HU-to-mass density CT calibration curve used in RayStation version 4.5 to 2024B including …

Potential for reported SSD to be too high.

A use error that has occurred with RayStation/RayPlan, where material override using Silicon, Si, was incorrectly selected for a silicone gel polymer implant.

An issue was found in RayCare 5B, 6A, including service packs, where values will not be visible for documents in a read-only state when opened outside the Documents workspace when using document fields configured with single- or multi-selectable values.

An issue was found in Software RayCare 5A, 5B, 6A, including service packs, where an allergy warning against medication substance (drug ingredient) will not be displayed as expected under certain circumstances

It is possible to set a non-zero collimator angle in the Virtual Simulation module. The angle will be correct in the user interface but if the plan is DICOM exported by using the VSIM Export button, the angle will not be correct in the exported RT plan. In the exported RT plan,…

This notice concerns two issues found related to the display of Linear Energy Transfer (LET) in RayStation 11B including some service packs. First, when using a dose threshold for an evaluation dose, LET display might be misleading. Second, a displayed beam-specific LET distri…

An issue with propagation of treatment course information from RayStation with RayTreat to RayCare has been identified. During some workflows, information may not be propagated to RayCare.

If a new primary image set is selected while the cine loop is running, the primary image set will be displayed as both primary and secondary image set in all side-by-side views. This will also be true for any new patient or case opened while the cine loop is running

An issue where the combined density in a dose grid voxel partially covered by the External ROI and also partially covered by an ROI of type Bolus, Support or Fixation may be unexpected.The density in the voxel can be both under- and overestimated

If the dynamic jaw mode is used and an optimization is continued after changing the dose grid or modifying the target ROI, the positions of the jaws may change unexpectedly for some control points. User must be aware to avoid unnecessary jaw openings during treatment planning

Initial delivery positions will be set incorrectly when having setup beam(s) at the localization point.

Evaluation of a clinical goal for the voxelwise worst dose distributions may be misleading after editing the clinical goal. It also describes an issue with contouring when the spacing between slices is d 1 mm, present in RayStation/RayPlan versions from 6 up to 10A.

When using more than one plan in a treatment course, the Total dose display in Dose tracking may be incorrect. There may be a mismatch between the fractions that appear as selected in the Treatment course list in Dose tracking and the fractions that are included in the dose sum…

Flags edited in RayCare after a patient has been checked in may not always be updated in RayTreat.

Patient related messages created in RayCare 3B, RayCare 4A will be lost when upgrading from RayCare 2 to RayCare 3B or later

For some LINAC types, merging clinical beams with beams of approximate dose may lead to the approximate dose erroneously labeled as clinical dose. Merge beams can be used manually, in scripting, or as part of the Automated breast planning feature. In some cases, when merging two…

Two issues were found with the treatment plan report: 1) There may be incorrect information for the percent of a region of interest with a clinical goal that is outside the dose grid; and 2) For RayStation and RayPlan 9B and 10A, 6D couch angles may be incorrect.

If a region of interest (ROI) or point of interest (POI) that is referenced from an imported plan is missing in the imported RT Structure Set, the reference may become linked to the wrong ROI or POI.

When performing offline image review in RayCare 2C, RayCare 3A and RayCare 3B an offline image review task will guide you to the image viewer with the treatment image related to the fraction and the planning image selected. When starting the task, an error message might be displa…

It is not obvious that the manual import of a treatment record into RayCare PACS does not automatically import the same data into RayTreat. In addition, there is an issue found with the display of planned and recorded Gantry Angle in the delivered beam list in RayTreat.

Software error was identified in the Pencil Beam Scanning (PBS) and Line Scanning (LS) dose calculation algorithms that could result in a local underestimation of expected dose.

Due to physical limitations of the treatment machine, the maximum field opening for Siemens Virtual Wedge fields recommended by the LINAC vendor will be more restricted in the wedged direction than the maximum field opening without a wedge. Delivering a larger field opening with …

There is a potential for erroneous propagation of the current tabletop positions when applying pitch or roll correction. Even though pitch and roll correction is never propagated, non-zero pitch or roll causes the lateral, longitudinal and vertical values propagated to be incorre…

Three issues found: i) The Map ROI options in the ROI list in the Structure Definition module may generate unintended ROI geometries ii) Elekta guard leaf behavior. There is an interoperability issue with Elekta regarding setting of guard leaves. iii)SSD, when intended as source…

Editing a static arc beam may unexpectedly set the MU of the beam to its initial default value of 200 MU. If the bug is triggered, the dose is invalidated and needs to be recalculated before the plan can be approved or exported.

Isocenter shifts when using dose tracking in RayStation 3.5, RayStation 4.0, RayStation 4.5, RayStation 4.7, RayStation 5, RayStation 6, RayStation 7 and RayStation 8A. In these versions, isocenter shifts in dose tracking are incorrectly interpreted according to the DICOM pati…

Robust optimization for plans using beam set + background dose is not supported in RayStation 4.5, RayStation 4.7, RayStation 5, RayStation 6 and RayStation 7.

If the beam model has a highly asymmetric primary source, it is not correctly taken into account in the calculation of DMLC fields when the collimator is rotated. This could lead to potentially significant overdosage at delivery. The user must be aware of the issue to avoid inco…

The firm has learned that some RayStation/RayPlan users have commissioned machines with erroneous Beam profile correction parameters. These parameters affect the dose calculated in corners of large or off-axis fields. This effect cannot be seen in the Beam Commissioning module a…

The dose calculation accuracy may in some situations be less than expected. The user must be aware in order to avoid incorrect dose calculations during treatment planning.

Software issue with Center Beam in Field functionality. Issue can result in incorrect treatment volume delivered to patient.

When calculating electron Monte Carlo dose with a very large number of histories, the dose calculation may be wrong

For the proton QA preparation module in RayStation 6 (including SP1 and SP2), if the snout position or gap is modified in the QA module, the dose in the QA module may be computed for a different setup than what is used for QA measurements. This could result in an incorrect dosage…

An error in NVIDIA GPU (Graphics Processing Unit) card drivers can occur for certain software programs. In a non-standard Citrix environment where the GPU settings are configured with a virtual Citrix graphics board (graphics card) an erroneous calculation may be allowed.

Software anomaly; an issue was found with the proton Pencil Beam Scanning (PBS) dose calculation in RayStation 4.0, 4.5, 4.7 and 5.0. For treatment plans with a combination of range shifter, large air gap and beams that enter the patient surface at an oblique angle, the dose cal…

An error may occur with the display of dose computed on images other than the planning CT (auxiliary CT) when using multiple patient cases in RayStation 5. If a CT image set with the same Frame of Reference as the displayed auxiliary CT set exists in another case, the dose displa…

RaySearch became aware of the problem as it was discovered in cooperation with a customer experimenting with the dose calculation on a phantom. The correction concerns two issues found with the dose calculation when using a region of interest (ROI) of type Fixation or Support wit…

An issue was found with the evaluation of biological clinical goals in RayStation 3.0, RayStation 3.5, RayStation 4.0, RayStation 4.5, RayStation 4.7 and RayStation 5. Biological clinical goals for an adapted plan based on another planning CT than the original planning CT will sh…

For a treatment plan consisting of multiple beam sets, the table for ROI plan dose statistics in the report may show the statistics for a beam set dose. The error can only be triggered when using a report template where statistics for a beam set dose is included as the last dose…

A software issue with editing tools that use the left mouse button held down, for drawing in and interacting with the patient views and beams eye views. The views can become unsynchronized with the stored data if simultaneously right clicking, pressing Ctrl-S or Ctrl-Z while the …

An error caused by a floating point precision problem tends to cause a problem with the display of isodose lines for dose and dose difference and color tables for dose, dose difference and PET images

Issue with the algorithm for ROI contraction in RayStation 4.7 when non-uniform contraction distances are used. The ROI contraction tool uses six distances as input: right/left, inferior/superior and posterior/anterior. These contraction distances are, in error, pairwise reversed…

RaySearch Laboratories AB became aware of an issue with the dose calculation for some imported VMAT plans where controls points are defined with wide gantry angle spacing.

An issue with photon dose calculation for DMLC (Dynamic MLC) plans for machines where the MLC is positioned above the jaws, e.g. some Elekta linacs. The magnitude of the error depends on the beam model output factor corrections and on the individual DMLC plan characteristics.

This notice concerns a problem with the computation of ROI voxel volumes for cases where the CT has variable slice spacing. The dose grid volumetric representation of an ROI can be wrong. This affects all dose-volume properties for such ROIs, including DVH, dose statistics, clini…

RaySearch Laboratories has recalled "RaySearch Ray Station 2.0, 2.5, 3.0, 3.5 and 4.0" software due to dose miscalculations for bolus/external/fixation support structures on CT-image.

Potential for dose errors due to software program errors.

RaySearch Laboratories has recalled RaySearch Ray Station 4.0 software due to clinical dose calculation errors during radiation therapy.

Ray Search Laboratories found an issue with the dose calculation for Elekta motorized wedges in Ray Station 3.0, 3.5 and 4.0. The error presents when a wedge is used for a beam and the wedge angle differs from 60 degrees.

Under some circumstances, imported CT, MR and PET images are offset from their true positions by one pixel in one or two directions. Users must be aware of this information to avoid incorrect dose calculations during treatment planning.

The firm decided to recall when an issue was found with the dose calculation in RayStation 2.5, Raystation 2.5.1. The problem has not caused any patient mistreatment or other incidents. However, the user must be aware of this information to avoid incorrect dose calculations durin…

This notice concerns behavior of the SharePlan that may be unexpected and not clearly described in the user manual. This behavior has not caused patient mistreatment or other incidents. However, the described user actions must be adhered to for best agreement between treatment pl…

This field notice concerns two behaviors of the SharePlan (Multiple Fraction Groups and Depth Offset) that may be unexpected and are not clearly described in the user manual. None of these behaviors have caused patient mistreatment or other incidents. However, the described user …