Payers deploying Health Cloud Contact Center require: (1) Health Cloud Platform PSL for core health entities, (2) Contact Center for Health Cloud PSL for console & record alert features, and (3) OmniStudio User PSL for guided interaction components. OmniStudio separates presentation, guided interaction, Salesforce data access, and server-side orchestration through FlexCards, OmniScripts, DataRaptors/Data Mappers, and Integration Procedures. Benefits Eligibility and Verification exposes insurance coverage information such as eligibility, copays, deductibles, coinsurance, and benefit limits through healthcare-specific workflows and integrations. 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 (OmniStudio User permission set license; Contact Center for Health Cloud permission set license; Health Cloud Platform permission set license) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - OmniStudio; Benefits

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