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 [2021/02/17 21:34] – [DICOM Import] dpatenaude | electronrt:userguide:userguide [2023/03/09 20:59] (current) – [General] dpatenaude | ||
---|---|---|---|
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 (.decimal Customer Account number) that has been licensed for use of the decimal eRT application | - 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 | - This account needs specific .decimal Permission for accessing the eRT modules | ||
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 ==== | ||
Line 51: | Line 54: | ||
- | ===== Feature/ | + | ===== Application Usage ===== |
- | The following | + | The following |
* [[electronrt: | * [[electronrt: | ||
Line 59: | Line 62: | ||
* [[electronrt: | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
+ | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
Line 66: | Line 70: | ||
* [[electronrt: | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
+ | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
+ | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
* [[electronrt: | * [[electronrt: | ||
Line 76: | 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 86: | Line 92: | ||
Below are listed the known application limitations, | Below are listed the known application limitations, | ||
- | === General === | + | ==== General ==== |
- | + | ||
- | - decimal eRT does not show the MU value for beams and treatment plans. | + | |
- | - 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: ''" | + | |
- | === Organization Configuration | + | ^ 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/ | ||
+ | * 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) |
- | === DICOM Import === | + | | 1 | All | Closing the application immediately after importing |
+ | | 2 | 0.9.0 | Only plan files with a valid bolus in at least one beam will import properly. | | ||
- | - Closing the application immediately after importing a DICOM patient and before the job ' | + | ==== DICOM Export ==== |
- | === Beams === | + | ^ ID ^ Affected Version(s) |
- | - Adding more than one beam with an optimized thickness bolus results in the DVH inspection performance being slow. | + | | 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 |
- | | + | ==== Beams ==== |
- | === QA === | + | ^ 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 | ||
electronrt/userguide/userguide.1613597693.txt.gz · Last modified: 2021/07/29 18:22 (external edit)