Vault Clinical Operations - Vault CRM Connection
Customers can streamline collaboration between clinical study teams and Medical Science Liaisons (MSLs) using the Vault Clinical Operations - Vault CRM Connection. This connection increases visibility of all interactions across both systems by providing a complete view of clinical and site interactions. HCP data is automatically synchronized between Vault Clinical and Vault CRM, allowing organizations to coordinate interactions more effectively.
The Clinical Operations - Vault CRM Connection enables bidirectional sharing of information between Vault Clinical Operations and Vault CRM. In Vault CRM, you can select Send to Vault Clinical to send a call report from Medical CRM to a connected Clinical Operations Vault as a Medical Activity. Additionally, Clinical Activities you capture in your Clinical Operations Vault are visible in CRM as Vault Clinical Interactions.
Who can use this feature?
- Medical Science Liaisons - Browser, iPad, iPhone, Windows
- Exchanging Medical Data Between Vault Clinical and Vault CRM
- Syncing Call Report Data with Vault Clinical
- Users require a Vault Clinical Operations license
Configuring the Vault Clinical Operations - Vault CRM Connection for
To configure this feature:
- Ensure the New Content Supply Chain Country Integration and PromoMats/Medical-CRM Country Integration are active. See About the PromoMats-CRM Connection for more information.
- Ensure the following features are configured:
- Call Reporting
- Medical Discussions (if using with Call Reporting)
- Navigate to Admin > Users & Groups > Permission Sets.
- Select the appropriate permission set.
- Select the Objects tab.
- Grant the following permissions:
Object
Object Permission
Object Types
Fields
Field Permission
vault_clinical_study__v
R
All Object Types
- modified_date__v
- study_recruitment_status__v
- vault_clinical_product__v
Read
vault_clinical_study_country__v
R
All Object Types
- country__v
- lifecycle_state__v
- link__sys
- modified_date__v
- name__v
- status__v
- study__v
Read
vault_clinical_site__v
R
All Object Types
- modified_date__v
- study_country__v
- site_recruitment_status__v
- site_name__v
- site_status__v
- vault_clinical_study__v
Read
connection_settings__v
RE
clinical_connection_settings__v
- clinical_person_identifier__v
- crm_account_identifier__v
Edit
call2_discussion__v
RE
All Object Types
study_country__v
Edit
medical_discussion__v
RE
All Object Types
study_country__v
Edit
- Navigate to Admin > Objects > connection_settings__v.
- Ensure the Display in Business Admin check box is selected on the Details tab
- Select the Layouts tab
- Create a layout for the clinical_connection_settings__v object type
- Select Done
- Select the Object Types tab.
- Ensure the clinical_connection_settings__v object type is enabled for the clinical_person_identifier__v and crm_account_identifier__v fields
- Navigate to Business Admin > Objects > connection__settings__v.
- Select Create
- Select Clinical Connection Setting
- Select Continue
- Populate the following fields to map person and account matching keys:
- Clinical Person Identifier - ID field on the Person object in the Vault Clinical Operations application
- CRM Account Identifier - ID field on the account__v object that is used for matching a person from Vault Clinical Operations. For example, account__v.veevaid__v
A valid 1:1 match between the Clinical Person Identifier and CRM Account Identifier is required. If multiple matches or no matches are found, the record is skipped.
- Select the applicable territories and country values from the Country Filter pick list to activate standard country-matching filters.
It is recommended that Country Match is always used if operating a global ClinOps Vault connected to regional CRM Vaults. For example, this prevents European CRMs from displaying US-only clinical activities.
- Select Save.
- Navigate to Business Admin > Objects > vmobile_object_configuration__v.
- Ensure VMOCs are enabled for the following objects for the appropriate platforms:
- vault_clinical_study__v
- vault_clinical_study_country__v
- vault_clinical_site__v
- Complete the required configuration steps in Vault Clinical. For more information, see Configuring the Clinical Operations to Medical CRM Connection.
Exchanging Medical Data Between Vault Clinical and Vault CRM as
TheVault Clinical Operations - Vault CRM Connection exchanges the following data:
- From Vault Clinical to Vault CRM:
- Vault Clinical activities - pushed into Vault CRM as Call records.
- Clinical Study information - pushed into Vault CRM as study data on Call records. Admins can also view this information from the Clinical Studies tab.
- Clinical Site information - pushed into Vault CRM as study site data on Call records. Admins can also view this information from the Clinical Sites tab.
- Study Country
- From Vault CRM to Vault Clinical:
- Call Report records (Includes call discussions and medical discussions) - pushed from Vault CRM and created as Medical Activities in Vault Clinical
This connection allows MSLs to view medical activity information about an HCP in Vault CRM with both Vault Clinical details and Vault CRM activities displayed. MSLs select a record to view the Study, Study Country, and Study Site discussed.
MSLs can also view clinical interactions in the Vault CRM Account Timeline. When a Clinical Research Associate (CRA) logs an activity in Vault Clinical, the activity automatically displays on the HCP's Account Timeline in Vault CRM. These records have the object type vault_clinical_interaction__v.
Syncing Call Report Data with Vault Clinical as
MSLs send call report data to Vault Clinical to provide CRAs with valuable Vault CRM medical information.
To send call report data to Clinical Operations:
- Create a call report in Vault CRM.
- Add a Medical Discussion or Call Discussion.
- Ensure a relevant Study Country is selected.
- Select the Send to Vault Clinical check box.
- Select Save. The system sends a notification to Vault Clinical to pull the data. The Send to Vault Clinical check box on the record becomes read-only and cannot be deselected.

