Displayable Reports

<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

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

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

<See Help - Tips and Tricks for details on inserting an image/graphic.>

Benefits

<List the key benefits the profile provides (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>

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: Public Comment

A 2005 Supplement to the IHE Cardiology Technical Framework defined a new Displayable Reports Integration Profile (DRPT). It described a means to distribute “display ready” cardiology clinical reports from the department to the enterprise. During the Trial Implementation period of June 2005 through March 2006, inconsistencies were noted between the Profile and current understandings for the use of the HL7 Standard. Indeed, finding such inconsistencies is precisely the point of the Trial Implementation period. However, the IHE Cardiology Technical Committee has decided to reissue the Supplement with a major revision to the DRPT Profile. Because this reissued Supplement introduces substantive changes to the Profile’s Transactions, the DRPT Profile Connectathon results for 2006 will have a note that the Trial Implementation version of the Profile for that year is substantially different from the Profile in 2007 and subsequent years.

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:

• Vol. 1 - Section 5 (SWF Profile)
• Vol. 2 - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
• Vol. 3 - Appendix E

Underlying Standards:

<list all the standards on which the profile is based; if possible with links to sources>

• DICOM
• HL7
• ...

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 Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >

This page is based on the Profile Overview Template