Load balancing Epic EHR
About Epic EHR
The Epic EHR (Electronic Health Records) software suite brings together essential tools for clinicians and patients in the healthcare space, including Epic Hyperspace and Epic MyChart.
Epic Hyperspace is a clinician-facing platform. It’s a front-end client used to access most parts of the Epic software suite, including patient charts, prescribing, and even print services.
Epic MyChart is a patient-facing web portal. It gives patients the ability to view their medical records and test results, manage their appointments and prescriptions, and more.
Key benefits of load balancing
Here are a few key benefits:
- Ensures the application is always available
- Provides a stable, optimal performance
- Ability to isolate servers which reduces risk when performing upgrades/maintenance
How to load balance Epic EHR
The Epic EHR applications require sessions to stick to the same real server. Source IP address affinity is used to achieve this. To provide load balancing and high availability (HA) for Epic EHR, the following virtual services are required:
- Hyperspace redirect (to force inbound HTTP traffic to use HTTPS)
Optionally, additional virtual services may be required as follows:
- MyChart redirect (to force inbound HTTP traffic to use HTTPS)
Our recommended configuration is to use a clustered HA pair of load balancers to provide a highly available and resilient load balancing solution.
We recommend that the Primary appliance should be configured first, then the Secondary should be added. Once the Primary and Secondary are paired, all load balanced services configured on the Primary are automatically replicated to the Secondary over the network using SSH/SCP.
The clustered HA pair uses Heartbeat to determine the state of the other appliance. Should the active device (normally the Primary) suffer a failure, the passive device (normally the Secondary) will take over.