Ranked filter groups

AD
DM

Administrators and Data Managers can create groups of filters to apply to match configurations. The filter groups are ranked so they are applied in a specific order. For example, you can filter matched HCPs to include only those that have a Doctor of Osteopathic Medicine medical degree and consider only HCPs that are Prescribers.

Filters can also be created on individual match rules and on all match rules in the match configuration. For details see Conditional matching.

How ranked group filters work

For incoming data, ACT and ASK matches are determined as usual using the existing match configuration and confidence values. The ranked filter groups are then applied. The matched pair is chosen based on the highest rank of the group filter.

Supported Network features

Ranked filter groups are applied at the match configuration or subscription level.

  • Source Subscriptions

  • Data Deduplication

  • Match Default Configuration

  • Add Request Match Configuration

  • Match Rule Collections

  • Ad Hoc Match

Ranked filter group highlights

  • Filters can include or exclude records.

  • Filters configured on individual match rules override ranked filter groups.

  • You can choose to apply filters to incoming records and records already in your Network instance or only to records already in your instance.

  • When more than one filter group exists, you can manually rank them to prioritize the order in which they are applied.

Create a ranked filter group

Ranked filter groups can be created in any match configuration.

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

  2. Select the Ranked Filter Groups tab and click Add filter group.

    Define the following details:

  3. Entity - Choose the object that the filter will be applied to.

  4. Filter Group - Type a unique name for the group. A maximum of 255 characters are supported.

  5. Description - Define a meaningful description of the filter. A maximum of 255 characters are supported.

  6. Apply Filters To - Choose the data that the filters will be applied to:

    • All data - Incoming data and existing data in your Network instance.

    • Existing data (default) - Only existing data in your Network instance.

      If a source subscription or data deduplication job has selected the Match & Download from OpenData option, existing data also includes not-yet-downloaded OpenData records.

  7. Function - Choose the records that will be considered for the match.

    • Include - Only records with that value in the specified field will be compared to each other.

    • Exclude - Records with that value in the specified field will be excluded from the rule.

  8. Field - Choose the field that will be used to filter the match. The fields in the list apply to the selected entity.

    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.

  9. Value - Type or select the field value. Multiple values can be defined.

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

    Note: Multiple values are treated as ORs; for example, the HCO type is a hospital OR a clinic.

  10. To include another filter, click Add filter group and complete steps 5 to 10.

    Note: Multiple filters in a group are considered an AND operation. For example, match only if the HCP is a Prescriber AND a Doctor of Osteopathic Medicine.

  11. If a match is not found in the defined groups, select one of the options to determine the matched pair:

    • Continue matching within the records not covered by the groups - All match pairs found throughout the match process are included.

    • Do not continue matching - Match pairs that are not found in these filter groups are excluded. These records will be treated as unmatched.

      Note: Use this setting with caution because duplicate records might be created.

    These options are dimmed and cannot be selected until ranked filter groups are configured.

Unmatched records

Source subscriptions

When records are not matched using the ranked filter groups, the Action for Unmatched & Suspect Match setting determines what happens to the record. This is existing behavior for all match rules and match rule collections that are used in source subscriptions.

Ad hoc match

If the data in a file doesn't match to an existing record based upon the match rules, the data is not added to your Network instance..

Add request match configuration

If incoming data in an add request doesn't match to an existing record, the add request is created. A match would result in a change request.

Data deduplication job

Data deduplication jobs only use records already in your Network instance, data is not loaded. Consequently, any identified records that don't match to other records simply remain independent records.

Manage filter groups

Rank filters

If a filter group has multiple filters, use the Handle icon () to manually move the filters to prioritize the order in which they are applied. The Rank column adjusts to reflect any changes.

Deactivate a filter

To deactivate a filter but keep it in the group, toggle the Enabled button in the Status column. When the match process runs, the filter will not be considered.

Delete a filter

Expand the filter and click Delete to remove it from the match configuration.

Example 1 - Include hospitals

Find matches to hospitals and hospital groups.

Continue matching within the records not covered by the groups is selected, so any incoming records that didn’t match to hospitals or hospital groups using the filter will then be compared to HCOs that are not hospitals or hospital groups.

Example 2 - Exclude HCO departments

Find matches to HCOs that are not departments (Exclude).

Continue matching within the records not covered by the groups is selected, so any incoming records that didn’t match to non-department HCOs using the filter will then be compared to HCOs that are departments.

Example 3 - Include HCOs only

Find matches only to HCOs that are hospitals.

Do not continue matching is selected, so no other matches are considered for incoming records that didn’t match to hospitals. This could result in duplicate records being added to your Network instance.

Example 4 - Include hospitals in existing data only

Find matches to hospitals or hospital groups. Apply the ranked group filter to existing data only.

Continue matching within the records not covered by the groups is selected, so any incoming records that didn’t match to hospitals or hospital groups using the filter will then be compared to HCOs that are not hospitals or hospital groups.

The filters are applied to Existing data only, so incoming data can have any value in the HCO type field; the ranked group filters are only applied to existing data in the instance.

Match log

The Match + Data Group Analysis log includes a column called Rank Group to display the ranked group filter name where the match was found.

The column is empty if ranked group filters do not exist, or the match pair was not found in a ranked group.