Ad hoc match
Ad hoc matching A user-initiated match of a user-supplied file against Network data that typically results in high confidence matches. enables you to match an external source, such as a marketing campaign list, to the data in Network without persisting the data. It produces high confidence matches that you can export along with your original source data.
Ad hoc match uses a specific set of match rules A definition that determines which fields in a record are a possible match and when a record comparison is considered a suspect match. See features and feature sets. to compare source data that you provide against Network data. By default, it finds the highest confidence matches possible. Source data can also be matched against Veeva OpenData records when specific requirements are met.
Working with ad hoc match rules:
Depending on match rules, ad hoc match against Network data might look at the name field and require an exact match (where source and Network data are identical), or it might allow for similar (but not identical) specialties. A match on a similar item would occur, for example, when your source data includes only one specialty for an HCP, where the Network data includes multiple specialties.
- defined using fields or field groups along with match strength
- fields may include Name, NPI, Specialty, and so on
- field groups may include Address, which includes other fields such as street, city, or zip code
- match strength can be weak, strong, or exact
Enabling this feature
- Define permissions for ad hoc matching in data visibility profiles A user-assigned profile that contains permissions and the profile layouts that are used when viewing HCP or HCO records..
- Update match rules if required.
The following activities are available depending on the user type:
|Activity||Standard User||Data Steward||Data Manager||Administrator|
|Match files against Network data||
|Update ad hoc match configuration||
|View all ad hoc match jobs||
|View ad hoc match actions in the System Audit History||