Health-Cloud-Accredited-Professional Salesforce Health Cloud Accredited Professional Exam (SU24) Questions and Answers

 The two connectivity options that a consultant should leverage as the scheduling engine for Intelligent Appointment Management in Health Cloud are Electronic Health Record (EHR) System and Salesforce Scheduler. An EHR System is an external system that stores and manages clinical data and appointments for patients or members. Salesforce Scheduler is a native Salesforce feature that allows users to schedule appointments with customers or prospects.

According to the Health Cloud Data Model Developer Guide, two ways that a data architect can ensure PHI/PII data visibility is minimized during the migration of patient data from an existing Service Cloud org to a new Health Cloud org are:

Use Salesforce Data Masking when moving data to a sandbox. Data Masking is a tool that helps you protect sensitive data in sandboxes by masking it with anonymized values.

Use Data Templates to exclude PHI/PII data from being added to partial copy sandboxes. Data Templates are files that specify which objects and fields to include or exclude when creating a partial copy sandbox. Exporting data to a spreadsheet to remove PHI before importing it into a sandbox is not a recommended way, as it can introduce errors and security risks. Ensuring sandboxes have Platform Shield enabled is not a valid way, as Platform Shield is not a feature of sandboxes. Platform Shield is a product that allows encryption of data at rest in production orgs.

According to the Health Cloud Implementation Guide, the two permission set licenses that are required to utilize and access Health Cloud features and functionalities are Health Cloud and Health Cloud Permission Set License. Health Cloud is a base license that enables access to Health Cloud objects and tabs. Health Cloud Permission Set License is an add-on license that enables access to Health Cloud Lightning components and pages. Health Cloud for Community, Health Cloud Platform, and Health Cloud Standard are not valid permission set licenses for Health Cloud.

To migrate from the individual model to person accounts, you need to do the following steps:

Enable person accounts on your org.

Configure your person account record type in the Individual Record Type Migration custom setting.

Use a CSV file and map PersonRecordTypeId to the person account record type.

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).

According to the Salesforce documentation3, Practitioner Relationship is an object in Health Cloud that is used to track the relationship between a provider and another provider or a facility. Practitioner Relationship includes information such as the relationship type, start date, end date, and status. Practitioner Relationship can be used to help sales teams view all providers related to a specific facility3.

A is correct because obtaining verified parental consent before collecting and storing any personal information of children is one of the main requirements of COPPA. The consent must be obtained in a way that ensures that the person providing consent is the child’s parent or legal guardian, such as using a credit card, digital signature, or video conference.

B is correct because disclosing the organization’s privacy policy to parents and obtaining their consent is another requirement of COPPA. The privacy policy must explain what information the organization collects from children, how it uses and discloses it, and what rights parents have to review or delete their children’s information.

C is incorrect because ensuring that Bloomington Caregivers’ system implementation partner has met all COPPA regulations during the build phase is not a consideration for the company, but for the partner. The company is ultimately responsible for complying with COPPA, regardless of who builds their system.

D is correct because implementing appropriate security measures to safeguard children’s personal information is another requirement of COPPA. The organization must establish and maintain reasonable procedures to protect the confidentiality, security, and integrity of personal information collected from children.

References: : Children’s Online Privacy Protection Act (COPPA) : Children’s Online Privacy Protection Rule ("COPPA")

According to the Salesforce documentation2, to display device information on a patient card, you need to create an asset record and a care registered device record that look up to the patient. An asset record represents the device that is used by the patient, such as a blood pressure monitor, a glucose meter, or a pulse oximeter. A care registered device record represents the relationship between the patient and the device, such as the device name, serial number, status, and start and end dates2.

After deploying a care plan template from a sandbox to a final environment using Data Loader, the consultant should recommend the following two steps to enable users to successfully leverage the new template:

Confirm User access to Care plan objects: The consultant should ensure that the users have the appropriate permissions and sharing settings to access the care plan objects, such as Care Plan Template, Care Plan Template Problem, Care Plan Template Goal, and Care Plan Template Task1. The users should also have access to the parent records of the care plan objects, such as Account or Contact2.

