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

• Announcement Date: June 11, 2026
• Release Date: June 25, 2026

Verato MDM Cloud

Identity

New Features and Improvements

Pub/Sub and notification enhancements

• Source metadata included in outbound notifications
  Organizations that pass contextual metadata through the Verato APIs — such as source login name, username, location, and transaction type — can now see that metadata reflected in outbound pub/sub notifications. This enables downstream consumers and audit integrations to correlate platform events with the originating source-system user and transaction context, without requiring additional lookups or custom enrichment.

• Granular identity-updated notifications
  Downstream consumers subscribed to identity update events now receive more granular, targeted notifications rather than a single broad identity.updated event. Teams building real-time integrations and streaming pipelines can now trigger more precise actions based on the specific nature of each change.d.

Match Tiers™ and source tier accuracy

• Case-insensitive source name resolution for Match Tier™ assignment
  Source names are now matched case-insensitively when determining Match Tier™ assignment. Previously, a case mismatch — such as "Epic" vs. "EPIC" — would silently fall through to the default tier, resulting in incorrect match scoring without any error signal. Source names now resolve correctly regardless of case, ensuring the intended tier is applied and match quality is preserved.

Audit log

• Source system context captured in audit log events
  Source-system context — including login name, username, location, and transaction type — is now captured in the audit log for identity ingestion, merge, link, unlink, soft-delete, and reactivation events. Organizations that require traceability of the originating source-system user for audit and compliance reporting now have that context available directly in the audit log record.

Identity record management

• "County/District" label added to the District address attribute
  The address cluster attribute previously labeled only "District" now displays as "County/District" in the Verato MDM Cloud™ UI. This resolves widespread confusion for organizations using county-level segmentation — particularly in the US — who did not realize the "District" attribute represented county-level data. No underlying data model or integration changes are required.

Provider stewardship workflow

• Perspectives now available on provider stewardship task views
  Data stewards reviewing provider identity tasks can now use configurable Perspectives to control which attribute clusters are displayed in the task view — the same capability available in Entity 360®. Stewards can also apply filters and manage source records directly from the task view, reducing visual noise and enabling role-based workflow optimization for clinical vs. demographic review scenarios.
   

Bug Fixes

• Identity name blank in task view for Match Same Source tasks
  The Identity Name column was appearing blank in the task view for Match Same Source and Potential Match Same Source task types, making it difficult for stewards to identify records at a glance. The identity name is now populated correctly at task creation time for all task categories, consistent with other task types.

• Address abbreviation "DR" incorrectly normalized to "Drive"
  Address normalization was incorrectly converting the abbreviation "DR" — as in Doctor — to "Drive," and "ST" — as in Saint — to "Street," affecting address accuracy across person and provider records. The normalization logic has been corrected to preserve the intended meaning of these abbreviations. 

• Prevented Match task incorrectly generating a duplicate Potential Match task
  Under certain matching conditions, creating a Prevented Match Same Source task was also incorrectly generating a spurious Potential Match Same Source task for the same pair of records. Stewards now see only the correct task type, eliminating erroneous items from the stewardship queue.

• Entity 360® side panel rendering empty for certain identities
  The Entity 360® side panel was rendering empty for certain link IDs due to an issue with how source metadata was handled in the identity query response. The panel now loads correctly for all valid link IDs.

• Verato Managed Record identities not appearing in provider search after reactivation
  Identities composed exclusively of Verato Managed Records did not appear in provider search results immediately after a deactivated record was reactivated. Search results now correctly surface these identities following reactivation.

• Attribute deactivation failing for name clusters
  Attempting to deactivate a name attribute from Entity 360® was returning an "Attribute name not found" error because the UI was constructing the deactivation request with an incorrect field reference. This was a blocker-severity issue found during certification testing. The UI now reads the correct value from the cluster-groups API and deactivation completes successfully.

Connect

New Features and Improvements 

Provider Batch Operations

• Merge and delete identity batch jobs now available for provider stacks
  The merge identities and delete source identity batch jobs are now fully operational for provider stacks, matching the capability already available for person stacks. Organizations managing provider data at scale through Verato's batch framework can now perform bulk merges and deletions against provider identity data without requiring individual API calls.

Insights

New Features and Improvements 

Verato Insights

• API Request Type filter added to User & Usage Analysis
  Analytics and operations teams reviewing platform usage data in Verato Insights can now filter the User & Usage Analysis report by API Request Type. This gives teams a more precise view of how the platform is being accessed — distinguishing between request types to support usage auditing, capacity planning, and operational reporting.