Epic

 

1Introduction

Epic develop software for mid-size and large medical groups, hospitals and integrated healthcare organizations, working with customers that include community hospitals, academic facilities, children's organizations, safety net providers and multi-hospital systems. Epic’s applications support functions related to patient care, including:

  • Registration and scheduling
  • Clinical systems for doctors, nurses, emergency personnel and other care providers
  • Systems for lab technologists, pharmacists and radiologists
  • Billing systems for insurers

The KEMP LoadMaster is used to load balance the Epic workload. The LoadMaster offers advanced Layer 4 and Layer 7 server load balancing, SSL Acceleration and a multitude of other advanced Application Delivery Controller (ADC) features. The LoadMaster intelligently and efficiently distributes user traffic among the application servers so that users get the best experience possible.

1.1Document Purpose

This document provides the recommended LoadMaster settings used when load balancing the Epic workload. The KEMP Support Team is available to provide solutions for scenarios not explicitly defined.

The KEMP support site can be found at: https://support.kemptechnologies.com.

1.2Intended Audience

Network administrators who are deploying Epic with a KEMP LoadMaster.

2Epic Template

KEMP has developed a template containing our recommended settings for Epic. You can install this template on the LoadMaster and use it when creating Virtual Services. Using a template automatically populates the settings in the Virtual Services, which is quicker and easier than manually configuring each Virtual Service. If needed, you can make changes to any of the Virtual Service settings after using the template.

Download released templates from the Templates section on the KEMP documentation page: http://kemptechnologies.com/documentation/.

For more information and steps on how to import and use templates, refer to the Feature Description, Virtual Services and Templates.

For steps on how to manually add and configure each of the Virtual Services, refer to Section 4 of this document.

3Architecture

Figure 3‑1: Architecture

The above network architecture diagram depicts how the LoadMaster connects to the different backend components in Epic Systems.

4Configure the LoadMaster

The deployed Epic Systems environment determines which of the following setups is used.

4.1Enable Subnet Originating Requests Globally

It is best practice to enable the Subnet Originating Requests option globally.

In a one-armed setup (where the Virtual Service and Real Servers are on the same network/subnet), Subnet Originating Requests is usually not needed. However, enabling Subnet Originating Requests should not affect the routing in a one-armed setup.

In a two-armed setup where the Virtual Service is on network/subnet A, for example, and the Real Servers are on network B - Subnet Originating Requests should be enabled on LoadMasters with firmware version 7.1-16 and above.

When Subnet Originating Requests is enabled, the LoadMaster routes traffic so that the Real Server sees traffic arriving from the LoadMaster interface that is in that network/subnet.

When Subnet Originating Requests is enabled globally, it is automatically enabled on all Virtual Services. If the Subnet Originating Requests option is disabled globally, you can select whether or not to enable Subnet Originating Requests on a per-Virtual Service basis.

To enable Subnet Originating Requests globally, follow the steps below:

  1. In the main menu of the LoadMaster WUI, go to System Configuration > Miscellaneous Options > Network Options.

Figure 4‑1: Subnet Originating Requests

  1. Select the Subnet Originating Requests check box.

4.2Create an Epic Medical Systems HTTP Virtual Service

The following are the steps involved and the recommended settings to configure the Epic Systems HTTP Virtual Service:

  1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services> Add New.

Figure 4‑2: Virtual Service parameters

  1. Enter a valid Virtual Address.
  2. Enter 80 as the Port.
  3. Enter a recognizable Service Name, such as Epic Medical Systems HTTP.
  4. Click Add this Virtual Service.
  5. Configure the settings as recommended in the following table:

Section

Option

Value

Comment

Standard Options

Persistence Mode

Active Cookie

 
 

Timeout

1 Hour

 
 

Cookie name

JSESSIONID

Click Set Cookie.

 

Idle Connection Timeout

900

Click Set Idle Timeout.

Real Servers

URL

/

Click Set URL.

Figure 4‑3: Epic Medical Systems HTTP Virtual Service Recommended Settings

  1. Add the Real Servers:

a)Click the Add New button.

b)Enter the address of the Epic Medical Systems HTTP Server.

c)Fill out the other fields as needed.

d)Click Add this Real Server. Click OK to the pop-up message.

e)Repeat the steps above to add more Real Servers as needed, based on the environment.

4.3Create an Epic Medical Systems HTTPS Virtual Service

The following are the steps involved and the recommended settings to configure the Epic Systems HTTPS Virtual Service:

  1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services> Add New.

Figure 4‑4: Virtual Service parameters

  1. Enter a valid Virtual Address.
  2. Enter 443 as the Port.
  3. Enter a recognizable Service Name, such as Epic Medical Systems HTTPS.
  4. Click the Add this Virtual Service button.
  5. Configure the settings as recommended in the following table:

Section

Option

Value

Comment

Standard Options

Persistence Mode

Source IP Address

 
 

Timeout

1 Hour

 
 

Idle Connection Timeout

900

Click Set Idle Timeout.

Advanced Properties

Add a Port 80 Redirector VS

https://%h%s

Click the Add HTTP Redirector button. This automatically creates a redirect on port 80. This option is only visible if there is no existing port 80 redirect for this Virtual Service.

Figure 4‑5: Epic Medical Systems HTTPS Virtual Service Recommended Settings

  1. Add the Real Servers:

a)Click the Add New button.

b)Enter the address of the Epic Medical Systems HTTPS Server.

c)Click Add this Real Server. Click OK to the pop-up message.

d)Repeat the steps above to add more Real Servers as needed, based on the environment.

4.3.1Configure the Epic Medical Systems HTTPS-HTTP Redirect Virtual Service

