You are here:
Claims Harmonization Overview
Claims harmonization involves moving claims data from custom objects in the Vlocity managed package object model to standard objects in the Salesforce object model. The Vlocity model supports the Asset → InsuranceClaim relationship between policies and claims. The Salesforce model supports the InsurancePolicy → Claim relationship between policies and claims. Services and LWCs are updated to work with claims data in the Salesforce data model.
In an org harmonized for claims:
-
There are no references to the Vlocity Party model. ClaimParticipant replaces InsuranceClaimPartyRelationship and directly uses ContactId, AccountId, and InsurancePolicyParticipantId instead of using PartyId.
-
The
InsuranceClaimInvolvedInjury__candInsuranceClaimInvolvedProperty__ccustom objects are consolidated into theClaimItemobject. TheClaimItem.Categoryfield designates the Claim Item as Involved Injury or Damaged Property. -
The
ClaimLineItem__cobject is split into these three objects to allow for specificity in object design:-
ClaimCoveragePaymentDetail -
ClaimCoveragePaymentAdjustment -
ClaimCoverageReserveDetail
-
-
The
vlocity_ins__InsClaimReserveTransaction__cis replaced withClaimCoverageReserveAdjustment.
Underlying services support both Vlocity and Salesforce object models. But in the context of claims, the term "Item" in service and LWC names means "Financial Item" for both models, not "damaged/involved Item."
For details on Claims harmonized objects and the field mappings for each object, see Vlocity InsuranceClaim__c to FSC Claim Harmonized Object Model Mapping.
This diagram shows a high-level view of Claims objects in the Salesforce data model.
