Difference between revisions of "IHERO UseCase 2013 Query Retrieve In Radiation Oncology"

From IHE Wiki
Jump to navigation Jump to search
(First Draft)
 
 
(4 intermediate revisions by the same user not shown)
Line 12: Line 12:
 
==2. The Problem==
 
==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.
+
The amount of data available throughout a work-flow in radiation oncology has been increasing over the years. One reason is the constantly increasing capability of imaging modalities of creating image information with smaller slice thicknesses, resulting in a higher number of slices. Another reason is the increasing number and variety of image series and related information.
 +
 
 
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.
 
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.
 
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==
 
==3. Key Use Case==
  
===Retrieving a specific plan===
+
See also [[IHERO_2007UseCase_Instance-level_Query_Retrieve|an older proposal]], which dates back to 2006.
 
 
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
 
  
 +
* Retrieve images, structures, plan from CTSim/Archive for planning
 +
* Retrieve secondary images from an archive or a modality to assist in planning
 +
* Retrieve plan and doses from other planning systems for comparison
 +
* Retrieve treatment records and verification images for offline review
 +
* Retrieve plan and dose for dose accumulation
 +
* Retrieve a complete set of patient treatment planning data for clinical trials submission
  
===Search for data with non-trivial relations===  
+
===Technical Considerations===
  
Define usage of relational queries in RT.
+
* speed of retrieval (multiple associations, asynchronous associations)
 +
* multiple sources of data
 +
* identification on patient/series/object level
 +
* relational dependencies of data (through registrations)
  
 
==4. Standards and Systems==
 
==4. Standards and Systems==

Latest revision as of 06:25, 29 October 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. One reason is the constantly increasing capability of imaging modalities of creating image information with smaller slice thicknesses, resulting in a higher number of slices. Another reason is the increasing number and variety of image series and related information.

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.

  • Retrieve images, structures, plan from CTSim/Archive for planning
  • Retrieve secondary images from an archive or a modality to assist in planning
  • Retrieve plan and doses from other planning systems for comparison
  • Retrieve treatment records and verification images for offline review
  • Retrieve plan and dose for dose accumulation
  • Retrieve a complete set of patient treatment planning data for clinical trials submission

Technical Considerations

  • speed of retrieval (multiple associations, asynchronous associations)
  • multiple sources of data
  • identification on patient/series/object level
  • relational dependencies of data (through registrations)

4. Standards and Systems

  • DICOM Standard Query/Retrieve model as defined in PS3.4

5. Discussion