What are custom search views?
Verato® MDM Cloud™ lets you tailor the search experience to how your team actually works. Instead of one fixed search screen, you can build multiple search views — each scoped to an entity (and, for Provider, a domain), with its own search criteria and its own results layout. A view built for stewardship might surface different fields than one built for a call-center lookup, even though both search the same underlying data.
Search, by entity and domain
The entity selector sits at the top of the Search page, where you choose whether to search the Person, Organization, or Provider entity. For the Provider entity, a second selector appears for domain — Practitioner or Health Facility — reflecting the two out-of-the-box provider domains.
Search criteria appear on the left side of the page and results on the right. Above the criteria panel, a view selector lets you switch between the search views available for the selected entity (and domain, for Provider), alongside actions to edit, duplicate, or create a view. The criteria shown adjust automatically based on how the active view is configured to search — by Demographics, Link ID, or Source + Native ID.
Creating a search view
To create a view, select the entity (and domain, if Provider) you want to build for, then select + New search view. Creating a view is a three-step flow.
Step 1: View information and access
Name the view. The entity — and domain, for Provider — is already set based on your selection. You'll also choose which user groups have access to the view.
Note: View access is granted at the user group level.
Step 2: Search criteria
Choose how this view searches: by Demographics, Source + Native ID, or Link ID.
Note: A search view supports exactly one search method. If you need to search the same entity a different way — Demographics versus Source + Native ID, for example — create a separate view for it.
Demographics
Select which attributes should be available for searching from the list of available fields; selected attributes appear grouped by cluster in a separate panel. From there, you can reorder clusters, drag and drop individual attributes within a cluster, or remove attributes you don't need.
Important: Only attributes configured with a search type of fuzzy or exact are available for selection. Attributes without a search type configured won't appear as an option.
Source + Native ID
Optionally choose a default source. That source is preselected whenever the view is opened, though users can still search against any source they have access to — a default source isn't required.
Link ID
No further setup is needed. The view will present a single field for entering a Link ID.
Step 3: Results display format
Choose which attribute clusters appear as columns in the results grid, including system attributes such as Match Score, Link ID, number of source records, and Domain. Selected clusters appear as columns, which can be reordered by drag and drop to control display order.
Note: If a selected cluster has nested clusters, the nested cluster is included automatically and displayed within the parent's column rather than as its own column.
Selecting Create view finishes the flow. The new view is immediately available from the view selector for that entity and domain.
Managing search views
Existing views can be edited or duplicated from the view selector. Duplicating a view copies its full configuration — user group access, search criteria, and results columns — into the new copy, which is a fast way to start a new view from one that's close to what you need.
Searching on individual attributes
This search experience also supports searching on individual attributes on their own — for example, First Name alone, or Citizenship alone — rather than requiring a specific combination of attributes as earlier versions of search required.
Permissions and access
Creating and editing search views requires the Manage Search Views permission. Access to a specific view — separate from who can edit it — is granted at the user group level and is set during Step 1 of view creation.
Why customize your search experience
Personalized views: build views around a role, an objective, or a workflow, rather than working from one generic search screen.
Entity- and domain-specific: tailor views separately for Person, Organization, or Provider, down to the Practitioner or Health Facility domain.
Efficient by design: surface only the fields and columns that matter for a given view, and prioritize them with drag and drop.
Governed by user group: control who can create or edit views, and who has access to each one.
Flexible search methods: search by Demographics, Source + Native ID, or Link ID, depending on the view.
Consistent across teams: duplicate a well-built view to standardize how a team searches, instead of building from scratch each time.
Comments
0 comments
Article is closed for comments.