Clicking the Add HTTP Redirector button automatically creates a port 80 redirect Virtual Service. This is optional, but the purpose of this Virtual Service is to redirect any clients who have connected via HTTP to the HTTPS Virtual Service.

KEMP recommends changing some settings in the Epic Medical Systems HTTPS-HTTP Redirect Virtual Service. The recommended settings are below:

Section

Option

Value

Standard Options

Persistence Mode

None

Real Servers

Real Server Check Method

None

Figure 4‑6: Epic Medical Systems HTTPS HTTP Redirect Virtual Service Recommended Settings

4.4Create an Epic Medical Systems HTTPS Offloaded Virtual Service

The following are the steps involved and the recommended settings to configure the Epic Systems HTTPS Offloaded Virtual Service:

  1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services> Add New.

Figure 4‑7: Virtual Service parameters

  1. Enter a valid Virtual Address.
  2. Enter 443 as the Port.
  3. Enter a Service Name, for example Epic Medical Systems HTTPS Offloaded.
  4. Click Add this Virtual Service.
  5. Configure the settings as recommended in the following table:

Section

Option

Value

Comments

Standard Options

Persistence Mode

Active Cookie

SSL Acceleration must be enabled before Active Cookie can be selected as the Persistence Mode.

 

Timeout

1 Hour

 
 

Cookie name

JSESSIONID

Click Set Cookie.

 

Idle Connection Timeout

900

 

SSL Properties

SSL Acceleration

Enabled

 
 

Cipher Set

BestPractices

 

Advanced Properties

Add a Port 80 Redirector VS

https://%h%s

Click the Add HTTP Redirector button. This will automatically create a redirect on port 80. This option is only visible if there is no existing port 80 redirect for this Virtual Service.

Real Servers

URL

/

 

Figure 4‑8: Epic Medical Systems HTTPS Offloaded Virtual Service Recommended Settings

  1. Add the Real Servers:

a)Click the Add New button.

b)Enter the address of the Epic Medical Systems HTTPS Server.

c)Click Add this Real Server. Click OK to the pop-up message.

d)Repeat the steps above to add more Real Servers as needed, based on the environment.

4.4.1Configure the Epic Medical Systems HTTPS Offloaded HTTP Redirect Virtual Service

Clicking the Add HTTP Redirector button automatically creates a port 80 redirect Virtual Service. This is optional, but the purpose of this Virtual Service is to redirect any clients who have connected via HTTP to the HTTPS Virtual Service.

KEMP recommends changing some settings in the Epic Medical Systems HTTPS HTTP Redirect Virtual Service. The recommended settings are below:

Section

Option

Value

Standard Options

Persistence Mode

None

Real Servers

Real Server Check Method

None

Figure 4‑9: Epic Medical Systems HTTPS Offloaded HTTP Redirect Virtual Service Recommended Settings

4.5Create an Epic Medical Systems HTTPS Re-encrypt Virtual Service

The following are the steps involved and the recommended settings to configure the Epic Systems HTTPS Re-encrypt Virtual Service:

  1. In the main menu of the LoadMaster Web User Interface (WUI), go to Virtual Services> Add New.

Figure 4‑10: Virtual Service parameters

  1. Enter a valid Virtual Address.
  2. Enter 443 as the Port.
  3. Enter a Service Name, for example Epic Medical Systems HTTPS Re-encrypt.
  4. Click Add this Virtual Service.
  5. Configure the settings as recommended in the following table:

Section

Option

Value

Comments

Standard Options

Persistence Mode

Active Cookie

SSL Acceleration must be enabled before Active Cookie can be selected as the Persistence Mode.

 

Timeout

1 Hour

 
 

Cookie name

JSESSIONID

Click Set Cookie.

 

Idle Connection Timeout

900

 

SSL Properties

SSL Acceleration

Enabled

 
 

Reencrypt

Enabled

 
 

Cipher Set

BestPractices

 

Advanced Properties

Add a Port 80 Redirector VS

https://%h%s

Click the Add HTTP Redirector button. This automatically creates a redirect on port 80. This option is only visible if there is no existing port 80 redirect for this Virtual Service.

Real Servers

Real Server Check Method

HTTPS Protocol

 
 

URL

/

Click Set URL.

Figure 4‑11: Epic Medical Systems HTTPS Re-encrypt Virtual Service Recommended Settings

  1. Add the Real Servers:

a)Click the Add New button.

b)Enter the address of the Epic Medical Systems HTTPS Server.

c)Click Add this Real Server. Click OK to the pop-up message.

d)Repeat the steps above to add more Real Servers as needed, based on the environment.

4.5.1Configure the Epic Medical Systems HTTPS Re-encrypt HTTP Redirect Virtual Service

Clicking the Add HTTP Redirector button automatically creates a port 80 redirect Virtual Service. This is optional, but the purpose of this Virtual Service is to redirect any clients who have connected via HTTP to the HTTPS Virtual Service.

KEMP recommends changing some settings in the Epic Medical Systems HTTPS Re-encrypt HTTP Redirect Virtual Service. The recommended settings are below:

Section

Option

Value

Standard Options

Persistence Mode

None

Real Servers

Real Server Check Method

None

Figure 4‑12: Epic Medical Systems HTTPS Re-encrypt HTTP Redirect Virtual Service Recommended Settings

References

Unless otherwise specified, the following documents can be found at http://kemptechnologies.com/documentation.

Feature Description, Virtual Services and Templates

Document History

Date

Change

Reason for Change

Version

Resp.

Aug 2016

Initial draft

First draft of document

1.0

LB

Was this article helpful?

0 out of 0 found this helpful

Comments