Treatment Planning Plan Content: Difference between revisions

From IHE Wiki
Jump to navigation Jump to search
Jpercy (talk | contribs)
Jpercy (talk | contribs)
Line 2: Line 2:


==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 profile describes the RT Plan content exchanged between Treatment Planning Systems (TPS), Treatment
 
Management Systems (TMS) or other TPS's. The purpose for this profile is to ensure accurate and automatic
 
transfer of the planning information into the treatment management system for treatment delivery without
''<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.  .>''
ambiguity and human data entry or into another TPS for re-calculation or re-planning.  
 
This profile addresses a broad variety of treatment techniques that exist in Radiation Therapy. The Treatment
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
Planning System is responsible to provide all Beam Parameters (including SRS cones, wedges, and other
accessories) pertinent to the treatment technique applied for a specific plan. This information must be
seamlessly transferred from the TPS to the TMS and from one TPS to another.


==Benefits==
==Benefits==

Revision as of 11:59, 27 December 2023

Summary

This profile describes the RT Plan content exchanged between Treatment Planning Systems (TPS), Treatment Management Systems (TMS) or other TPS's. The purpose for this profile is to ensure accurate and automatic transfer of the planning information into the treatment management system for treatment delivery without ambiguity and human data entry or into another TPS for re-calculation or re-planning. This profile addresses a broad variety of treatment techniques that exist in Radiation Therapy. The Treatment Planning System is responsible to provide all Beam Parameters (including SRS cones, wedges, and other accessories) pertinent to the treatment technique applied for a specific plan. This information must be seamlessly transferred from the TPS to the TMS and from one TPS to another.

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.>

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.>

<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.>

  • 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: Final Text

Documents: RO Framework

Underlying Standards: DICOM

See Also

Related Profiles

Consumer Information

Reference Articles




This page is based on the Profile Overview Template