Vault CRM
The Vault CRM Connector is a Medical Information Cloud Labs package that enables bi-directional data exchange between Medical Information Cloud and Veeva Vault CRM. The connector provides three capabilities that can be enabled independently:
- Account Search - searches Vault CRM for Healthcare Professionals (HCPs) and Healthcare Organizations (HCOs) and returns them as Medical Information Cloud Accounts.
- User Search - resolves the Vault CRM user (Sales Representative) who submitted an inquiry into a Medical Information Cloud Account, so inbound forms can be attributed correctly.
- MIRF Integration - synchronizes Medical Inquiry Records (MIRFs) between Vault CRM and Medical Information Cloud in both directions.
The connector can integrate with multiple Vault CRM instances and can run in parallel with the other account data sources, such as the Veeva Network and Veeva CRM integrations.
Veeva Vault CRM is a distinct product from the classic Veeva CRM integration. If you are configuring the classic integration, see the Veeva CRM topic instead.
Installation
Install the connector from the Komodo Health installer:
https://install.komodohealth.com/products/mic-veeva-connectors/latest
The installer can also deploy the connector's default configuration (the custom metadata records, field mappings, and value mappings that ship with the connector). This gives you a working baseline that you can adjust to match your Vault CRM instance.
Install the default configuration into a development (sandbox) org first, customize it there to match your Vault CRM instance and business rules, and then deploy your customized configuration to higher environments (such as UAT and Production). Installing the default configuration directly into a higher environment can overwrite existing settings and is not recommended.
Architecture overview
The connector is built on a shared base layer that handles authentication, session management, and HTTP communication with Vault CRM:
- Authentication - the connector authenticates to each Vault CRM instance with a username and password supplied through a Salesforce External Credential and Named Credential.
- Session caching - Vault sessions are cached in the Salesforce Platform Cache to avoid re-authenticating on every callout.
- API communication - all queries are issued as Vault Query Language (VQL) requests against the Vault CRM REST API.
Configuration summary
Each capability is configured separately, but they share the same connection setup. At a high level:
- Create the External Credential and Named Credential for each Vault CRM instance and grant access to the relevant users.
- Configure Account Search using the Medical Information Cloud Master Data Management (MDM) custom metadata.
- (Optional) Configure User Search to resolve the submitting Sales Representative.
- (Optional) Configure the MIRF Integration and schedule its pull and push batch jobs.
Declarative components
The connector ships two custom metadata types that are specific to the MIRF Integration:
| Custom metadata type | Purpose |
|---|---|
KLAB_VaultCRM_Org__mdt | Registers each Vault CRM instance and its connection settings. |
KLAB_VaultCRM_MIRF_Field_Mapping__mdt | Defines the MIRF field mappings for inbound pull and outbound push. |
The Account Search and User Search capabilities reuse the standard Medical
Information Cloud MDM custom metadata types (MED_MDM_Connection__mdt,
MED_MDM_Field_Mapping__mdt, and MED_MDM_Value_Mapping__mdt). For details
on these types, see Master Data Management.
The connector does not ship any Lightning pages (FlexiPages). It does include two record-management page layouts, one for each custom metadata type above, so administrators can edit records in Setup.