This topic describes how to configure the Healthcare Providers data product.

Adding Data to Your Data Product

Configuring Attributes

Map attributes from your source records to the attributes in the industry-standard schema for your selected data product. Where possible, Tamr Cloud automaps input attributes to appropriate attributes in the unified schema.

For example, in the image below, the primary key attribute must be mapped. Additionally, you can see Tamr Cloud automatically mapped source attributes to the NPI and First Name attributes.

Note: For License attributes, only the Tamr recommended value is available.

Writing Consolidation Rules

Configuring Uniformity Score

Note: You cannot configure uniformity score for License attributes.

Configuring Sensitive Attributes

You data product may include sensitive information such as birth date, national IDs, email addresses, and so on, that you may not want all users to access. You can choose to hide sensitive data from users with the data product viewer role.

You can mark predefined or custom attributes as sensitive. Select the attribute name and then choose the Contains sensitive information checkbox.

For Addresses, Phones, Emails, and Licenses, you are not able to mark individual attributes as sensitive. Instead, you configure sensitivity for all address or license attributes.

Sensitive attributes are shown with a Lock icon next to the attribute name.

See Protecting Sensitive Data for more information on restricting access to sensitive data.

Configuring Enrichment

In this data product, your data is enriched with NPPES Enrichment.

You can choose whether to use NPPES match data to inform clustering.

When enabled, Tamr uses high confidence NPPES match results to inform clustering (nppes_match_status is either MATCH_NPI or MATCH_NAME_STREET_ADDRESS). A records' source data and matched NPPES attributes such as addresses, phone numbers, and emails will influence the cluster predictions.

If this option is disabled, Tamr uses only the NPI numbers to inform clustering. Tamr continues to use high confidence NPI numbers to inform clustering, which are NPI numbers provided in source records and NPI matches based on the combination of the providers's name and address (nppes_match_status is either MATCH_NPI or MATCH_NAME_STREET_ADDRESS).

Configuring Clustering Rules

Configuring Data Cleaning

NPI Value Cleaning

In this data product, Tamr also cleans specific, invalid NPIs. See Automatically Cleaned Data Values for the list of values removed by Tamr.

Configuring Address Standardization

Running Your Data Product and Viewing Results

Configuring Your Data Product for Tamr RealTime

If you are using the Tamr RealTime offering with this data product, see About Tamr RealTime for instructions on configuring the data product for real-time use cases.