Match

Data groups for similar names

Data groups that contain name fields can now be configured to include similar names instead of only identical names. For example, John Smith and Jon Smith can now be grouped in the same block so they are compared during the match process.

This enhancement is available by default in your Network instance.

When name fields are used in a data group, the option to group similar names displays. Administrators can select the option to instruct Network to include similar names in the group.

Default behavior

Data groups organize data from your Network instance and incoming files into smaller, specific blocks. This reduces the amount of data that needs to be compared during the match process.

By default, only identical strings in field values are grouped.

In this example, John Smith and Jon Smith are organized in different blocks because they are not identical.

This can result in missed matches because these records will not be compared to each other during the match process.

When the option to group name fields based on fuzzy logic (similar names) is enabled, similar names are grouped.

Now, the match process will compare the John Smith and Jon Smith records.

Note: The match process has not changed.

Supported fields

The following name fields for HCOs and HCPs are supported.

If any of these fields are included in a data group, the option to group similar name values displays.

HCP name fields	HCO name fields
alternate_first_name__v	corporate_name__v
alternate_middle_name__v	alternate_name_1__v
alternate_last_name__v	alternate_name_2__v
family_full_name__v	alternate_name_3__v
first_name__v	alternate_name_4__v
first_name_cda__v	alternate_name_5__v
formatted_name__v	alternate_name_6__v
full_name__v	alternate_name_7__v
international_name__v	alternate_name_8__v
last_name__v	alternate_name_9__v
last_name_cda__v	alternate_name_10__v
maiden_name__v	hco_name_cda__v
middle_name__v	international_name__v
middle_name_cda__v	pinyin_name__v
nickname__v
pinyin_name__v
source_full_name__v

Supported match configurations

The option to block on similar names is available for all match configurations.

• Ad Hoc Match Configuration

• Add Request Match Configuration

• Match Default Configuration

• Data Deduplication

• Match Rule Collections

• Source subscriptions

• Match API

Match log

The Data Group Analysis Log contains a new column, Group Creation Method, to identify the way the data group was created:

• Exact match

• Fuzzy match

Add request match rules

The default match rules used by add requests and change requests are improved to reduce the potential for over matching.

This enhancement is enabled by default in your Network instance.

Countries

Changes will be made to the following countries:

• EMEA region

• United States

View default match rules

All countries supported by Veeva OpenData have default match rules for add and change requests.

To view the match rules:

1. In the Admin console, click System Interfaces > Add Request Match Configuration.

2. Choose a country.

   Data groups, match rules, and filters display for the country and selected entity.

3. If the Default is selected, the entity uses the default match rules. If Override is selected, the rules have been customized.

Custom match rules

If you have made changes to the default match rules, these updates will not impact your custom rules.