Difference between revisions of "Basic Radiation Therapy Objects"

From IHE Wiki
Jump to navigation Jump to search
Line 1: Line 1:
'''The ''Normal Treatment Planning (Simple) profile (NTPL-S)'' defines the process and mechanisms for image based (3 dimensional) radiation therapy treatment planning. '''<br>
+
'''Normal Treatment Planning - Simple (NTPL-S)'' defines the process and mechanisms for image based (3 dimensional) radiation therapy treatment planning.
<br>
+
 
 +
 
 
__TOC__
 
__TOC__
  
Line 11: Line 12:
  
 
* Defines discrete processes of treatment planning for vendors
 
* Defines discrete processes of treatment planning for vendors
* Provides transactions required for interoperability between multi-vendor systems
 
 
* Provides a common process upon which more complex treatment planning can expand
 
* Provides a common process upon which more complex treatment planning can expand
  
Line 19: Line 19:
 
A radiation oncology PACS is required to archive the single series image set, contours structure set, geometric plan, dosimetric plan, and dose under a unique identifier (UID) for each patient.  The transactional process of storage and retrieval between the TPS archive, contourer, geometric planner, dosimetric planner, and dose displayer is what is specifically defined by this profile. The object of the profile is to ensure interoperability between vendors for each component which will allow users to move data between systems for maximum patient benefit.
 
A radiation oncology PACS is required to archive the single series image set, contours structure set, geometric plan, dosimetric plan, and dose under a unique identifier (UID) for each patient.  The transactional process of storage and retrieval between the TPS archive, contourer, geometric planner, dosimetric planner, and dose displayer is what is specifically defined by this profile. The object of the profile is to ensure interoperability between vendors for each component which will allow users to move data between systems for maximum patient benefit.
  
[[image:RT_NTPLS_transactions.jpg|frame|right| Actors and Transactions for this profile. ]]
 
  
 
==Systems Affected==
 
==Systems Affected==
 
* Radiation Oncology PACS
 
* Radiation Oncology PACS
 
* Treatment Planning Systems
 
* Treatment Planning Systems
 +
 +
'''Actors & Transactions:'''
 +
 +
[[image:RT_NTPLS_transactions.jpg]]
  
 
==Specification==
 
==Specification==
Line 29: Line 32:
 
'''Profile Status:''' [[Comments| Final Text]]   
 
'''Profile Status:''' [[Comments| Final Text]]   
  
 
+
'''Documents:''' [http://www.ihe.net/Technical_Framework/index.cfm#rad_onc IHE Radiation Oncology Technical Framework:]
'''Documents:'''  
 
 
 
[http://www.ihe.net/Technical_Framework/index.cfm#rad_onc IHE Radiation Oncology Technical Framework:]
 
 
* [http://www.ihe.net/Technical_Framework/upload/IHE_RO_TF_v1.pdf IHE-RO Technical Frameworks 1.0] - Section 3 and Appendix A & B
 
* [http://www.ihe.net/Technical_Framework/upload/IHE_RO_TF_v1.pdf IHE-RO Technical Frameworks 1.0] - Section 3 and Appendix A & B
 
* [ftp://ftp.ihe.net/RadiationOncology/IHE_2007/IHE_RO_Volumes1and2_2007_v1.6_TI.pdf IHE-RO Technical Frameworks 1.6]
 
* [ftp://ftp.ihe.net/RadiationOncology/IHE_2007/IHE_RO_Volumes1and2_2007_v1.6_TI.pdf IHE-RO Technical Frameworks 1.6]

Revision as of 14:49, 23 May 2008

'Normal Treatment Planning - Simple (NTPL-S) defines the process and mechanisms for image based (3 dimensional) radiation therapy treatment planning.


Summary

This profile provides the structural mechanisms for the radiation therapy image based treatment planning process. Following image acquisition and archival storage of the image set, the profile defines the workflow and mechanisms utilized to create a patient’s treatment plan. The single or multi-series image set is retrieved and the relevant anatomical structures are contoured. The structure set is then stored and the user proceeds to define the geometrical elements (i.e. isocenter, beam angle, field size, etc.) of the proposed plan. Once the geometric characteristics are stored the user then defines the dosimetric properties (i.e. prescription, dose matrix, modeling algorithm, etc.) and calculates the dose. The user then displays the dose in a clinically useful manner (i.e. dose normalization, isodose distribution, dose volume histograms, etc.). The dosimetric plan is then stored to the archive.

Counterclock wise from the top left: CT dataset is retrieved, a contour is drawn, a field is placed, dose is calculated and displayed.

Benefits

  • Defines discrete processes of treatment planning for vendors
  • Provides a common process upon which more complex treatment planning can expand

Details

The profile provides a common process for vendors based on current DICOM standards. Transactions required between treatment planning system (TPS) components (actors) is defined. Simple planning is limited to the use of a CT image dataset, external beam photons, wedges and blocks/MLC (i.e. no IMRT, electronic compensators, bolus, electron beams, etc.).

A radiation oncology PACS is required to archive the single series image set, contours structure set, geometric plan, dosimetric plan, and dose under a unique identifier (UID) for each patient. The transactional process of storage and retrieval between the TPS archive, contourer, geometric planner, dosimetric planner, and dose displayer is what is specifically defined by this profile. The object of the profile is to ensure interoperability between vendors for each component which will allow users to move data between systems for maximum patient benefit.


Systems Affected

  • Radiation Oncology PACS
  • Treatment Planning Systems

Actors & Transactions:

RT NTPLS transactions.jpg

Specification

Profile Status: Final Text

Documents: IHE Radiation Oncology Technical Framework:

Underlying Standards:

See Also

Related Profiles

Consumer Information

  • The NTPL-S FAQ answers typical questions about what the Profile does.
  • The NTPL-S Purchasing describes considerations when purchasing equipment to deploy this Profile.

Implementer Information


This page is based on the Profile Template