Match Rules
Helps you to identify duplicate profiles and then consolidate it for one golden copy or operational value of attributes for each entity.
Loading records from the source file creates duplicate record of the profiles that are already available in the data tenant. A match rule helps you to identify duplicate profiles, and then consolidate it for one golden copy or operational value of attributes for each entity.
| Type of match rule | Description | Example |
|---|---|---|
| Exact | An Exact match rule matches records that have identical values in match columns. | As per a match rule defined for the HCP entity type, one of its attribute's value that is First Name is Exact. In such a case, all the HCP records that have the exact first name such as 'John', are duplicate profiles. |
| Fuzzy | A Fuzzy match rule matches similar records based on probabilistic match determinations that consider likely variations in data patterns such as misspellings, transpositions, omissions, and phonetic variations. | As per a match rule defined for the HCP entity type, one of its attribute's value that is Name is Fuzzy. In such a case, all the HCP records that have the approximately same name such as 'John Smith' or 'John S' or 'J Smith' or 'Jon Smith', are duplicate profiles. |
| Exact and Equal (EE) | An Exact and Equal match rule is a combination of two features of match rules. It ensures that in multiple nested values, only corresponding entries are compared. | As per a match rule defined for the HCP entity type, one of its attribute's value that is State License Number is Exact and Equal (EE). In such a case, all the HCP records that have the exact Identifier Type (such as 'NPI' or 'DEA'), and exactly the same Identifier Value, are duplicate profiles. |
| Exact or Null (EON) | An Exact or Null match rule is used for attributes that should be either exact or null. | As per a match rule defined for the HCP entity type, one of its attribute's value that is Middle Name is either Exact or Null (EON). In such a case, all the HCP records that have either exact middle name such as 'Michael' or no information in the middle name, are duplicate profiles. |
Note: All match rules defined for HCO and HCP entities (not for Location entity), list duplicate records as suspect matches.
For more information on match rules, see topic Rule Element.