Salesforce Field-Level Security strictly applies to Patient/Member Lists. If a user lacks FLS Read access to any field used in a list ' s filter criteria, the list will fail to load or will be inaccessible to that user. 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 (If a user cannot access a field used in a filter on a patient or member list, they will not be able to see the list.) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - Security

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