---
title: "FAQs: Common Questions About Vim Implementation"
description: Provider Implementation FAQ
---

[Skip to content](https://knowledgebase.getvim.com/home/faqs-common-questions-about-vim-implementation#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. [Help Center](https://knowledgebase.getvim.com/home/help-center?hsLang=en)

# FAQs: Common Questions About Vim Implementation

### **1. What is Vim Connect?**

Vim Connect is an **overlay technology** that works directly with your Electronic Health Record (EHR) system.

- It is **context-aware**, meaning it recognizes what a user is doing in the EHR and surfaces helpful tools or workflows at the right moment — without disrupting your existing processes.
- Vim allows for **rapid deployment** and **seamless integration** across different EHRs, making it easy for practices to adopt without heavy IT involvement.

### **2. What is an MSI?**

**MSI** stands for **Microsoft Software Installer**, which is the framework used to install software on Windows.

Vim Connect can be installed using an MSI file. This approach ensures:

- A **“one solution fits all”** model rather than separate installers for each EHR.
- Compatibility with both **web applications** and **installed Windows applications**.

### **3. Does Vim work on tablets or mobile devices?**

Vim is **not currently supported** on tablets or mobile devices (including iPads or Chrome tablets).

### **4. Is Vim compatible with Windows and Mac?**

**Yes!** Vim Connect works on **Windows** and **Mac** computers.

### **5. How long does it take to download and install Vim?**

- **Console account activation:** ~5 minutes
- **Download per device:** ~3–4 minutes  
  If your practice has an **IT representative**, Vim recommends having them join your onboarding call — they can help push Vim to all devices remotely for faster setup.

### **6. Why does Vim need my EHR URL?**

Your EHR URL allows Vim to generate a **unique practice identifier**.  
This identifier enables:

- Secure access for your users through their **existing EHR usernames**.
- A seamless experience without needing extra passwords or logins.

### **7. Is Vim HIPAA compliant?**

**Yes!** Vim is fully **HIPAA compliant** and also **HiTrust certified**.  
For more details, see our[Security Overview](https://getvim.com/technology-security/).

### **8. How much does Vim cost?**

Vim Connect’s VBC core applications are **free** for your practice — **sponsored by the applicable data source (payers, ACOs and MCOs)**.

Additionally, Vim offers a **Marketplace** with other integrated applications:

- Some are **free**, while others are **subscription-based**.
- Vim **does not handle billing or payment** for third-party apps.
- Your account owners and admins [control access](https://knowledgebase.getvim.com/home/managing-marketplace-access-in-console?hsLang=en) to the marketplace via the admin Console.

Explore the Marketplace here:  
[How to Access and Manage Marketplace Apps in Console](https://knowledgebase.getvim.com/home/how-to-access-and-manage-marketplace-apps-in-console?hsLang=en)

### **9. Can I control which users have access to Vim?**

**Yes!** You can **manage user access and permissions** directly through **Vim’s Admin Console**.  
This gives your practice complete control over who uses Vim and which apps they can access.

### **10. What are the next steps?**

We just need to collect a few clinic details to create your account in preparation for an implementation call. Be sure to **invite your IT person** (if you have one) to the call when we send the invite over.

- [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)
    - [Vim Scribe](https://knowledgebase.getvim.com/home/applications?hsLang=en#vim-scribe)
- [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