Difference between revisions of "Displayable Reports"

From IHE Wiki
Jump to navigation Jump to search
 
(11 intermediate revisions by 3 users not shown)
Line 1: Line 1:
''<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>''
+
Displayable Reports (DRPT) manages creation and distribution of “display ready” (PDF or CDA) clinical reports from the creating application, to the department, and to the enterprise.
  
''e.g. Scheduled Workflow (SWF) integrates ordering, scheduling, imaging acquisition, storage and viewing for Radiology exams.''
 
  
 
__TOC__
 
__TOC__
  
 
==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.>''
 
  
''<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 Displayable Reports Profile supports the creation, revision, intra/inter-department transmission, and reading of display-ready clinical reports. In the imaging procedure context, it provides linkage between the report, the imaging and other evidence of the procedure. The report is provided to actors outside the department for broad distribution (e.g., using other profiles such as XDS or RID).  
  
''<See [[Help:Contents#Tips_.26_Tricks| Help - Tips and Tricks]] for details on inserting an image/graphic.>''
+
The DRPT Profile requires the use of the Portable Document Format (PDF) or the HL7 Clinical Document Architecture (CDA), which are both means of encoding documents ready for presentation, including graphical content. For reporting on imaging procedures, especially on cardiac procedures, they are able to present the full range of documentation generated by a wide variety of reporting packages.
  
 
==Benefits==
 
==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>''
+
The DRPT profile defines a consistent approach to handling report creation and management. This allows independently developed analysis applications to be used seemlessly in departmental workflow, and thus enables clinicians to purchase best of breed reporting applications.
 +
 
 +
The profile also defines a mechanism for archiving reports in the PACS. This allows leveraging the robust srchival capabilities of the PACS, as well as aggregation of the complete imaging study data (images, analyses, and reports) in a consistent format and single locationThis facilitates subsequent single point access to the study for coparison or export.
  
 
==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.>''
+
The most common displayable report format currently in use is PDF, which allows both textual and graphical content. In the past few years, the HL7 Clinical Document Architecture (CDA) has emerged as a consensus format for a wide variety of clinical reports (see PCC Content Profiles, especially [[Medical Summary]])The DRPT Profiles permits the use of both of these formats.
 
 
''<If the user might be familiar with the mechanisms used by the profile, you can mention them hereE.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 shortE.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.>''
+
Reports are transmitted from the Report Creator application to a Report Manager, typically a Cardiovascular or Radiology Information System (CVIS or RIS).  The Report Manager is responsible for ensuring signature and release of the report.  It maintains a copy of the report within the department (either in its own data store, or in the PACS), and also forwards a copy or a link to an Enterprise Report RepositoryYet another copy of the report is submitted to close out the order for the study.
 
   
 
   
 
==Systems Affected==
 
==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.''
+
* Reporting applications on image display workstations create reports in a displayable format (PDF or CDA)
* ''Display systems may query, retrieve and display Evidence Documents.''
+
* CVIS/RIS systems manage the report signature cycle, storage, and distribution
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
+
* PACS systems may store, manage, and/or display the reports
 +
* Enterprise repositories (clinical data record systems) store and manage the reports for broad institutional use
 +
* Image display systems may query, retrieve and display reports from the PACS using DICOM
 +
* Other clinical workstations may retrieve and display reports from the departmental data store (the PACS or the CVIS/RIS), or from the Enterprise repository using web integration techniques.
  
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
  
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+
[[File:DRPT.PNG]]
  
 
==Specification==
 
==Specification==
  
'''Profile Status:''' [[Comments|Public Comment]]   
+
'''Profile Status:''' [[Comments| Trial Implementation]]   
  
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,
+
DRPT was originally issed in a 2005 Supplement to the IHE Cardiology Technical Framework. 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. The IHE Cardiology Technical Committee reissued the Supplement in 2007 for a further Trial Implementation period with a major revision to correct this inconsistency.
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.
 
  
 +
Since 2007, CDA has emerged as the pricipal format for new health report document specifications.  The IHE Cardiology Technical Committee has again updated and reissued the Supplement in 2010 for a continued Trial Implementation, this time with support for CDA as well as PDF documents.
  
 
'''Documents:'''  
 
'''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.>''
+
https://www.ihe.net/uploadedFiles/Documents/Cardiology/IHE_CARD_Suppl_DRPT.pdf
 
 
[http://www.ihe.net/Technical_Framework/index.cfm#radiology IHE Radiology Technical Framework:]
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8.pdf Vol. 1] - Section 5 (SWF Profile)
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-2.pdf Vol. 2] - Sections 4.8 to 4.10, 4.14 to 4.19, and 4.23
 
:* [http://www.ihe.net/Technical_Framework/upload/ihe_tf_rev8-3.pdf Vol. 3] - Appendix E
 
  
 
'''Underlying Standards:'''
 
'''Underlying Standards:'''
  
''<list all the standards on which the profile is based; if possible with links to sources>''
+
* [http://www.hl7.org HL7] is used for report communication from the creator, to the manager, to the enterprise repository.
:* [http://dicom.nema.org DICOM]
+
* [http://dicom.nema.org DICOM]is used for the (optional) storage of the report in the PACS.
:* [http://www.hl7.org HL7]
 
:* ...
 
  
 
==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.>''
+
* Radiology [[Simple Image and Numeric Report]] [SINR] defines a similar function, and was one basis for DRPT
 
+
* IT Infrastructure [[Retrieve Information for Display]] [RID] provides a web-integration function for clinical workstation access to reports stored in the department.  This is a required adjunct to DRPT.
* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
+
* IT Infrastructure [[Patient Administration Management]] [PAM] provides the mechanism to update patient demographics for the metadata associated with a stored report
* ''[[Simple Image & Numeric Reports]] [SINR] may include data copied from Evidence Documents.''
+
* Cardiology [[Cardiac Imaging Report Content]] [CIRC] defines the content of a Cardiac Imaging Report (encoded as an HL7 CDA document) that can be created, stored and exchanged using the mechanism defined in DRPT.
* ''[[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. >''
 
 
 
  
  
Line 96: Line 65:
  
 
[[Category:Profiles]]
 
[[Category:Profiles]]
 +
[[Category:Cardiac Profile]]
 +
[[Category:DICOM]]

Latest revision as of 16:57, 20 November 2019

Displayable Reports (DRPT) manages creation and distribution of “display ready” (PDF or CDA) clinical reports from the creating application, to the department, and to the enterprise.


Summary

The Displayable Reports Profile supports the creation, revision, intra/inter-department transmission, and reading of display-ready clinical reports. In the imaging procedure context, it provides linkage between the report, the imaging and other evidence of the procedure. The report is provided to actors outside the department for broad distribution (e.g., using other profiles such as XDS or RID).

The DRPT Profile requires the use of the Portable Document Format (PDF) or the HL7 Clinical Document Architecture (CDA), which are both means of encoding documents ready for presentation, including graphical content. For reporting on imaging procedures, especially on cardiac procedures, they are able to present the full range of documentation generated by a wide variety of reporting packages.

Benefits

The DRPT profile defines a consistent approach to handling report creation and management. This allows independently developed analysis applications to be used seemlessly in departmental workflow, and thus enables clinicians to purchase best of breed reporting applications.

The profile also defines a mechanism for archiving reports in the PACS. This allows leveraging the robust srchival capabilities of the PACS, as well as aggregation of the complete imaging study data (images, analyses, and reports) in a consistent format and single location. This facilitates subsequent single point access to the study for coparison or export.

Details

The most common displayable report format currently in use is PDF, which allows both textual and graphical content. In the past few years, the HL7 Clinical Document Architecture (CDA) has emerged as a consensus format for a wide variety of clinical reports (see PCC Content Profiles, especially Medical Summary). The DRPT Profiles permits the use of both of these formats.

Reports are transmitted from the Report Creator application to a Report Manager, typically a Cardiovascular or Radiology Information System (CVIS or RIS). The Report Manager is responsible for ensuring signature and release of the report. It maintains a copy of the report within the department (either in its own data store, or in the PACS), and also forwards a copy or a link to an Enterprise Report Repository. Yet another copy of the report is submitted to close out the order for the study.

Systems Affected

  • Reporting applications on image display workstations create reports in a displayable format (PDF or CDA)
  • CVIS/RIS systems manage the report signature cycle, storage, and distribution
  • PACS systems may store, manage, and/or display the reports
  • Enterprise repositories (clinical data record systems) store and manage the reports for broad institutional use
  • Image display systems may query, retrieve and display reports from the PACS using DICOM
  • Other clinical workstations may retrieve and display reports from the departmental data store (the PACS or the CVIS/RIS), or from the Enterprise repository using web integration techniques.

Actors & Transactions:

DRPT.PNG

Specification

Profile Status: Trial Implementation

DRPT was originally issed in a 2005 Supplement to the IHE Cardiology Technical Framework. 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. The IHE Cardiology Technical Committee reissued the Supplement in 2007 for a further Trial Implementation period with a major revision to correct this inconsistency.

Since 2007, CDA has emerged as the pricipal format for new health report document specifications. The IHE Cardiology Technical Committee has again updated and reissued the Supplement in 2010 for a continued Trial Implementation, this time with support for CDA as well as PDF documents.

Documents:

https://www.ihe.net/uploadedFiles/Documents/Cardiology/IHE_CARD_Suppl_DRPT.pdf

Underlying Standards:

  • HL7 is used for report communication from the creator, to the manager, to the enterprise repository.
  • DICOMis used for the (optional) storage of the report in the PACS.

See Also

Related Profiles

  • Radiology Simple Image and Numeric Report [SINR] defines a similar function, and was one basis for DRPT
  • IT Infrastructure Retrieve Information for Display [RID] provides a web-integration function for clinical workstation access to reports stored in the department. This is a required adjunct to DRPT.
  • IT Infrastructure Patient Administration Management [PAM] provides the mechanism to update patient demographics for the metadata associated with a stored report
  • Cardiology Cardiac Imaging Report Content [CIRC] defines the content of a Cardiac Imaging Report (encoded as an HL7 CDA document) that can be created, stored and exchanged using the mechanism defined in DRPT.


This page is based on the Profile Overview Template