Match rules for Life Sciences

Learn what match rules are preconfigured in entity types for Reltio for Life Sciences.

Match rule define the criteria Reltio uses to determine whether two records are duplicates.

Match rules help in identifying duplicate profiles and help consolidate for one golden copy or operational value of attributes for each entity. Some preconfigured entity types in the Reltio for Life Sciences data model come with match rules.

All the match rules except for location are defined as suspect match rule, which you can change to an automatic rule, based on your data profiling or business use case.

Note: The location configuration is set up to deduplicate and is also consistent with the Salesforce connector requirement. Do not change this configuration. If there is a business requirement, contact Apps PM team to review before you make any changes.

For general information on match rules, see topic Reltio match and merge. For details on the preconfigured entity types that come with Reltio for Life Sciences, see Entity types for Life Sciences.

HCO entity type match rules (Life Sciences)

This table identifies the Reltio for Life Sciences match rules for the Location entity type. Use these match rules to create a record for an address.


Label	Description	Match queries
BaseRule1: Fuzzy (Name), Exact(Identifier)	Create potential matches	( Exacton Identifiers/ID [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Identifiers/Type [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and Fuzzyon Name [Comparator class:OrganizationNamesComparator] [Match token:OrganizationNameMatchToken]
BaseRule2: Fuzzy (Name), Exact (Address1, Zip)	Create potential matches	( Exacton Address/Address Line 1 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Zip/Zip5 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and Fuzzyon Name [Comparator class:OrganizationNamesComparator] [Match token:OrganizationNameMatchToken]
BaseRule3: Fuzzy (Name), Exact (Address1, State)	Create potential matches	( Exacton Address/Address Line 1 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/State [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and Fuzzyon Name [Comparator class:OrganizationNamesComparator] [Match token:OrganizationNameMatchToken]
LSRule1: Exact(Name, Address & NPI)	Automatically merge	( Exacton Name [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Address Type [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Address Line 1 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/City [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/State [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Country [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Zip/Zip5 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Zip/Zip4 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Verification Status [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Identifiers/ID [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and Exact Or All Nullon Address/Address Line 2 and ( Equalson Address/Verification Status [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Identifiers/Type )
LSRule2: Exact(Name, Address & DEA)	Automatically merge	( Exacton Name [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Address Type [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Address Line 1 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/City [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/State [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Country [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Zip/Zip5 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Zip/Zip4 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Verification Status [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Identifiers/ID [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and Exact Or All Nullon Address/Address Line 2 and ( Equalson Address/Verification Status [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Identifiers/Type )

HCP entity type match rules (Life Sciences)

This table identifies the Reltio for Life Sciences match rules for the Location entity type. Use these match rules to create a record for an address.


Label	Description	Match queries
BaseRule1: Fuzzy(First Name, Last Name); Exact (Address1, Zip5); ExactOrNull(Suffix, Email)	Create potential matches	( Exact on Address/Address Line 1 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Zip/Zip5 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and ( Exact Or Nullon Email/Email [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Suffix Name [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and ( Fuzzyon First Name [Ignored in token] [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] and Last Name [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] )
BaseRule2: Fuzzy(First Name, Last Name); Exact (Identifier, Identifier Type)	Create potential matches	( Exacton Identifiers/ID [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Identifiers/Type [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and ( Fuzzyon First Name [Ignored in token] [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] and Last Name [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] )
BaseRule3: Fuzzy (First Name, Last Name); Exact(Email)	Create potential matches	Exacton Email/Email [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and ( Fuzzyon First Name [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] and Last Name [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] )
BaseRule4: Fuzzy (First Name, Last Name); Exact(Phone)	Create potential matches	Exacton Phone/Number [Comparator class:PhoneNumberComparator] [Match token:ExactMatchToken] and ( Fuzzyon First Name [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] and Last Name [Comparator class:DoubleMetaphoneComparator] [Match token:DoubleMetaphoneMatchToken] )
LSRule1: Exact(Name, Address & NPI)	Automatically merge	( Exact on First Name [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Last Name [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Address Type [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Address Line 1 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/City [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/State [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Country [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Zip/Zip5 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Zip/Zip4 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Verification Status [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Identifiers/ID [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and ( Exact Or All Nullon Middle Name and Suffix Name [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Address Line 2 ) and ( Equalson Address/Verification Status [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Identifiers/Type )
LSRule2: Exact(Name, Address & DEA)	Automatically merge	( Exacton First Name [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Last Name [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Address Type [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Address Line 1 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/City [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/State [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Country [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Zip/Zip5 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Zip/Zip4 [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Address/Verification Status [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Identifiers/ID [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] ) and ( Exact Or All Nullon Middle Name and Suffix Name and Address/Address Line 2 ) and ( Equalson Address/Verification Status [Comparator class:BasicStringComparator] [Match token:ExactMatchToken] and Identifiers/Type )

Location entity type match rules (Life Sciences)

This table identifies the Reltio for Life Sciences match rules for the Location entity type. Use these match rules to create a record for an address.


Label	Description	Match queries
[Auto] Exact (Addr1, City, State, Country, Zip5, Verification Status) EOAN(Addr2, Zip4, Building, SubBuilding)	Automatically merges records when the full address OR the when the address line 2 and Zip code are an exact match or are null.	( Exacton Address Line 1 and City and State and Country and Zip/Zip5 and Verification Status ) and ( Exact Or All Nullon Address Line 2 and Zip/Zip4 and Building and Sub Building ) and Equalson Verification Statusvalues : Verified,Partially Verified

Unify and manage your data

Match rules for Life Sciences

HCO entity type match rules (Life Sciences)

HCP entity type match rules (Life Sciences)

Location entity type match rules (Life Sciences)

Footer