User Tools

Site Tools


planning:userguide:tutorials:importing

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
planning:userguide:tutorials:importing [2017/10/10 16:00] – [Importing Patient Data] kmobileplanning:userguide:tutorials:importing [2021/07/29 18:28] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Importing Patient Data ======  ====== Importing Patient Data ====== 
  
-Now that a patient has been uploaded from DICOM to the Thinknode RKS, the Planning App should recognize that new patient files are available to import into a Planning patient.+Now that a patient has been uploaded from DICOM, the Planning App should recognize that new patient files are available to import into a Planning patient.
  
   - Open the Astroid Launcher and launch the Planning App from your realm   - Open the Astroid Launcher and launch the Planning App from your realm
Line 16: Line 16:
     - Matched, Assigned, and Custom structures are designated with corresponding tags at the end of the structure name in the structure list     - Matched, Assigned, and Custom structures are designated with corresponding tags at the end of the structure name in the structure list
       - You may only edit structures that are shown as //Custom//, which indicates the name did not exactly match a course structure from the //Treatment Site// template selected above       - You may only edit structures that are shown as //Custom//, which indicates the name did not exactly match a course structure from the //Treatment Site// template selected above
-      - For all custom structures, the type is by default set to "Other", unless it contains the letters "TV" (as in PTV or CTV), in which case it is assigned the type of "Target"; the type may be changed here if needed+      - For all custom structures, the type is by default set to the value from the DICOM file. If there is no type specified in the DICOM file the type will be set to "Other", unless it contains the letters "TV" (as in PTV or CTV), in which case it is assigned the type of "Target"; the type may be changed here if needed
       - Alternatively you may //Assign// a //Custom// structure to a course level template structure using the provided drop down menu (this is useful when structure names contain typos or contour names otherwise do not match your standard site protocols)         - Alternatively you may //Assign// a //Custom// structure to a course level template structure using the provided drop down menu (this is useful when structure names contain typos or contour names otherwise do not match your standard site protocols)  
         - Assigning a custom structure to a defined course structure will result in the imported structure inheriting all the predefined structure properties (e.g. name, type, color) {{ :planning:userguide:tutorials:import_structure_info.png?300 |}}         - Assigning a custom structure to a defined course structure will result in the imported structure inheriting all the predefined structure properties (e.g. name, type, color) {{ :planning:userguide:tutorials:import_structure_info.png?300 |}}
Line 24: Line 24:
  
  
-====== Structures ======+===== Structures in the Data Model =====
  
-There are multiple levels that various structures can live at. Each level will effect how the structure will relate to the plan. +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.
  
-==== Site Level Structures ==== 
  
-Site level structures are predefined templated structures. The user is not allowed to edit any aspect of a Site Level structure. 
  
  
  
planning/userguide/tutorials/importing.1507651258.txt.gz · Last modified: (external edit)