Verato-Defined Domains

Verato® organizes identity data around two core concepts: entities and domains.

An entity (Person, Provider, or Organization) represents the real-world object whose identity Verato MDM Cloud™ resolves and manages.

A domain represents a contextual view of that entity — the specific set of attributes and workflows that apply based on how the entity is being used. For the full concept explanation, see Entities and domains in Verato MDM Cloud.

Verato MDM Cloud™ ships with five Verato-Defined (out-of-the-box) domains across the three entities:

Person entity

Core Person

Core Person is the base domain for the Person entity — every other Person domain builds on it. It represents the canonical, non-clinical view of an individual: who they are, how to reach them, and how they're identified, independent of any specific use case.

Use it for: general demographic, contact, and identity data that isn't tied to a specific context like care delivery.

Key clusters:

• Names

• Addresses

• Phone numbers

• Emails

• Dates of birth

• Gender and gender identity

• Social Security numbers

• Citizenship, race, ethnicity, and religious affiliation

• Marital status and sexual orientation

• Communication languages

• Photos

• Death details

• External and alternate identifiers

• Multiple birth indicators

• Qualifications, consents, and preferences

Patient

Extends: Core Person. The Patient domain inherits every Core Person cluster and adds healthcare-specific attributes on top. It doesn't create a separate identity — it's the same underlying person, viewed through a healthcare-specific lens.

Use it for: clinical, administrative, or operational workflows — scheduling, billing, patient access — where healthcare-specific data is required.

Key clusters added on top of Core Person:

• Health insurance coverage

• Guarantor (the person financially responsible for the patient)

• Upcoming appointments

• Recent encounters

Provider entity

Practitioner (Type 1)

Practitioner represents an individual clinician or care provider — physicians, nurses, and other licensed practitioners — acting in a professional healthcare role.

Use it for: provider directory, referral, credentialing, or network participation use cases involving an individual person, as opposed to an organization.

Key clusters:

• Names and demographics (including SSN, citizenship, race, ethnicity, and photos)

• Contact information (address, phone, fax, and email)

• National Provider Identifiers (NPI) and licenses

• Specialties and sub-specialties

• Practitioner roles and participation (accepting new patients, service mode, availability)

• Accepted insurances

• Clinical expertise and programs

• Medicare and compliance information

• Background and profile (education, practice history, research)

• Qualifications, consents, and preferences

• Alternate and external identifiers

Health Facility (Type 2)

Health Facility represents an organization or location that delivers care — hospitals, clinics, labs, and imaging centers.

Use it for: provider directories, contracting, referrals, or network participation involving a facility or organization rather than an individual.

Key clusters:

• Organization names

• Contact information

• National Provider Identifiers (NPI) and licenses

• Specialties and taxonomies

• Alternate, external, and employer identifiers (EIN)

• Authorized officials

• Products and service lines

• Accepted insurances

• Industry classification (NAICS/SIC) and legal status

• Operational profile (employee count, founding date, revenue)

• Qualifications

Organization entity

Core Organization

Core Organization represents a non-clinical organization — payers, employers, vendors, partners, or other corporate entities.

Use it for: legal, operational, or business identity that sits outside direct care delivery.

Key clusters:

• Organization names

• Contact information

• Alternate, external, and employer identifiers (EIN)

• Authorized officials

• Industry classification (NAICS/SIC) and legal status

• Products and services

• Operational profile

• Qualifications

Need something these domains don't cover?

If your use case needs attributes, or a domain name, that none of the five Verato-Defined domains provide, Verato MDM Cloud™ supports creating a custom domain based on any of them. See Creating custom domains for details.