|
|
| (7 intermediate revisions by the same user not shown) |
| 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.>''
| | The Treatment Delivery Record Content (TDRC) Profile specifies the content of the RT Beams |
| | Treatment Record being transferred from the Treatment Delivery Record Producer storage to the |
| | Treatment Record Consumer. |
| | It will: |
|
| |
|
| | *make the therapists’ workflow easier and faster, because it incorporates all information needed for treatment delivery record keeping. |
| | *enable therapists to concentrate more on finalizing the details of patient treatment rather dealing with technical issues. |
| | *reduce the time physicists and therapists need to gather and review treatment delivery information. |
|
| |
|
| ''<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. .>''
| | The profile will not specify how to validate the treatment delivery parameters, but will ensure that they are available, and well formatted. |
| | |
| ''<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.>''
| | TDRC contributes to patient safety, because it will standardize the content which is reviewed to |
| | assess if delivery of treatment was accurate to the plan. |
|
| |
|
| ==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.>''
| | ==Systems Affected== |
| | |
| ''<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.>'' | | * ''Treatment Delivery Devices (TDD)'' |
|
| | * ''Treatment Management Systems (TMS)'' |
| ==Systems Affected==
| | * ''Treatment Planning Systems (TPS)'' |
| ''<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.>'' | | * ''Quality Assurance 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:''' | | '''Actors & Transactions:''' |
|
| |
|
| ''<Insert an actor-transaction diagram, and or list of Content Definitions>''
| | [[File:TDRC_Actor_Transaction_Diagram.JPG]] |
|
| |
|
| ==Specification== | | ==Specification== |
| Line 43: |
Line 43: |
|
| |
|
| ==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.>''
| |
|
| |
| * ''[[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''' | | '''Consumer Information''' |
|
| |
|
| 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 [[TDRC FAQ]] answers typical questions about what the Profile does. |
|
| |
|
| 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>'' | | * The [[TDRC Purchasing]] describes considerations when purchasing equipment to deploy this Profile. |
|
| |
|
| '''Implementer Information''' | | '''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>'' | | * The [[TDRC Implementation]] provides additional information about implementing this Profile in software. |
|
| |
|
| '''Reference Articles''' | | '''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. >''
| |
|
| |
|
|
| |
|
| Line 80: |
Line 68: |
| [[Category:RO Profile]] | | [[Category:RO Profile]] |
| [[Category:DICOM]] | | [[Category:DICOM]] |
| [[Category:RO todo]]
| |
Summary
The Treatment Delivery Record Content (TDRC) Profile specifies the content of the RT Beams
Treatment Record being transferred from the Treatment Delivery Record Producer storage to the
Treatment Record Consumer.
It will:
- make the therapists’ workflow easier and faster, because it incorporates all information needed for treatment delivery record keeping.
- enable therapists to concentrate more on finalizing the details of patient treatment rather dealing with technical issues.
- reduce the time physicists and therapists need to gather and review treatment delivery information.
The profile will not specify how to validate the treatment delivery parameters, but will ensure that they are available, and well formatted.
Benefits
TDRC contributes to patient safety, because it will standardize the content which is reviewed to
assess if delivery of treatment was accurate to the plan.
Details
Systems Affected
- Treatment Delivery Devices (TDD)
- Treatment Management Systems (TMS)
- Treatment Planning Systems (TPS)
- Quality Assurance Systems
Actors & Transactions:
Specification
Profile Status: Trial Implementation
Documents:
Underlying Standards:
See Also
Related Profiles
Consumer Information
- The TDRC FAQ answers typical questions about what the Profile does.
- The TDRC Purchasing describes considerations when purchasing equipment to deploy this Profile.
Implementer Information
- The TDRC Implementation provides additional information about implementing this Profile in software.
Reference Articles
This page is based on the Profile Overview Template
