Match filters

Match rules can be filtered to include or exclude specific records for consideration in match pairs. For example, you can filter an HCO match rule to apply only to active HCO records that are hospitals.

There are three ways filters can be applied to rules in a match configuration:

Methods Applies to Match Rules Configured Details
Filter individual match rules A single match rule. Match Rules tab See Defining features.
Create subscription-level filters All match rules that include fields for the object defined in the filter. Match Filters tab See the information in this topic.
Create groups of filters that are ranked so they are applied in a specific order All match rules that include fields for the object defined in the filter. Ranked Filter Groups tab See Ranked filter groups.

Create subscription-level filters

AD
DM

Defining filters on the Match Filters tab simplifies the process by allowing filters to be applied to all match rules that include fields for the defined object. It eliminates the need to create the same filters for each rule.

Example

Create a match filter to ensure that only active HCPs are considered for match pairs.

Whenever the Default Match Configuration is used for a subscription, this filter will be applied to any HCP feature on the Match Rules tab that mentions HCP fields.

Note: It will not be applied to HCP features for other object fields, for example, address fields.

Match Filter highlights

  • Match filters are applied to rules for the specific objects on the Match Rules tab.

  • Filters defined on individual match rules (Match Rules tab) override the filters on the Match Filters tab.

  • Filters can include or exclude records.

  • Filters can be applied to incoming records that do not have a value in a filtered field.

  • Match Filters can be applied in Basic (UI) or Advanced (XML) mode.

Supported match configurations

Match filters apply to all match rules for the specified object in a match configuration.

They are applied at the match configuration or subscription level.

  • Default Match Configuration

  • Ad Hoc Match Configuration

  • Add Request Match Configuration

  • Source subscriptions

  • Match Rule Collections

  • Data Deduplication data maintenance subscriptions

How Match Filters work

Filters defined on the Match Filters tab are applied to the existing match configuration to include or exclude specific records for consideration.

ACT and ASK matches are then determined based on the resulting record pairs and confidence values.

Filters on individual rules

Filters applied to individual rules on the Match Rules tab override any subscription-level filters (Match Filters tab) when that match rule is processed.

Example use cases

Use these match filters to immediately include or exclude specific records from consideration during the match process.

  • Only match on active HCOs; do not include non-active HCOs.

  • Only match on active hospitals; do not include any HCOs that are not active and HCOs that are not hospitals

  • Only match on pharmacies; do not include HCOs that are not pharmacies

Create match filters

Add a filter that applies to all defined match rules an object in the match configuration.

  1. Open a match configuration and select a country group.

  2. Click the Match Filters tab.

  3. Expand the Entity list and choose the object for the match filter.

    Tip: To add filters for sub-objects, see Defining match configurations in Advanced mode.

  4. Click Add Filter.

  5. Expand the Function list and choose one of the following:

    • Include - Choose to define the records that the match rule will apply to.

    • Exclude - Choose to define the records that match rules will not apply to.

  6. Choose the Field to filter match rules on.

    Supported fields

    • active fields for the selected country and entity type

    • reference and text fields

    • Veeva standard fields and custom fields

    • Network hashtags

      Hashtags can be used in filters and applied to incoming records because hashtags are dynamically calculated; they are not stored on records. Hashtags are associated with incoming records if the records contain the fields and values used in the hashtag configuration.

  7. Select the Value to filter match rules on. One or more values are supported.

    If the selected Field is Hashtag (#Hashtag), all enabled hashtags associated to the entity display when you click Value.

    Note: If the filter contains multiple values, the match rule considers all values.

    Example

    • Function: Include

    • Field: Hashtag (#Hashtag)

    • Values: #hospital, #dept, #clinic

    Result: The match rule considers records that are Hospitals, or Departments, or Clinics.

  8. To include another filter, click Add Filter.

    When multiple filters are defined, the filters are combined as an AND operation.

    Example

    • Filter 1: Include active HCO records

    • Filter 2 Exclude HCOs that are health systems

    Result: Match rules will consider all active HCOs and all HCOs except health systems.

  9. Save your changes.

The filter will now be applied to all match rules for that entity and country group.

Applying filtered match rules to incoming records

When filters are applied, the rules can consider incoming records even if they are missing the field value of the filter.

To define the behavior:

  1. Click the Match Rules tab.

  2. Select one of the options:

    • Apply match rules whether incoming records have a value in the filtered field or not.

    • Apply match rules only if incoming records have a value in a filtered field.

Supported match rules

  • Individual match rules (Match Rules tab)

  • Subscription-level match rules (Match Filters tab)

Supported match filters

This is supported when the filter function is Include.

Exclude functions require the records to have the specified field and value.

Filters on individual match rules

Filters on individual match rules override any filters defined at the subscription level (Match Filters, Ranked Group Filters).

A message displays on individual match rules (Match Rules tab), when a filter is added to the rule and if filters are configured on the Match Filters tab.

Define match filters in Advanced mode

Match filters can be defined using XML.

For details, see Defining match configurations in Advanced mode.

Logging filters

The Match filters in use column in the Match + Data Group Analysis log indicates if a match filter was used when the match pair was found.

Column values

  • Yes - At least one subscription-level filter is enabled and used.

    Note: Filters are applied to one object. Some matches might be found using rules that aren't filtered. The value will still be Yes to indicate that filters were in use.

  • No - No subscription-level filters exist or were used to find the match pair.