Activate the new care plan template: The consultant should activate the new care plan template by changing its status from Draft to Active3. This will make the template available for users to apply to their patients. The consultant does not need to activate the problems, goals, and tasks associated with the template separately, as they are automatically activated when the template is activated3.

References:

1: Permissions Required for Care Plans - Salesforce 2: Give Caseworkers Access to Goal Assignments and Benefit Assignments Related to Care Plans - Salesforce 3: Create a Care Plan Template - Salesforce

To help the payer organization electronically receive requests for services from Bloomington Caregivers, a consultant should recommend the following business level APIs:

Prior Authorization API: This API allows Bloomington Caregivers to create requests for prior authorization for services that require approval from the payer organization. The API also allows Bloomington Caregivers to update or cancel existing requests or query the status of requests9.

Care Services API: This API allows Bloomington Caregivers to create requests for care services that are covered by the payer organization’s benefit plans. The API also allows Bloomington Caregivers to update or cancel existing requests or query the status of requests10.

Referral Request API: This API allows Bloomington Caregivers to create requests for referrals to other providers that are part of the payer organization’s network. The API also allows Bloomington Caregivers to update or cancel existing requests or query the status of requests11. Admission, Discharge, and Transfer (ADT) API or Benefit Verification API are not business level APIs that can fulfill this requirement.

According to the Salesforce documentation, Health Cloud is a health IT solution that helps healthcare organizations deliver personalized and collaborative care across every touchpoint. Some of the characteristics of Health Cloud are:

Health Cloud is an engagement layer that connects patients, providers, payers, and partners on a single platform. It enables seamless communication and collaboration across the healthcare ecosystem.

Health Cloud is part managed package and part core services. The managed package contains custom objects, fields, tabs, apps, components, and more that are specific to healthcare use cases. The core services include standard Salesforce features and functionality that are available across all Salesforce products.

To leverage Utilization Management features in Health Cloud, users need to have Health Cloud Permission Set License, Health Cloud Utilization Management Permission Set, and Health Cloud Foundation Permission Set. Health Cloud Permission Set License grants access to the Health Cloud platform objects and features. Health Cloud Utilization Management Permission Set grants access to utilization management objects so users can manage care requests and reviews. Health Cloud Foundation Permission Set assigns read access to additional Health Cloud platform capabilities4. Health Cloud Analytics Permission Set and Health Cloud Platform Permission Set License are not required for Utilization Management.

To create Salesforce reports to analyze patient outcomes and patient referrals, a consultant should recommend the following steps:

Create custom report types for clinical objects, such as Condition, Medication, or Encounter, to access the data stored in Health Cloud’s clinical data model1.

Assign appropriate permissions to internal users, such as the Health Cloud Analytics permission set, to enable them to view and create reports and dashboards2.

Adjust template care management reports and dashboards, such as Patient Outcomes or Patient Referrals, to customize them for the customer’s specific needs34. Enabling the enhanced Analytics for Healthcare setting or leveraging the Patient Referral Management unmanaged package are not required steps for this requirement.

According to the Salesforce documentation1, the Health Cloud Provider data model is an optional data model that can be used to represent providers and their relationships in Health Cloud. It is not required for all Service Cloud to Health Cloud migrations, and it can coexist with the existing data model. The Custom Provider Search Lightning component is a custom component that can be used to search for providers using any data model, including the Health Cloud Provider data model or a custom provider data model. The Health Cloud Provider Search component is a standard component that can be used to search for providers using the Health Cloud Provider data model only. It can be extended or customized, but not replaced by a custom component1.

According to the Salesforce documentation1, there are two ways to request a rep-to-rep transfer in Health Cloud:

When creating an order authorization for a visit, you can request a transfer from another rep’s inventory location by selecting the Transfer option in the Product Selection screen1.

