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

Reference and details below.

According to theHealth Cloud Implementation Guide, Lead is the object that is leveraged to track patient referrals. Lead is a standard object that represents a potential customer or patient who has expressed interest in a product or service. Leads can be converted into person accounts or contacts when they are qualified. Care Request, Care Program Enrollee, and Cases are not objects that are used to track patient referrals.

According to theHealth Cloud Implementation Guide, Contact Tracing is a feature in Health Cloud that allows providers to perform contact tracing of their internal employees or their patients during an infectious disease outbreak or pandemic. Contact Tracing helps providers identify and monitor people who have been exposed to an infected person and provide them with guidance and resources. With the help of Contact Tracing, providers can perform the following three actions:

Perform contact tracing of their internal employees during an infectious disease outbreak or pandemic. This action allows providers to track and manage the health status of their employees who may have been exposed to an infection at work or in the community.

Perform contact tracing of their patients during an infectious disease outbreak or pandemic. This action allows providers to track and manage the health status of their patients who may have been exposed to an infection during a visit or in the community.

Track the location, duration, and number of participants in each contact encounter that the infected person was involved in. This action allows providers to collect and analyze data about the exposure risk and transmission patterns of an infection. Performing an audit of the Contact Record to keep track of the changes made to the Contact record by users is not an action that providers can take with the help of Contact Tracing. Tracking their patients as contacts by using Contact entity in Salesforce is not an action that providers can take with the help of Contact Tracing.

According to theHealth Cloud Data Model Developer Guide, CareProviderSearchableField is the object that external users need read access to allow patients to search and find providers that fit selected criteria. CareProviderSearchableField is a custom object that defines which fields on the CareProvider object are searchable by external users. CareProvider is a custom object that represents a provider who delivers care or services to patients. CareProviderFacilitySpeciality, HealthcarePractitionerFacility, and CareProviderSearchConfig are not objects that external users need read access to for provider search.

According to theHealth Cloud Implementation Guide, the three steps that an administrator should take to ensure all tasks identify the role 'Care Consultant' are:

Update/Add the organization roles in the CarePlan_Role_Patient key:value pair in Health Cloud Setting. This step allows the administrator to define or modify the roles that are available for assigning tasks to patients.

Update the organization roles in the CarePlan_Role_Care_Coordinator key:value pair in Health Cloud Setting. This step allows the administrator to define or modify the roles that are available for assigning tasks to care coordinators.

Update the corresponding roles in the Assigned To picklist for the Care Plan Template Task object. This step allows the administrator to update the values in the picklist field that determines who is responsible for completing a task in a care plan template. Creating an ETL script to update the previously assigned To picklist values of Tasks created in the past is not a recommended step, as it can introduce errors and data loss. Updating the Care Plan Record Type custom metadata type to reflect the care coordination processes specific to the Care Coordinators is not a relevant step for changing the role name.

Reference and details below.

According to theHealth Cloud Data Model Developer Guide, two ways that an administrator can ensure that Patient Risk scores are recalculated periodically are:

Set up a scheduled Apex batch job. This method allows the administrator to create an Apex class that implements Database.Batchable interface and Schedulable interface, and schedule it to run at specified intervals using Apex Scheduler.

Set up an Apex batch job and run it manually. This method allows the administrator to create an Apex class that implements Database.Batchable interface, and execute it manually using anonymous Apex code or developer console. Using CMS recalculation API is not a valid way, as CMS recalculation API is not a feature of Health Cloud. Using a third party API to recalculate CMS risk score is not a recommended way, as it can introduce security and integration risks. Creating a Healthcare Provider enrollment flow is not a relevant way, as it has nothing to do with patient risk scores.

According to theHealth Cloud Data Model Developer Guide, CarePlan Template Task, TimelineViewConfiguration, and CarePlanGoal are three Health Cloud objects that are part of the standard Care Management data model. CarePlan Template Task is a custom object that represents a task that is part of a care plan template. TimelineViewConfiguration is a custom object that defines how to display timeline events for a care plan. CarePlanGoal is a custom object that represents a goal that is part of a care plan. CareSpeciality and CareProgramGoal are not Health Cloud objects that are part of the standard Care Management data model.

Reference and details below.

According to theHealth Cloud Implementation Guide, Program Enrollee Settings is the place within Health Cloud Settings where a Health Cloud administrator can make changes to accomplish the requirement of enabling the members to enroll in and out of Care Program multiple times. Program Enrollee Settings allow the administrator to configure how members can be enrolled in or removed from care programs, such as allowing multiple enrollments, setting enrollment statuses, and defining enrollment criteria. Care Program Settings, Health Cloud Settings, and Care Request Settings are not places where the administrator can make changes to enable multiple enrollments.

According to theHealth Cloud Implementation Guide, two statements that are true about Care Teams are:

Care Team Members are optional on a Care Plan. This statement is true because a care plan can be created without any care team members assigned to it. However, adding care team members can help with collaboration and coordination of care.

A Care Plan must have a Coordinator as a member of the Care Team before a Care Plan Template can be applied. This statement is true because a coordinator is required to manage the tasks and goals of a care plan template. A coordinator can be either an internal or external user who has access to Health Cloud. If the Problem and Goal objects use Private Sharing, Care Team Membership provides access to these objects is not a true statement, as care team membership does not grant access to objects that use private sharing. Communities must be enabled before External Care Team members can be added is not a true statement, as external care team members can be added without enabling communities.