February 2026

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

  • Announcement Date: February 5, 2026
  • Release Date: February 19, 2026

As Verato continues the transition toward the unified MDM Cloud experience, both interfaces—the current platform and the new MDM Cloud — will coexist for a period of time. Features and updates may be delivered to each interface independently, depending on where they provide the most value for customers during this transition.

UMPI Portal & Verato MDM Cloud

Patient Journey

Bug Fixes

  • Fixed an issue where sources created by the createDataSource endpoint were not being reflected in MDM Cloud.
  • Fixed an issue where identities were not being brought together under a single household ID despite meeting the configured household definitions.
  • Fixed an issue where certain household notifications weren't being sent when households were being bridged together

Patient Journey & Provider

New Features and Improvements

  • Added an optional capability that automatically infers a cluster’s active or inactive status based on whether it appears in the most recent postIdentity to that record.

    • Example:

    • Jan. 1st - Posted S1N1 with phone number 919-413-9964 - this makes it an ‘active’ phone number by our inferred status logic.

    • Feb. 1st - Re-posted S1N1 with two phone numbers: 919-413-9964 and 919-460-0354. Both of these values are now ‘active’.

    • Mar 1st - Re-posted S1N1 with only the 919-460-0354 phone number. With this feature active - that is the only ‘active’ value, and the older value (919-413-9964) is considered 'inactive'.

Verato MDM Cloud

Identity

Bug Fixes

  • Fixed a bug where child clusters were unable to be deleted from identities (contact information, channels and preferences, etc.)
  • Improved resilience when handling intermittent 401 authorization errors, preventing failures in identity loading and overlay application.
  • Fixed an issue where some active addresses were missing from the activeOnly response for provider identities.
  • Fixed an issue where the auditId field was returned in an incorrect format.
  • Fixed an issue that prevented an identity from loading in the UI when one or more date fields were null.

Insights

New Features and Improvements

  • Cohort Analyzer now supports Custom Attribute exploration capability, automatically surfacing data from customer-defined domains and attributes, as configured in Verato MDM Cloud. Custom Domains and flattened custom attributes are available in Cohort Analyzer explores based on stack, entity, and user access. Any addition or changes to the configuration in MDM Cloud, will be reflected in Cohort Analyzer the next calendar day, after overnight refresh. Customers without custom domains or attributes are not impacted.