To request a transfer from a specific inventory location, you can navigate to Products, select the product you want to transfer, and then click Request Transfer in the Related list1.

The best way to conduct discovery to define a workflow for the call center users is to identify personas and ask them to walk through a day in their life, taking notes and identifying opportunities for optimization. This approach will help the consultant understand the current state of the process, the pain points and challenges, the goals and expectations, and the potential solutions.

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.

According to the Salesforce documentation1, the Health Cloud Reports for Patient Referral Management is an unmanaged extension package that provides a prebuilt dashboard with reports on important aspects of referral management, such as referral status, referral source, referral age, and referral efficiency. The package also includes custom fields, custom objects, and custom report types to support the dashboard. To use this package, a consultant should install it in their org and assign the appropriate permissions to the users who need to access the dashboard. The package is compatible with Health Cloud and CRM Analytics.

References:

1: Provide Referral Management Reports | Health Cloud Administration | Salesforce Developers

A is correct because Intelligent Appointment Management (IAM) is a solution for care coordinators to book appointments without having to manually check availability and resources themselves. IAM aggregates multiple scheduling engines, such as Salesforce Scheduler or Electronic Health Record (EHR) scheduling engines, or both, so that schedulers and patients can see all available appointments in one place. IAM also supports complex appointment types, such as infusions, that require multiple steps or resources.

References: : Meet Intelligent Appointment Management : Intelligent Appointment Management

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.

 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.

The consultant should create a criteria-based Account sharing rule to expand this access. A criteria-based Account sharing rule allows the consultant to share accounts that meet certain criteria with a specific group of users, such as auditors. This way, the auditors can view patient records that they do not own in Health Cloud.

A is correct because ensuring the user has the right object permissions is the first step in troubleshooting this issue. The Enhanced Timeline for Contact Center displays records from various objects, such as Case, Engagement Interaction, Engagement Topic, and Task. The user needs to have at least read access to these objects and their fields to view them on the timeline. The administrator can check and modify the user’s object permissions from their profile or permission set.

References: : Enhanced Timeline for the Contact Center : Object Permissions

FHIR (Fast Healthcare Interoperability Resources) is a standard for exchanging healthcare information electronically. FHIR V4 is the latest version of FHIR, and it is aligned with Health Cloud3. Option A is incorrect, because there is no FHIR V5 yet. Option C is incorrect, because FHIR V3 is an older version of FHIR that is not aligned with Health Cloud. Option D is incorrect, because FHIR V1 is also an older version of FHIR that is not aligned with Health Cloud.

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.

 According to the Health Cloud Implementation Guide, Health Cloud – Console is the console that is available within Lightning Experience. It is a customizable workspace that allows users to view and manage multiple records on a single screen.

 Health Cloud Consent Management provides features such as email for signature and e-signature. Email for signature allows users to send consent documents to participants via email and track their status. E-signature allows participants to electronically sign consent documents using a third-party service such as DocuSign1. Capture Data Use Purpose, Delegated Signing, and Capture IP Address during completion are not features of Health Cloud Consent Management.

Advanced Therapy Management can help the pharma company with its personalized medicine programs, as it enables them to coordinate the various steps involved in the process, such as apheresis and infusion. Advanced Therapy Management provides a set of features and tools that allow users to create and manage complex care plans, track the progress of each patient, and monitor the inventory and logistics of the therapy products.

According to the Health Cloud Implementation Guide, a Health Cloud administrator can change the default sub-tab when opening a record by going to setup, navigating to Custom Settings, and editing the Default Subtab setting. This setting allows you to specify which sub-tab should be displayed by default when opening a record in Health Cloud – Console. The other options are not relevant for changing the default sub-tab.

According to the Health 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.

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.

According to the Salesforce documentation, a life sciences company can track the following terms about a care program using program management in Health Cloud:

The clinical indicators that need to be monitored in the care program, such as blood pressure, cholesterol level, or weight.

The products that are associated with a given care program, such as medications, devices, or services.

