electronrt:userguide:userguide
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
electronrt:userguide:userguide [2020/09/18 15:02] – [Feature/Task Descriptions] dpatenaude | electronrt:userguide:userguide [2023/03/09 20:59] (current) – [General] dpatenaude | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== Overview ===== | ===== Overview ===== | ||
- | The decimal ElectronRT (eRT) application is used for treatment | + | 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 |
===== Purpose ===== | ===== Purpose ===== | ||
Line 19: | Line 19: | ||
* [[electronrt: | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
- | * [[electronrt: | + | * [[electronrt: |
==== Precautions ==== | ==== Precautions ==== | ||
- | It is the responsibility of those utilizing this application to ensure | + | 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 ==== | ==== Initial Setup ==== | ||
- | Once decimal eRT has been purchased, .decimal staff will assist with beam model creation, software installation, | + | Once decimal eRT has been purchased, .decimal staff will assist with beam model creation, software installation, |
=== Installation === | === Installation === | ||
Line 34: | Line 34: | ||
The main high level requirements for using the decimal Launcher and decimal eRT application are: | The main high level requirements for using the decimal Launcher and decimal eRT application are: | ||
- | - .decimal Direct | + | - .decimal Direct account credentials |
- | - This account needs association with a site ID that has been granted | + | - This account needs association with a Site ID (.decimal Customer Account number) |
- This account needs specific .decimal Permission for accessing the eRT modules | - This account needs specific .decimal Permission for accessing the eRT modules | ||
- The decimal Launcher installed | - The decimal Launcher installed | ||
Line 46: | Line 46: | ||
The [[electronrt: | The [[electronrt: | ||
+ | === DICOM Receiver === | ||
+ | |||
+ | The decimal ElectronRT application supports importing DICOM patients via a DICOM listener/ | ||
==== Keyboard and Mouse Controls ==== | ==== 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: | + | 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: |
- | ===== Feature/ | + | ===== Application Usage ===== |
- | The following | + | The following |
* [[electronrt: | * [[electronrt: | ||
Line 59: | Line 62: | ||
* [[electronrt: | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
+ | * [[electronrt: | ||
+ | * [[electronrt: | ||
+ | * [[electronrt: | ||
+ | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
+ | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
+ | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
Line 73: | Line 82: | ||
* [[electronrt: | * [[electronrt: | ||
- | ===== System Usage ===== | ||
- | ==== Improper System Usage ==== | + | |
+ | ===== 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. | 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. | ||
Line 85: | Line 94: | ||
==== General ==== | ==== General ==== | ||
- | - Astroid uses DICOM patient | + | ^ ID ^ Affected Version(s) |
+ | | 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: '' | ||
+ | </ | ||
+ | | 3 | All | Random Application Crashes:< | ||
+ | * If the [[electronrt: | ||
+ | </ | ||
+ | | 4 | All | Network patient database:< | ||
+ | * If the application is set to use a [[electronrt: | ||
+ | * The application crashes or a network connection is interrupted during a SQL commit that allows the ' | ||
+ | * 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 " | ||
+ | </ | ||
+ | | 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 | ||
+ | </ | ||
+ | ==== DICOM Import ==== | ||
+ | |||
+ | ^ ID ^ Affected Version(s) | ||
+ | | 1 | All | Closing the application immediately after importing a DICOM patient and before the job ' | ||
+ | | 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) | ||
+ | | 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) | ||
+ | | 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+ | ||
+ | |||
+ | ==== Plans ==== | ||
+ | ^ ID ^ Affected Version(s) | ||
+ | | 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' | ||
+ | | 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: ''" | ||
+ | | 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.| | ||
+ |
electronrt/userguide/userguide.1600441349.txt.gz · Last modified: 2021/07/29 18:22 (external edit)