Summary

This document describes how to add a button in Epic to launch ImageMover solutions, such as ImageMover Mobile and ImageMover Media.

The audience for this document is IT personnel and local Epic build teams. These instructions assume experience with HL7, DICOM, and Epic EHR software.

Introduction

To launch ImageMover from Epic, add a button to Hyperspace using the information provided in this Technical Note. After you have created the button, Epic will be able to launch ImageMover by sending patient information to the ImageMover Server via the https network protocol. The ImageMover Server receives and parses the URL from Epic and returns a web page that permits the uploading of DICOM files. After exams have been uploaded to the server, the server can add localized patient information and forward exams to PACS/VNA or another DICOM destination.

The workflow steps to integrate ImageMover with Epic Hyperspace are:

Create an FDI integration record and configure the ImageMover launch URL.
Create an activity record (E2N) and add the FDI record.
Create a menu record (E2U) for the button and add an activity record (E2N) to it.

The remainder of this document describes the three required Epic record items used to launch ImageMover.

1. Integration record (FDI)

FDI records let Epic integrate with third-party application software. These records are most commonly used to launch a PACS viewer from Hyperspace. Using a similar approach, you can launch ImageMover by creating a new FDI record and linking it to the activity record described above. The FDI record contains the URL string that launches ImageMover from Hyperspace. (See "ImageMover EHR Standard Integration Model" for URL details.) Your Epic Radiant TS can assist with the mapping of internal Epic patient demographic variables (such as %PATID%) to the URL string.

2. Activity record (E2N)

The activity record (E2N) maps the button to a particular activity. When you click the button in Hyperspace, Epic executes the activity described in the E2N record. The recommended method for launching third-party applications is to map the E2N record to an FDI integration record.

3. Menu record (E2U)

The menu record (E2U) is a placeholder used to structure the user interface in Hyperspace, including buttons. To begin this step, determine the Epic screen where you will place the button. Depending on usage, it can be placed in the left-most navigation bar, or under the "Activities" menu. Your Ambulatory team can assist with the placement and creation of the button, which is typically named "Photo Upload" (for ImageMover Mobile) or "Media Upload" (for ImageMover Media).

Additional information

For more information, contact your local Epic TS. If you are unsure of your contact or require additional assistance, contact ImageMover Support.