The .decimal Astroid Planning App is used for treatment planning of proton radiation therapy treatments. The Astroid Planning App is an interactive end user application that leverages the existing .decimal Dosimetry App functions for device creation, dose calculation, and optimization to facilitate efficient development of proton radiation treatment plans.

The purpose of this document is to provide guidance on the setup, access, and usage of the Astroid Planning App.

Proper use of this software is critical to safe and effective treatment of patients using plans generated by this application. Users are expected to read and understand this complete User Guide including the Instructions for Use, which outlines the general usage principles and limitations of the Astroid Planning App. Users must read and understand these instructions before operating the system for clinical use. Refer to each section below for complete details:

• Instructions for Use
  • Overview and Indications for Use
  • User Responsibilities
  • Warning
  • Intended Use
  • User Profile
  • Product Features
  • Data Model

It is the responsibility of those utilizing this application to ensure all that all usages of this product relating to patient treatments are performed by trained and qualified personnel only and that such personnel is aware that the quality of any generated treatment plans is highly dependent on the quality and correctness of the input data; therefore if any questions or uncertainties exist regarding the quality, units, or identification of input data arise, they must be investigated and resolved before the data are used.

Once Astroid has been purchased, Astroid staff will assist with beam model creation, software installation, and user training. Users will be generally be trained at two separate levels, system administrators and end users. System administrators will be setup with appropriate access and tools for managing software including both the local and cloud resources. End users will be primarily trained on the details of generating high-quality treatment plans using the local client portion of the application suite. The beam modeling and equipment setup processes are explained more fully in the Dosimetry App Commissioning Guide.

The Astroid Planning App includes both a local User Client and a cloud-based calculation provider, therefore, there are specific requirements on computers in which the local client application can be installed. Please see the System Requirements page for details.

The astroid Planning App provides a RKS record for specifying site level configurations and defaults. The RKS entry exists at the root level of the realm for which the app is installed. The record holds a site_info, whose definition can be viewed at the astroid Manifest Documentation site. An empty sample json version of the site_info is provided.

To update the site_info RKS record, perform the following steps. Note: you must have Thinknode “iam:buckets:unlockEntries” policy permissions in order to unlock this RKS record to update it.

1. Using the Thinknode Client or manual RKS GET routes view the RKS records for the realm in which you wish to update the site_info
2. Find, or create if it's missing, the RKS record named “site_info” at the root level of the RKS entries
3. Unlock the site_info RKS record using the Thinknode PUT /rks/:id/unlock route
4. Edit the site_info by either:
   1. Editing in place the site_info data using the Thinknode Client or
   2. Post new site_info data as an immutable object and update the Reference ID for the RKS entry
5. Lock the site_info RKS record using the Thinknode PUT /rks/:id/lock route to prevent unrestricted changes.

The site_info for the astroid Planning App references the astroid Dosimetry App machine model. This model must be posted and referenced from within the site_info rks record.

Astroid utilizes keyboard shortcuts to help streamline many commonly used functions and display controls. A complete listing of these shortcuts along with a full description of the mouse controls is located at the Keyboard and Mouse Controls page.

The following task descriptions are thorough guides providing complete information about each task within the Astroid Planning Application.

• Launching the Astroid Planning App
• Uploading DICOM Patient Files
• Importing Patient Data
• Courses, Intents, and Directives
• Patient Models
• Creating a Plan
  • Structures
  • Dose Grid
  • Proton Beams
    • Defining an Aperture
    • Defining a Range Compensator
  • Astroid Optimization (PBS)
    • PBS Fraction Groups
    • Defining Constraints
    • Feasibility & Constraints
    • Setting Objectives
    • Running the Optimizer
    • Dose Normalization
    • Navigating the Solutions
  • Beam Delivery (SOBP)
    • SOBP Fraction Groups
  • Using the Plan History
  • Publishing a Plan
• Plan Templates
• Exporting a Plan

• More coming soon …

The following walkthroughs will take you through the process of creating complete treatment plans in the Astroid Planning App. They provide detailed steps so that any user can begin using the software. Each guide covers a specific type of treatment plan, and although some walkthroughs share certain steps, each has been written as a self-contained unit so that you may begin with whatever guide is the most useful.

• Prostate Plan Walkthrough

When using the Astroid Planning App, as with any complex program, there is the potential for misuse. The various Astroid Apps comprise a suite of radiotherapy treatment planning tools that are intended to be used by experienced and knowledgeable professionals working in the field of radiation therapy.

