|
|
| (8 intermediate revisions by the same user not shown) |
| Line 11: |
Line 11: |
|
| |
|
| ==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 Offline Recording (TDOR) Profile is an extension to the Treatment |
| | | Delivery Workflow - II (TDW-II) Profile dealing with the recording of treatment sessions in case |
| ''<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. .>''
| | of system outages and/or crashes. It is applicable for managed treatment sessions only, i.e., the |
| | | treatment sessions have to be initially scheduled in the TMS and retrieved by the TDD along the |
| ''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
| | transactions specified in TDW-II |
|
| |
|
| ==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.>''
| | The standardization of the recording process allows for a safe |
| | continuation of the next treatment session upon successful recovery of the system and the |
| | treatment artifacts. |
|
| |
|
| ==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.>''
| |
|
| |
| ''<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== | | ==Systems Affected== |
|
| |
|
| Line 44: |
Line 40: |
|
| |
|
| [https://www.ihe.net/uploadedFiles/Documents/Radiation_Oncology/IHE_RO_Suppl_TDOR.pdf TDOR Trial Implementation Supplement] | | [https://www.ihe.net/uploadedFiles/Documents/Radiation_Oncology/IHE_RO_Suppl_TDOR.pdf TDOR Trial Implementation Supplement] |
|
| |
|
| |
|
| '''Underlying Standards:''' | | '''Underlying Standards:''' |
| Line 50: |
Line 45: |
|
| |
|
| ==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.>''
| | * [[RT Treatment Delivery Workflow-II| Treatment Delivery Workflow (TDW-II)]] |
| | |
| * ''[[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 [[TDRO 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 [[TDOR 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 [[TDOR 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. >''
| |
|
| |
|
| [[Category:Profiles]]
| | |
| | |
|
| |
|
| This page is based on the [[Profile Overview Template]] | | This page is based on the [[Profile Overview Template]] |
|
| |
|
| [[Category:Templates]] | | [[Category:Profiles]] |
| <noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
| |
| | |
| <!--
| |
| Categorize the Domain of your Profile with one of the following (delete the rest):
| |
| [[Category:Cardiac Profile]]
| |
| [[Category:Dental Profile]]
| |
| [[Category:Endoscopy Profile]]
| |
| [[Category:Eye Profile]]
| |
| [[Category:ITI Profile]]
| |
| [[Category:PaLM Profile]]
| |
| [[Category:PCC Profile]]
| |
| [[Category:PCD Profile]]
| |
| [[Category:PHARM Profile]]
| |
| [[Category:QRPH Profile]]
| |
| [[Category:RO Profile]] | | [[Category:RO Profile]] |
| [[Category:RAD Profile]]
| |
|
| |
| Categorize key standards used in your Profile with one or more of the following (delete the rest):
| |
| [[Category:CDA]]
| |
| [[Category:FHIR]]
| |
| [[Category:DICOM]] | | [[Category:DICOM]] |
| [[Category:DICOMweb]]
| |
| [[Category:HL7v2]]
| |
| [[Category:XDW]]
| |
| [[Category:DocShare]]
| |
| [[Category:RFD]]
| |
| [[Category:HL7v3]]
| |
|
| |
| And if people forget to do this, we'll comment this out and you can forget to opt-in. :-)
| |
| -->
| |
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.
Summary
The Treatment Delivery Offline Recording (TDOR) Profile is an extension to the Treatment
Delivery Workflow - II (TDW-II) Profile dealing with the recording of treatment sessions in case
of system outages and/or crashes. It is applicable for managed treatment sessions only, i.e., the
treatment sessions have to be initially scheduled in the TMS and retrieved by the TDD along the
transactions specified in TDW-II
Benefits
The standardization of the recording process allows for a safe
continuation of the next treatment session upon successful recovery of the system and the
treatment artifacts.
Details
Systems Affected
- Treatment Delivery Device (TDD)
- Treatment Management System (TMS)
Actors & Transactions:
Specification
Profile Status: Trial Implementation
Documents:
TDOR Trial Implementation Supplement
Underlying Standards:
See Also
Related Profiles
Consumer Information
- The TDRO FAQ answers typical questions about what the Profile does
- The TDOR Purchasing describes considerations when purchasing equipment to deploy this Profile.
Implementer Information
- The TDOR Implementation provides additional information about implementing this Profile in software.
Reference Articles
This page is based on the Profile Overview Template
