Difference between revisions of "NTPL-S OLD (do not use)"
(→Details: first draft) |
|||
| Line 30: | Line 30: | ||
==Systems Affected== | ==Systems Affected== | ||
| − | + | Radiation Oncology PACS | |
| − | + | Treatment Planning Systems | |
| − | |||
| − | |||
'''Actors & Transactions:''' | '''Actors & Transactions:''' | ||
Revision as of 16:17, 3 April 2008
This is a template page. 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.
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 simple planning profile provides the structural mechanisms for the radiation therapy image based treatment planning process. Following image acquisition and archival storage of the image set, the profile defines the workflow and mechanisms utilized to create a patient’s treatment plan. The image set is retrieved and the relevant anatomical structures are contoured. The structure set is then stored and the user proceeds to define the geometrical elements (i.e. isocenter, bean angle, field size, etc.) of the proposed plan. Once the geometric characteristics are stored the user then defines the dosimetric properties (i.e. prescription, dose matrix, modeling algorithm, etc.) and calculates the dose. The user then displays the dose in a clinically useful manner (i.e. dose normalization, isodose distribution, dose volume histograms, etc.). The dosimetric plan is then stored to the archive.
Benefits
• Defines discrete processes of treatment planning for vendors
• Provides transactions required for interoperability between multi- vendor systems
• Provides a common process upon which more complex treatment planning can expand
Details
The profile provides a common process for vendors based on current DICOM standards. Transactions required between treatment planning system (TPS) components (actors) is defined. Simple planning is limited to the use of a CT image dataset, external beam photons, wedges and blocks/MLC (i.e. no IMRT, electronic compensators, bolus, electron beams, etc.).
The radiation oncology PACS is required to archive the single series image set, contours structure set, geometric plan, dosimetric plan, and dose under a unique identifier (UID) for each patient. The transactional process of storage and retrieval between the TPS archive, contourer, geometric planner, dosimetric planner, and dose displayer is what is specifically defined by this profile. The object of the profile is to ensure interoperability between vendors for each component which will allow users to move data between systems for maximum patient benefit.
Systems Affected
Radiation Oncology PACS
Treatment Planning Systems
Actors & Transactions:
<Insert an actor-transaction diagram, and or list of Content Definitions>
Specification
Profile Status: 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.>
IHE Radiology Technical Framework:
Underlying Standards:
<list all the standards on which the profile is based; if possible with links to sources>
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.>
- 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 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 something. You might be surprised. >
This page is based on the Profile Template