The plans that enrollees have been engaged in as part of the care program, such as education plan, adherence plan, or follow-up plan. Therefore, options A, B, and E are correct. Option C is incorrect, because marketing campaigns are not tracked by program management in Health Cloud. Option D is incorrect, because budget and expense are not tracked by program management in Health Cloud.

B is correct because creating a new record for the HCBenVerConnect custom setting is required to access the Benefit Verification component in Health Cloud. The HCBenVerConnect custom setting stores the configuration details for the connection to the external benefit service that provides the patient’s insurance coverage information.

D is correct because creating a named credential to support authenticated callouts is required to access the Benefit Verification component in Health Cloud. A named credential specifies the URL of the external benefit service and the authentication protocol and credentials to use for callouts to that service.

References: : Set Up Data for Benefit Verification : [Named Credentials]

C is correct because Social Determinants of Health (SDOH) are the non-medical factors that influence health outcomes, such as socioeconomic and cultural barriers. Health Cloud provides a feature that allows users to capture and track SDOH data for patients, such as housing status, food security, transportation access, and education level. This feature can help the pharmaceutical company to support patients throughout their clinical journey by identifying and addressing their SDOH needs.

References: : Social Determinants of Health at CDC

B is correct because Program Enrollment Flow is the out-of-the-box Health Cloud feature that helps users to register patients to care programs while capturing their consent. Program Enrollment Flow is a prebuilt flow template that guides users through the steps of selecting a program, adding related records, and obtaining consent from the patient. The flow also creates a care plan for the patient based on the program template.

References: : Care Programs in Health Cloud : Configure the Program Enrollment Flow

Owner (A) and Status © are two fields that are required when creating a new care plan task. Problem (B), Goal (D), and Due Date (E) are optional fields when creating a new care plan task.

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.

 To use the Enhanced Timeline functionality, a consultant needs to create a new Timeline View Configuration record and specify the object, fields, and filters for the timeline view. This allows the customer to view a patient’s health conditions and clinical encounters as a sequence on the patient’s Person Account page. Cloning the HCTimeline FlexCard, adding a record to the HealthCloudTimelineConfig custom setting, or creating a new Timeline record within Setup are not required for this functionality1.

According to the Health Cloud Data Model Developer Guide, Orders is the underlying object that helps with sales compliance with sales agreements. Orders is a standard object that represents a confirmed request to purchase one or more products. Orders can be used to track the fulfillment and invoicing of products that are sold to customers. Orders can also be linked to contracts or agreements to ensure compliance with the terms and conditions of the sales. Opportunities, Contacts, and Forecasts are not objects that help with sales compliance with sales agreements.

Reference and details below.

B is correct because Care Request and Care Request Item are the standard objects in Health Cloud that are used to set up prior authorizations. Care Request represents a request for authorization of a service or procedure, and Care Request Item represents a specific service or procedure within the request. These objects can be integrated with an external system that manages the end-to-end prior authorization process, and display the preauthorization outcomes from that system.

References: : Care Request : Care Request Item : Prior Authorization in Health Cloud

Reference and details below.

According to the Salesforce documentation, to grant users read access to health insurance records and also create, read and update access to utilization management records, you need to assign them the HC Utilization Management permission set. This permission set grants users access to various objects, fields, tabs, apps, and components related to utilization management in Health Cloud.

Mask is a Salesforce product that helps you anonymize sensitive data in production copy sandboxes to ensure privacy, compliance, and regulatory requirements are met3. Mask replaces sensitive data with fictitious yet realistic data that preserves the characteristics of the original data. It also prevents unauthorized access to sensitive data by masking it before it is copied to a sandbox3.

Custom label (A), Patient Card ©, and Timeline (D) are components that are customizable within Health Cloud. EHR data (B) is not a component, but a type of data that can be integrated with Health Cloud. Life Events (E) is not a customizable component, but a standard object in Health Cloud.

According to the Health 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.

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.

