Difference between revisions of "Import and Display of External Priors"

From IHE Wiki
Jump to navigation Jump to search
(→‎See Also: Added additional related profiles)
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Import and Display of External Priors (IDEP) specifies the trigger events, transactions, and data mappings necessary to automate the discovery of relevant prior imaging studies and reports and the transfer between different facilities, i.e., “external priors”.
+
Import and Display of External Priors (IDEP) automates the discovery and import of relevant prior imaging studies and reports from affiliated facilities, i.e., “external priors”.
  
 
__TOC__
 
__TOC__
  
 
==Summary==
 
==Summary==
It is common for patients to move between healthcare facilities that serve a shared patient population. Many of these healthcare facilities already have a shared secure network
+
Patients move between healthcare facilities that serve a shared patient population. Many of these healthcare facilities have a shared secure network infrastructure.  
infrastructure. Upon receipt of an order for a new imaging study, the IHE Radiology Import and Display of External Priors (IDEP) Profile provides a method to automatically retrieve images and reports throughout the shared network, independent of a common Patient Identifier. The exchange includes “localizing” the data such that both the radiology images and reports may be displayed in the same system in the expected manner for side-by-side comparison and report display.
+
 
 +
In the IDEP Profile, upon receipt of an order for a new imaging study, images and reports throughout the shared network are automatically located and retrieved, independent of a common Patient Identifier. The imported images and reports are “localized” so they display together with local data for side-by-side comparison.
  
 
[[Image:IDEP_Intro_Diagram.png | center | 800px | Flow of external prior images and reports between facilities]]
 
[[Image:IDEP_Intro_Diagram.png | center | 800px | Flow of external prior images and reports between facilities]]
  
 
==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.>''
+
* Provides ability to locate, access, and view external priors for direct comparison
 +
** Specifically during the short time frame required to be relevant to reading
 +
* Supports side-by side image comparison of current studies and external priors using local hanging protocols and viewing tools
 +
* Reduces re-scanning of patients (see Nagels, J., Macdonald, D. & Coz, C. J Digit Imaging (2017). https://doi.org/10.1007/s10278-017-9963-8)
 +
* Provides a consistent mechanism for retrieving external prior reports
 +
* Minimizes impact on existing systems
 +
** Importer actor does the bulk of the work
 +
** Local PACS / RIS / EMR systems should require minimal changes to support
  
 
==Details==
 
==Details==
 +
'''IDEP Workflow'''
 +
# Local Order Filler (RIS / EMR) sends Procedure Scheduled message to Importer
 +
# Importer extracts patient and procedure information from message
 +
# Importer finds studies for the patient at each external site and identifies priors relevant to the scheduled procedure
 +
# Importer retrieves relevant priors from external sites
 +
# Importer localizes external studies and reports to use local identifiers, procedure codes, etc.
 +
# Importer stores external prior studies and reports in local systems (Image Manager, Report Manager)
 +
[[Image:IDEP_Overview_Diagram.png | center | 800px | IDEP Overview]]
  
''<A few paragraphs, if appropriate, providing more details (mostly in user-speak, not tech-speak) on what the profile does and how it works.>''
+
'''IDEP Key Points'''
 +
* Each site participating in IDEP workflow both retrieves priors from other sites ''and'' provides priors to other sites
 +
* The Importer and other key infrastructure can be centralized or implemented at each site
  
''<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==
 
==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 may receive and display external prior studies and respond to prior study search requests''
 
+
** Image Manager actor
* ''PACS systems may store, manage, and/or display Evidence Documents.''
+
* ''RIS / EMR systems may initiate external prior workflow, receive / display external prior reports, and respond to search requests for prior reports''
* ''Display systems may query, retrieve and display Evidence Documents.''
+
** DSS / Order Filler and Report Manager actors
* ''Reporting workstations may retrieve, process and include details from Evidence Documents in reports
+
* ''VNA / EIR systems may execute the external prior workflow and manage the movement of external prior studies and reports''
 +
** Importer actor
  
 
'''Actors & Transactions:'''
 
'''Actors & Transactions:'''
 
+
<center>'''IDEP Actor Diagram'''</center>
''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+
[[Image:IDEP_actor_diagram.png | center | IDEP Actor Diagram]]
 +
<center>'''IDEP XDS Options Actor Diagram'''</center>
 +
[[Image:IDEP_xds_actor_diagram.png | center | IDEP XDS Options Actor Diagram]]
  
 
==Specification==
 
==Specification==
Line 69: Line 86:
  
 
'''Reference Articles'''
 
'''Reference Articles'''
 
+
* Measuring the Benefits of a Regional Imaging Environment, Nagels, J., Macdonald, D. & Coz, C. J Digit Imaging (2017). https://doi.org/10.1007/s10278-017-9963-8
''<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]]
 
[[Category:Profiles]]
Line 78: Line 94:
 
[[Category:DICOM]]
 
[[Category:DICOM]]
 
[[Category:HL7v2]]
 
[[Category:HL7v2]]
[[Category:FHIR]]
+
[[Category:DocShare]]

Latest revision as of 22:24, 13 November 2019

Import and Display of External Priors (IDEP) automates the discovery and import of relevant prior imaging studies and reports from affiliated facilities, i.e., “external priors”.

Summary

Patients move between healthcare facilities that serve a shared patient population. Many of these healthcare facilities have a shared secure network infrastructure.

In the IDEP Profile, upon receipt of an order for a new imaging study, images and reports throughout the shared network are automatically located and retrieved, independent of a common Patient Identifier. The imported images and reports are “localized” so they display together with local data for side-by-side comparison.

Flow of external prior images and reports between facilities

Benefits

  • Provides ability to locate, access, and view external priors for direct comparison
    • Specifically during the short time frame required to be relevant to reading
  • Supports side-by side image comparison of current studies and external priors using local hanging protocols and viewing tools
  • Reduces re-scanning of patients (see Nagels, J., Macdonald, D. & Coz, C. J Digit Imaging (2017). https://doi.org/10.1007/s10278-017-9963-8)
  • Provides a consistent mechanism for retrieving external prior reports
  • Minimizes impact on existing systems
    • Importer actor does the bulk of the work
    • Local PACS / RIS / EMR systems should require minimal changes to support

Details

IDEP Workflow

  1. Local Order Filler (RIS / EMR) sends Procedure Scheduled message to Importer
  2. Importer extracts patient and procedure information from message
  3. Importer finds studies for the patient at each external site and identifies priors relevant to the scheduled procedure
  4. Importer retrieves relevant priors from external sites
  5. Importer localizes external studies and reports to use local identifiers, procedure codes, etc.
  6. Importer stores external prior studies and reports in local systems (Image Manager, Report Manager)
IDEP Overview

IDEP Key Points

  • Each site participating in IDEP workflow both retrieves priors from other sites and provides priors to other sites
  • The Importer and other key infrastructure can be centralized or implemented at each site

Systems Affected

  • PACS may receive and display external prior studies and respond to prior study search requests
    • Image Manager actor
  • RIS / EMR systems may initiate external prior workflow, receive / display external prior reports, and respond to search requests for prior reports
    • DSS / Order Filler and Report Manager actors
  • VNA / EIR systems may execute the external prior workflow and manage the movement of external prior studies and reports
    • Importer actor

Actors & Transactions:

IDEP Actor Diagram
IDEP Actor Diagram
IDEP XDS Options Actor Diagram
IDEP XDS Options Actor Diagram

Specification

Profile Status: Trial Implementation

Documents:

Underlying Standards:

See Also

Related Profiles


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

This page is based on the Profile Overview Template