We are pleased to announce 360 pages for companies and healthcare providers, as well as improvements to the home page, data products, and Tamr RealTime.

360 Pages for Companies and Healthcare Providers

With our comprehensive 360 pages for company and healthcare provider golden records, business users can easily explore the data powering their most important analytics and system. Learn more.

Home Page Improvements

• The number of golden records is now included on the data product card, for data products built with the new configuration experience.
• You can now filter to specific data products on the home page.

Data Product Improvements

• A new Data Cleaning feature is available on request for data products built with the new configuration experience. When configuring the data product, you can choose to replace known bad values in your source data with null. This helps to ensure that these values are not used for matching or included in your golden records. Learn more about data cleaning in our Data Product Guides. Contact Tamr Support ([email protected]) if you would like to enable this feature.
• For B2B Customers data products being used for healthcare organizations, the Public Sources firmographic enrichment provider now includes data from the Centers for Medicare and Medicaid Services (CMS). This change is available in both new and existing data products created with these templates. Learn more about public source enrichment.
• Our new filters make it easier to configure published datasets. Quickly search for specific attributes, or filter to attributes that are selected or not selected for publishing. These filters are available for data products built with the new configuration experience. Learn more about publishing.

Tamr RealTime Updates

• Preview the results of the search then create or update record endpoint, using the new optional dryRun body parameter. See the Search Changelog for more details.
• The get record response has been updated with the first of two planned changes to make the response format consistent with the response format for other record endpoints. The first change is additive to allow time for users to migrate to the new format, which will be enforced with the second change. See the Records Changelog for more details.

Bug Fixes and Other Improvements

• General styling and usability improvements.