C is correct because the dataset required needs to read two SObjects with a clearly defined relationship is a scenario where a single DataRaptor can be used. A DataRaptor Extract can query data from one or more Salesforce sObjects and their related fields using SOQL. A DataRaptor Load can save data to one or more Salesforce sObjects by creating or updating records.

References: : DataRaptor Extract : DataRaptor Load

According to the Health Cloud Implementation Guide, Householding Map is the visual representation in Health Cloud that enables a care coordinator to see all the relationships between a patient and the people and organizations participating in the patient’s care, including those across multiple care plans. Householding Map shows a graphical view of the patient’s household members, care team members, providers, and other related entities. Timeline View, Care Team, Lightning Empower Components, and Patient Card are not visual representations that show all the relationships between a patient and their care participants.

A visit is an object that represents a field rep’s trip to a retail store or a customer location to perform certain tasks, such as selling products, conducting surveys, or taking orders1. A visit can be created from a work type, which is a template that defines the key parameters and skill requirements for the visit2. A visit can also be associated with a location, which is an object that stores the address and geolocation of a place where a visit can occur3.

A consultant should configure the visit object to track the surgical case visits for reps to sell their product leveraging Intelligent Sales. This way, the reps can use the Intelligent Sales app to create and manage their visits, view their assigned tasks, scan products, and capture signatures4. The consultant can also use work types to standardize the duration, preparation, and wrap-up time for each visit type, and use locations to specify the service territories where the visits can take place.

References:

1: Visit - Salesforce 2: WorkType | Field Service Developer Guide | Salesforce Developers

According to the Salesforce documentation2, Remote Patient Monitoring is a feature in Health Cloud that enables healthcare organizations to use the data generated by connected devices used by patients to monitor their health and provide personalized care. Remote Patient Monitoring allows healthcare organizations to:

Use a meaningful subset of the data generated by connected devices to drive patient engagement and intervention. Remote Patient Monitoring helps healthcare organizations filter and prioritize the device data based on predefined rules and thresholds, and trigger actions such as alerts, tasks, or messages when certain conditions are met2.

Use the data generated by connected devices used by patients to monitor their health. Remote Patient Monitoring helps healthcare organizations collect and store the device data in Health Cloud, and display it in various views such as charts, dashboards, or reports. This helps healthcare professionals gain insights into the patients’ health status, trends, and outcomes2.

A is correct because administrators can restrict access to patient or member lists using standard Salesforce sharing settings on the list. The Patient List object has an organization-wide default sharing setting that determines the baseline access level for all users in the org. Administrators can also use sharing rules, manual sharing, or Apex managed sharing to grant additional access to specific users or groups.

B is correct because users with profile or permission sets that restrict access to an object cannot create a list using that object. Users need to have at least read access to the objects and fields that they want to use as filters or display columns in their lists. Administrators can check and modify the user’s object and field permissions from their profile or permission set.

C is incorrect because administrators cannot restrict access using HCPatientListSecurity custom setting. This custom setting is used to control the visibility of patient or member lists in the Patient List tab, not the access to the lists. Administrators can use this custom setting to specify which lists are visible to which profiles or permission sets, or hide all lists from a profile or permission set.

D is correct because when a user’s field-level security restricts access to a field used as a display column, the column does not appear in the list. This is because the field-level security settings override the list settings and prevent the user from viewing the field value. Administrators can check and modify the user’s field-level security settings from their profile or permission set.

References: : Manage Your Patient or Member Lists : Control Access to Patient or Member Lists

According to the Health 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.

Shield is a Salesforce product that allows encryption of protected health information (PHI) data at rest to enhance Health Cloud2. Shield Platform Encryption encrypts sensitive data at rest without compromising critical platform functionality. It helps you address privacy policies, regulatory requirements, and contractual obligations for data protection2.

Medication Review and Medication Reconciliation are two Health Cloud solutions that can help a company based in the United States to track medications that patients take in a standardized format and detect potential drug-to-drug interactions.

