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

• Announcement Date: October 15, 2026
• Release Date: October 29, 2026

Verato MDM Cloud

Identity

New Features and Improvements

Audit Log Enhancements

Audit Log access is now granted explicitly

To reduce unnecessary exposure of audit trail data, Audit Log access is no longer included by default in any standard role, including System Administrator and Data Steward. Organizations now grant Audit Log access only to the users and roles that need it, giving compliance and security teams tighter control over who can see audit history. Users who previously had Audit Log access through a default role may no longer see it until access is provisioned.

Quarantine and release activity now visible in the audit log

Summary

Data stewards and compliance teams can now see quarantine activity directly in the audit log, giving them a complete record of when a record was quarantined and when it was released. When an incoming record creates a quarantined applied overlay task, the audit log shows who posted the record and that a quarantined task was created. When a steward releases a quarantined record, the audit log shows who released it. These entries are available immediately with no configuration required.

Details

How it works

• Quarantine entries. An overlay that results in a quarantined record appears as an entry stating that the user posted the source record to the identity, creating a quarantined applied overlay task.

• Release entries. Releasing a quarantined record from the UI appears as an entry stating that the user unquarantined the source record.

Stewardship workspace and matching improvements

Match scores for tasks created from the workspace with more than two identities

Summary
When creating a task from the Workspace, stewards now see a match score even when the workspace holds more than two Link IDs. Previously the score appeared only for exactly two. Stewards get a reference point for the likelihood of a match without having to narrow the workspace first.

Details

How it works

• Score shown for any workspace size. The match score appears in the Workspace regardless of how many Link IDs it contains, displayed to three decimal places. In workspaces with more than two Link IDs, the score is evaluated on the first two.

• No change for two Link IDs. Workspaces with exactly two Link IDs behave as before.

Consistent match scores across stewardship reports

Data stewards and analysts will now see the same task counts when grouping tasks by match score in Data Explorer and in Operational Reports. Task match scores are now stored with a consistent three-decimal precision, so every report groups and displays scores the same way rather than rounding them differently on the fly. Existing match behavior and match thresholds are unchanged. 

Workspace Retains Added Identities Across Searches

Stewards can now add identities to the Workspace across multiple searches within the same session. Previously, starting a new search after opening the Workspace could clear identities already added, so working with two or more identities at once required resolving each one before starting the next search.

Identities now remain in the Workspace until a steward removes them individually via the Workspace panel.

Match Breakdown explanation shown less often

Data stewards who use the Match Breakdown panel regularly will see the introductory explanation of how match scores are calculated less often, so they can get to the breakdown faster.

Provider Reference Data Search

Find Verato reference matches without retyping your search

Provider data stewards can now move from searching their own records to searching Verato reference data without entering their criteria again. When you switch from the My Organization tab to the Verato Reference tab in provider search, every field that exists on both tabs is filled in with what you already entered. Criteria that have no matching field on Verato Reference are simply left out, and the search runs only on the values shown.

Identity relationships

Capture when relationships were active and add custom context

Summary

Data stewards and integrations can now attach custom details that matter to their organization, such as the location where a patient and practitioner encounter took place. Custom key-value pairs are saved with the relationship and returned whenever it is read through the relationship API. Relationships without custom details continue to work without error.

Details

How it works

• Custom key-value pairs. A custom dictionary supplied at creation is stored alongside the relationship and returned unmodified.

• Optional fields. When no custom key-value pairs are set, the response omits or empties that field without error.

What this means for your integrations

• Additive response change. Relationship API responses can now include custom metadata fields when they are populated.

Relationship Metadata Now Visible in Entity 360

Stewards reviewing a record’s connections can now see the full context of each relationship directly in Entity 360, without needing to look elsewhere. Relationship start and end dates, along with any custom key-value pairs, now appear alongside each relationship in the UI, so teams can tell when a relationship was active and what additional details describe it.

Create relationships using your own source identifiers

Summary

Integration teams can now create relationships between identities straight from their source systems, without first looking up a Verato Link ID or maintaining a separate crosswalk. The relationship API now accepts a source name and native ID for either or both sides of a relationship, and Verato MDM Cloud™ resolves each record to its identity before creating the relationship. This makes API-driven relationship creation practical at scale. Relationships created with Link IDs continue to work as before.

Details

How it works

• Mix and match identifiers. Each side of a relationship can use a Link ID or a source and native ID pair, in any combination.

• Clear errors. If a source and native ID pair does not resolve to an existing identity, the API returns an error identifying which record could not be resolved.

• Entity type validation. When a relationship type limits which entity types can appear on each side (such as patient, practitioner, or health facility), Verato validates the resolved identities before creating the relationship.

• Active records only. Records that are merged, quarantined, or soft-deleted cannot be used to create a relationship.

• Two distinct identities. Both sides must resolve to different identities, and one identity cannot be referenced by both its Link ID and a source and native ID in the same relationship.

What this means for your integrations

• New request option. Relationship creation requests can now supply source and native identifiers in place of Link IDs. Existing Link ID requests are unchanged.

Smart Views® and View Builder

Filter view values by attribute type

Summary

Administrators building Smart Views® can now show only the values of a specific type within an attribute, for example only primary email addresses, so each view presents exactly the data its audience needs. Verato MDM Cloud™ reads the new filter rules in the view definition and applies them when building the view response. Existing view definitions without these rules behave as before.

Details

How it works

• Filter by value type. A view rule can now include filtering.filterByValues, which limits returned values to those whose sub-attribute matches the listed values.

• Works with existing filters. filterByValues can be combined with existing filterBy options such as active-only filtering.

