Intro
For on-premise EHR and PM connections, the Healthjump agent (jumpagent.exe) is a small, lightweight application that allows Healthjump to safely and effortlessly extract EHR and PM data from its source and to the Healthjump cloud.
The agent installation requirements (Technical Specifications) can be found here: The Healthjump Agent (jumpagent.exe)
Please note, upon installing and binding the Healthjump agent to the secret key generated during the initial installation, the data points needed to connect to the EHR/PM will already be populated. Thus, the only action typically needed when the agent is initially opened is to verify the information and conduct the connection test. Unless a change to the DB credentials or source database location occurs, the GUI should not need to be accessed after the initial setup.
For information on updating the agent settings, please see this article: JumpAgent Re-Installation and Configuration Guide
Post install, the GUI will be accessible via a desktop icon created during the install: 
, or can be accessed from the install directory : C:\Program Files (x86)\Healthjump\JumpAgent\
The Healthjump GUI
EMR
1. EMR - This is the EMR the agent is configured to connect to.
2. Version - If available, the version can should entered. This helps Healthjump track version changes that may require an update to our extraction process.
Local Windows User
Healthjump can utilize both DB credentials or Windows credentials with permissions to the EHR or PM SQL database. If Windows User is the selected connected method, this section should be populated.
3. Username - This is the windows domain and username. (domain\username)
4. Password - Windows user password
5. Allow RDP - When selected, this feature allows Healthjump to RDP into the agent workstation strictly for trouble shooting purposes.
Database
6. Server IP - This is the database IP Address. Please note the agent does not need to be installed on the database server, just be able to connect to the database IP Address.
7. Port - The database port
8. DB Version - SQL Server, MySQL, Postgres, Oracle, etc.
9. DB Name - The EHR or PM Database Name (ie. NGPROD, EMR, etc.)
10. Use Windows Authentication - If the connection will be using windows auth as mentioned above, this checkbox should be selected.
11. SQL Username - The SQL DB username. Note: Healthjump will typically only need read-only credentials.
12. SQL Password - SQL DB username password.
13. Test Connection - Upon opening the agent GUI, most of the settings will already be populated as the information is captured during the install and secret key binding. Testing the connection will validate the credentials provided will grant the Healthjump agent access to the EHR or PM database.
Local Settings
14. Secret Key - The secret key that is bound to the installed agent. Once bound, only a Healthjump engineer can update the key.
15. Process Directory - During the Healthjump extraction process, file extracts from the source EHR/PM system are stored in the process directory prior to uploading to the Healthjump cloud. By default, this directory is the install path of the agent C:\Program Files (x86)\Healthjump. This directory can be changed to point to a drive or directory with more space. Healthjump recommends 5GBs to ensure enough space to support the initial extracts from a system.
16. Save and Restart - Save changes and restart the service.
17. Exit - Close the GUI.