Salesforce Certified Health Cloud Accredited Professional Practice Test - Questions Answers, Page 10

List of Patient/Member Conditions (B), Gender , and Date of Birth and Age (E) are three types of basic Patient or Member information that are displayed on the Patient info component. Primary Care Coordinator (A) and Thumbnail of Chatter Photo (D) are not displayed on the Patient info component.

Coverage data model (B) is the data model that is used to represent information via standard object and record types on standard objects to manage how care is covered. Health Insurance data model (A), Payer data model , Plan data model (D), and Benefit data model (E) are not valid data models in Health Cloud.

nder Custom Metadata Types, Update the Health cloud 'HCFeature'... and Under Custom Metadata Types, Create a mapping records for Person accounts (E) are two Health Cloud specific settings that must be configured in a Health Cloud org that has Lightning Experience enabled person account. Under Custom Metadata Types, enable the Health cloud Setting (A) and Disable ''Use Individual Data Model'' in custom setting (B) are not required settings for Health Cloud. Enable ''Use Person Accounts'' custom setting (D) is not a valid setting in Health Cloud.

The individual Data Model may be used to represent members ......(B) is the recommended approach to represent members and patients during the implementation by Patient Managers as per the Salesforce recommendation. Leveraging Person Accounts is not the recommended approach to .........(A), as Person Accounts are used to represent providers, not members or patients. Salesforce does not recommend using Member Accounts to represent members ......, as Member Accounts are used to represent payer organizations, not members or patients. Leveraging Candidate Accounts are not the recommended approach to .........(D), as Candidate Accounts are used to represent potential members or patients, not existing ones.

Einstein Analytics Predictions is an add-on license that enhances Health Cloud to allow you to highlight times when a patient is most likely to attend an appointment.It uses machine learning to analyze historical data and generate predictions based on various factors2. Einstein Vision, Einstein Bots, and Einstein Activity Capture are not related to this use case.

Concurrent review is a type of care request review that ensures that a member is getting the right care in a timely and cost-effective way.It involves reviewing the medical necessity and appropriateness of an ongoing service or admission3. Disposition review, care review, preauthorization review, and retrospective review are not the correct terms for this type of review.

The design considerations that the administrator has to be aware of when creating the application for utilization management are:

Each care request has to have an associated case.A case is the standard Salesforce object that represents a care request in Health Cloud4.

New care requests can be created using the 'Create Care Request' component.This component allows users to create a new care request from any page in the Health Cloud console5.

Path can be used to visually represent the status of a care request.Path is a standard Salesforce feature that displays the stages of a process, such as a care request, and guides users along the steps in Salesforce Lightning Experience6.

Care request functionality is not included in the Health Cloud managed package. It requires installing the Utilization Management unmanaged package for Health Cloud and assigning the Health Cloud Utilization Management permission set to users along with Health Cloud permission set licenses.

Care requests do not have empower components that can be exposed within Communities. Empower components are custom Lightning components that allow patients or members to view and manage their health information in Communities. Care requests are not part of the empower components.

The steps required to display a custom field from the HealthCondition object that categorizes High Risk Conditions on the Patient Card are:

Create a custom formula field on the Custom HealthCondition object. This field can use logic to determine whether a health condition is high risk or not based on certain criteria.

Add the newly created custom formula field on the Patient Card referencing the HealthCondition object. This can be done by creating or editing a patient card configuration record and adding the field API name in the Field Name column.

Code Sets are the entity in the new data model of Health Cloud that can be used to store mappings between different coding systems such as ICD and HCC codes.Code Sets are a collection of codes that represent a specific concept or value in a terminology system1.