A customer wants to view a patient ' s health conditions and clinical encounters as...

In Salesforce Setup under Timeline, administrators create a new Timeline record configuration, define the base object and related objects/fields (e.g., Conditions, Encounters), and place the component on the page. 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. Enhanced Timeline displays configured records chronologically while enforcing the user ' s underlying object, field, and record access. 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 (Create a new Timeline record within Setup.) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - Person Account; Enhanced Timeline

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