Planning and Delivery of Radiation
The purpose of the Planning and Delivery of Radiation (PDR) profile is to provide a standard approach for exchange of information related to radiation treatments. This kind of exchange enables greater unity between a patient’s Radiation Oncology Information System (ROIS) chart and the corresponding chart in the broader Health Information System (HIS). This assists providers who work primarily in the HIS to review information about their patients’ radiation treatments, and providers who work primarily in the ROIS to receive relevant patient details around planning treatments. Moreover, administrative functions run from the HIS, like data analytics, chart coding and release of information, can also include radiation information without requiring users to log in to multiple systems and manually synthesize data from multiple sources.
Radiation therapy is a complex domain. Many organizations manage the planning and administration of such therapy electronically using dedicated specialty software systems. A Radiation Oncology Information System (ROIS) enables users to perform complex and specialized tasks related to the planning and delivery of radiation. At the same time, many healthcare organizations keep a single comprehensive health record for patients in a centralized software system, such as a Hospital Information System (HIS), which provides information access for users across disciplines so that all providers can make well-informed decisions about each patient’s care.
A provider wanting the complete picture of a patient would need access to both the ROIS and the HIS. Challenges with providing access and training for providers in both systems can lead to impediments for care. Some systems mitigate this risk through the use of other interoperability methods such as exchanging scheduling and charging data. The remaining gaps in information, however, are substantial and are often addressed by double documentation—identical data manually entered in two systems—if they are addressed at all.
The purpose of the Planning and Delivery of Radiation (PDR) profile is to provide a standard approach for exchange of information related to radiation treatments. This kind of exchange enables greater unity between a patient’s ROIS chart and the corresponding chart in the broader HIS. This assists providers who work primarily in the HIS to review information about their patients’ radiation treatments, and providers who work primarily in the ROIS to receive relevant patient details around planning treatments. Moreover, administrative functions run from the HIS, like data analytics, chart coding and release of information, can also include radiation information without requiring users to log in to multiple systems and manually synthesize data from multiple sources.
<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.>
<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>
Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>
<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.>
<list all the standards on which the profile is based; if possible with links to sources>
<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>
<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.
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>
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>
<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