====== decimal eRT User Guide ====== ===== Overview ===== The decimal ElectronRT (eRT) application is used for planning of electron radiation therapy treatments. decimal eRT is an interactive end user application that allows users to design treatment plans and electron beam shaping devices (e.g.: bolus, blocks, and intensity modulators) and order those devices for fabrication by .decimal. ===== Purpose ===== The purpose of this document is to provide guidance on the setup, access, and usage of decimal eRT. ===== Getting Started ===== 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 [[electronrt:instructions_for_use:instructions_for_use|Instructions for Use]], which outlines the general usage principles and limitations of the decimal eRT app. Users must read and understand these instructions before operating the system for clinical use. Refer to each section below for complete details: * **[[electronrt:instructions_for_use:instructions_for_use|Instructions for Use]]** * [[electronrt:instructions_for_use:instructions_for_use#overview_and_indications_for_use|Overview and Indications for Use]] * [[electronrt:instructions_for_use:instructions_for_use#user_responsibilities|User Responsibilities]] * [[electronrt:instructions_for_use:instructions_for_use#warning|Warning]] * [[electronrt:instructions_for_use:instructions_for_use#intended_use|Intended Use]] * [[electronrt:instructions_for_use:instructions_for_use#user_profile|User Profile]] * [[electronrt:instructions_for_use:instructions_for_use#product_features|Product Features]] * [[electronrt:instructions_for_use:instructions_for_use#decimal_ert_patient_data_model|Patient Data Model]] ==== Precautions ==== It is the responsibility of those utilizing this application to ensure 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 regarding the quality, units, or identification of input data arise, they must be investigated and resolved before the data are used. ==== Initial Setup ==== Once decimal eRT has been purchased, .decimal staff will assist with beam model creation, software installation, and user training. Users will generally be trained at two separate levels, system administrators and end users. System administrators will be setup with appropriate access and tools for managing the software, including both the local resources and user accounts. End users will be primarily trained on the details of generating high-quality treatment plans using the local client portion of the application. Additionally, the medical physics team will be trained and assisted in completing the beam modeling and equipment setup processes, which are explained more fully in the Commissioning Guide (this guide is not available at this time). === Installation === The decimal eRT application is installed via the [[decimalauncher:decimallauncher|decimal Launcher]] client application. Refer to the decimal Launcher [[decimalauncher:decimallauncher|user guide]] for details on using the decimal Launcher. The main high level requirements for using the decimal Launcher and decimal eRT application are: - .decimal Direct account credentials - This account needs association with a Site ID (.decimal Customer Account number) that has been licensed for use of the decimal eRT application - This account needs specific .decimal Permission for accessing the eRT modules - The decimal Launcher installed Please refer to the decimal eRT [[electronrt:userguide:systemrequirements|System Requirements]] page for complete details on hardware and network requirements. === Site Settings and Facility Model === When using the decimal eRT app for the first time users will be required to setup and configure their site facility settings. This includes organization level details (name, report logo, override materials, etc) and specific site details (ordering address, physicians, DICOM export servers, QA options, and machine commissioning). The [[electronrt:userguide:tutorials:all_tutorials#organization_configuration| Organization Configuration]] user guide section describes each of the blocks and configuration interfaces. === DICOM Receiver === The decimal ElectronRT application supports importing DICOM patients via a DICOM listener/receiver. Refer to the [[electronrt:userguide:dicom_receiver|ElectronRT DICOM Receiver setup guide]] for instructions for enabling and configuring this method of DICOM patient import into the eRT application. ==== Keyboard and Mouse Controls ==== The decimal eRT app 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 [[electronrt:userguide:keyboard_controls| Keyboard and Mouse Controls page]]. ===== Application Usage ===== The following sections are thorough guides providing complete information about each task within the decimal eRT application. * [[electronrt:userguide:tutorials:all_tutorials#launching_electronrt|Launching decimal eRT]] * [[electronrt:userguide:tutorials:all_tutorials#dicom_patient_import|DICOM Patient Import]] * [[electronrt:userguide:tutorials:all_tutorials#patient_courses|Patient Courses]] * [[electronrt:userguide:tutorials:all_tutorials#electron_treatment_plans|Electron Plans]] * [[electronrt:userguide:tutorials:all_tutorials#prescription|Prescription]] * [[electronrt:userguide:tutorials:all_tutorials#patient_geometry|Patient Geometry]] * [[electronrt:userguide:tutorials:all_tutorials#points|Points]] * [[electronrt:userguide:tutorials:all_tutorials#uniform_thickness_boluses|Uniform Thickness Bolus]] * [[electronrt:userguide:tutorials:all_tutorials#Imaging|Imaging]] * [[electronrt:userguide:tutorials:all_tutorials#density_overrides|Density Overrides]] * [[electronrt:userguide:tutorials:all_tutorials#electron_beams|Electron Beams]] * [[electronrt:userguide:tutorials:all_tutorials#electron_block_creation|Electron Block Creation]] * [[electronrt:userguide:tutorials:all_tutorials#skin_collimator_creation|Electron Skin Collimator Creation]] * [[electronrt:userguide:tutorials:all_tutorials#electron_bolus_creation|Electron Bolus Creation]] * [[electronrt:userguide:tutorials:all_tutorials#intensity_modulator_device|Electron Intensity Modulator]] * [[electronrt:userguide:tutorials:all_tutorials#electron_beam_normalization|Electron Beam Normalization]] * [[electronrt:userguide:tutorials:all_tutorials#plan_approval|Plan Approval]] * [[electronrt:userguide:tutorials:all_tutorials#plan_reports|Plan Reports]] * [[electronrt:userguide:tutorials:all_tutorials#plan_qa|Plan QA]] * [[electronrt:userguide:tutorials:all_tutorials#dicom_export|DICOM Export]] * [[electronrt:userguide:tutorials:all_tutorials#organization_configuration|Organization Configuration]] * [[electronrt:userguide:tutorials:all_tutorials#sandbox_testing|Sandbox Testing]] * [[electronrt:userguide:tutorials:all_tutorials#decimal_ert_settings|App Settings]] ===== Improper System Usage ===== When using decimal eRT, as with any complex program, there is the potential for misuse. The decimal eRT app is a radiotherapy treatment planning tool that is intended to be used by experienced and knowledgeable professionals working in the field of radiation therapy. ===== Known Application Limitations ===== Below are listed the known application limitations, defects, or inconsistencies. ==== General ==== ^ ID ^ Affected Version(s) ^ Description ^ | 1 | 0.0.1\\ 0.0.2\\ 0.0.3\\ 0.0.4| decimal eRT does not show the MU value for beams and treatment plans. | | 2 | All | Simultaneous record access: * If multiple instances of the application have the same treatment plan record opened, changes will be prevented from being pushed to the patient database if the treatment plan is changed first by another user. This will cause the other simultaneous instances to become outdated. Changes to the local application on outdated instances will be blocked from pushing plan changes to the patient database, but the changes may still appear to have happened in the local application. Users will be warned of their changes being blocked by the error: ''“Plan revision is outdated. Please close and reopen the treatment plan to continue using this plan."'' | | 3 | All | Random Application Crashes: * If the [[electronrt:instructions_for_use:instructions_for_use#network_local_data_cache|local or network disk cache]] becomes corrupted the application may crash at seemingly random places while calculations are computing. Clearing the [[electronrt:userguide:tutorials:all_tutorials#local_disk_cache|local disk cache]] within the application settings may help resolve unreproducible application crashes during calculations running. | | 4 | All | Network patient database: * If the application is set to use a [[electronrt:instructions_for_use:instructions_for_use#patient_database_file_storage|network patient directory]] shared with multiple users there may be a risk for 'database is locked' errors. This is due to the application using SQLite as it's database engine, which does not robustly support concurrent database users and reading/writing. While normal usage between one or two users may not pose a problem with this, having a significant number of users simultaneously accessing the network database or the following scenarios can cause the database to lock and throw this error: * The application crashes or a network connection is interrupted during a SQL commit that allows the 'unlock' step to be missed OR * The file is locked due to other network usage (e.g.: the file is in use by an external service such as an Antivirus scan, backup, etc) OR * Multiple simultaneous users are attempting to read/write to the database at the same time * If you receive the error "database is locked" you'll have to wait and try again once the database is unlocked | | 5 | All | Application fails to load computed data: Under the following scenario, the application request and state handling has a known bug that results in computed data not loading within the application until a application close and re-open is performed: * A patient/plan is opened and a user interface or task is opened * Data begins computing (e.g.: a dose, beam, or device) * While the data is computing the user navigates to another user interface within the application * If the data finishes computing for the first user interface while the user is navigated to a new user interface and then the user navigates back to the first user interface, the application may not know the data is computed to display or use the results. | ==== DICOM Import ==== ^ ID ^ Affected Version(s) ^ Description ^ | 1 | All | Closing the application immediately after importing a DICOM patient and before the job 'copy_imported_dicom_files_to_course' completes will cause an incomplete CT Image Set when exporting DICOM later in the application. | | 2 | 0.9.0 | Only plan files with a valid bolus in at least one beam will import properly. | ==== DICOM Export ==== ^ ID ^ Affected Version(s) ^ Description ^ | 1 | 0.0.1\\ 0.0.2\\ 0.0.3| Exporting local DICOM files and providing no export directory will cause the DICOM files to be exported to the local application installation folder. This will cause the decimal Launcher application to invalidate the local eRT install and require a re-download of the application. | ==== Beams ==== ^ ID ^ Affected Version(s) ^ Description ^ | 1 | All | Adding more than one beam with an optimized thickness bolus can sometimes result in the DVH inspection performance being slow. | | 2 | All | Optimized Bolus outside shape is generated to the target size and not the block size. So if manual edits are performed on the block that expand the block shape, the bolus extents may be undersized. This can be remedied by increasing the bolus block outer border.| | 3 | 0.0.3+ | Skin collimator devices may cause interference with fitting inside of the electron bolus when fitting on the patient surface. This is due to sharp corners that result from a rough patient surface contour.| ==== Plans ==== ^ ID ^ Affected Version(s) ^ Description ^ | 1 | All | (Approved Plans) Users should understand that the eRT application stores only user input information and not computed data. However, since machine models and dose calculation algorithms can change over time, certain calculated data and equipment model data that is considered critical to the patient's treatment record is stored with each plan upon approval. This stored data includes: treatment device shapes (e.g. bolus, collimators, intensity modulators), 3D dose fields per beam, and beam model data. However, it should be noted that data derived from these stored results may be recomputed and is therefore subject to change if Approved Plans are loaded in future eRT versions. One such example would be DVH curves. While the dose is stored and will never change for an Approved Plan, the sampling scheme used in DVH calculations can change over time, therefore DVH curves may change even for Approved Plans if such changes are made in the eRT application. Patient-to-applicator collisions, structure volumes, and QA Dose Calculations are additional examples of information that could change in future application versions as this data remains computed, not stored, even for Approved Plans. | | 2 | 0.0.1 - 0.0.4 | (Unapproved Plans) Unapproved treatment plans created versions earlier than eRT version 0.0.4 will not have the plan prescription filled in (denoted by the error: ''"Prescription statement not found in plan"'') resulting in dose not being displayed within the treatment plan displays. Users can resolve this by re-adding the prescription that previously existed in the corresponding Course. | | 3 | 0.0.1 - 0.7.0 | (Approved Plans) Approved treatment plans created versions earlier than eRT version 0.8.0 that contain a skin collimator will no longer be able to load the approved skin collimator when opening the plan. Users will be required to clone the approved plan and re-approve the plan to allow the skin collimator devices to be exported or ordered.|