---
updatedAt: 2026-09-08T16:34:27.000Z
agentTools:
  projectIndex: https://cloud.docs.tamr.com/llms.txt
---

# About Tamr-Managed Reference Data Standards

Tamr provides a number of reference data standards for use in all of RealTime data products on your tenant.  These standards are fully managed by Tamr; you cannot edit these standards.

Open a standard from the **Reference Data** page to view the standard's full list of canonical values and the source value variations that map to each value.

# Tamr-Managed Reference Data Standards

<Table>
  <thead>
    <tr>
      <th>
        Tamr-Managed Reference Data Standard
      </th>

      <th>
        Type
      </th>

      <th>
        Description
      </th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td>
        Common Null Values
      </td>

      <td>
        Lookup
      </td>

      <td>
        Replaces known bad values will `null`.
      </td>
    </tr>

    <tr>
      <td>
        Consent Status
      </td>

      <td>
        Normalization
      </td>

      <td>
        Standardizes communication consent values associated with phone numbers, emails, and addresses to either `OPT-IN` or `OPT-OUT`. <br /><br />Unrecognized values, blank strings, and absent or null attributes are standardized to `OPT-OUT`.
      </td>
    </tr>

    <tr>
      <td>
        Date/Datetime Format
      </td>

      <td>
        Normalization
      </td>

      <td>
        Standardizes date and datetime values in common formats to the selected target format.<br /><br />You can choose to remove invalid values from your source records. Otherwise, values that cannot be parsed as a date or datetime are left unchanged. <br /><br />When you use this standard in a data product, you can choose the date format:&#x20;

        - ISO 8601 (`yyyy-mm-dd`)
        - ISO 8601 datetime (`yyyy-mm-ddThh:mm:ss`)
        - Month/Day/Year (`mm/dd/yyyy`)
        - Day/Month/Year  (`dd/mm/yyyy`)
      </td>
    </tr>

    <tr>
      <td>
        Healthcare Provider Specialty
      </td>

      <td>
        Lookup
      </td>

      <td>
        Replaces an abbreviated provider specialty to the canonical speciality name (for example, replacing "FM" with "Family Medicine").<br /><br />Values not found in the lookup are left unchanged.
      </td>
    </tr>

    <tr>
      <td>
        ISO Country Codes
      </td>

      <td>
        Lookup
      </td>

      <td>
        Replaces country name variations with ISO 3166-1 codes or long names, such as replacing `United States`, `USA`, and  `U.S.A` with either `US` or `United States of America`. <br /><br />When you use this standard in a data product, you can choose whether to standardize to the ISO alpha-2 code or the ISO long name.<br /><br />Optionally, you can map a state attribute to infer the country if it is not available in the record (for US and Canada only).&#x20;
      </td>
    </tr>

    <tr>
      <td>
        ISO State/Province Codes
      </td>

      <td>
        Lookup
      </td>

      <td>
        Replaces US state and Canadian province name variations with ISO 3166-2 codes or long names, such as replacing `California` and `Calif.` with `CA` or `CALIFORNIA`. <br /><br />When you use this standard in a data product, you can choose whether to standardize to the ISO 3166-2 code or the long name.
      </td>
    </tr>

    <tr>
      <td>
        Name Prefix
      </td>

      <td>
        Lookup
      </td>

      <td>
        Maps name prefix variations to canonical abbreviations, such as

        - Replacing `Doctor` and `Dr` with  `Dr.`
        - Replacing `Chief Executive Officer` with `CEO`
      </td>
    </tr>

    <tr>
      <td>
        NPI Format
      </td>

      <td>
        Normalization
      </td>

      <td>
        Cleans NPI numbers:

        - Removes trailing `0` decimal values
        - Replaces known NPI placeholder values with `null`
      </td>
    </tr>

    <tr>
      <td>
        Phone Format
      </td>

      <td>
        Normalization
      </td>

      <td>
        Standardizes phone numbers into a single, uniform format.  <br /><br />When you use this standard in a data product, you choose whether to normalize each phone number to the E.164, National, or International format.<br /><br />You also can choose to remove invalid phone values from source records.<br /><br />You must specify a country attribute when using this standard.
      </td>
    </tr>

    <tr>
      <td>
        URL Format
      </td>

      <td>
        Normalization
      </td>

      <td>
        Reduces a website value to its host.  For example, reduces `https://www.acme.com/about` to `acme.com` <br /><br />For social or aggregator hosts such as LinkedIn and Facebook, retains the path and the host.  For example, reduces `https://www.linkin.com/company/acme/` to `linkedin.com/company/acme`.<br /><br />Values that cannot be reduced to a valid host are left unchanged.
      </td>
    </tr>
  </tbody>
</Table>

# Reviewing Details for Each Standard

1. Select **Reference Data** from the main menu access all Tamr-managed standards as well as any user-defined standards created in the current project.

![](https://files.readme.io/58f401485ab9b96a6867b34a66ef99303c7ebba96e52cc4d23dc953b60bcec10-referenceDataPage.png)

2. Select a standard on this page to open it.  The page includes a description of the standard, configurable parameters, and the list of canonical values mapped to source value variations.

![](https://files.readme.io/0a5ff723125182a9b89ee7696a831f96d9e0bff58a533e56e2626b1709762c82-sampleStandardsTable.png)

<br />

<br />

<br />