decimal App Documentation

User Tools

Site Tools

Trace:
planning:instructions_for_use:instructions_for_use

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

planning:instructions_for_use:instructions_for_use [2017/10/12 15:27] – [Descriptions] dpatenaudeplanning:instructions_for_use:instructions_for_use [2021/07/29 18:23] (current) – external edit 127.0.0.1
Line 3: Line 3:
 ===== Overview and Indications for Use ===== ===== Overview and Indications for Use =====
  
-The Astroid Planning App is an interactive end user application that leverages the existing .decimal Astroid Dosimetry App [FDA 510(k) K150547] library of functions (accessed through the Thinknode® cloud services framework) for device creation, dose calculation, optimization, and many other purposes, for the intended use and primary purpose of enabling radiotherapy professionals to efficiently design and analyze proton radiotherapy treatment plans. Typical indications for use are for the treatment of persons with cancer, over a wide range of potential disease locations. In the most common use case of the software, users will import patient data from existing imaging and contouring software programs, manage physician prescription and intent information, develop a proton treatment plan, and analyze the plan to determine how well it meets the physician’s goals. Since the critical treatment planning functions and calculations are handled outside this software application, by a software of known quality and pedigree, the primary and most frequently used functions of this software are the record keeping service (for patient data storage), user interface controls, and visualization tools.+The Astroid Planning App is an interactive end user application for proton treatment planning for the intended use and primary purpose of enabling radiotherapy professionals to efficiently design and analyze proton radiotherapy treatment plans. This Astroid Planning App leverages the existing .decimal Astroid Dosimetry App [FDA 510(k) K150547], which is a library of treatment planning functions accessed through the Thinknode® cloud services framework, for device creation, dose calculation, optimization, and all other dosimetry and processing calculations. Since the Astroid Dosimetry App is responsible for performing the calculations, the scope of this Astroid Planning App is to be the interface for end users to input treatment planning data and review the results. Typical indications for use of this application are for the treatment of persons with cancer, over a wide range of potential disease locations. In the most common use case of the software, users will import patient data from existing imaging and contouring software programs, manage physician prescription and intent information, develop a proton treatment plan, and analyze the plan to determine how well it meets the physician’s goals. Since the critical treatment planning functions and calculations are handled outside this software application, by a software of known quality and pedigree, the primary and most frequently used functions of this software are the record keeping service (for patient data storage), user interface controls, and visualization tools.
  
 Furthermore, since the accuracy of information computed and displayed by an application such as this is very important to the proper treatment of patients, it is critical that users have the appropriate educational and clinical experience backgrounds to adequately understand and use the product. Additionally, since each radiotherapy treatment machine produces a unique beam of radiation, there is much responsibility on the end users to adequately commission and test this software over the full range of expected treatment conditions before the system is utilized for patient treatment. Furthermore, since the accuracy of information computed and displayed by an application such as this is very important to the proper treatment of patients, it is critical that users have the appropriate educational and clinical experience backgrounds to adequately understand and use the product. Additionally, since each radiotherapy treatment machine produces a unique beam of radiation, there is much responsibility on the end users to adequately commission and test this software over the full range of expected treatment conditions before the system is utilized for patient treatment.
Line 104: Line 104:
  
 By using the astroid Launcher, users can log in to multiple realms with each realm using a different app version. This allows for scenarios of using non-clinical or research application versions from the same user account or workstation without the overhead of managing multiple installations. By logging into a realm, the user is required to use the installed client version for that realm. By using the astroid Launcher, users can log in to multiple realms with each realm using a different app version. This allows for scenarios of using non-clinical or research application versions from the same user account or workstation without the overhead of managing multiple installations. By logging into a realm, the user is required to use the installed client version for that realm.
 +
 +Details regarding the specific requirements for computers on which the Launcher and Planning App client applications will be installed can be found on the [[planning:userguide:systemrequirements|System Requirements]] page.
 === Releasing a new App Version === === Releasing a new App Version ===
  
