Click Follow in the Release Notes section to be notified when new releases are available.

• Announcement Date: August 06, 2026
• Release Date: August 27, 2026

Verato MDM Cloud

Identity

New Features and Improvements

Quarantined Applied Overlays

• Verato now supports quarantining Applied Overlay updates before they reach matching and linking. When a source system sends an update flagged as an Applied Overlay and quarantining is enabled, the record is held in a temporary quarantine state — untouched, unmatched, and unmerged — until a data steward reviews and resolves the associated Applied Overlay task. Quarantine is lifted only by deliberate steward action; there's no automatic expiration, so a record doesn't re-enter matching until someone has actually reviewed it. While a record is quarantined, any further updates to that source and native ID are rejected until the task is resolved, so the record's Link ID — and any records tied to it — stay stable.

Why It Matters

Previously, an applied overlay update could be matched or linked into other records before anyone had a chance to review it, creating a risk of contaminating the broader identity. Untangling a bad merge after the fact is far more costly than preventing it in the first place. This gives stewardship and compliance teams a non-bypassable control: once enabled, no record with a pending Quarantined Applied Overlay task can be linked, merged, or matched until it's explicitly cleared.

Reach out to your Verato account team to learn how Quarantined Applied Overlays is a right fit for your matching strategy.

• Expanded communication-preferences data model
  Organizations managing communication preferences can now capture richer, more auditable detail — including source attribution, validity windows, lifecycle status, per-channel language, specific contact endpoints, and most-recent opt-out dates. These additions lay the groundwork for surfacing preference conflicts across systems and support TCPA-style audit trails. All new fields are optional, preserving backward compatibility with existing records.

Audit Log

• Audit Log now shows readable source names
  Data stewards reviewing audit events now see the configured source display name instead of an internal source code, making it immediately clear which source system drove an identity change without cross-referencing configuration. Where no display name is configured, the source code is shown as a fallback.

Provider Reference Search & Verato Managed Records

• New "Verato Reference Search" tab on the Provider search screen
  Data stewards working Provider records can now search Verato's Provider Carbon reference database directly from a dedicated tab, without leaving the search interface or using a separate tool. Fixed columns (NPI, name, specialty, address, existing-identity indicator); visible only to users with the new "Provider Reference Search" permission.
• Create Provider Verato Managed Records pre-populated from verified reference data
  Data stewards creating a new Provider Verato Managed Records can now select a result from Verato Reference Search and have the Verato Managed Records creation form pre-populated with that identity's demographics, eliminating manual rekeying. Pre-populated fields remain editable before saving.

Performance

• Faster processing for large, complex identities
  Identities with deep source history—many accumulated names, addresses, or external identifiers—could experience sharply rising latency during matching. A rebuilt cluster-merge step removes that bottleneck, substantially lowering latency for the largest and most complex records with no change to match accuracy. This is enabled by default for all customers.

Bug Fixes

• Corrected household change notifications
  Organizations relying on householding notifications were receiving change events that omitted the previous household identifier when a person's household changed. Notifications now include both the previous and the new household identifiers, so downstream systems can track household changes accurately.

• Health insurance coverage no longer split in API responses
  When posting multiple health insurance coverages, the API response could split a single coverage into separate, partial clusters. Coverage records are now returned intact and correctly grouped. 

• Deceased-status details returned consistently
  The deceased-status detail was missing from the grouped-by-source response format, so stewards reviewing identities by source could not rely on it. It is now returned consistently across all response formats.

• Facility name searches containing a dash now succeed
  Searching for a health facility whose name contains a dash could return an index error instead of results. Organization and facility name searches that include a dash now complete successfully. 

Insights

New Features and Improvements 

Verato Insights

• Verified address and data quality detail in Verato Insights
  Practitioner and facility semantic views now include verified address and data quality detail fields, matching the Cohort Analyzer® schema. Customers can analyze verified provider addresses and record quality through Verato's Cortex-powered Insights analytics.

Cohort Analyzer®

• New provider and consent attributes for cohort building
  Analysts can now build and filter cohorts on payer mix, academic medical center status, and current-record flag directly in the Cohort Analyzer® interface, enabling more precise provider and population segmentation.

• Expanded preferences and consents fields
  Twenty additional preferences and consents fields from the Core Person model are now available in Cohort Analyzer®, giving analysts finer control over consent- and preference-based segmentation.

Provider record quality dashboards

• Record quality dashboards for practitioners and facilities
  New record quality dashboards for practitioner and health facility data give data stewards and analysts a clear, ongoing view of completeness and quality across their provider records, making it easier to prioritize data-quality work.