Multimodality Registration for Radiation Oncology: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
' | '''Multimodality Registration for Radiation Oncology (MMR-RO)''' registers image sets specifically for Radiation Oncology. | ||
__TOC__ | __TOC__ | ||
| Line 10: | Line 10: | ||
* defines how DICOM objects for spatial registration and the images themselves are created, stored, queried, retrieved, processed and displayed | * defines how DICOM objects for spatial registration and the images themselves are created, stored, queried, retrieved, processed and displayed | ||
==Details== | ==Details== | ||
This Integration Profile specifies how images, RT Structure Sets, RT Doses, and associated spatial registration information can be exchanged, stored, processed and displayed. For a display workstation, it is essential that a workstation correctly identifies the corresponding image sets, matches data from single-slice and multi-slice datasets, matches coordinate systems, and performs spatial translations. The use of relevant DICOM objects (Spatial Registration) is clarified and constrained in order to avoid misinterpretation. | This Integration Profile specifies how images, RT Structure Sets, RT Doses, and associated spatial registration information can be exchanged, stored, processed and displayed. For a display workstation, it is essential that a workstation correctly identifies the corresponding image sets, matches data from single-slice and multi-slice datasets, matches coordinate systems, and performs spatial translations. The use of relevant DICOM objects (Spatial Registration) is clarified and constrained in order to avoid misinterpretation. | ||
Image Registration Integration Profile focuses on content for image registration and does not define a registration workflow. Such workflow could be managed by using mechanisms described in the Post-Processing Workflow Integration Profile. | Image Registration Integration Profile focuses on content for image registration and does not define a registration workflow. Such workflow could be managed by using mechanisms described in the Post-Processing Workflow Integration Profile. | ||
The Image Registration Integration Profile currently only handles rigid registration. The intention is to add deformable registration as an extension to the Profile in the future. | The Image Registration Integration Profile currently only handles rigid registration. The intention is to add deformable registration as an extension to the Profile in the future. | ||
The Image Registration Profile does not specify the use of quantification methods for the image data that is created or displayed. In particular interoperability for PET Standard Uptake Values (SUV) is considered a relevant future work item for IHE. Note that vendors may wish to prodovide SUV capability even though not required under this Profile. | The Image Registration Profile does not specify the use of quantification methods for the image data that is created or displayed. In particular interoperability for PET Standard Uptake Values (SUV) is considered a relevant future work item for IHE. Note that vendors may wish to prodovide SUV capability even though not required under this Profile. | ||
==Systems Affected== | ==Systems Affected== | ||
* Radiation Oncology PACS | * Radiation Oncology PACS | ||
* Treatment Planning Systems | * Treatment Planning Systems | ||
'''Actors and Transactions:''' | |||
[[image:RT_REG_transactions2.jpg|frame|100px|right| Actors and Transactions defined in the Radiology Fusion profile. ]] | |||
''<The Fusion Profile doesn't actually define any of those actors>'' | |||
[[image:RT_REG_transactions.jpg]] | |||
==Specification== | ==Specification== | ||
'''Profile Status:''' [[Comments| | '''Profile Status:''' [[Comments| Trial Implementation]] | ||
[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_Supplement_Image_Registration_PublicComment_2007_08_20.pdf Image Registration Supplement] - Chapter 4 and Appendix A & B | * [http://www.ihe.net/Technical_Framework/upload/IHE_RO_TF_Supplement_Image_Registration_PublicComment_2007_08_20.pdf Image Registration Supplement] - Chapter 4 and Appendix A & B | ||
* [http://www.ihe.net/Technical_Framework/upload/IHE_RAD-TF_Suppl_FUS_TI_2006-04-13.pdf Radiology Image Fusion profile (FUS)] - Chapter 3 | * [http://www.ihe.net/Technical_Framework/upload/IHE_RAD-TF_Suppl_FUS_TI_2006-04-13.pdf Radiology Image Fusion profile (FUS)] - Chapter 3 | ||
| Line 48: | Line 53: | ||
'''Related Profiles''' | '''Related Profiles''' | ||
* | * [[Normal Treatment Planning-Simple]] (NTPL-S) ''<describe the nature of the relationship between this profile and MMR-RO>'' | ||
* | * [[RT Treatment Workflow]] (TRWF) ''<describe the nature of the relationship between this profile and NTPL-S>'' | ||
* | * [[Image Fusion]] (FUS) provides some of the actors and transactions required by this profile. | ||
'''Consumer Information''' | '''Consumer Information''' | ||
Revision as of 15:09, 23 May 2008
Multimodality Registration for Radiation Oncology (MMR-RO) registers image sets specifically for Radiation Oncology.
Summary
Transmitting registration information within the Radiation Oncology domain is becoming an increasingly important to the process of external beam radiation treatments. Currently, registration can be performed on individual workstations designed for that purpose and planning systems, but the results are not readily transferable between systems, often due either to proprietary or inconsistent implementations. This profile addresses the ability to convey registered data from one system to another for further processing. This profile addresses issues dealing with multiple coordinate systems but does not specifically address the issue of repeatable fused displays. A collection of DICOM objects exists to address the problem. Their use is constrained and clarified to avoid misinterpretation and promote compatibility.
Benefits
- defines how DICOM objects for spatial registration and the images themselves are created, stored, queried, retrieved, processed and displayed
Details
This Integration Profile specifies how images, RT Structure Sets, RT Doses, and associated spatial registration information can be exchanged, stored, processed and displayed. For a display workstation, it is essential that a workstation correctly identifies the corresponding image sets, matches data from single-slice and multi-slice datasets, matches coordinate systems, and performs spatial translations. The use of relevant DICOM objects (Spatial Registration) is clarified and constrained in order to avoid misinterpretation.
Image Registration Integration Profile focuses on content for image registration and does not define a registration workflow. Such workflow could be managed by using mechanisms described in the Post-Processing Workflow Integration Profile.
The Image Registration Integration Profile currently only handles rigid registration. The intention is to add deformable registration as an extension to the Profile in the future.
The Image Registration Profile does not specify the use of quantification methods for the image data that is created or displayed. In particular interoperability for PET Standard Uptake Values (SUV) is considered a relevant future work item for IHE. Note that vendors may wish to prodovide SUV capability even though not required under this Profile.
Systems Affected
- Radiation Oncology PACS
- Treatment Planning Systems
Actors and Transactions:
<The Fusion Profile doesn't actually define any of those actors>
Specification
Profile Status: Trial Implementation
Documents: IHE Radiation Oncology Technical Framework:
- Image Registration Supplement - Chapter 4 and Appendix A & B
- Radiology Image Fusion profile (FUS) - Chapter 3
Underlying Standards:
See Also
Related Profiles
- Normal Treatment Planning-Simple (NTPL-S) <describe the nature of the relationship between this profile and MMR-RO>
- RT Treatment Workflow (TRWF) <describe the nature of the relationship between this profile and NTPL-S>
- Image Fusion (FUS) provides some of the actors and transactions required by this profile.
Consumer Information
- The MMR-RO FAQ answers typical questions about what the Profile does.
- The MMR-RO Purchasing describes considerations when purchasing equipment to deploy this Profile.
Implementer Information
- The MMR-RO Implementation provides additional information about implementing this Profile in software.
This page is based on the Profile Template