Line 175: Line 177:
 The following page describes the hierarchy of data used to manage patient data records within the Astroid planning environment. The following page describes the hierarchy of data used to manage patient data records within the Astroid planning environment.
  
-===== Hierarchy =====+==== Hierarchy ====
  
   * __**Patient**__   * __**Patient**__
Line 204: Line 206:
           * Constraints           * Constraints
           * Objectives           * Objectives
 +          * Optional Fluence Override
           * Dose Results           * Dose Results
  
Line 211: Line 214:
  
 */ */
-===== Descriptions =====+==== Descriptions ====
  
   * **__Patient__**:   * **__Patient__**:
Line 227: Line 230:
       * A specific model of a target, OAR, or other structure. A physician may provide an initial target contour and a treatment plan generated using this information. The physician may later (using the same CT image set) provide a revised target contour. Rather than import this revision as a new structure or override the original, you may specify this new contour as a variant of the original. Each contour may have only a single "active" variant and the plan will automatically update based on the selection of the active variant. However, in some cases it is not desirable to update the plan, so the user may also choose to lock the plan and simply recompute DVH and other volume based statistics based on the new active variant geometry. In either case, variants can be used to streamline workflows and prevent accidental misuse of out-dated contours.       * A specific model of a target, OAR, or other structure. A physician may provide an initial target contour and a treatment plan generated using this information. The physician may later (using the same CT image set) provide a revised target contour. Rather than import this revision as a new structure or override the original, you may specify this new contour as a variant of the original. Each contour may have only a single "active" variant and the plan will automatically update based on the selection of the active variant. However, in some cases it is not desirable to update the plan, so the user may also choose to lock the plan and simply recompute DVH and other volume based statistics based on the new active variant geometry. In either case, variants can be used to streamline workflows and prevent accidental misuse of out-dated contours.
   * **__Plan__**:    * **__Plan__**: 
-    * A detailed model of a proton therapy treatment. Most aspects of the patient planning information are stored here (e.g. Beams, Fraction Groups, Optimization Information, and Dose Results). A Plan will specify the portion of the Prescription it should meet and physicians will publish (approve) a Plan to indicate it is ready to proceed to QA and (if successful) on to actual patient treatment. __There should be only one "published" Plan per Prescription__.+    * A detailed model of a proton therapy treatment. Most aspects of the patient planning information are stored here (e.g. Beams, Fraction Groups, Optimization Information, and Dose Results). A Plan will specify the portion of the Prescription it should meet and physicians will publish (approve) a Plan to indicate it is ready to proceed to QA and (if successful) on to actual patient treatment. __There should be only one "published" Plan per Prescription__. Plans may optionally contain a fluence override vector that will be used in place of the actual optimized fluence results from the plan (note there are no UI tools to add such overrides and they must be added via user controlled scripts).
  
-===== Structures in the Data Model =====+==== Structures in the Data Model ====
  
 There are multiple levels that various structures can live at. Each level and structure type will effect how the structure will relate to the plan. Refer to the [[planning:userguide:tutorials:all_tutorials#structure_data_model|Structure Data Model Guide]] for more details. There are multiple levels that various structures can live at. Each level and structure type will effect how the structure will relate to the plan. Refer to the [[planning:userguide:tutorials:all_tutorials#structure_data_model|Structure Data Model Guide]] for more details.
Line 235: Line 238:
  
 ---- ----
-<WRAP center 10%>//USR-###//</WRAP> +<WRAP center 60%>.decimal LLC, 121 Central Park Place Sanford, FL. 32771 1-800-255-1613</WRAP>
- +
-<WRAP center 50%>.decimal LLC, 121 Central Park Place, Sanford, FL. 32771</WRAP>+
  
    
planning/instructions_for_use/instructions_for_use.1507822047.txt.gz · Last modified: 2021/07/29 18:22 (external edit)