Health Condition records (representing a patient ' s medical condition) require foreign keys pointing to the patient ' s Account (Person Account) and standard clinical terminology/coding contained in the Code Set object. Health Cloud uses Person Accounts for individuals such as patients or members, combining Account and Contact behavior while preserving the security and relationship model expected by healthcare features. 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 (Account; Code Set) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Deploy - Person Account

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