Differences

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

--- planning:userguide:tutorials:importing [2017/08/18 20:09] – kerhart
+++ planning:userguide:tutorials:importing [2021/07/29 18:28] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
 ====== 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
@@ Line 15: / Line 15: @@
     - Here you may choose whether or not to import each structure by checking or unchecking the box beside each structure name
     - 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 directive 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 directive 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 directive 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 |}}
   - Once all structures have been selected, assigned, and edited as needed, click the //Import// button to create the patient and import the CT Images and Structures into it
   - The patient is now created and all available data has been imported
   - Click on the //Back to Import// button to return back to the //Imports// task
+===== 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.