Introduction

When first planning to implement ImageMover, our recommendation is to set up two servers, one server designed for your Test environment and one for Production. This configuration will allow an organization to fully test new features and bug fixes within a controlled environment. With the Test server in place, Production will be considered a stable environment. Further, this server will be updated with only what has been confirmed as functional on the Test server.

To begin the process of creating these servers, we need certain information regarding your network and DICOM storage setup. We have prepared a Technical Specifications form with the information we require. On the form, organizations can specify if the network and DICOM storage information is meant for their Test or Production environment. If requesting both servers to be created, the organization will need to fill out two forms, one per environment. Please allow for two to three business days for the creation of the Virtual Machine (VM). Unless otherwise requested, the VMs will be delivered to your team as OVA files through our SFTP site.

Deploys, Updates, and New Features

The following outlines the process for updating and adding features to the Test and Production servers. It assumes these two servers have been implemented.

Updating Production

Providing Production with updates is a simple process:

1. We will deploy the Test version of the ImageMover Enterprise Platform from the previous month into Production.
2. We will then update the Test server with the latest version of the ImageMover Enterprise Platform.

The recommended schedule for these updates to occur is monthly, during the early hours of the morning on the third Thursday of each month. System downtime is typically less than five minutes unless otherwise noted. This maintenance window covers both software updates and operating system patches (if required).

We will email release notes in advance of each update, and customers generally have one month before new features will be deployed into Production. With at least four hours' notice before the update window, we can delay the deployment of code from Test into Production.

We will support the current ImageMover version, and two previous versions of all server software.

Diagram Update Flow

Before updating a customer's Test and Production environments, we internally validate the latest version of the ImageMover Enterprise Platform. After testing, we forward release notes to all customers.

1. The latest version of the ImageMover Enterprise Platform is tagged for release.
2. We update customers' Test servers
   • Users can execute test scripts and other ad hoc testing before the release is deployed into Production. Release notes are provided with each new version, so users can also test new features.
3. Once validated in a Test environment, we will update Production servers based on the established release timeline.