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.
About the matching process
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. The job will find the best match it can, as opposed to no match at all.
By default, it finds the highest confidence matches possible, but unlike all other match configurations in Network, the ad hoc match process uses any feature set it can. Matches that are found using only part of a feature set are reported as ambiguous matches. For example, if an ACT match rule matches on Name and NPI value and ad hoc match finds a match using only the NPI feature of that feature set, the match is reported as ambiguous.
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.
Key points for ad hoc match
- 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
- Administrator:
- 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.
- Define permissions for ad hoc matching in data visibility profiles
User activities
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 |
|