To make Provider Search available to external portal users, the admin must place the Provider Search component on an Experience Cloud site page and grant the external profile Read access to Care Provider Searchable Field. Provider Search uses healthcare-specific provider and facility relationships so users can search by criteria such as specialty, location, network, and practice attributes. From a deployment perspective, the configuration must be activated, licensed, permissioned, or migrated in the correct sequence so that the functionality is available to users without weakening the organization ' s existing security and governance controls. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Give the site user profile Read access to the Care Provider Searchable Field object.; Use Experience Builder to add the Provider Search component to a page on the site.) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.
Study Guide references/topics:Deploy - Provider Search
===============
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit