Difference between revisions of "Invoke Image Display"

Latest revision as of 10:54, 14 August 2019

Invoke Image Display (IID) allows an EHR/PHR/RIS to request a PACS (IM/IA/ID) to display images of a patient or study.

Summary

Invoke Image Display (IID) is an IHE Integration Profile that simplifies the task of integrating non-image-aware systems like EHRs, EMRs, PHRs, RIS and other information systems with image-aware systems like PACS, VNA and Image Sharing solutions, by providing a standard mechanism to request the that imaging studies be displayed.

Benefits

Provides a minimalist means of image-enabling non-image-aware systems
Uses the simplest available HTTP-based technology
Supports patient and study level invocation, usable with or without a priori knowledge of individual study identifiers
Requires servers to provide interactive viewing, and both review or diagnostic quality, and key images, under the control of the user

Problem Statement

EHR/EMR/PHR/RIS/HIS/portals don’t store imaging studies
EHR/EMR/PHR/RIS/HIS/portal users want to see images
Static links to individual rendered consumer format images may are insufficient for interactive viewing, and may grow stale
Interfaces from EHR/EMR/PHR/RIS/HIS/portals to PACS to request display of imaging studies possible but n:m customization/scaling problem
CCOW at study level (similar to IHE Patient Synchronized Applications) has issues with web technologies, proprietary alternatives abound, bidirectional synchronization is not required
US Meaningful Use requirements emphasize the need for the “View” part of “View, Download and Transmit” for imaging studies and results, possibly via a link

Value Proposition

IID provides a simple HTTP Request with patient/study identifiers and small number of parameters in URL
Without the complexity of SOAP-based web services
With sufficiently defined expected behavior for display
Without limiting the type of viewer technology
Without precluding diagnostic use
Mobile device friendly
Capable of leveraging, but not dependent on, any particular choice of authentication, access control or audit trail protocols

Details

ID defines a simple HTTP GET request that contains in the URL either a patient identifier or a list of study identifiers, and a small set of additional parameters to dictate display behavior.

The profile specifies requirements for the display to provide interactive viewing of a complete set of diagnostic images, if requested. The interactivity required includes windowing, zooming and panning as well as image navigation.

Security is addressed through normal HTTP mechanisms.

The display can take the form of a browser based viewer, a separate applet, plugin or thick client based viewer or even a separate physical machine; the invocation remains the same and is agnostic to the viewer implementation mechanism.

Systems Affected

Image Display Invoker (such as EHR, PHR, RIS) requests display
Image Display (such as PACS or VNA with Viewer) performs display

Actors & Transactions:

Process Flow:

Examples:

http://<location>/IHEInvokeImageDisplay?requestType=PATIENT&patientID=99998410^^^AcmeHospital&mostRecentResults=1
http://<location>/IHEInvokeImageDisplay?requestType=STUDY&accessionNumber=93649236
http://<location>/IHEInvokeImageDisplay?requestType=STUDY&studyUID=1.2.840.113883.19.110.4,1.2.840.113883.19.110.5&viewerType=IHE_BIR&diagnosticQuality=true

Specification

Profile Status: Trial Implementation

Documents:

IID TI Supplement

Underlying Standards:

@@ Line 1: / Line 1: @@
-'''Invoke Radiology Image Display Service (IRIDS)''' allows an EHR-S to request a PACS (IM/IA) to display images of a study.
+'''Invoke Image Display (IID)''' allows an EHR/PHR/RIS to request a PACS (IM/IA/ID) to display images of a patient or study.
 __TOC__
 ==Summary==
+Invoke Image Display (IID) is an IHE Integration Profile that simplifies the task of integrating non-image-aware systems like EHRs, EMRs, PHRs, RIS and other information systems with image-aware systems like PACS, VNA and Image Sharing solutions, by providing a standard mechanism to request the that imaging studies be displayed.
 ==Benefits==
