dicom:userguide:userguide
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
dicom:userguide:userguide [2015/07/10 12:36] – [Overview] dpatenaude | dicom:userguide:userguide [2021/07/29 18:23] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 3: | Line 3: | ||
===== Overview ===== | ===== Overview ===== | ||
- | The astroid Dicom App is used to provide access to functions which are used for reading a dicom file and returning more useable standard data types, such as those from the RT Types App available on the thinknode framework. The astroid Dicom App device is not an interactive end user application. Users of the system will write scripts or use a fully interactive software program that makes calls to the functions provided by the astroid Dicom App. The core functionality includes parsing dicom RT_Plan, Structure Set, CT Image, and Dose file types. The Dicom App adheres to the Dicom PS3.3 2015c dicom specification. | + | The astroid Dicom App is used to provide access to functions which are used for reading a dicom file and returning more useable standard data types, such as those from the RT Types App available on the thinknode framework. The astroid Dicom App device is not an interactive end user application. Users of the system will write scripts or use a fully interactive software program that makes calls to the functions provided by the astroid Dicom App API. The core functionality includes parsing dicom RT_Plan, Structure Set, CT Image, and Dose file types. The Dicom App adheres to the Dicom PS3.3 2015c dicom specification. |
- | Access to the astroid Dicom App is provided by the thinknode™ framework using http json formatted requests. thinknode™ provides the 'backbone' | + | Access to the astroid Dicom App is provided by the thinknode™ framework using http json formatted requests. thinknode™ provides the backbone used to send and receive requests, maintain users, realms and organizations, |
The [[http:// | The [[http:// | ||
Line 14: | Line 14: | ||
===== Getting Started ===== | ===== Getting Started ===== | ||
- | FIXME | + | |
- | The primary purpose of the astroid | + | The primary purpose of the astroid |
==== Connecting to thinknode™ ==== | ==== Connecting to thinknode™ ==== | ||
- | The Dicom App, and all its released versions | + | The Dicom App, and all its released versions |
Basic information needed to communicate with the Dicom App through thinknode™: | Basic information needed to communicate with the Dicom App through thinknode™: | ||
Line 31: | Line 31: | ||
==== Precautions ==== | ==== Precautions ==== | ||
- | FIXME | + | |
- | It is the responsibility of those utilizing this application to ensure all that all usages of this product relating to patient treatments | + | It is the responsibility of those utilizing this application to ensure all that all usages of this product relating to dicom information handling |
+ | |||
+ | <WRAP center 80% important round> | ||
+ | Any data posted to thinknode™ is immutable and can not be deleted. Please ensure when posting dicom files that you have anonymized patient data in the dicom files or that you are posting the data to a private bucket in thinknode™. | ||
+ | </ | ||
+ | |||
+ | ===== Proton Delivery System Conventions ===== | ||
+ | |||
+ | {{page> | ||
===== Functions ===== | ===== Functions ===== | ||
- | FIXME | ||
- | The Dosimetry App exposes three primary classes of functions through its API: dose calculation functions (DCF), design task functions (DTF), and radiotherapy support functions (RSF). Each function has its own type of input argument specifications and output results specifications. It is worthy of pointing out the interdependence of these function classes upon one another. Specifically, | ||
- | * Details | + | The Dicom App exposes a few key functions through its API. Below is a list and brief explanation of a few of the most common functions. A full function list as well as details |
- | * Notes about manifest documentation: | + | |
- | - Previous versions of the dosimetry documentation can be found at the [[dosimetry:dosimetry_versions|Dosimetry Versions]] page. | + | * //**add_dcm_file_to_study:**// |
- | - If a manifest is manually pulled down from the thinknode framework, that manifest will not match the one outlined | + | * Takes in a rt_study and dicom file blob, parses |
+ | * // | ||
+ | * Adds dicom files to an existing study and returns the updated study. | ||
+ | * // | ||
+ | * Makes a new study and initializes plan, ss and ct for importing dicom files | ||
+ | * // | ||
+ | * Writes a dicom dose file for the beam specified | ||
+ | * // | ||
+ | * Writes a dicom ct image file as a blob from cradle rt_study data. | ||
+ | * // | ||
+ | * Writes all dicom ct image files as blobs from cradle rt_study data. | ||
+ | * // | ||
+ | * Writes 3D image data containing dose information into a binary blob dicom dose file. | ||
+ | * // | ||
+ | * Returns a filesystem_item of the patient dicom files. | ||
+ | * // | ||
+ | * Writes dicom plan file as a blob from cradle plan data. | ||
+ | * // | ||
+ | * Writes a dicom dose file for the plan in the study | ||
+ | * // | ||
+ | * Writes dicom structure set file as a blob from cradle structure set data. | ||
+ | See the [[dicom: | ||
===== Data Types ===== | ===== Data Types ===== | ||
Details of each datatype used by the Dosimetry App can be found at the [[http:// | Details of each datatype used by the Dosimetry App can be found at the [[http:// | ||
- | ===== Examples ===== | + | ===== Calc Provider |
- | ==== thinknode™ ==== | + | ==== thinknode™ |
- | Official thinknode™ user guide documentation can be found at [[https:// | + | Official thinknode™ user guide documentation can be found at [[https:// |
* **[[dicom: | * **[[dicom: | ||
- | * [[dicom: | + | * [[dicom: |
- | * [[dicom: | + | * [[dicom: |
- | + | ||
- | ==== Dicom App Functions ==== | + | |
- | + | ||
- | Refer to the [[dicom: | + | |
===== System Usage ===== | ===== System Usage ===== | ||
Line 70: | Line 94: | ||
When using the astroid Dicom App, as with any complex program, there is the potential for misuse. The thinknode™ framework and Dicom App limit most of the potential misuse of exposed functions and data types, but there' | When using the astroid Dicom App, as with any complex program, there is the potential for misuse. The thinknode™ framework and Dicom App limit most of the potential misuse of exposed functions and data types, but there' | ||
+ | |||
+ | {{page> | ||
===== Known Application Limitations ===== | ===== Known Application Limitations ===== | ||
Line 80: | Line 106: | ||
---- | ---- | ||
- | <WRAP center 10%>// | ||
- | <WRAP center | + | <WRAP center |
dicom/userguide/userguide.1436531790.txt.gz · Last modified: 2021/07/29 18:21 (external edit)