Bug Fixes

Prevented Match Same Source Tasks No Longer Duplicated

Summary

Data stewards at some organizations saw duplicate open Prevented Match Same Source tasks created for the same records, adding unnecessary work to the stewardship queue. This occurred when a potential cross-source match task was also present for the identity. Duplicate detection now correctly recognizes the existing task, so only one task is created. No action is required.

Details

What's fixed

If you still see this

Contact Verato Support with the task IDs of the duplicate tasks and the approximate time they were created.

Editing Fields in Entity 360 No Longer Causes Query Errors

Summary

Organizations that edited a field in Entity 360 on an identity augmented through Verato Referential Matching® could find that the identity no longer returned successfully from query APIs. Reference data used for matching was being retained incorrectly as deleted data on the identity after the edit. Now only the fields from your own source records that you actually changed are recorded, and query APIs return the identity as expected.

Details

What happened

When a user edited a field on an augmented identity in Entity 360, the update also recorded reference data sources in the identity's deleted data. Subsequent query API calls for that identity then failed. This affected augmented identities edited since the May 2026 release.

What's fixed

If you still see this

Contact Verato Support with the Link ID of the affected identity and the time of the edit.

searchTasksWs Now Returns Tasks When Searching by Trigger Record

Summary

Integrations using the searchTasksWs API to find a task by its trigger record previously received no results, even though the same task was correctly returned when searching by one of its related records. 

This has been resolved: searchTasksWs now returns tasks consistently regardless of which record on the task, trigger or related, you search by. No action is required. 

Details

What's fixed

Contact Verato Support with the time of the request and the task ID you expected to see.

Smart Views Now Display an NPI When One Exists

Summary

Smart Views® now return only the attribute values your downstream systems and users need, for Person, Provider, and Organization identities. For example, instead of returning every address on an identity, a view can return just the addresses where address type is “WORK.” This reduces the filtering and cleanup consumers must do on their side, and ensures each audience sees only relevant data. Existing Smart Views behave as before.

Details

How it works

• Smart Views return the mastered view of an identity. An identity often holds several values for the same attribute, such as multiple addresses, phone numbers, or emails, contributed by different records.

• Smart Views can now select values by field. For any attribute on a Person, Provider, or Organization identity, a view can return only the values where a field matches a value you specify. Example: an identity has a HOME, a WORK, and a MAILING address. A view set to Address Type = “WORK” returns only the WORK address. The same approach applies to any other attribute, such as returning only PRIMARY emails.

• No match, no attribute. If none of an identity’s values match the condition, that attribute is left out of the view.

• Works with existing filters. Combine this with existing options, such as returning only active values.

Setup

Verato Support configures Smart Views. To add this filter to a view, contact your Verato Customer Experience team.

Match Breakdown No Longer Labels Unweighted Attributes as "No Information" 

Insights

New Features and Improvements

Cohort Analyzer is now Data Explorer

Summary

Cohort Analyzer is now called Data Explorer. The new name better describes what the module does: it gives your teams self-service access to explore, segment, and analyze trusted identity data across Verato MDM Cloud™. This is a name change only. Your dashboards, saved reports, scheduled deliveries, data, and user access work exactly as before, and no action is required.

What this means for your organization

• No change to access. Users who had access to Cohort Analyzer automatically have the same access to Data Explorer.
• Custom names are not changed. Verato renamed only its standard roles, permissions, and user groups. If your administrators created custom user groups or roles that include “Cohort Analyzer” in the name, those keep their current names. You can rename them whenever you like.
• Existing content carries over. Dashboards, saved reports, and scheduled deliveries remain available under Data Explorer.

Data Explorer

Updated Names in Data Explorer
As part of the rebranding of Cohort Analyzer to Data Explorer, explore names now follow a consistent pattern and no longer include the “Cohort” prefix. For example, Cohort Person is now Person Explorer, and Cohort Practitioner Tasks is now Tasks Practitioner.

Clearer Enrichment Statistics Dashboards
Organizations using Verato enrichment can now read their enrichment match results more easily in Data Explorer. The Customer Population Statistics, Customer Population Email Statistics, and Customer Population Phone Statistics dashboards now format numbers with thousands separators and show totals alongside the adult population (aged 18 and older), giving a complete picture of enrichment match rates.

Encrypted S3 Export from Data Explorer
Organizations using Data Explorer can now export query results directly to their own S3 bucket. The new "Export to S3 (Encrypted)" action supports CSV, XLSX, JSON - Simple, JSON - Detailed, and Inline formats, with credentials kept masked and encrypted throughout. This requires an existing Verato hosted SFTP channel to be in place. No manual configuration or engineering support is needed to run an export.

Data Share

New metadata columns in Notification Data Share views
Organizations that receive Verato Notifications through Data Share views can now trace each notification event back to the source system user who triggered it, the type of transaction, and the location associated with it. Four new columns (SOURCE_LOGIN_NAME, SOURCE_USER_NAME, TRANSACTION_TYPE, and LOCATION) are now included in the VERATO_NOTIFICATION_OVERLAY, VERATO_NOTIFICATION_NEW_RECORD, and VERATO_NOTIFICATION_LINK_ASSIGNMENT_CHANGES views. 

Bug Fixes

Data Explorer Performance

Faster Loading for Stewardship Dashboards in Data Explorer
The Person Task Stewardship Analyzer dashboard in Data Explorer was exhibiting slow report rendering performance. A query optimization was applied for when the underlying task views of the reporting warehouse are included. The dashboard now renders visualizations in a more performant manner. No customer action is required.