To get a comprehensive view of a patient's prescriptions, including history, to improve health outcomes, a consultant should leverage the Medication Management capability in Health Cloud. Medication Management is a feature that helps providers and care coordinators manage the medication regimen of their patients, helping to improve patient safety and reduce healthcare costs. Medication Management allows providers and care coordinators to develop a curated list of current medications, review medications with the patient, make clinical decisions and recommendations based on the review, and communicate the recommendations to the patient and the patient's prescriber6. Intelligent Appointment Management, Integrated Care Management, or Virtual Care are not capabilities that can fulfill this use case.

To implement remote monitoring functionality in Health Cloud, an administrator should populate the following records:
Code Sets: These are records that define the codes and descriptions for various types of data, such as care metrics, care observations, or units of measure. Code sets help standardize the data and enable interoperability with external systems1.
Units of Measure: These are records that define the units of measurement for various types of data, such as weight, blood pressure, or temperature. Units of measure help convert the data into a common format and enable comparison and analysis2.
Care Metric Targets: These are records that define the target values or ranges for various types of care metrics, such as blood glucose level, heart rate, or oxygen saturation. Care metric targets help monitor the patient's health status and identify any deviations or risks3.
Care Observations: These are records that store the data collected from patient devices, such as blood pressure monitors, glucose meters, or pulse oximeters. Care observations help track the patient's health progress and provide insights for care management4. Remote Monitoring Device Types, Biometrics, Chart Metrics, or Care Episodes are not records that are required for remote monitoring functionality.

Events can be specified to appear when the Health Cloud home page first loads (B), the patient timeline supports standard and custom objects (D), and filters can be used to limit the number of records shown in the patient timeline (E) are three statements that are true about the patient timeline view. The patient timeline cannot be used in any Salesforce application (A), as it is specific to Health Cloud. The patient timeline is not a Health Cloud Empower component , but a standard component in Health Cloud.