Use cases and supported data domains
Learn which entities and business scenarios are supported in the Reltio–Veeva Vault CRM integration.
The Reltio Integration for Veeva Vault CRM supports bi-directional data exchange across core life sciences entities. This topic outlines the supported object types and explains the kinds of updates and sync scenarios that can be configured using prebuilt recipes in the Reltio Integration Hub (RIH).
Supported data domains
| Data Domain | Description |
|---|---|
| HCP (Healthcare Professional) | Includes demographic, credential, license, and identifier fields |
| HCO (Healthcare Organization) | Captures institution type, address, contact, and hierarchy data |
| Location | Address-level data linked to HCPs or HCOs via reference attributes |
| Relationships | Includes HCP–HCO affiliations, HCO–HCO hierarchies, and crosswalks |
| Identifiers | External IDs and system-specific keys for entity mapping |
| Reference Data | Dropdown values and lookup values (through RDM) used in Veeva Vault CRM |
Integration use cases by direction
The integration supports the following system-to-system actions:
- Create or update HCP and HCO entities
- Propagate changes to location, license, or identifier attributes
- Send HCP–HCO and HCO–HCO relationships
- Push entity merges and remove losing records through end-dating
- Reflect entity deletes using crosswalk or source-based logic (real-time only).This behavior is not applicable in batch mode..
- Ingest new accounts, addresses, or affiliations
- Raise DCRs for review in Reltio based on field edits
- Send changes to existing HCO hierarchies
- Update master records based on approved changes in Vault CRM
Integration mode support
Each of these use cases can be configured using real-time or batch mode, depending on your performance, volume, and scheduling needs.
For a comparison of real-time and batch processing, see Real-time and batch integration flows.