Below are listed the known application limitations, defects, or inconsistencies.

1. Astroid uses DICOM patient space coordinates for all slice and 3D views and IEC 61217 coordinate systems for BEV (other options, such as machine based coordinate systems are NOT available at this time)
2. If a user's computer is abruptly shut down (e.g. computer crash or power failure) while the Astroid Planning App has a plan open, there is a potential for the user's local data cache index file to become corrupted. If this happens, generally the Planning App will automatically close (crash) whenever the user tries to open the plan that was active at the time of crash. In order to fix this, the user must close the Planning App and delete the entire cache folder. The default directory location for this folder should be C:\Users\All Users\Astroid2\cache. If the location has been changed, the new location can be found within the Planning App from the View–>Settings menu.
3. If a user starts a calculation using the calculation status UI (e.g.: feasibility or MCO) and is outside the block the interface is in when the calculation finishes, the status of the calculation will remain “calculating”. Manually refreshing data (pressing F5) or re-launching the application resolves this issue.
   • This issue may also apply to other requests and calculations in the application too
4. Treatment plans store an optional fluence override vector which will be used instead of the optimization fluence results if present. These overrides must be added via scripts outside the Planning App UI. If an override is present in a plan the Planning App UI becomes mostly read-only to limit the potential for changes that could invalidate the fluence override. However there are no hard stops to ensure that the fluence override vectors are properly sized for the plan at hand, so users must ensure properly sized fluence vectors are set in their scripts.

1. The Uploads block must remain open while uploading DICOM files.

1. Computed treatment plan dose is required prior to users being able to export DICOM files.
   • Note: Users may still be able to attempt to export DICOM files from the user interface, but may encounter errors if their plan does not have, or is unable to, compute dose.
2. DICOM Export of CT and SS files searches the RKS for the CT image record, therefore modifying the RKS record of the CT images can cause changes to the exported data even on an approved plan (deleting the record will prevent export of CT and SS altogether)

1. When importing a new patient, the default physician will be set from the DICOM file. When this physician selection is changed, either during import or later in the Patient Overview, there is no way to re-select the original from DICOM physician.

1. Plan templates are unable to be edited and/or removed from within the Planning App without manually manipulating the RKS record.
2. All referenced and used structures in the original plan template must exist in the new patient model for which the plan template is being used.

1. When changing a structure type from a TARGET, whether at the Patient Model or Plan level, if that structure was an existing optimization constraint or objective with maximize options selected, those options will continue to be selected and will unable to be changed in the UI. They can be viewed in the optimization constraint and objective summaries, but will not be editable unless the structure type is changed back to TARGET.
   1. This can result in you having constraints or objectives that might not be ideal for this type of structure. Always double check the constraint/objective summaries if you need to change a structure type from TARGET after you've added optimization parameters to that structure.
2. Structures that are expanded in the axis of the CT image slices will have the expansion distance limited by the CT image spacing. So the expansion distance may appear to be an incorrect distance.
3. When creating a new target for a PBS beam via the Create subtask from the Geometric Target drop down, you are able to create a non target structure and have it be selected in this drop down. This is only possible when the Create subtask automatically populates the dropdown upon finishing, and you will not be able to select this target manually if you change the selection.

1. When multiple machines are defined in the facility model each room must have a unique name within the entire facility model. The treatment_plan references a treatment_room by it's name and assumes this name will only exist one time in the facility model.

1. Astroid does not detect possible collisions between the patient and snout or the treatment table and snout. It is the users responsibility to ensure that there is enough distance between the patient/table and the snout so as to avoid collisions.

1. For SOBP plans with patch fields, dose overlap at the patch junction may result in a maximum dose that exceeds the limits of the isobands and DHV displays
2. If a patch field is added to an existing thru-beam that's already in a fraction group, the thru-beam must be removed and re-added to the fraction group for the patch field to be included in the fraction group's beam list.

See Thinknode Errors for common problems that can occur during usage of the Planning app.

Should you discover or suspect any additional errors or limitations not noted above, please alert the .decimal Astroid Planning App development team by providing creating a ticket at dotdecimal.freshdesk.com including details of your concerns and steps to reproduce the issue. All concerns will be addressed as quickly as possible and follow up with the submitter will occur throughout the inquiry and correction process.

Please refer to the Planning App ResultsAPI Guide for a more detailed look at explanation, usages, and examples of the Planning App ResultsAPI.