---
title: "Onboarding to Vim: NextGen Enterprise"
description: "Onboard your NextGen Enterprise self-hosted organization to Vim: install Vim Connect on your NextGen servers, then set up single sign-on (SSO)."
---

[Skip to content](https://knowledgebase.getvim.com/home/onboarding-to-vim-nextgen#main-content)

[![Logotype-primary (1).png\]](https://knowledgebase.getvim.com/hs-fs/hubfs/Knowledge%20Base/Logotype-primary%20(1).png?height=50&name=Logotype-primary%20(1).png)](https://knowledgebase.getvim.com/home?hsLang=en)

Open main navigation

Close main navigation

- [Console](https://console.getvim.com/organization-admin/accounts?iss=https%3A%2F%2Fauth.getvim.com%2F)

[Console](https://console.getvim.com/organization-admin/accounts?iss=https%3A%2F%2Fauth.getvim.com%2F)

 Hello! How can we help you use Vim?

- There are no suggestions because the search field is empty.

1. [Practice Knowledge Base](https://knowledgebase.getvim.com/home?hsLang=en)
2. [Onboarding](https://knowledgebase.getvim.com/home/onboarding?hsLang=en)
3. [Technical Implementation](https://knowledgebase.getvim.com/home/onboarding?hsLang=en#technical-implementation)

# Onboarding to Vim: NextGen Enterprise

## Install Vim Connect on your NextGen servers, then set up single sign-on (SSO). Here's what to expect at each step and what your IT team will need to provide.

**NextGen Office is not supported at this time.** This article applies to NextGen Enterprise only.

Onboarding guideNextGen Self Hosted

On this page  
[Overview](https://knowledgebase.getvim.com/home/onboarding-to-vim-nextgen#overview)  
[Step 1: Install Vim Connect](https://knowledgebase.getvim.com/home/onboarding-to-vim-nextgen#step-1)  
•[Server requirements](https://knowledgebase.getvim.com/home/onboarding-to-vim-nextgen#requirements)  
[Step 2: Set up SSO](https://knowledgebase.getvim.com/home/onboarding-to-vim-nextgen#step-2)  
•[If you are not using SSO](https://knowledgebase.getvim.com/home/onboarding-to-vim-nextgen#no-sso)  
[NextGen-hosted practices](https://knowledgebase.getvim.com/home/onboarding-to-vim-nextgen#hosted)

**Overview**

NextGen Enterprise **self-hosted** organizations onboard to Vim in two parts:  
•Install Vim Connect on your NextGen servers  
•Then set up single sign-on (SSO)  
This article explains what to expect at each step and what your IT team will need to provide.

1

Install Vim ConnectOn every NextGen server users log in to

2

Set up SSOConnect your identity provider to Vim

Vim runs on NextGen through the **Vim Overlay**, a Windows application that launches when users log in to NextGen.

**Using Citrix or Remote Desktop Services (RDS)?** Vim must be installed on each server users connect to.

Step 1 · IT team

**Install Vim Connect on your NextGen servers**

Your IT team installs Vim Connect using the NextGen MSI installer and your **organization key**.

1. 1
   
   Download the NextGen MSI.[vim.health/desktop\_nextgen](https://vim.health/desktop_nextgen)
2. 2
   
   Get your **Organization Key** from your Vim implementation contact.
   
    Unique to your organization. Keep it internal.
3. 3
   
   Follow the install steps in [Installing Vim Connect on your PC (MSI installer)](https://knowledgebase.getvim.com/home/installing-vim-connect-on-your-pc-msi-installer-0?hsLang=en), entering your Organization Key when prompted.
4. 4
   
   For Citrix or RDS environments, repeat the install on **every server in the pool**.

**Server requirements**

Plan server capacity per concurrent Vim user:

| Resource | Per user |
| --- | --- |
| RAM | **200–600 MB**, depending on usage |
| CPU | **1–2%** |

Step 2 · IT team + Vim

**Set up single sign-on (SSO)**

SSO is the preferred login method for NextGen. Users are signed in to Vim automatically when the Vim Overlay starts at NextGen login.

1. 1
   
   Vim
   
   Vim sends you a unique identifier for your organization (for example, your-org-name).
2. 2
   
   Your IT teamCreate the Vim app in your identity provider (IdP) and enter that identifier, using the guide for your IdP:
   
   [Azure Active Directory / Microsoft Entra ID](https://knowledgebase.getvim.com/home/configure-vim-connect-sso-via-azure-active-directory?hsLang=en)[Active Directory Federation Services (ADFS)](https://knowledgebase.getvim.com/home/configure-vim-connect-sso-via-active-directory-adfs?hsLang=en)
3. 3
   
   Your IT teamSend Vim two items:
   
   SSO login URLSecurity (signing) certificate
4. 4
   
   VimVim completes the connection on our side and schedules a short test with your team.

**Backup sign-in:** if SSO ever fails, users can still sign in with a one-time password (OTP).

**If you are not using SSO**

Without SSO, Vim can use **silent login**, which requires both of the following:

Roaming profiles are set up for your users.

Each user's %appdata% folder is cached.

Seamless login is not yet available for the NextGen agent.

NextGen-hosted

**Is NextGen hosting your practice?**

If NextGen hosts your NextGen Enterprise servers, your IT team can't install Vim Connect directly. Request the install from NextGen instead, then continue with Step 2 to set up SSO.

**Request NextGen to install Vim**

1. 1
   
   Get your **Organization Key** and the NextGen MSI link (vim.health/desktop\_nextgen) from your Vim implementation contact.
2. 2Submit an install request to NextGen via your organization's typical request process and cc your Vim implementation specialist.
3. 3
   
   Include in your request:
     - Your practice name and \[NEXTGEN CLIENT ID\]
     - A request to install Vim Connect on every hosted server your users connect to
     - The NextGen MSI link and your Organization Key, shared securely
     - Your approximate number of concurrent Vim users (see [Server requirements](https://knowledgebase.getvim.com/home/onboarding-to-vim-nextgen#requirements))
4. 4NextGen confirms the install date. Let your Vim implementation contact know once it's scheduled.

 

- [Welcome to Vim](https://knowledgebase.getvim.com/home/welcome-to-vim?hsLang=en#main-content)

    - [How Vim fits into clinical workflows](https://knowledgebase.getvim.com/home/welcome-to-vim?hsLang=en#how-vim-fits-into-clinical-workflows)
    - [Vim Canvas Marketplace overview](https://knowledgebase.getvim.com/home/welcome-to-vim?hsLang=en#vim-canvas-marketplace-overview)
- [Onboarding](https://knowledgebase.getvim.com/home/onboarding?hsLang=en#main-content)

    - [Getting Started](https://knowledgebase.getvim.com/home/onboarding?hsLang=en#getting-started)
    - [Technical Implementation](https://knowledgebase.getvim.com/home/onboarding?hsLang=en#technical-implementation)
- [Applications](https://knowledgebase.getvim.com/home/applications?hsLang=en#main-content)

    - [Care Insights](https://knowledgebase.getvim.com/home/applications?hsLang=en#care-insights)
    - [Clinical Data Exchange (CDE)](https://knowledgebase.getvim.com/home/applications?hsLang=en#clinical-data-exchange-cde)
    - [Enhanced Eligibility](https://knowledgebase.getvim.com/home/applications?hsLang=en#enhanced-eligibility)
    - [Prior Authorization](https://knowledgebase.getvim.com/home/applications?hsLang=en#prior-authorization)
    - [Order Assist](https://knowledgebase.getvim.com/home/applications?hsLang=en#order-assist)
    - [Customer Programs](https://knowledgebase.getvim.com/home/applications?hsLang=en#customer-programs)
- [User Resources](https://knowledgebase.getvim.com/home/user-resources?hsLang=en#main-content)

    - [Vim Connect Users (For end users in the EHR)](https://knowledgebase.getvim.com/home/user-resources?hsLang=en#vim-connect-users-for-end-users-in-the-ehr)
    - [Vim Console Admins & Owners (For practice admins managing Console access)](https://knowledgebase.getvim.com/home/user-resources?hsLang=en#vim-console-admins-owners-for-practice-admins-managing-console-access)
    - [Vim Terminology](https://knowledgebase.getvim.com/home/user-resources?hsLang=en#vim-terminology)
- [How-to Guides](https://knowledgebase.getvim.com/home/how-to-guides?hsLang=en#main-content)

    - [Console Guides](https://knowledgebase.getvim.com/home/how-to-guides?hsLang=en#console-guides)
    - [Vim Connect Guides](https://knowledgebase.getvim.com/home/how-to-guides?hsLang=en#vim-connect-guides)
- [Help Center](https://knowledgebase.getvim.com/home/help-center?hsLang=en)
- [Get Involved](https://knowledgebase.getvim.com/home/get-involved?hsLang=en#main-content)

    - [Practice Experience Advisory Team (Invitation Only)](https://knowledgebase.getvim.com/home/get-involved?hsLang=en#practice-experience-advisory-team-invitation-only)
    - [Champion Program (Vim Console Admins & Owners)](https://knowledgebase.getvim.com/home/get-involved?hsLang=en#champion-program-vim-console-admins-owners)

[![Logotype-primary (1)](https://knowledgebase.getvim.com/hs-fs/hubfs/Knowledge%20Base/Logotype-primary%20(1).png?width=75&height=32&name=Logotype-primary%20(1).png "Logotype-primary (1)")](https://getvim.com/wp-content/uploads/2022/05/Transparent-logo.svg)

[getvim.com](https://getvim.com/)

Copyright © 2026, Vim