--- updatedAt: 2026-09-21T19:21:58.000Z agentTools: projectIndex: https://cloud.docs.tamr.com/llms.txt --- # About the RealTime Healthcare Providers Data Product ### Limited Release RealTime data products are in limited release. Some functionality is still in development and is subject to change. If you are interested in using these data products, contact Tamr Support ([help@tamr.com](mailto:help@tamr.com)). The RealTime Healthcare Providers data product provides a consolidated view of Type 1 (individual) healthcare providers. You can use this information, for example, to help streamline operations and provide optimal patient care. This data product is not designed to master Type 2 (organization) healthcare data. This data product provides: * An industry-standard schema for healthcare provider data. * A pre-trained matching configuration to identify duplicate healthcare provider records. * Default rules to determine the best values for your golden records. These rules also include a final value condition as a tiebreaker if rules resolve to multiple values. ## Healthcare Provider Schema, Match Logic, and Default Consolidation Rules ### Single Attributes The following table provides: * The default schema for Healthcare Providers data products. * Explains whether each attribute is used by the default Tamr model to identify matching Healthcare Provider records. See [Healthcare Providers Match Labels](https://cloud.docs.tamr.com/tamr-cloud/reference/healthcare-providers-search-labels) for the full list of match labels for this data product, which indicate matching, partially matching, and missing attribute values. * Explains whether each attribute is included by default in the [cluster uniformity score.](https://cloud.docs.tamr.com/tamr-cloud/docs/configuring-uniformity-scores) * Provides the default [record consolidation rules](https://cloud.docs.tamr.com/tamr-cloud/docs/about-record-consolidation-rules-for-realtime-data-products) for each attribute.
Attribute Used In Matching Included in Cluster Uniformity Score by Default Default Record Consolidation Rule
Primary Key (required) no no Not applicable
Full Name (required if First and Family Names are not provided) If your source does not include an attribute for full name values, you **must** derive a full name value from other name attributes when configuring the data product. This ensures that your golden records and 360 pages include a Full Name value. See [Adding and Configuring a RealTime Data Product](https://cloud.docs.tamr.com/tamr-cloud/docs/adding-and-configuring-a-realtime-data-product). **yes** yes Most common Full Name Final value condition: Smallest value
First Name (required if Full Name is not provided) **yes**

Tamr also considers common first name variations, such as "Bob" for "Robert", when matching records.

**See note below table.** 		yes Most common First Name associated with the most common Full Name Final value condition: Smallest value
Middle Name no yes Most common Middle Name associated with the most common Full Name Final value condition: Smallest value
Family Name (required if Full Name is not provided) **yes** yes Most common Family Name associated with the most common Full Name Final value condition: Smallest value
Name Prefix no no Most common Name Prefix value associated with the most common Full Name Final value condition: Smallest value
Name Suffix no no Most common Name Suffix value associated with the most common Full Name Final value condition: Smallest value
Gender no yes Most common Gender
Final value condition: Smallest value
Date of Birth no yes Most common Date of Birth Final value condition: Smallest value
Organization Name **yes** yes Distinct list of Organization Names Final value condition: Smallest value
Npi

This should be a type 1 (individual) NPI 		**yes** yes Most common NPI Final value condition: Smallest value
Credentials **yes** yes Most common Credentials Final value condition: Smallest value
Degree no no Most common Degree Final value condition: Smallest value
Graduation Year no yes Most common Graduation Year Final value condition: Smallest value
Provider Specialty no yes Most common Provider Specialty Final value condition: Smallest value
> ![](https://files.readme.io/4e9086e-warning-icon-color.png)**Important Note for First Name matching: **Matching on first name variations was released on September 21, 2026 for new data products.** **For data products created before this date, **Tamr does not consider common first name variations** when matching records. If you are interested in updating an existing data product to consider first name variations, contact Tamr Support (). ### Address Attributes The data product schema includes **Primary** address attributes by default. You can choose to include attributes for additional address types, including: * Office * Corporate * Previous * Mailing * Shipping * Registered * Billing * Other Each address type includes the following attributes: | Address Attribute | Used in Matching | Included in Cluster Uniformity Score by Default | | :------------------------------------------------------------------------------------- | :--------------- | ----------------------------------------------- | | Address
(Map source fields with address line 1 or complete address to this field) | **yes** | yes, for Primary address only | | Address Line 2 | **yes** | no | | Address Line 3 | no | no | | Address Line 4 | no | no | | City | **yes** | yes, for Primary address only | | State | **yes** | yes, for Primary address only | | Country | **yes** | yes, for Primary address only | | Postal Code | **yes** | yes, for Primary address only | | Latitude | no | no | | Longitude | no | no | **Default consolidation rule for all addresses:** For all address attributes in the address group, Tamr selects the golden record values from the single source record with: 1. The most common non-null Address. If the most common value is null, THEN 2. The most common non-null City. If the most common value is null, THEN 3. The most common non-null State. If the most common value is null, THEN 4. The most common non-null Postal Code. If the most common value is null, THEN 5. The most common non-null Country. If the most common value is null, THEN 6. The most common Address Line 2. Final value condition: Smallest value ### Phone Attributes The data product schema includes **Mobile** phone number attributes by default. You can choose to include attributes for additional phone number types, including: * Home * Work * Office * Other Each phone type includes the following attributes: | Phone Attribute | Used in Matching | Included in Cluster Uniformity Score by Default | | :---------------- | :--------------- | ----------------------------------------------- | | Phone | **yes** | yes, for Mobile phone only | | Alternative Phone | **yes** | no | **Default consolidation rule for all phones:** For all phone attributes in the phone group, Tamr selects the golden record values from the single source record with the most common value for Phone. Final value condition: Smallest value ### Email Attributes The data product schema includes **Personal** email address attributes by default. You can choose to include attributes for additional email address types, including: * Work * Office * Other Each email type includes the following attributes:
Email Attribute Used in Matching Included in Cluster Uniformity Score by Default Default Record Consolidation Rule
Email **yes** yes, for Personal email only Most common Email Final value condition: Smallest value
## License Attributes You can add up to 20 provider licenses. Each license includes the following attributes: | License Attribute | Used in Matching | Included in Cluster Uniformity Score by Default | | :---------------- | :--------------- | ----------------------------------------------- | | Number | **yes** | no | | State | **yes** | no | | Country | **yes** | no | | Status | **yes** | no | **Default consolidation rule for all licenses:** List of distinct values # Custom Attributes You can add any number of custom attributes to the unified schema. These attributes are not used by Tamr's trained matching logic to identify duplicate records. **Default consolidation rule for custom attributes:** Most common value for that attribute. Final value condition: Smallest value