+* Provides a minimalist means of image-enabling non-image-aware systems
+* Uses the simplest available HTTP-based technology
+* Supports patient and study level invocation, usable with or without a priori knowledge of individual study identifiers
+* Requires servers to provide interactive viewing, and both review or diagnostic quality, and key images, under the control of the user
+'''Problem Statement'''
+* EHR/EMR/PHR/RIS/HIS/portals don’t store imaging studies
+* EHR/EMR/PHR/RIS/HIS/portal users want to see images
+* Static links to individual rendered consumer format images may are insufficient for interactive viewing, and may grow stale
+* Interfaces from EHR/EMR/PHR/RIS/HIS/portals to PACS to request display of imaging studies possible but n:m customization/scaling problem
+* CCOW at study level (similar to IHE Patient Synchronized Applications) has issues with web technologies, proprietary alternatives abound, bidirectional synchronization is not required
+* US Meaningful Use requirements emphasize the need for the “View” part of “View, Download and Transmit” for imaging studies and results, possibly via a link
+'''Value Proposition'''
+* IID provides a simple HTTP Request with patient/study identifiers and small number of parameters in URL
+* Without the complexity of SOAP-based web services
+* With sufficiently defined expected behavior for display
+* Without limiting the type of viewer technology
+* Without precluding diagnostic use
+* Mobile device friendly
+* Capable of leveraging, but not dependent on, any particular choice of authentication, access control or audit trail protocols
 ==Details==
+ID defines a simple HTTP GET request that contains in the URL either a patient identifier or a list of study identifiers, and a small set of additional parameters to dictate display behavior.
+The profile specifies requirements for the display to provide interactive viewing of a complete set of diagnostic images, if requested. The interactivity required includes windowing, zooming and panning as well as image navigation.
+Security is addressed through normal HTTP mechanisms.
+The display can take the form of a browser based viewer, a separate applet, plugin or thick client based viewer or even a separate physical machine; the invocation remains the same and is agnostic to the viewer implementation mechanism.
 ==Systems Affected==
-* EHR-S requests display
+* Image Display Invoker (such as EHR, PHR, RIS) requests display
-* PACS performs isplay
+* Image Display (such as PACS or VNA with Viewer) performs display
 '''Actors & Transactions:'''
-''<Insert an actor-transaction diagram, and or list of Content Definitions>''
+[[Image:IID-actor-transaction.png]]
+'''Process Flow:'''
+[[Image:IID-processflow.png]]
+'''Examples:'''
+* <code><nowiki>http://<location>/IHEInvokeImageDisplay?requestType=PATIENT&patientID=99998410^^^AcmeHospital&mostRecentResults=1</nowiki></code>
+* <code><nowiki>http://<location>/IHEInvokeImageDisplay?requestType=STUDY&accessionNumber=93649236</nowiki></code>
+* <code><nowiki>http://<location>/IHEInvokeImageDisplay?requestType=STUDY&studyUID=1.2.840.113883.19.110.4,1.2.840.113883.19.110.5&viewerType=IHE_BIR&diagnosticQuality=true</nowiki></code>
 ==Specification==
-'''Profile Status:''' [[Comments| Final Text]]
+'''Profile Status:''' Trial Implementation
-''<Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>''
 '''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_IID.pdf IID TI 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:'''
-''<list all the standards on which the profile is based; if possible with links to sources>''
-:* [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'''
+* ''[[Basic Image Review]] [BIR] defines a set of baseline features and user interface relevant to the simple review of DICOM images.''
-'''Related Profiles'''
+'''IHE Webinar'''
-''<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.>''
+* [[media:IHE-RAD-IID-Webinar-Clunie_20130708.pdf|Invoke Image Display (IID) IHE Webinar]]
-* ''[[Reporting Workflow]] [RWF] may use Evidence Documents as inputs to the reporting process.''
+'''External Links'''
-* ''[[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.''
+* ''[https://en.wikipedia.org/wiki/Invoke_Image_Display Wikipedia Entry]''
 '''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]]
 [[Category:Profiles]]
+[[Category:RAD Profile]]
-<noinclude>''<'''Delete this Category Templates line''' since your Profile page is no longer a template.>'' </noinclude>
+[[Category:DICOM]]
+[[Category:DICOMweb]]

Difference between revisions of "Invoke Image Display"

Latest revision as of 10:54, 14 August 2019

Contents

Summary

Benefits

Details

Systems Affected

Specification

See Also

Navigation menu

Search