Customizing Entity 360®

Entity 360® is the complete, 360-degree view of a resolved identity in Verato® MDM Cloud™ — bringing together every attribute, source record, and related activity into a single screen. It's available for Person, Provider, and Organization entities, giving your team one place to see who's who, where their data comes from, and what needs attention.

Entity 360® is organized around two main areas:

• Summary — a curated snapshot built from Tiles and Cards

• Details — the underlying source records and raw attribute data

The Summary view is fully configurable using the View Builder in the Verato MDM Cloud™ Admin Console. Verato ships with a set of predefined views, and additional views can be built to match how different teams work.

Every Entity 360® deployment starts with a set of Verato-defined views, tailored by entity type:

• Person — Person – Generic, Person – Patient

• Organization — Organization – Generic

• Provider — Provider – Practitioner (Type 1), Provider – Health Facility (Type 2)

Each view is made up of Tiles and Cards.

Tiles appear on the left side of Entity 360® and summarize information beyond core identity data — for example, Sources, Pending Tasks, or Household. The Summary tile is included in every view by default; other out-of-the-box (OOTB) tiles can be added or removed depending on the use case.

Cards make up the main content area of the Summary view and are organized around clusters of attributes. A view can draw from Verato-defined cards (grouped by entity domain), Enrich cards (where applicable), or fully custom cards. For each card, configuration controls which attribute clusters and attributes appear, their cardinality, and their sort order (by assertion date, source priority, or both).

Editing any Verato-defined card converts it into a custom card. Once that happens, it's no longer automatically updated by Verato, so future OOTB improvements to that card won't carry over automatically.

The Details tab uses Perspectives to control which source records and attributes appear in the Stewardship grid. Unlike Views, Tiles, and Cards, Perspectives can be created and managed directly by any user in Entity 360®.

A Perspective selector sits at the top of the Details tab, defaulting to Default - Verato Defined. From there, you can:

• Save changes to the current Perspective

• Duplicate the current Perspective — name the copy and, optionally, set it as your default

• Revert to discard unsaved changes

• Open Manage Perspectives to view, rename, or delete your saved Perspectives

The Filters tab of Filters & Columns narrows down which source records appear in the grid:

• Match Tier — show only records at specific match tiers

• Source Records — optionally include inactive or merged records, which are excluded by default

• Sources — narrow the grid to specific sources, or leave set to All

Each Perspective's grid can be refined using Filters & Columns. On the Columns tab, search for an attribute and move it between Attributes Shown and Attributes Hidden.

Beyond building views and controlling who has access to them, Verato MDM Cloud™ lets you set defaults for each User Group — which tab Entity 360® opens on, and which view loads automatically for each entity type.

The Entity 360 Default Tab setting controls which tab loads first when a user in that group opens an Entity 360® page — for example, Summary or Details.

For each entity type — Person, Organization, Provider (Type 1), and Provider (Type 2) — you can select a default view that's applied automatically for the User Group. This is separate from managing who has access to a view: a group can have access to several views while only one loads as its default.

Views, Tiles, Cards, and the default landing tab are configured using the View Builder in the Verato MDM Cloud™ Admin Console — a point-and-click interface. Admin Console access isn't currently available to customers directly, so to request a change, contact your Customer Success representative with:

• The entity type affected (Person, Provider, or Organization)

• The use case or persona the view is intended for

• Which Tiles or Cards should be added, removed, or reconfigured

• Whether the default landing tab should be Summary or Details

• Entity 360®

• Search: customizing your search view experience