Multimodality Registration for Radiation Oncology: Difference between revisions

Revision as of 22:00, 3 April 2008

The Image Registration Integration Profile (REG) specifies communications between systems creating and registering image sets.

Summary

Transmitting registration information within the Radiation Oncology domain is becoming an increasingly important to the process of external beam radiation treatments. 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.

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. Coordination of data across the RT objects and registration of Image studies is discussed. A collection of DICOM objects exists to address the problem. Their use is constrained and clarified to avoid misinterpretation and promote compatibility.

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 how DICOM objects for spatial registration and the images themselves are created, stored, queried, retrieved, processed and displayed
Provides transactions required for interoperability between multi-vendor systems

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

Specification

Profile Status: Final Text

Documents:

IHE Radiation Oncology Technical Framework:

Vol. 1 - Section 3 and Appendix A & B
Radiology registration profile

Underlying Standards:

DICOM
DICOM-RT <add a link for DICOM-RT or DICOM Working Group 7>
HL7

@@ Line 1: / Line 1: @@
-{{{1|'''This is a template page.  [[:Category:Templates|CLICK HERE]] if you're not sure how to use it.  DO NOT MODIFY this page unless you are changing the template for all future users.'''
+'''The ''Image Registration Integration Profile (REG)'' specifies communications between systems creating and registering image sets.'''<br>
+<br>
-''This template is for the one or two page user-oriented overview of an IHE Profile that is in Final Text, Trial Implementation or perhaps Public Comment.  Delete text in italics and replace it with your material.  Don't forget to delete the double quotes too.''
-''Your page name should simply be Full Profile Name with spaces, with capitals, without the acronym. e.g. Scheduled Workflow. so it provides a title to the page. You can redirect the acronym to the full named page if you like for bonus points.''
-''<IN ONE LINE, tell a user what the profile is about (including the acronym) so they can decide if they're on the right page.  Basically this should be the same sentence that appears on the [[Profiles]] catalog page>''
-''e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.''
-}}}
 __TOC__
 ==Summary==
-{{{2|''<Describe the profile in about a paragraph using user-oriented language.  Focus on what it accomplishes for a user (i.e. the Use Cases).  Don't get into how it works, leave that to the Details section.>''}}}
+Transmitting registration information within the Radiation Oncology domain is becoming an increasingly important to the process of external beam radiation treatments. 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.
-''<Insert a simple graphic that, at a glance, visually summarizes what the profile is about.  Do not use an actor/transaction diagram here.  Show your graphic to someone for 5 seconds (literally) and ask them what it's about.  If what they say hits the main points in your summary paragraph, you have succeeded.  E.g. a graphic of a hospital, a clinic, and a lab with patient records moving between them.  .>''
+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. Coordination of data across the RT objects and registration of Image studies is discussed. A collection of DICOM objects exists to address the problem. Their use is constrained and clarified to avoid misinterpretation and promote compatibility.
-''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
+[[image:RT_planning_process.jpg|frame|100px|right|Counterclock wise from the top left: CT dataset is retrieved, a contour is drawn, a field is placed, dose is calculated and displayed. ]]
 ==Benefits==
-''<List the key benefits the profile provides (e.g. error reduction, increased throughput) and how they come about (e.g. SWF reduces patient errors due to mistyped demographics at the modality by transfering demographics electronically from the Order Filler).  Consider using a bullet list for readability>''
+* defines how DICOM objects for spatial registration and the images themselves are created, stored, queried, retrieved, processed and displayed
+* Provides transactions required for interoperability between multi-vendor systems
+*
 ==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.
+<br>
+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.
+<br>
+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.
+<br>
+[[image:RT_NTPLS_transactions.jpg|frame|100px|right| Actors and Transactions. ]]
-''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
-''<If the user might be familiar with the mechanisms used by the profile, you can mention them here.  E.g. Evidence Documents is based on DICOM Structured Report (SR) Templates.>''
-''<If the user might have an appreciation for the problems addressed in the profile, you can mention them here, but keep it short.  E.g. Mapping HL7 Order fields to DICOM Modality Worklist attributes can be inconsistent in the marketplace, so Scheduled Workflow provides vendors with more detailed instructions.>''
 ==Systems Affected==
-''<List (in user terms) the types of systems they might expect to have implemented actors from this profile, e.g. RIS, PACS, HIS, CAD Workstation, etc. and for each, how it would participate.>''
+* Radiation Oncology PACS
+* Treatment Planning Systems
-* ''PACS systems may store, manage, and/or display Evidence Documents.''
-* ''Display systems may query, retrieve and display Evidence Documents.''
-* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
-'''Actors & Transactions:'''
-''<Insert an actor-transaction diagram, and or list of Content Definitions>''
 ==Specification==
 '''Profile Status:''' [[Comments| Final Text]]
-''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
 '''Documents:'''
-''<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile.  This is a simple inventory of official normative and informative text.  If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below.  If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>''
+[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 Vol. 1] - Section 3 and Appendix A & B
-[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
+:* Radiology registration profile
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
-:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 '''Underlying Standards:'''
-''<list all the standards on which the profile is based; if possible with links to sources>''
 :* [http://dicom.nema.org DICOM]
+:* [http://??? DICOM-RT] <add a link for DICOM-RT or DICOM Working Group 7>
 :* [http://www.hl7.org HL7]
-:* ...
 ==See Also==
-''<The following sections can be left out if there is nothing to point to.  This is just to show where such information can go.>''
 '''Related Profiles'''
-''<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one.  Start with the name of the other profile as a link and then explain the relationship.>''
+* ''[[Normal Treatment Planning (Simple) NTPL-S]] may use ....''  <link will be added by Colin later>
+* ''[[Managed Delivery Workflow]]  may include ....'' <link will be added by Colin later>
-* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
-* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
-* ''[[Cross-enterprise Document Sharing for Imaging]] [XDS-I] can be used to share Evidence Documents between sites over a network.''
-* ''[[Portable Data for Imaging]] [PDI] can store Evidence Documents on media such as CDs.''
-* ''[[Import Reconciliation Workflow]] [IRWF] can fix patient ids, etc. of Evidence Documents when importing.''
 '''Consumer Information'''
-The [[{{{3|Profile FAQ Template}}}]] answers typical questions about what the Profile does.  ''<Replace the link with a link to the actual FAQ page for the Profile>''
+* The [[NTPL-S_FAQ|NTPL-S FAQ]] answers typical questions about what the Profile does.
+* The [[NTPL-S_Purchasing|NTPL-S Purchasing ]] describes considerations when purchasing equipment to deploy this Profile.
-The [[{{{3|Profile Purchasing Template}}}]] describes considerations when purchasing equipment to deploy this Profile.  ''<Replace the link with a link to the actual Purchasing page for the Profile>''
 '''Implementer Information'''
+* The [[NTPL-S_Implementation|NTPL-S Implementation]] provides additional information about implementing this Profile in software.
-The [[{{{3|Profile Implementation Template}}}]] provides additional information about implementing this Profile in software.  ''<Replace the link with a link to the actual Implementation page for the Profile>''
 '''Reference Articles'''
 ''<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis).  Go ahead, Google: IHE <Profile Name> abstract   or something.  You might be surprised. >''
 This page is based on the [[Profile Template]]
 [[Category:Profiles]]