Medication Review is a Health Cloud feature that allows users to capture standardized information related to medication, such as drug name, dosage, frequency, route, and indication1. Users can also add notes and recommendations for each medication, and view the medication history of a patient1. Medication Review supports the RxNorm standard, which is a normalized naming system for generic and branded drugs in the US2.

Medication Reconciliation is a Health Cloud feature that allows users to efficiently manage and reconcile a patient’s medications list using the Patient Medication Manager lightning component3. Users can easily review the patient’s medication information, identify errors and adverse drug interactions, and add recommendations and notes, all from one place3. Medication Reconciliation also supports the RxNorm standard, and uses the National Library of Medicine API to check for drug-to-drug interactions4.

References:

1: Medication Management and Medication Review - Salesforce

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.

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 Health Cloud Implementation Guide, leveraging Person Accounts is the recommended approach to represent Members and Patients during the basic set-up of Health Cloud console for Care Coordinators and Managers. Person Accounts are a type of account that combines account and contact information in a single record. They are suitable for representing individual consumers in healthcare and life sciences. The other options are not recommended approaches to represent Members and Patients.

To implement Home Health scheduling with Health Cloud, a consultant should assign Healthcare Visit Manager permission set license to users who need to schedule visits. This permission set license grants users access to objects and fields related to home health visits, such as Service Appointment, Service Resource, Service Territory, Service Report Template, etc7. This permission set license also enables users to use Salesforce Scheduler for Health Cloud feature, which allows users to schedule home health visits based on various criteria, such as availability, location, skills, etc8. Field Dispatch Scheduler, Manage Home Health, or Execute Health Scheduling are not permission set licenses that can fulfill this scenario.

C is correct because Provider Relationship Management is a Health Cloud add-on that helps payers to recruit, credential, and onboard providers into their network. Provider Relationship Management provides features and tools that allow payers to manage provider contracts, track provider performance, monitor provider satisfaction, and streamline provider communication.

References: : Provider Relationship Management : Provider Relationship Management Implementation Guide

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 ensure compliance with HIPAA regulations, a Health Cloud feature that is essential is user authentication and access control. This feature allows Health Cloud administrators to verify the identity of users who access patient health information and assign appropriate permissions and sharing rules to limit their access to the minimum necessary2. User authentication and access control helps protect patient privacy and prevent unauthorized access or disclosure of protected health information (PHI). Real-time monitoring and alerts, social media integration, or data visualization and analytics are not features that directly help ensure HIPAA compliance.

According to the Salesforce documentation1, to install the health cloud claims unmanaged package, you need to have the health cloud managed package installed first. 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 claims unmanaged package is an extension that contains additional objects, fields, tabs, apps, components, and more that are specific to claims management1.

Salesforce Surveys is the best solution for moving existing PROMs surveys to Health Cloud. It allows for question banks and version control for this standardized survey.

A is incorrect because setting Person Accounts to Private is not a valid organization-wide default setting. Person Accounts inherit their sharing settings from Accounts and Contacts.

B is correct because setting Contact to Controlled by Parent ensures that the original business unit that leverages Service Cloud does not have visibility into protected health information (PHI) stored in Contact records. This setting means that the access level for Contact records depends on the access level for their parent Account records.

C is correct because setting related clinical objects to Controlled by Parent or Private ensures that the original business unit that leverages Service Cloud does not have visibility into protected health information (PHI) stored in clinical objects, such as Allergy, Diagnosis, Medication Order, and Procedure Order. These objects are related to either Account or Contact objects, and their sharing settings should match or be more restrictive than their parent objects.

D is incorrect because setting Health Details to Controlled by Parent or Private is not a valid organization-wide default setting. Health Details is a custom object that stores health information for patients and members. It is related to the Person Account object, and its sharing settings are controlled by its parent object.

E is correct because setting Account and Contract to Private ensures that the original business unit that leverages Service Cloud does not have visibility into protected health information (PHI) stored in Account and Contract records. This setting means that users can only access the records that they own or are explicitly shared with them.

References: : Protect Privacy in Health Cloud : Organization-Wide Default Access Settings