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

• Announcement Date: July 9, 2026
• Release Date: July 30, 2026

Verato MDM Cloud

Identity

New Features and Improvements

Vera AI assistant

Verato MDM Cloud™ now includes Vera, an AI-assisted chatbot that makes it faster to search identity records and easier to understand why identities did or did not match — available now in Beta on the new Verato MDM Cloud™ UI.

• Vera for conversational identity search
  Data teams can now find identity records by describing what they're looking for in plain language, instead of building a structured query or knowing Verato's underlying data model. From the new Verato MDM Cloud™ UI, users can ask Vera to find all patients named John Smith born in 1975 in Virginia and get back ranked candidate identities, along with the matched fields and confidence signals behind each result — all within each user's existing access permissions. This gives stewards, analysts, and support teams a faster entry point into identity search, alongside Verato's existing structured search tools.

• Vera for match explainer
  Stewards, compliance officers, and data governance teams can now ask Vera why two identities did or did not match, and get a plain-language explanation instead of a bare score, directly in the new Verato MDM Cloud™ UI. Vera surfaces the match score, the individual signals that contributed to it, and any enhancements applied — replacing an opaque number with reasoning your team can review, act on, and explain to auditors or clinicians when needed. This works alongside your existing stewardship workflows; it does not change how matches are made, only how the decision behind them is understood.

How to get Vera enabled
Vera is being enabled account by account. To turn it on for your organization, contact Verato Support or your Customer Success representative.

Smart Steward Moving to Opt-In

With the introduction of Vera, our new AI assistant, Verato is moving to an opt-in approach for all AI-powered features — meaning a feature will be enabled for a customer only after that customer requests it. Smart Steward, available via the "AI Assist" button on the task details page, will follow this same approach.

Starting with the July 2026 software release, Smart Steward will be disabled by default. Customers who want to keep using it can request it be re-enabled by submitting a helpdesk ticket, and our team will turn requests around quickly.

Stewardship Experience

• Richer context on hover in the task view. 
  Stewards reviewing records in a task can now see post-ingestion metadata, prior merge history, and prior link history directly on hover, without leaving the current task. Surfacing this context inline helps stewards make faster, better-informed resolution decisions.
• First and Last Asserted metadata on hover in Tasks UI.
  Stewards reviewing cluster values across the Identity, Column, and Row task views can now hover to see First Asserted and Last Asserted metadata, giving immediate visibility into the recency, source, and context of an attribute value without leaving the task.
• API status banner relocated for clearer visual hierarchy.
  The API status indicator now appears down mid-page rather than at the top of the console sections, reducing the impression that API availability issues are frequent.

• Edit Verato Managed Record demographic attributes directly from the UI.
  Permissioned data stewards can now correct stale or inaccurate demographic attributes on a Verato Managed Record using the same inline editing experience already available for source record attributes, without needing API access or a delete-and-repost workflow.

Audit Log

• Audit Log now honors source-level access permission.
  Organizations operating under strict access-control and HIPAA requirements can now trust that Audit Log visibility respects “Restrict by Source” permissions. Users see audit events for restricted sources, but core event details are redacted when they are not authorized to access the source; authorized users see the full audit information, and administrators retain full visibility. This tightens least-privilege access control and supports SOC 2 access-control objectives.
• API request metadata now visible in Audit Log detail.
  Stewards can now see the metadata behind an API-driven change — such as the originating user or source-system context — directly in the Audit Log event detail, rather than only the Verato service account. This makes it possible to identify which downstream user or process actually triggered an identity change. Events without metadata display cleanly with no empty sections.

We're enabling audit logs in phases to ensure a smooth rollout for every customer. If you'd like this enabled sooner in your production environment, reach out to your Verato representative or Support team, and we'll evaluate the request.

Identity Resolution

• More accurate handling of middle names in name parsing.
  Organizations ingesting records where the middle name is duplicated into the first-name field will see cleaner, more accurate resolved identities. The parsing logic now removes a trailing first-name token only when it exactly matches the middle name or its initial, preserving the integrity of the original data everywhere else. This improves match fidelity for customers with demographically inconsistent source data.

Identity Data Model

• Consistent code-set matching regardless of casing.
  Stewards working with code-set attributes stored in uppercase will no longer see false mismatches against Console-configured values. Code-set comparisons are now case-insensitive, so a stored value of "MALE" correctly matches a configured value of "Male" — improving data reliability without altering stored values.

Bug Fixes

• Reliable reactivation of previously deactivated Provider records.
  Organizations that deactivate and later reactivate a Provider's source record — for example, when a customer account is temporarily deactivated and reinstated — will now see the record correctly rejoin its original Link ID instead of being flagged as an unmergeable "do-not-link" cluster. This was a customer-reported, customer-escalated issue affecting downstream systems that depend on Link ID continuity. No action is required.

