Guides

Approaching Your First Installation

Introduction

There are a few key things to keep in mind for a smooth installation. This guide provides a comprehensive overview of how a dental office functions, the various types of staff you may encounter, and the dynamics within the office environment. As a developer working on software solutions for dental practices, understanding these elements is essential for creating effective and user-friendly applications.

Office personas – Who You May Be Working With

To begin your installation, you will likely need to collaborate with someone in the office or their IT partner. Here are a few personas you may encounter:

  • Doctor/Dentist/Owner: While the doctor, dentist, or owner of the practice may not be the person you work directly with, their buy-in is crucial for a smooth installation. They can also provision additional users in the health record system, which might be required for installing the Synchronizer.
  • Office Manager: The Office Manager is responsible for keeping the office running smoothly and handling tasks such as scheduling, billing, and patient communications. They usually have access to the server computer and can often provision additional users in the health record system or install a Chrome extension on an office computer.
  • IT Partner: Many dental offices work with an IT partner to manage their health record system and office devices. This partner is often relied upon when implementing third-party software.

The First Call

Setting Expectations

The first call with the office is an opportunity to help them understand the installation process and build trust and confidence, ensuring a smooth experience for everyone. This call is also a chance to share more information about your product’s onboarding process and outline the next steps the office can expect.

During this call, you may need to address questions about how your app will use their data, explain what the Synchronizer is, clarify whether IT involvement is necessary, or determine if an additional health record system user needs to be provisioned.

Server-Based Installation

A server-based installation requires access to the office’s server computer. Typically, you’ll work with the Office Manager to gain access, so it’s important to be prepared to answer their questions. You can also self-install the Synchronizer for offices using Dentrix, Eaglesoft, or Open Dental.

System requirements are an operating system of Windows 10 or greater; Windows 2012 R2 Server or greater. 500 MB of RAM and 320 MB of storage (recommend: 1-2 GB).

Refer to the information below for scoping questions that will guide you through the server-based installation process.

Please note that you may encounter questions regarding NexHealth security.

Cloud installation

Most cloud installations will also require the NexHealth Chrome extension. Key points to note about the cloud installation process include:

  • A user must be created in the health record system to maintain the sync.
  • The office will need to install the NexHealth Chrome extension on all office computers, that access the health record system.
    • The Chrome extension does not place a load on the server—there is no impact on the machine’s performance.
    • The extension is limited to relevant domains.
  • NexHealth is SOC2 compliant.

Scoping Questions For Installing The Synchronizer

Server-Based Questions:

General: Best practices For Identifying The Server Computer

Here are some guiding questions you can use if the office isn’t sure what or where their server computer is before moving into more specific scoping questions based on the health record system:

  1. Is there a computer that is always on in the office?
  2. Is there a computer in the office that no one touches?
  3. Is there a computer that may not have a screen or keyboard?
  4. Verify the name of the machine where you’re installing the Synchronizer. Often they will have the word “SERVER” in their name.

Dentrix

Here are the most helpful scoping questions to ask offices that are using Dentrix.

  • What Version of Dentrix are you running?
  • Do you have in-house IT or do you outsource to a third party?
    • Who manages Dentrix for you?
  • Where is your Dentrix Server located? (The server)
    • Note: The server is often a machine in a back room and doesn’t always have a monitor. Generally, the doctor, office manager, or IT manages the server.
  • Does your server meet the following hardware requirements:
    • Free Storage: 320 MB
    • RAM: 512MB
  • What operating system is the server running?
    • NexHealth supports Windows 10 or greater; and Windows 2012 R2 Server or greater.
  • Is there anything unique that should be mentioned about your setup?
  • Can IT whitelist the following if needed?
    Ports

Dentrix Enterprise

Here are the most helpful scoping questions to ask offices that are using Dentrix Enterprise. Note that Dentrix Enterprise generally supports multi-location practices, so there may be an operations manager or centralized IT partner that you will be working with instead of an individual office manager to remote into the server computers.

  • What Version of Dentrix Enterprise are you running?
  • Do you have in-house IT or do you outsource to a third party?
  • Who manages Dentrix for you?
  • Where is your Dentrix Server located? (The server)
    *Note: The server is often a machine in a back room and doesn't always have a monitor. Generally, the doctor, office manager, or IT manages the server.
  • Does your server meet the following hardware requirements:
    • Free Storage: 320 MB
    • RAM: 512MB
  • What operating system is the server running?
    • NexHealth supports Windows 10 or greater; and Windows 2012 R2 Server or greater.
  • Do you allow vendors to install directly on the server?
  • Can IT whitelist the following if needed?

