Difference between revisions of "Treatment Planning - Plan Content"

From IHE Wiki
Jump to navigation Jump to search
 
(10 intermediate revisions by 3 users not shown)
Line 3: Line 3:
  
 
==Summary==
 
==Summary==
−
''<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.>''
+
This integration profile involves the exchange of RT Plan information between treatment planning systems and between treatment planning systems and treatment management systems.
−
 
 
−
''<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.  .>''
 
−
 
 
−
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
 
  
 
==Benefits==
 
==Benefits==
−
''<If the profile can improve Cost, Safety, Quality or Efficiency then list the specific examples of that benefit (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.  Such benefits help users and vendors make the business case for the profile.  If the profile does not improve any aspect of Cost, Safety, Quality or Efficiency feel free to talk about something else here.>''
+
This profile aims to reduce ambiguity in re-planning and delivering planning information with fidelity and consistency to the treatment management system in anticipation of transfer to a treatment delivery system.
  
 
==Details==
 
==Details==
  
−
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+
This profile addresses a broad variety of “Beam Techniques” that exist in Radiation Therapy. Rather than define actors that had broad involvement in many optional transactions, a large number of actors were defined which have specific mandatory/required transactions and a small number of optional transactions related to beam modifiers. The actors are either producers or consumers of a DICOM RT Plan.
  
−
''<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.>''
+
==Systems Affected==
  
−
''<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.>''
 
  
−
* ''PACS systems may store, manage, and/or display Evidence Documents.''
+
* Treatment Planning Systems will implement one or more of the “producer” actors and / or the "consumer" actors
−
* ''Display systems may query, retrieve and display Evidence Documents.''
+
**    The actors implemented will depend on the intended functionality
−
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
+
**    If a Treatment Planning System will read other Planning System plans, then it should implement the behavior of the intended "consumer"
 +
* Oncology Information Systems, Oncology Information Management, or Electronic Medical Record for Oncology will implement many "consumer" actors i.e., consume many Beam Techniques.
 +
* Other systems such as QA Systems may implement these beam consumer actors as well.
  
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
  
−
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+
* Basic Static Beam Storage
 +
* Basic Static Beam Retrieval
 +
* Basic Static MLC Beam Storage
 +
* Basic Static MLC Beam Retrieval
 +
* Arc Beam Storage
 +
* Arc Beam Retrieval
 +
* MLC Fixed Aperture Arc Beam Storage
 +
* MLC Fixed Aperture Arc Beam Retrieval
 +
* MLC Variable Aperture Arc Beam Storage
 +
* MLC Variable Aperture Arc Beam Retrieval
 +
* Hard Wedge Beam Storage
 +
* Hard Wedge Beam Retrieval
 +
* Virtual Wedge Beam Storage
 +
* Virtual Wedge Beam Retrieval
 +
* Motorized Wedge Beam Storage
 +
* Motorized Wedge Beam Retrieval
 +
* Static Electron Beam Storage
 +
* Static Electron Beam Retrieval
 +
* Step & Shoot Beam Storage
 +
* Step & Shoot Beam Retrieval
 +
* Sliding Window Beam Storage
 +
* Sliding Window Beam Retrieval
 +
* IMAT/VMAT Beam Storage
 +
* IMAT/VMAT Beam Retrieval
 +
* Photon Applicator Beam Storage
 +
* Photon Applicator Beam Retrieval
 +
* Photon Applicator Arc Beam Storage
 +
* Photon Applicator Arc Beam Retrieval
  
 
==Specification==
 
==Specification==
  
−
'''Profile Status:''' [[Comments| Final Text]]   
+
'''Profile Status:''' [[Comments| Final Text]]  (Technical Framework integration is underway)
−
''<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#radiology IHE Radiology Technical Framework:]
 
−
:* [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:'''
 
'''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.nema.org DICOM]
−
:* [http://www.hl7.org HL7]
 
−
:* ...
 
  
 
==See Also==
 
==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'''
 
'''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.>''
+
* [[Basic_Radiation_Therapy_Objects-II]] (BRTO-II)  Provides base requirements for Structure Set and RT Plan Objects.
−
 
 
−
* ''[[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 and Implementer Information'''
  
−
'''Consumer Information'''
+
* [http://ihe-ro.org/doku.php?id=doc:profiles IHE-RO Profiles] including the TPPC profile.
−
 
 
−
The [[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 [[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 [[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 Google: IHE <Profile Name> and under the "more" select "Scholar".  You might be surprised. >''
 
−
 
 
  
  
 
This page is based on the [[Profile Overview Template]]
 
This page is based on the [[Profile Overview Template]]
  
−
[[Category:Template]]
+
[[Category:Profiles]]
−
 
+
[[Category:RO Profile]]
−
<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
+
[[Category:DICOM]]

Latest revision as of 16:52, 2 December 2019

Summary

This integration profile involves the exchange of RT Plan information between treatment planning systems and between treatment planning systems and treatment management systems.

Benefits

This profile aims to reduce ambiguity in re-planning and delivering planning information with fidelity and consistency to the treatment management system in anticipation of transfer to a treatment delivery system.

Details

This profile addresses a broad variety of “Beam Techniques” that exist in Radiation Therapy. Rather than define actors that had broad involvement in many optional transactions, a large number of actors were defined which have specific mandatory/required transactions and a small number of optional transactions related to beam modifiers. The actors are either producers or consumers of a DICOM RT Plan.

Systems Affected

  • Treatment Planning Systems will implement one or more of the “producer” actors and / or the "consumer" actors
    • The actors implemented will depend on the intended functionality
    • If a Treatment Planning System will read other Planning System plans, then it should implement the behavior of the intended "consumer"
  • Oncology Information Systems, Oncology Information Management, or Electronic Medical Record for Oncology will implement many "consumer" actors i.e., consume many Beam Techniques.
  • Other systems such as QA Systems may implement these beam consumer actors as well.

Actors & Transactions:

  • Basic Static Beam Storage
  • Basic Static Beam Retrieval
  • Basic Static MLC Beam Storage
  • Basic Static MLC Beam Retrieval
  • Arc Beam Storage
  • Arc Beam Retrieval
  • MLC Fixed Aperture Arc Beam Storage
  • MLC Fixed Aperture Arc Beam Retrieval
  • MLC Variable Aperture Arc Beam Storage
  • MLC Variable Aperture Arc Beam Retrieval
  • Hard Wedge Beam Storage
  • Hard Wedge Beam Retrieval
  • Virtual Wedge Beam Storage
  • Virtual Wedge Beam Retrieval
  • Motorized Wedge Beam Storage
  • Motorized Wedge Beam Retrieval
  • Static Electron Beam Storage
  • Static Electron Beam Retrieval
  • Step & Shoot Beam Storage
  • Step & Shoot Beam Retrieval
  • Sliding Window Beam Storage
  • Sliding Window Beam Retrieval
  • IMAT/VMAT Beam Storage
  • IMAT/VMAT Beam Retrieval
  • Photon Applicator Beam Storage
  • Photon Applicator Beam Retrieval
  • Photon Applicator Arc Beam Storage
  • Photon Applicator Arc Beam Retrieval

Specification

Profile Status: Final Text (Technical Framework integration is underway)

Underlying Standards:

See Also

Related Profiles

Consumer and Implementer Information


This page is based on the Profile Overview Template

Retrieved from "http://wiki.ihe.net/index.php?title=Treatment_Planning_-_Plan_Content&oldid=119130"