Guides

Preparing for a scheduled onprem NexHealth installation

An installation guide for onprem/server based EHRs that are not supported via self serve and must be scheduled with the NexHealth team. The applicable EHRs are Dentrix Enterprise, Dolphin, and Orthotrac.

Suggest Edits

In order to complete a manual installation with the NexHealth API, please use the developer portal to schedule server access with the NexHealth installation team and the practice’s IT. Before that call, please prepare the practice’s IT with the following information:

  • An overview of what service you provide
  • A copy of your BAA or verification of an executed BAA with the appropriate parties
  • Why we need server access (see below)
  • What tables/data we will be reading or writing (see below)

In order to set expectations and ensure that the correct team members are on the call, please communicate that we need IT’s help to perform the following tasks:

  • For Dentrix Enterprise: Create a SQL user or provide existing user credentials to SQL Server Management Studio
  • For Dolphin/Orthotrac: Create a SQL user or provide existing user credentials to Microsoft SQL Server Management Studio with the following database permissions:
    • db_owner permission
    • public permission
    • mapped to Main_OMS database
  • Whitelist files and folders for antivirus software (list provided below)
  • Whitelist ports for firewall (list provided below)

Why do we need server access?
NexHealth is our integration partner. To get started, the NexHealth team needs access in order to install their services on the hosting server (or another network machine) and UI access to your practice management system in order to QA once the connection is established.

Setting up remote access
NexHealth uses ConnectWise for remote access which will allow the team to temporarily take control of the server. At the start of the call, the team will provide a URL and code to set up that session. The connection will be disconnected once the installation and QA process has been completed.

How does the NexHealth synchronizer work?
The NexHealth integration utilizes a SQL user which will query the database roughly every 10 minutes for new data. It writes back in near real time.

What tables/data will we be reading or writing?
By default, our team will ask for the most permissions allowable so that you will have access to all existing and future API functionality.

However, we can provide a list of tables and SQL user permissions customized to your needs.
In this case, please note that permissions may need to be adjusted if you wish to add new functionality in the future. If you are unclear on how your app translates to database table access, please have a conversation with your NexHealth support representative.

Items for whitelisting

Ports

  • 4506, 4505, and 443

File paths

  • C:\NexHealth*
  • C:\Program Files\Salt Project\Salt*

Domain names

Updated 25 days ago