Ports

  • 4506, 4505, and 443

File paths

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

Domain names

http://nexhealth-backend-state-cache-development-us-east-1.s3.amazonaws.com/

Eaglesoft

  • What Version of Eaglesoft are you running?
  • Do you have in-house IT or do you outsource to a third party?
    • Who manages Eaglesoft for you?
  • Where is your Eaglesoft program hosted? (The server)
    • Note: The server is often a machine in a back room and doesn't always have a monitor. Generally, the doctor, office manager, or IT manages the server.
  • Is more than one location hosted on your server?
  • Does your server meet the following hardware requirements:
    • Free Storage: 320 MB
    • RAM: 512MB
  • What operating system is the server running?
    • NexHealth supports Windows 10 or greater; and Windows 2012 R2 Server or greater.
  • Do you allow vendors to install directly on the server?
  • Can IT whitelist the following if needed?
    Ports

Open Dental

Here are the most helpful scoping questions to ask offices that are using Open Dental.

  • What Version of Open Dental are you running?
  • Do you have in-house IT or do you outsource to a third party?
    • Who manages Open Dental for you?
  • Where is your Open Dental Server hosted? (The server)
    • Note: The server is often a machine in a back room and doesn't always have a monitor. Generally, the doctor, office manager, or IT manages the server.
  • Is more than one location hosted on your server?
  • Do you know if you have middle-tier enabled?
  • What operating system is the server running?
    • NexHealth supports Windows 10 or greater; and Windows 2012 R2 Server or greater.
  • Do you allow vendors to install directly on the server?
  • Can IT whitelist the following if needed?

Ports

  • 4506, 4505, and 443

File paths

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

Domain names

OrthoTrac and Dolphin

  • What Version of Orthotrac/Dolphin are you running?
  • How do you cancel appointments in Orthotrac/Dolphin?
  • Do you have in-house IT or do you outsource to a third party?
    • Who manages Orthotrac/Dolphin for you?
  • Where is your Orthotrac/Dolphin Server hosted?
    • Note: The server is often a machine in a back room and doesn't always have a monitor. Generally, the doctor, office manager, or IT manages the server.
  • Is this a multi-location setup?
    • What locations would you like us to sync? This information should be shared with NexHealth.
  • Can you give us SQL database access?
  • What operating system is the server running?
    • NexHealth supports Windows 10 or greater; and Windows 2012 R2 Server or greater.
  • Do you allow vendors to install directly on the server?
  • Applicable only for online booking use-case:
    • What appointment type should we insert into your schedule?
    • This must be shared with NexHealth Developer Support when submitting the installation
  • Can IT whitelist the following if needed?
    Ports

Cloud Questions:

🚧

Always test credentials!

For cloud systems, credentials should always be tested to work before submitting an installation request in the NexHealth Developer Portal. This will expedite the processing time for your installation request.

🚧

Chrome Extension Required:

Unless otherwise stated, for cloud systems the Synchronizer will require the deployment of the Chrome Extension to office workstations to provide the most accurate and stable data read.

Athena
Curve
Denticon
Dentrix Ascend
eClinicalWorks
Cloud9

Athena

Here are the most helpful scoping questions to ask offices that are using Athenahealth (Athena).

  • Who manages Athena for your team?
  • Do you have a way to mass-deploy software to all of your workstations? (e.g., Windows group policy; ConnectWise Automate; NinjaRMM; etc.)
  • Do you have in-house IT or do you outsource to a third party?
  • What web browser are you using?
    • Nexhealth requires either Edge or Chrome because of the Chrome Extension requirements.
  • Can you provide us with the required permissions for a user?
    • Administrative user (specific privileges available upon request- contact NexHealth Developers Support)
      • BEST PRACTICE - Credentials should always be tested to work before submitting an installation.
  • What Departments would you like to sync?
    • This should be shared with NexHealth Developers Support when installation is submitted.

Cloud 9

Here are the most helpful scoping questions to ask offices that are using Cloud 9.

  • Who manages Cloud9 for your team?
  • Applicable only for online booking use-case:
    • Is there a default appointment type you would like to use (applicable if using online booking)
      • This must be shared with NexHealth Developer Support when submitting the installation.
  • Do you have a way to mass-deploy software to all of your workstations? (e.g., Windows group policy; ConnectWise Automate; NinjaRMM; etc.)
    • Do you have in-house IT or do you outsource to a third party?
  • What locations would you like to sync?
    • This should be shared with NexHealth Developers Support when installation is submitted.
  • Can you provide us with the required permissions for a user?
    • Administrative user (specific privileges available upon request, contact NexHealth Developers Support)
    • BEST PRACTICE - Credentials should always be tested to work before submitting an installation
  • Can you provide us with your unique practice URL for Cloud9?
  • What web browser are you using?
    • Nexhealth requires either Edge or Chrome because of the Chrome Extension requirements.

