Launch URL

Summary

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

Introduction

The ImageMover server can be deployed as an Open Virtual Appliance (OVA) file. Once installed, the server can receive patient information passed to it from the EHR by invoking ImageMover via the https network protocol. The ImageMover server receives and parses the URL from the EHR and returns a QR code that is read by the ImageMover mobile application. This QR code contains an unique key that links the patient information to the image capture session. After images have been captured and sent from the mobile app to the server, the server adds patient information to the images and forwards them to PACS/VNA.

Launching ImageMover

Follow these steps to prepare the EHR for launching ImageMover:

1. Add an "ImageMover" (or similar) button on the main menu within the EHR

2. Map the button to the redirector control application activity

3. Create the EHR URL string for launching ImageMover, described below

URL

Patient- or encounter-specific information is included within the URL and associated with the sent images. Create the launch URL by substituting the string in bold below with information provided by the EHR. Only the patientExternalId parameter is absolutely necessary to begin transmitting images using ImageMover. However, the EHR integration becomes more meaningful when additional patient information is provided via the URL. This URL will trigger an HTTPS GET request to the ImageMover server.

The right-most column in the following table correspond to the currently supported URL parameters per EHR system integration. These are subject to change as ImageMover software (and/or EHR software) is updated with new versions.

https://hostname/embedded/?patientExternalId=[MRN]&patientLastName=[last name]&patientFirstName=[first name]&patientGender=[gender]&accessionNumber=[accession]&etc...

Custom Parameters

In addition, any additional parameters included in the URL will automatically be made available to ImageMover. Examples of custom parameters includepatientFavoriteColor, providerSpecialty and billingCode. These values are stored securely in ImageMover and can be leveraged when sending HL7 messages, sending DICOM images or other with features of the ImageMover platform.

Your ImageMover customer success representative can help you integrate custom parameters for your organization.

Custom Default Tab

By default, ImageMover will open the Mobile Image Capture tab or, if navigationTabs has been customized, the first available tab based in their natural order on the screen (Mobile, DICOM Uploader, Media Uploader, Modality, etc.).

To control which tab is active by default, add #!/[tab] to the end of the URL after all other launch parameters. Values can include dicom, media, mobile, modality and, if not configured in standalone mode, rounds.

For example, to open the Modality tab by default from the EHR, the launch URL should be configured like this:

https://hostname/embedded/?patientExternalId=[MRN]&patientLastName=[last name]&patientFirstName=[first name]&patientGender=[gender]&accessionNumber=[accession]#!/modality

Sending HL7 Messages from ImageMover

After sending images to PACS/VNA via DICOM, ImageMover can optionally send an HL7 message to the EHR. Depending on workflow, this step is typically performed by the PACS/VNA as described in the next section.

Example ORM O01 Order Message

MSH|^~\&|sendingApplication|sendingFacility|receivingApplication|receivingFacility|now||ORM^O01|34101|processingId|2.3
PID|||patientExternalId^^^assigningAuthority^^assigningFacility||patientLastName^patientFirstName^patientMiddleName^patientTitle^patientSuffix||patientDateOfBirth|patientGender||||||||||patientAccountNumber
PV1|1|encounterMode|encounterDepartment|||||||||||||sensitive|||visitNumber
ORC|orderControl|accessionNumber|||orderStatus
OBR|1|accessionNumber^assigningAuthority||examCode^studyDescription^codingSystem|||now||||overread||deviceName|||providerExternalId^providerLastName^providerFistName|||modality||D|now||modality|F||1||||^studyReason|operatorExternalId&operatorLastName&operatorFirstName||operatorExternalId&operatorLastName&operatorFirstName
OBX|1|TX||1|observationValue||||||F

*Unless otherwise noted in the table below, the variables highlighted in the example message above come straight from the ImageMover session. See the Launch Parameters section for more information about those variables.

Processing the HL7 Messages

To link to the images sent from the ImageMover server to PACS/VNA, the EHR must create a link using an HL7 "order" message. When the images are available, PACS/VNA typically forwards an HL7 ORU message to the EHR. This message contains a link (usually a URL) used to launch a viewer with the appropriate study. A basic connectivity diagram is shown below:

ImageMover basic HL7 connection diagram

Note! In most clinical workflows, it is preferable for point-of-care mobile images to be directly assocated with the originating patient encounter. Enable MDM message generation inside of ImageMover or route HL7 BSCN messages to an MDM (transcription) interface to accomplish this.

As is noted in the diagram, for most clinical workflows, it is preferable for point-of-care mobile images to be directly associated with the originating patient encounter. This can be most easily accomplished by passing the encounter CSN to ImageMover in the accessionNumber parameter. ImageMover can be configured to combine the passed encounter CSN with a prefix to facilitate routing HL7 BSCN messages from a PACS/VNA to an MDM (transcription) interface.

Getting Support

Contact ImageMoverMD by phone 608-620-4980 ext 2 or email support@imagemovermd.com.