Difference between revisions of "Invoke Image Display"
| Line 7: | Line 7: | ||
==Benefits== | ==Benefits== | ||
| − | Provides a simple HTTP Request with patient/study | + | * Provides a simple HTTP Request with patient/study |
identifiers and small number of parameters in URL | identifiers and small number of parameters in URL | ||
| − | Without the complexity of SOAP-based web services | + | * Without the complexity of SOAP-based web services |
| − | With sufficiently defined expected behavior for display | + | * With sufficiently defined expected behavior for display |
| − | Without limiting the type of viewer technology | + | * Without limiting the type of viewer technology |
| − | Without precluding diagnostic use | + | * Without precluding diagnostic use |
| − | Mobile device friendly | + | * Mobile device friendly |
| − | Capable of leveraging, but not dependent on, any | + | * Capable of leveraging, but not dependent on, any |
particular choice of authentication, access control or | particular choice of authentication, access control or | ||
audit trail protocols | audit trail protocols | ||
Revision as of 10:56, 29 September 2015
Invoke Image Display (IID) allows an EHR/PHR/RIS to request a PACS (IM/IA/ID) to display images of a 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 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 Manager/Archive/Display (such as PACS) performs display
Actors & Transactions:
<Insert an actor-transaction diagram, and or list of Content Definitions>
Specification
Profile Status: Trial Implementation
Documents:
Underlying Standards:
See Also
Related Profiles
- Basic Image Review [BIR] defines a set of baseline features and user interface relevant to the simple review of DICOM images.
Consumer Information
Implementer Information
Reference Articles
This page is based on the Profile Overview Template