Denticon

Here are the most helpful scoping questions to ask offices that are using Denticon.

  • Who manages Denticon for your team?
  • How many workstations do you have across your offices
  • Do you have in-house IT or do you outsource to a third party?
    • Do you have a way to mass-deploy software to all of your workstations? (e.g., Windows group policy; ConnectWise Automate; NinjaRMM; etc.)
  • What locations would you like to sync?
    • This must be shared with NexHealth Developer Support when submitting the installation.
  • Can you provide us a user with the required permissions?
    • Administrative user (specific privileges available upon request- contact NexHealth Developers Support).
    • No time-based login restrictions
    • BEST PRACTICE - Credentials should always be tested to work before submitting an installation.
  • What web browser are you using?
    • Nexhealth requires either Edge or Chrome because of the Chrome Extension requirements.

Dentrix Ascend

Here are the most helpful scoping questions to ask offices that are using Dentrix Ascend.

  • Who manages Dentrix Ascend for your team?
  • Do you have a way to mass-deploy software to all of your workstations? (e.g., Windows group policy; ConnectWise Automate; NinjaRMM; etc.)
    • Do you have in-house IT or do you outsource to a third party?
  • What locations would you like to sync?
    • required, this should be shared with NexHealth developers support when installation is submitted.
  • Can you provide us with the required permissions for a user?
    • New Dentrix Ascend username and password with administrative access (specific privileges available upon request, contact NexHealth Developers Support).
    • BEST PRACTICE - Credentials should always be tested to work before submitting an installation.
  • What web browser are you using?
    • Nexhealth requires either Edge or Chrome because of the Chrome Extension requirements.

eClinicalWorks (cloud-only)

Here are the most helpful scoping questions to ask offices that are using eClinicalWorks.

  • Who manages eClinicalWorks for your team?
  • How do your teams access ECW? Via a URL or desktop application?
    • If using a URL, can this be accessed outside of their network?
      • If not, contact NexHealth Developers Support.
    • Do they use the ECW browser plugin?
      • If yes, contact NexHealth Developers Support.
  • Do you have a way to mass-deploy software to all of your workstations? (e.g., Windows group policy; ConnectWise Automate; NinjaRMM; etc.)
    • Do you have in-house IT or do you outsource to a third party?
  • Can you provide us a user with the required permissions?
    • Administrative user (specific privileges available upon request, contact NexHealth Developers Support)
    • BEST PRACTICE - Credentials should always be tested to work before submitting an installation.
  • What clinics would you like to sync?
    • required, this should be shared with NexHealth developers support when installation is submitted.
  • What web browser are you using?
    • Nexhealth requires either Edge or Chrome because of the Chrome Extension requirements.

Curve

Here are the most helpful scoping questions to ask offices that are using Curve.

  • Who manages Curve for your team?
  • Can you provide us a user with the required permissions?
    • Office Manager or greater permissions.
    • BEST PRACTICE - Credentials should always be tested to work before submitting an installation.
  • Do you have in-house IT or do you outsource to a third party?
    • Do you have a way to mass-deploy software to all of your workstations? (e.g., Windows group policy; ConnectWise Automate; NinjaRMM; etc.)
  • What offices would you like to sync?
    • required, this should be shared with NexHealth developers support when installation is submitted.
  • What web browser are you using?
    • Nexhealth requires either Edge or Chrome because of the Chrome Extension requirements.

ModMed

Here are the most helpful scoping questions to ask offices that are using ModMed.
Note: ModMed does not require a Chrome extension, but will require two unique login credentials.

  • Who manages ModMed for your team?
  • What URL does your team use to log in? (Required)
  • What locations do you want us to integrate with? (Required)
  • Can you provide us with two users with the required permissions? (Required)
    • Staff account (specific privileges available upon request- contact NexHealth Developers Support).
    • Management Account with Administrator role (Not Assistant Administrator) account (specific privileges available upon request, contact NexHealth Developers Support).
    • BEST PRACTICE - Credentials should always be tested to work before submitting an installation.
  • Do you have in-house IT or do you outsource to a third party?
    • Do you have a way to mass-deploy software to all of your workstations? (e.g., Windows group policy; ConnectWise Automate; NinjaRMM; etc.)

Did this page help you?