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

Revision as of 02:56, 26 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. 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.

Retrieve images, structures, plan from CTSim/Archive for planning
Query PACS or modality for secondary imaging for planning
Plan with additional info from another TPS
A TPS retrieves the plan and related treatment records, RT Structure Sets, image series, SROs from a TMS
Retrieve plan and dose for dose accumulation
Retrieve the latest RT Course from the TMS

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

@@ Line 22: / Line 22: @@
 See also [[IHERO_2007UseCase_Instance-level_Query_Retrieve|an older proposal]], which dates back to 2006.
-===Retrieving a specific plan===
+* Retrieve images, structures, plan from CTSim/Archive for planning
+* Query PACS or modality for secondary imaging for planning
+* Plan with additional info from another TPS
+* A TPS retrieves the plan and related treatment records, RT Structure Sets, image series, SROs from a TMS
+* Retrieve plan and dose for dose accumulation
+* Retrieve the latest RT Course from the TMS
-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.
+===Technical Considerations===
-===Retrieving large image sets===
+* speed of retrieval (multiple associations, asynchronous associations)
+* multiple sources of data
-Define usage of asynchronous associations or multiple associations in order to transfer large image data sets
+* identification on patient/series/object level
+* relational dependencies of data (through registrations)
-===Search for data with non-trivial relations===
-Define usage of relational queries in RT.
 ==4. Standards and Systems==