Entities and domains in Verato MDM Cloud – Verato Support

Two concepts sit at the center of how Verato® MDM Cloud™ organizes identity data: entities and domains. Understanding them will help you make sense of how your data is structured, matched, and displayed across the platform.

What is an entity?

An entity represents a real-world object whose identity Verato resolves and manages. Verato supports three entity types:

Person — an individual human being
Provider — an individual clinician or a healthcare organization involved in delivering care
Organization — a non-clinical organization

Records within the same entity type share the same general kind of attributes and are matched using an approach tuned to those attributes. For example, Person records typically include name, date of birth, home address, and personal identifiers, so Verato applies matching logic built around those fields.

What is a domain?

A domain is a contextual view of an entity — it reflects the role or persona that entity plays in a given context. Domains determine which attributes apply and which workflows and APIs are relevant, without creating a separate identity. In other words, domains don't fragment a person's or organization's identity; they add context to a single, unified identity.

How entities and domains fit together

Verato ships with pre-built domains for each entity type out of the box:

Entity	Pre-built domain	What it covers
Person	Core Person	Canonical representation of a person with general demographic attributes
Person	Patient	Healthcare-specific view of a person, used in clinical and care delivery contexts
Provider	Practitioner	Individual clinicians or care providers
Provider	Health Facility	Organizations or locations where care is delivered
Organization	Core Organization	Canonical organizational identity

Verato MDM Cloud™ can also be configured with custom domains beyond these out-of-the-box options — for example, Member, Citizen, or Prospect under the Person entity, or Vendors under the Organization entity.

Why this matters

Because domains are contextual views of a single underlying identity, you get the best of both: a unified, trusted record for each person, provider, or organization, and the flexibility to see and work with that record differently depending on the use case — clinical, member engagement, credentialing, and more.

Where to go next

See the Verato MDM Cloud Introduction for a platform overview
Visit the Verato MDM Cloud UI Demo to see entities and domains in the console
For developer-level detail on the entity/domain API model, see the Verato developer documentation