Vim's Solution Overview

Vim Connect Overview

Vim is a healthcare middleware platform designed to enhance provider workflows by integrating actionable insights directly into the EHR at the point of care. Vim’s Data Source Integration allows healthcare organizations to share Care Gaps and Diagnosis Gaps through Vim to enhance provider workflows, enabling bi-directional communication, improving care delivery, and optimizing patient outcomes.

This document outlines the requirements, configurations, and processes for onboarding data source customers to Vim.

About Vim Connect

Vim Connect is the technology that powers the Vim applications to display as an overlay on top of the EHR. Vim Connect is the easiest, fastest, and most scalable way to support providers at the point of care. To unlock the connection between providers and data sources, Vim Connect must be installed by provider organization users.

Vim Hub

Once installed on the provider’s computer, Vim Connect allows Vim applications to be presented in the EHR at the point of care:

Supported EHRs

Vim Connect scales across EHRs through a flexible and modular integration architecture. Current EHR deployment is highlighted below for notable EHRs:

• AthenaHealth
• DrChrono
• eClinicalWorks (eCW) versions 11.52 and above (including web, - desktop and plugin access)
• Elation
• NextGen Enterprise
• Office Ally EHR 24/7
• Practice Fusion
• TouchWorks

New EHRs are added regularly in coordination with our customers and partners, and based on market demand.

Vim Applications Overview

Care Insights

Vim’s Care Insights app streamlines care delivery by directly embedding patient care and diagnosis gaps into EHR workflows, removing the need for manual reviews, spreadsheets, or external platforms. This centralized approach drives higher engagement from medical teams, empowering them to close gaps effectively at the point of care. By surfacing actionable data, Vim’s Care Insights app not only improves risk adjustment accuracy but also enhances HEDIS metrics and overall quality scores. The app reduces administrative burdens, supports value-based care models, and ultimately elevates the quality of patient care, enabling providers to focus on meaningful interactions.

Vim’s Care Insights application offers the data source customer the ability to present their gaps in care data to the providers to enhance collaboration, improve outcomes, and align with value-based care goals:

• Care Gaps: Allowing the data sources to present preventive care opportunities such as overdue screenings, immunizations, or chronic care management opportunities.
• Diagnosis Gaps: Focuses on improving diagnostic accuracy by identifying and updating diagnosis information, highlighting suspected or unconfirmed conditions to guide clinical decision-making.

Vim’s offering includes additional applications, as well as third-party applications, for more information, contact a Vim representative.

The High-Level Data Flow

Vim’s solution establishes a seamless bi-directional connectivity between data connections and providers, for sharing diagnosis and care gaps information with providers within the EHR workflow at the point of care:

1. A patient attends a visit, and Vim detects the patient in context within the EHR.
2. Vim checks the patient’s eligibility against the customer’s data set.
3. For eligible patients, Vim retrieves gaps in care from the customer data.
4. If gaps are returned, they are displayed to the user at the point of care, and the user can take action. Where supported, the relevant information is written back to the EHR.
5. Vim shares back users' actions with the customer.

Patient Matching Mechanism

To ensure protected health information (PHI) is only displayed for the relevant patient within the EHR, Vim’s patient matching mechanism is designed to securely and accurately compare patient details and demographic information from the EHR with data received from the data source. The following patient data is used for matching: first name, last name, date of birth, and at least one of the following identifiers: EHR identifier (MRN), health plan identifier (member/subscriber ID), or zip code. While not all data elements are required, providing more complete information significantly improves matching accuracy. File integration patient matching mechanism The matching process uses several “methods” - multiple combinations of the above elements that simultaneously compare combinations of the above elements. Each method leverages a combination of exact and fuzzy matching techniques, ignoring minor variations like case or formatting differences. The results of these methods are compared, and if they produce conflicting matches, Vim considers this as a failure to match. By employing multiple methods, Vim improves the accuracy of the matching process, reduces errors, and increases the likelihood of correctly identifying the patient.

Main Entities in the Vim System

The integration is focused on two main entities: patient, gap. Each of these entities must have a unique identifier, which will be used consistently throughout the system, for internal communication between Vim and the customer, as well as for reporting purposes. Data for both patients and gaps is encrypted during the data ingestion process. The resulting encrypted tokens serve as identifiers within the system. For Vim’s applications to function accurately, it's crucial that Vim and the data source align on the following identifiers:

1. Unique Patient ID: Essential for accurately presenting sensitive data on the patient at the point of care and disrupt billing processes as Vim relies on these IDs to differentiate patients
2. Unique Gap ID: Required to accurately track and manage each gap for a specific patient. This identifier enables advanced application features, such as filtering addressed gaps and supporting the “undo” function when needed The unique internal IDs will be assigned by the data connection and shared with Vim for use within the system. For any concerns with assigning a unique patient and gap ID, please contact a Vim representative.

Important note: a change to the unique IDs received from the customer during the calendar year, introduces a risk of hindering system integrity, potentially implicating on the functionality of different features and billing.