Difference between revisions of "Results Distribution"

From IHE Wiki
Jump to navigation Jump to search
 
(6 intermediate revisions by the same user not shown)
Line 2: Line 2:
  
 
==Summary==
 
==Summary==
The IHE Result Distribution Profile (RD) defines the communication of imaging results like radiology reports between Report Creators, Managers, and Consumers using an HL7 2.5.1 Observation Results (ORU) message to maximize compatibility with existing installed systems
+
The IHE Result Distribution Profile (RD) defines the communication of imaging results like radiology reports between Report Creators, Managers, and Consumers.  
 
[[File:RD.jpg]]
 
[[File:RD.jpg]]
  
 
==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 RD Profile provides key data in a structured format to trigger downstream activities like
 +
* Follow up of non-critical actionable findings
 +
* Additional billing
 +
* Consults
 +
* Submission to registries/analysis
 +
* Submission for inquiries to clinical trials
 +
* Business analysis
 +
 
 +
RD is a gap solution to bridge result communication until structured formats like CDA and SDC are more widely supported. It is designed to maximize communication between a wide variety of existing systems
  
 
==Details==
 
==Details==
Line 23: Line 31:
 
* Send an imaging result to an EMR  
 
* Send an imaging result to an EMR  
 
* Send an imaging result to a Follow-Up Source (i.e., Non-Critical Actionable Findings)
 
* Send an imaging result to a Follow-Up Source (i.e., Non-Critical Actionable Findings)
 +
 +
The profile is using an HL7 2.5.1 Observation Results (ORU) message to maximize compatibility with existing installed systems.
  
 
==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.''
+
Report Creators like
* ''Display systems may query, retrieve and display Evidence Documents.''
+
* Voice dictation system
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
+
* Point and click reporting solutions
 +
* Natural language processing systems
 +
* Template driven or text driven reporting solutions in Radiology or cardiology, etc
 +
 
 +
Report Managers like
 +
* Reporting systems  
 +
* PACS system
 +
* EMR
 +
 
 +
Report Consumers like
 +
* Report Viewers
 +
* EMRs
 +
* Research databases
 +
* Regulatory registries (e.g. ACC NCDR)
 +
* Follow-up Actionable Finding Mgr
 +
 
  
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
Line 37: Line 61:
 
==Specification==
 
==Specification==
  
'''Profile Status:''' [[Comments| Final Text]] 
+
'''Profile Status:''' Trial Implementation
''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
+
 
  
 
'''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/Radiology/IHE_RAD_Suppl_RD.pdf Result Distribution Supplement]
  
[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] Version 2.5.1
:* [http://dicom.nema.org DICOM]
 
:* [http://www.hl7.org 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. >''
 
 
 
[[Category:Profiles]]
 
 
 
This page is based on the [[Profile Overview Template]]
 
 
 
[[Category:Templates]]
 
<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: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: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. :-)
 
-->
 

Latest revision as of 08:33, 22 January 2020

Summary

The IHE Result Distribution Profile (RD) defines the communication of imaging results like radiology reports between Report Creators, Managers, and Consumers. RD.jpg

Benefits

The RD Profile provides key data in a structured format to trigger downstream activities like

  • Follow up of non-critical actionable findings
  • Additional billing
  • Consults
  • Submission to registries/analysis
  • Submission for inquiries to clinical trials
  • Business analysis

RD is a gap solution to bridge result communication until structured formats like CDA and SDC are more widely supported. It is designed to maximize communication between a wide variety of existing systems

Details

The Report Distribution profile facicitlates communication of imaging results (i.e., radiology reports) between physicians, medical staff, and various facilities. It provides a consistent mechanism, and definition of metadata, to simplify the distribution of imaging results. When a radiologist creates an interpretation, or a “result”, of an imaging study, the imaging result is often sent to an EMR for review by the physician who ordered the study. These imaging results are used to determine the on-going care, or “clinical care pathway”, for the patient. Additionally, radiologists often use prior (comparison study) imaging results in the interpretation of a new imaging procedure. Imaging results may also be used for data mining for public health studies or clinical trial evaluations.

Use cases addressed by this profile include:

  • Send an imaging result to an EMR
  • Send an imaging result to a Follow-Up Source (i.e., Non-Critical Actionable Findings)

The profile is using an HL7 2.5.1 Observation Results (ORU) message to maximize compatibility with existing installed systems.

Systems Affected

Report Creators like

  • Voice dictation system
  • Point and click reporting solutions
  • Natural language processing systems
  • Template driven or text driven reporting solutions in Radiology or cardiology, etc

Report Managers like

  • Reporting systems
  • PACS system
  • EMR

Report Consumers like

  • Report Viewers
  • EMRs
  • Research databases
  • Regulatory registries (e.g. ACC NCDR)
  • Follow-up Actionable Finding Mgr


Actors & Transactions:

RD ActorsTransactions.jpg

Specification

Profile Status: Trial Implementation


Documents:


Underlying Standards:

  • HL7 Version 2.5.1