Difference between revisions of "IHERO UseCase 2013 Query Retrieve In Radiation Oncology"
Line 19: | Line 19: | ||
==3. Key Use Case== | ==3. Key Use Case== | ||
+ | |||
+ | See also [[IHERO_2007UseCase_Instance-level_Query_Retrieve|an older proposal]], which dates back to 2006. | ||
===Retrieving a specific plan=== | ===Retrieving a specific plan=== |
Revision as of 13:25, 26 September 2013
1. Proposed Workitem: Query/Retrieve In Radiation Oncology
- Proposal Editor: Christof Schadt
- Editor: Christof Schadt
- Date: N/A (Wiki keeps history)
- Version: N/A (Wiki keeps history)
- Domain: Radiation Oncology
2. The Problem
The amount of data available throughout a work-flow in radiation oncology has been increasing over the years. There main reason for this is the constantly increasing capability of imaging modalities of creating image information with smaller slice thicknesses, resulting in a higher number of slices.
Usage of Registration objects to combine multiple image data sets (as defined by the MMRO profile), and data created upon multiple image data sets results in a complex structure of references among a large set of information objects.
The actual problem then arises when searching for some specific information within this data or retrieving it in a timely manner.
3. Key Use Case
See also an older proposal, which dates back to 2006.
Retrieving a specific plan
This could be any combination of image modalities, structure information, treatment plan or dose matrix): search for specific instance level attributes of e.g. DICOM image modalities, RT Structure Sets, RT Plan, RT Dose, RT Image and Treatment Records.
Retrieving large image sets
Define usage of asynchronous associations or multiple associations in order to transfer large image data sets
Search for data with non-trivial relations
Define usage of relational queries in RT.
4. Standards and Systems
- DICOM Standard Query/Retrieve model as defined in PS3.4