Prerequisites

• Service Account with Read-Only Rights
• HTTPS w/ Username enabled for Outgoing Data Services via Epic System Pulse Configuration Editor
• HTTPS enabled for Incoming Data Services via Epic System Pulse Configuration Editor
• Valid SSL Certificate applied to Epic System Pulse Server
  • A copy of the SSL Certificate (*.cer file) is needed for the configuration
• Epic System Pulse Server Address
• Epic resource group name that you'll be connecting to
• Epic resource type id for the above resource group

Article Contents

1. Testing the Epic System Pulse Connection
   1. Example Expected Output
2. Epic System Pulse Monitoring Configuration
3. Post Installation

Testing the Epic System Pulse Connection

Before proceeding with configuring the Epic System Pulse integration, please test your setup outside of the product to confirm all prerequisites have been met.

1. Download and extract the "epicSystemPulseTests" powershell script to the machine that will be hosting the Epic integration for Goliath
   1. Epic System Pulse Test Script 
2. Run the script as admin and follow the below prompts. The script will have two sections worth of prompts and validations:
   1. Confirming it can connect to the Epic System Pulse Server.
      1. Expected Prompts:
         1. Epic System Pulse Server Address
         2. Username of the service account that has rights to Epic
         3. Password of the service account that has rights to Epic
         4. resource type id
         5. resource group name
   2. Confirming it can pull data using the resource group information provided 
      1. Expected Prompts:
         1. The host ID(s) for the epic data. Please note, it will list the ones it sees available if there are none available, confirm you have the correct resource group name and resource group id
         2. Start Date/Time for the metric collection (click enter to use the defaults)
         3. End Date/Time for the metric collection (click enter to use the defaults)

Example Expected Output

Testing the Epic System Pulse Connection

1. If the connection is successful you'll expect to see the text "Request Successful" after entering the "resource group" name. This is shown with call out #1 in the above image.
2. You should also expect to see connection details following the "Request Successful" message. This is shown with call out #2 in the above image.

Collecting Epic System Pulse Data

1. If the metric collection is successful, you'll expect to see the text "Request Successful" and then a large block of data. This is shown with call out #1 in the above image.

Epic System Pulse Monitoring Configuration

These steps will take you through the configuration process to begin monitoring your Epic System Pulse  environment(s).

1. Ensure you have a copy of the Epic System Pulse SSL Certification file (*.cer) on the Goliath Server
2. Download and install the Keystore tool - https://keystore-explorer.org/
   
   1. Be sure to set the install directory to the agent JRE\bin folder
      1. If configuring this on the Goliath Server the default locations is either "C:\Program Files (x86)\MonitorIT\vma-api\jre1.8.0_221\bin" or "C:\Program Files\MonitorIT\vma-api\jre1.8.0_221\bin", depending on your Goliath version
      2. If configuring this on a machine that is not the Goliath Server the default locations is "C:\Program Files\MonitorIT\vma-api\jre1.8.0_221\bin"
3. Run Command Prompt as Admin
4. Navigate to the appropriate directory via the appropriate command:
   1. If on the Goliath Server run the applicable command:

      1. cd "C:\Program Files (x86)\MonitorIT\vma-api\jre1.8.0_221\bin"
         cd "C:\Program Files\MonitorIT\vma-api\jre1.8.0_221\bin"

   2. If on another machine:

      1. cd "C:\Program Files\MonitorIT\vma-api\jre1.8.0_221\bin"

5. Then run the following command to import the Epic System Pulse SSL Certification file into the Goliath Agent
   1. Example:
      1. The first red text is the path the the JRE folder, 1 level up from where the command line is current running.
      2. The second red text is the path the the .cer file 

      3. keytool -import -alias "epicsystempulse" -keystore "C:\Program Files\MonitorIT\vma-api\jre1.8.0_221\lib\security\cacerts" -file "C:\users\test\Downloads\systempulse.cer"

6. Close Command Prompt and Open the Goliath web Console
7. Click on the Configure menu option at the top of the page, and select the Inventory submenu option
8. On the Inventory page, find and select the line item for the local Goliath Server
9. Click on the Edit button at the top of the page
10. A new pane will appear, there will be a section labeled Epic EHR Monitoring in this section please do the following:
    1. In the User Name and Password fields, please enter the credentials for the Read Only Service account for Epic System pulse in the format of domain\user
    2. Check the box for Enable Epic Monitoring
    3. In the Epic Server Address field, please enter the IP Address or FQDN of the Epic System Pulse machine
    4. In the Epic Production Resource Group field, please enter the name of the Epic resource group. The default value is "PRD"
    5. In the Epic Production TypeID field, please enter the name of the Epic resource group. The default value is "3" 
       1. 
11. Once all information is filled in, click the Save button to complete the configuration
    1. It may take about 5 minutes or so before the data will appear

Post Installation

From the Views tab and clicking on the Performance Graphs submenu option allows you to view the dashboard-style performance graphs for Epic.

From the top Dashboards section of the left hand menu pane, you can view the Epic System Pulse information collected by clicking on the check box to the left of the folder named Epic and then clicking on the large + symbol in the middle of the screen labeled Add Dashboard from Left Pane

The two dashboards related to monitoring Epic Workflow & Activity will appear and look like this: