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

Health Cloud Foundation

Assigns read access to additional Health Cloud platform capabilities, including the Provider Management data model.

The Health Cloud Provider Network Management permission set grants access to provider management objects so users can manage credentialing and recruiting.

To use the Provider Network Management features of Health Cloud, assign both the Provider Network Management permission set and the Health Cloud permission set to your users

Users can access Provider Management standard objects by using Health Cloud, by assigning Health Cloud Platform Permission set licenses, and by assigning Health Cloud Foundation Permission set.Health Cloud is the industry-specific solution that includes Provider Management features such as provider search, provider network management, and provider credentialing3.Health Cloud Platform Permission set licenses grant access to the Health Cloud platform objects and features, including the Provider Management data model4.Health Cloud Foundation Permission set assigns read access to additional Health Cloud platform capabilities, including the Provider Management data model5. Service Cloud is not required to access Provider Management standard objects, and the Provider Permission set is not a standard permission set in Health Cloud.

Reference and details below.

Care Provider Searchable Field is the denormalized object that holds data to support the Provider Search feature in Health Cloud. Care Provider Searchable Field is a custom object that stores searchable fields from the Healthcare Provider and Healthcare Provider Facility objects. It allows users to search for providers based on various criteria such as name, location, specialty, and availability. Healthcare Provider Facility, Provider Search Sync Logs, and Healthcare Provider are not denormalized objects in Health Cloud.

The admin must configure all Lead field mappings including Medical Record Number, Source System and Source System ID (A), some Lead field mappings including Medical Record Number, Source System ID can be handled automatically by HC , and duplicate checks on Medical Record Number, Source System and Source System ID can be handled automatically by HC (E) are true statements about the steps the admin can take. The custom Convert to Patient button should be added to the Lead detail page, not the list view (B). The Lead to Individual Conversion apex class will not create a new Opportunity for the patient (D).

Timeline (A), Life Events , and Patient Card (D) are components that are customizable in HC. EHR Data (B) is not a component, but a type of data that can be integrated with HC. Custom Label (E) is not a component, but a metadata type that can be used to create labels for components.

Patients should be modeled as Person Accounts. Providers and non-clinical staff should be modeled as Contacts (D) is the correct answer. Patients, physicians and non-clinical staff should not be modeled as Person Accounts (B), as Person Accounts are only for patients. The individual Data Model is not recommended for HC, as it does not support all the features of HC . Providers and non-clinical staff can be modeled as Person Accounts or Contacts (A) is not a valid answer, as it does not specify which group should be modeled as Person Accounts.

Install HC managed package (B), verify that chatter is enabled , and configure the console view (D) are three steps required to configure HC. Install HC unmanaged Package (A) is not a valid step, as there is no unmanaged package for HC. Enable the options for contact to related with multiple accounts (E) is not a required step, as it is only needed if using Contacts instead of Person Accounts.

Case, Problems, Goals, Tasks, Care Plan Templates (D) are the standard objects that are included in the Care Plan Data Model. Care programs, Product, Patients (A), Life Events (B), and Benefits, Barriers, Provider Education are not standard objects in the Care Plan Data Model.

Add NPI for associated provider (A) and create a care program health care provider with an associated care program provider (E) are two steps required to create health care providers for health program. Choose associated facility for care program (B) is not a valid step, as facilities are not related to health care providers. Add the UPIN is not a required step, as UPIN is an optional field for health care providers. Create care program providers from the app launcher (D) is not a valid step, as care program providers are created from the related list on the care program record.