• Corrected record ordering in sourceRecordsQuery responses.
  Stewards viewing task records via MDM Cloud UI can now trust that the order of records is returned in a consistent order. Previously, paginating back and forth across source records on the task interface would cause an inconsistent display of records. No action is required.

• Fixed identity linking failure in Provider tasks.
  Stewards working Provider tasks can now successfully link identities without error. No action is required.

• Restored Pub/Sub notifications for unchanged records.
  Organizations relying on Pub/Sub to stream identity changes downstream were missing notifications when a record was posted with no demographic change — a regression affecting provider environments. This blocker-severity, customer-reported issue has been resolved so that expected notifications are delivered reliably. No action is required.

• Preserved name prefix in group-by-source responses.
  API consumers found that the name prefix field was silently dropped from the GroupBySource response format, even though it was returned in other formats. This has been corrected so that all submitted name attributes, including prefix, are consistently reflected back across response formats. No action is required.

• Reliable reactivation of deactivated attribute values. 
  Stewards updating attribute values could hit an error when reactivating a previously deactivated value, because the deactivated value lost its original casing. This blocker-severity issue has been resolved so deactivated values retain their original casing and reactivate without error. No action is required.

• Corrected source-name casing in task filtering.
  Some organizations were unable to locate tasks when filtering by certain sources, because source identifiers migrated in uppercase did not match the lowercase values the product expected. This high-priority, customer-reported issue has been resolved so that task filtering by source returns the expected results. No action is required.

• Corrected field name in consents.approvedChannels response.
  API consumers integrating with consent-channel data will no longer encounter the misspelled prefferedStartTime/prefferedEndTime fields; the response now correctly returns preferredStartTime/preferredEndTime across all response formats. No action is required.

• Graceful handling when a task's queue changes during Next/Previous navigation. 
  Stewards navigating between tasks with the Next or Previous controls now see a clear, user-friendly message when the task queue has changed — for example, due to filtering or reassignment — rather than an unexpected failure. This was a customer-escalated issue. No action is required.

Insights

New Features and Improvements 

Cohort Analyzer and reporting

• Provider identity fields now available in Cohort Analyzer® explores.
  Analysts working with practitioner data in Cohort Analyzer® can now filter and report on Verato provider identity-resolution IDs alongside name and NPI.
• Verified-address currency flag exposed in provider explores.
  Analysts can now use the current-address indicator on practitioner and facility verified-address views within Cohort Analyzer® explores, making it easier to distinguish current from historical address records in reporting.
• Verified-address views enabled for prospect provider data.
  Cohort Analyzer® now supports verified-address reporting for prospect practitioners and prospect health facilities, extending address-quality insight to non-affiliated provider datasets.
• Faster, more reliable task-based reporting in Cohort Analyzer®.
  Organizations that experienced slow or timing-out dashboard loads now benefit from a separate, optimized task-based explorer, improving the reliability and speed of routine reporting across affected tenants.

Cohort Analyzer and Snowflake data share

• New deferred-date field for task reporting in the Snowflake data share.
  Data stewards can now report on deferred tasks with accurate time-based metrics. The VERATO_TASKS Snowflake data share view now exposes a field capturing the most recent date a task was set to deferred status, mirroring how closed tasks are already reported by close date. This customer-requested enhancement supports productivity and operational trending on cross-source potential-match tasks that were previously only reportable by creation date.
  Affected Data Share Views:

  • VERATO_TASKS

  • VERATO_TASKS_PRACTITIONERS

  • VERATO_TASKS_HEALTH_FACILITIES

• Abstraction-layer logic applied to provider reference data.
  Provider reference practitioner and facility models now return the unique, most-recent record from the highest-ranked source, improving the consistency and reliability of provider reference data used in downstream reporting.

Insights dashboard experience

• Reorganized and consistently named Insights KPIs.
  Users of the Insights Launchpad now see KPIs grouped logically by related report and labeled in consistent Title Case, making the dashboard easier to scan and interpret at a glance.

• Standardized date formatting on time-based charts.
  Analysts viewing time-bound charts now see clean, consistent date labels across reporting dashboards — including week-start anchoring on weekly login trends — improving readability and reducing confusion when interpreting trends over time.

• Axis titles added across all Insights charts and reports
  Verato Insights charts and reports now display x-axis and y-axis titles across both Level 1 and Level 2 chart views. Labeled axes make Operational Insights reports easier to read and interpret at a glance, reducing ambiguity about what each chart is measuring and letting analysts and data stewards act on reporting without cross-referencing external documentation.

Bug Fixes

• Restored API Usage data refresh in Cohort Analyzer®.
  Organizations reviewing API usage information in Cohort Analyzer® found that it was intermittently not refreshing, resulting in stale data. The issue is now resolved and no action is required by customer end users.

• Resolved Cohort Analyzer® performance issues for affected tenants.
  Several organizations reported dashboard load times exceeding system and VPN timeout thresholds, degrading day-to-day reporting. Targeted inspections and remediation were completed on the affected tenants to restore reliable dashboard performance. No action is required.