Salesforce Certified Health Cloud Accredited Professional Practice Test - Questions Answers

According to the Salesforce documentation3, to leverage the health cloud utilization management capabilities, you need to install the health cloud managed package and the health cloud care request extensions managed package. The health cloud managed package contains the core objects, fields, tabs, apps, components, and more that are required for health cloud functionality.The health cloud care request extensions managed package contains additional objects, fields, tabs, apps, components, and more that are specific to utilization management3.

Reference and details below.

According to the Salesforce documentation, PurchasePlan is an object in Health Cloud that stores information about a plan purchased by an employer or an individual from a payer. PurchasePlan is to be used as a template for creating MemberPlan records for each member enrolled in the plan. MemberPlan is an object in Health Cloud that stores information about a member's enrollment in a plan, such as effective date, termination date, coverage type, and benefits.

According to the Salesforce documentation, the following capabilities of provider search would a customer service agent use to help prospective and returning patients find the right provider:

Use custom fields defined in healthcare provider and healthcare practitioner facility entities as part of search experience. The provider search allows customer service agents to use custom fields defined in healthcare provider and healthcare practitioner facility entities as part of the search criteria or filters. This helps them narrow down their search results based on specific attributes or preferences.

Use provider search in an authenticated community page. The provider search allows customer service agents to use provider search in an authenticated community page where they can log in with their credentials and access more features and information than an unauthenticated community page.

Control the list of fields displayed in the search panel and search results. The provider search allows customer service agents to customize which fields are displayed in the search panel and search results for different types of providers or facilities. This helps them find the most relevant information quickly and easily.

Encrypting the data using shield (A) and using field level security setting, record access setting and object permission (E) are two ways to prevent unauthorized users from accessing the data. Installing shield and enabling mask (B) is not enough to protect the data, as masking only obscures the data in reports and dashboards, but does not prevent access to the underlying data. Creating sharing sets and optimizing data using mask (D) are not relevant to data security.

Reference and details below.

Customizing the out of box enrollment flow to match requirements (A) and identifying the patient as approved candidate in the flow (D) are two steps that an administrator can take to configure the care program enrollment flow. Using the provider enrollment flow out of box (B) is not applicable, as it is for providers, not patients. Customizing the provider site flow and customizing the care coordinator flow for patient (E) are not related to the care program enrollment flow.

When creating a care plan with a template you can unselect tasks so they will not be included (A), the sort order of the Task group by Fields can be changed under custom setting task group (B), and care plan templates must include at least 1 problem, 1 goal and 1 task are true statements about Care Plan Templates. When creating a care plan with a template you can change the offsets of the tasks (D) is false, as you can only change the offsets of the tasks when creating a care plan without a template. Care plan templates can only be used when creating a new care plan (E) is false, as you can also use care plan templates when editing an existing care plan.

Goal and Problem (D) are optional fields when creating a new Care plan task. Status (A) and Task Owner (E) are required fields when creating a new Care plan task. Due Date (B) is not a field on Care plan task, but rather on Task object.

Claims data model leverages external objects to support the use case of integrating claims data from external systems into Health Cloud.External objects are similar to custom objects, except that they map to data that's stored outside your Salesforce org1.