A pharma company wants to leverage Provider Search to help patients find nearby infusion clinics.

Provider Search uses Data Processing Engine (DPE) jobs to aggregate, flatten, and denormalize complex provider and facility records into the Care Provider Searchable Field object for fast search performance. Provider Search uses healthcare-specific provider and facility relationships so users can search by criteria such as specialty, location, network, and practice attributes. From an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. 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 (Data Processing Engine) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - Provider Search

===============