Map and customize HCP, HCO, and relationship types
Align your Reltio model with Veeva Vault CRM by mapping entity types, relationships, and attributes for healthcare professionals (HCPs), healthcare organizations (HCOs), and associated data.
To enable accurate data synchronization, the Reltio model must reflect the entity types and relationships expected by Veeva Vault CRM. The integration is built to work with Reltio for Life Sciences Velocity Pack data model. This topic explains how to align or customize your Reltio entity definitions, attributes, and relationship types using mapping tables within the Reltio Integration Hub (RIH).
Understand the default model structure
The integration supports these key entity types and relationships for Reltio LS (Life Sciences) Velocity Pack by default:
- HCP (Healthcare Professional): This entity includes attributes such as name, credentials, specialty, licenses, and identifiers.
- HCO (Healthcare Organization): This entity includes name, address, organization type, and contact data.
- Location: This is modeled as a reference attribute linked to HCPs or HCOs.
- Relationships: The following types are supported:
- HCPisAffiliatedWithHCO (for provider affiliations)
- OrganizationHierarchy (for parent–child relationships between HCOs)
To learn more about supported data domains, see Use cases and supported data domains.
Customize your model and mappings in RIH
Follow these steps to align your entity types and attributes with Veeva Vault CRM expectations using the mapping lookup tables in your integration project.
- Your entity types (example,
HCP,HCO) and relationship types exist in your Reltio L3 configuration - You have access to edit lookup tables in your RIH project
- You understand which fields in Vault CRM need to be populated
- In your RIH account, go to
Lookup Tables - Open the relevant mapping table:
Veeva Integration Mapping – HCPVeeva Integration Mapping – HCOVeeva Integration Mapping – LocationVeeva Integration Mapping – Relationships
- Review the following column headers in the mapping table, and add a custom attribute if needed:
- Reltio URI – the attribute path in the Reltio model
- Veeva Object – the target object in Vault CRM
- Veeva Vault Field – the destination field nameTo add a custom attribute:
- Add a new row in the table.
- Enter the Reltio attribute URI.
- Specify the matching Veeva object and destination field
- Save the updated mapping table.
- If the attribute belongs to a custom entity or relationship, confirm that your recipes reference it correctly.
- Test the updated mapping using sample records.
Your recipes will now map Reltio attributes to the correct Veeva Vault CRM fields, including any custom attributes you've added. These mappings ensure data integrity during integration and reduce the need for manual intervention.
Verify that mapping updates are working as expected
- Run a test update in Reltio for an HCP or HCO with mapped attributes.
- Confirm that the update triggered a sync to or from Veeva Vault CRM.
- Review the job log in RIH to ensure the recipe ran without mapping errors.
- Verify in Vault CRM that the expected field values are present and correct.