The match model determines how your data is matched. You can use the predefined match model to identify and resolve duplicate records.
Customer 360 for Healthcare uses the Match Model for HCO Deduplication predefined match model to match and merge duplicate HCO business entity records. The following table describes the match model properties:
Descriptive Rule Rank
Match Objective
Match Strategy
Match Fields
Description
1
Resolve Duplicates
Exact
Exact match fields:
- X_infac360ls_subType
- X_infac360ls_type
- name
- PostalAddress.addressLine1
- PostalAddress.country
- PostalAddress.postalCode
- PostalAddress.state
Exactly matching name and address.
2
Resolve Duplicates
Fuzzy
Exact match fields:
- X_infac360ls_subType
- X_infac360ls_type
- AlternateIdentifier.idType
- AlternateIdentifier.altIdValue
- PostalAddress.country
- PostalAddress.postalCode
- PostalAddress.state
Fuzzy match fields:
- PostalAddress.addressLine1
- name
Strongly similar HCO name, address, and identifier.
3
Exact match fields:
- X_infac360ls_subType
- X_infac360ls_type
- AlternateIdentifier.idType
- AlternateIdentifier.altIdValue
Fuzzy match fields:
- name
Similar HCO name and alternate id
4
Exact match fields:
- X_infac360ls_subType
- X_infac360ls_type
- PostalAddress.country
- PostalAddress.postalCode
- PostalAddress.state
Fuzzy match fields:
- PostalAddress.addressLine1
- AlternateName.name
Similar HCO alternate name and address
Exact match fields:
- X_infac360ls_subType
- X_infac360ls_type
- PostalAddress.country
- PostalAddress.postalCode
- PostalAddress.state
Fuzzy match fields:
- PostalAddress.addressLine1
- name
Similar HCO name and address.
Customer 360 for Healthcare uses the Match Model for HCP Deduplication predefined match model to match and merge duplicate HCP business entity records. The following table describes the match model properties: