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

SourceSystemIdentifier is a custom object in Health Cloud that stores the business identifier for patient records from external systems like EHRs3. Option B is incorrect, because Contact is a standard object in Salesforce that stores the personal information of patients or members. Option C is incorrect, because Account is a standard object in Salesforce that stores the organizational information of providers or payers. Option D is incorrect, because Identifier is a field on the EhrPatient object in Health Cloud that stores the unique identifier for patient records within Health Cloud3.

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.

Utilization Management is the capability in Health Cloud that helps the payer accomplish its goal of balancing quality care and managing the cost of care effectively. It enables the payer to streamline its approval processes for care requests using predefined rules and workflows.

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

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.

According to the Salesforce website, Health Cloud solves for some of the common challenges that healthcare companies face from various sources. Some of these challenges are:

The need to drive sales while reducing cost: Health Cloud helps healthcare companies increase their revenue and efficiency by streamlining their processes, automating their workflows, and optimizing their resources.

Growing customer expectations for delivery of care everywhere: Health Cloud helps healthcare companies deliver personalized and collaborative care across every touchpoint, whether it is in person, online, or on mobile devices.

Growing demand for a more personalized care experience: Health Cloud helps healthcare companies provide tailored and holistic care for each customer by leveraging data insights, artificial intelligence, and digital engagement tools.

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.

Some entities have additional non-FHIR attributes to increase the usability of the data within Salesforce (A), the cardinality of a few attributes has been changed (e.g. in picklist scenarios) (B), and not all attributes in a given FHIR resource may be supported © are three options that explain why the new clinical data model in Health Cloud is labeled as FHIR aligned and not FHIR compliant. It does utilize the latest FHIR R4 standards (D), so this is not a reason for being FHIR aligned. It aligns with both FHIR DSTU2 and FHIR R4 specs (E), so this is not a reason for being FHIR aligned either.

According to the Salesforce documentation, Patient Immunization is an object in Health Cloud that is used to store the details of a vaccine being administered. It includes information such as the vaccine name, lot number, manufacturer, route of administration, site of administration, dose quantity, dose unit, expiration date, and adverse reaction.

According to the Salesforce documentation, there are three steps that should be followed when setting up Intelligent Sales in Health Cloud:

Enable Intelligent Sales: This step allows you to turn on the Intelligent Sales feature in Health Cloud and configure some settings such as default visit duration, visit report template, and visit report email template.

Set up permission set for Intelligent Sales: This step allows you to assign the appropriate permission sets to users who need access to Intelligent Sales features such as visit management, product catalog, order authorization, and inventory management.

Set Visit Inventory Management to enabled: This step allows you to enable the inventory management feature in Health Cloud and configure some settings such as default inventory location, default inventory transfer status, and default order authorization status.

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.

Mulesoft Accelerator for Healthcare (A) is the solution that includes pre-built APIs, connectors, implementation templates, and a prescriptive end-to-end reference architecture to enable EHR connectivity and power a patient 360 from any EHR into Health Cloud using HL7 V2 or FHIR standards. Shield (B) is a solution that provides encryption and auditing capabilities for data security. Specialty vendors © are not a solution, but a type of external partners that can provide integration services. Tableau CRM for Healthcare (D) is a solution that provides analytics and insights for healthcare data.

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

 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.

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.

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

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.

Reference and details below.

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

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.

To drive performance and scalability for Provider Search, a consultant should leverage the Data Processing Engine tool in Health Cloud. This tool allows pharma companies to map and transform the source data from the Provider Data Model into a searchable object called Care Provider Searchable Field. The Data Processing Engine also syncs the data with the Care Provider Searchable Field object once a day or manually as needed12. This process reduces the search time and improves the accuracy of the results. Flow for Industries, Pipeline Analytics, or Business Rules Engine are not tools that can fulfill this requirement.

 FHIRR4 is the industry data standard that a consultant should use with Health Cloud. FHIRR4 stands for Fast Healthcare Interoperability Resources Release 4, and it is a standard for exchanging healthcare information electronically. FHIRR4 enables interoperability between different systems and applications, and supports a variety of use cases, such as clinical, administrative, and financial.

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.

According to the [Health Cloud Integration and Interoperability Guide], the new clinical data model in Health Cloud is aligned with FHIR R4 standards, which is the latest version of the FHIR specification. Health Cloud supports data exchange with both HL7 and FHIR enabled systems, using different methods such as MuleSoft connectors, Salesforce APIs, or third-party integrations. Most EHR data exchange today is still done via legacy HL7 v2 – simple application interface, which is a widely adopted standard for exchanging clinical and administrative data. Health Cloud does not have a FHIR server, but it can connect to external FHIR servers using APIs or MuleSoft connectors. The new clinical data model in Health Cloud is not aligned with HL7 v2-simple application standard, which is a different standard from FHIR.

Health Cloud helps HLS organizations achieve HIPAA compliance (A), Health Cloud is HITRUST certified ©, and Health Cloud is GDPR certified (D) are three ways that Health Cloud meets compliance and regulatory requirements. Health Cloud is not HIPAA certified (B), as HIPAA certification does not exist. Health Cloud is not HL-7 compliant (E), as HL-7 is a standard for exchanging health information, not a compliance requirement.

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

To enable agents to answer questions from members regarding their benefits coverage, a consultant should recommend the Benefits Coverage component for the Member record page. This component displays information such as plan name, effective date, termination date, deductible amount, coinsurance percentage, copay amount, and out-of-pocket maximum for each benefit plan that the member is enrolled in. Benefits Verification, Eligibility Validation, or Coverage Confirmation are not components that exist in Health Cloud.

To get a patient’s allergy information from Bloomington Caregivers’ Health Cloud system, an external provider should use the Interoperability API. This API allows external systems to access and exchange clinical data with Health Cloud using FHIR standards. The Interoperability API supports various FHIR resources, including AllergyIntolerance, which represents a patient’s allergic or intolerant reaction to a substance1. AllergyMedication API, Patient Healthcare API, or Clinical Summary Healthcare API are not APIs that exist in Health Cloud.

FlexCards are Health Cloud features that allow users to view and navigate to critical information on a patient’s profile, such as insurance, clinical, and primary care physician information1. FlexCards can also display data from external sources, such as EHR systems or medical devices2.

Integration Procedures are OmniStudio features that enable users to read and write data from Salesforce and from external systems3. An Integration Procedure can be called from an OmniStudio component such as an OmniScript or FlexCard, an API, or even from an Apex method3.

DataRaptors are OmniStudio features that allow users to read, transform, and write Salesforce data4. DataRaptors can also trim, map, restructure, and transform data in JSON, XML, or Custom Schema4.

These three features can be used together to display patient information from both Salesforce standard objects and data from an external system on the patient record page. For example, a FlexCard can call an Integration Procedure that uses a DataRaptor to query and transform the data from both sources, and then display the data on the FlexCard component.

References:

1: Use the Advanced Patient Card - Salesforce 2: Display Data from External Sources in the Advanced Patient Card - Salesforce 3: Get Started with OmniStudio Integration Procedures - Trailhead 4: Discover DataRaptor Types - Trailhead

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]

The Healthcare Practitioner Facility object is used to model a physician’s locations of service, such as clinics or hospitals. It stores information about the facility name, address, phone number, and type.

The set of Health Cloud capabilities that should enable the company to build this business process are Intelligent Document Automation, Intelligent Appointment Management, Intelligent Document Reader, and Benefits Verification. Intelligent Document Automation allows the company to upload a patient’s insurance card and automatically create a Member Plan record. Intelligent Appointment Management allows the company to schedule on behalf of the patient with a provider. Intelligent Document Reader allows the company to extract data from the insurance card and populate the Member Plan fields. Benefits Verification allows the company to run a benefits verification check using a third-party service.

To enable care providers to conduct video visits with patients and capture socioeconomic factors that impact their care, a consultant should recommend the Telehealth capability in Health Cloud. Telehealth allows care providers to connect with patients through video calls, chat messages, and surveys within Health Cloud. Telehealth also enables care providers to collect and analyze social determinants of health (SDOH) data from patients using assessments and surveys3. Telehealth helps improve patient engagement, satisfaction, and outcomes by providing convenient and personalized care. Integrated Care Management, Intelligent Appointment Management, or Virtual Care are not capabilities that can fulfill this use case.

Reference and details below.

According to the Health Cloud Data Model Developer Guide, Risk scores are only recalculated for patients who are affiliated with a care program is the most likely reason why recalculation score for the patient is not displaying. Risk scores are calculated based on CMS-HCC (Centers for Medicare & Medicaid Services - Hierarchical Condition Categories) model, which assigns risk factors to patients based on their diagnoses and demographic factors. Risk scores are used to adjust payments for health plans and providers. Risk scores are only recalculated when the recalculate flag is set to TRUE and the patient is affiliated with a care program. Using CMS recalculation API is not a valid reason, as CMS recalculation API is not a feature of Health Cloud. CMS scores cannot be recalculated in health cloud is not a valid reason, as CMS scores can be recalculated in health cloud by setting the recalculate flag to TRUE. Using a third party API to recalculate CMS risk score is not a valid reason, as it has nothing to do with displaying the recalculation score.

According to the [Health Cloud Implementation Guide], the three actions that are possible in the program enrollment flow when adding in ‘Enroll in Program’ quick action to a record are:

Starting a new blank care plan. This action allows you to create a new care plan for the patient based on their needs and goals.

Signing enrollment consent form. This action allows you to capture the patient’s consent for enrolling in a program using an e-signature tool.

Selecting the provider associated with a product. This action allows you to choose the provider who will deliver the product or service to the patient as part of the program. Seeing a list of all products and selecting applicable products is not an action in the program enrollment flow. Creating a new care program is not an action in the program enrollment flow.

A is correct because barcode scanning is a capability that can be leveraged with Health Cloud out-of-the-box using Intelligent Document Automation (IDA). IDA can scan and extract data from barcodes on documents, such as patient wristbands, lab reports, or medication labels.

B is correct because record type association is a capability that can be leveraged with Health Cloud out-of-the-box using IDA. IDA can associate a document with a specific record type based on the document type, such as consent form, referral letter, or discharge summary.

C is incorrect because eFax connection is not a capability that can be leveraged with Health Cloud out-of-the-box using IDA. IDA does not support receiving or sending documents via eFax. However, it is possible to integrate IDA with third-party eFax services using custom code or connectors.

D is correct because automated document checklist item creation is a capability that can be leveraged with Health Cloud out-of-the-box using IDA. IDA can create document checklist items for documents that are received and processed, and update their status based on the document processing stage.

References: : Intelligent Document Automation : Intelligent Document Automation for Healthcare

B is correct because if a user cannot access a field used in a filter on a patient or member list, they will not be able to see the list. This is because the filter criteria are applied to the user’s query, and if the user does not have permission to view the field, the query will return no results. To avoid this issue, the administrator should ensure that the user has the appropriate field-level security settings for the fields used in the filter.

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

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.

According to the Salesforce documentation, care programs and care plans are different concepts in Health Cloud:

Care programs track a patient’s overall health journey from enrollment to completion. They provide guidance and support for patients to proactively manage their health by increasing their adherence to treatment plans.

Care plans are practical, actionable steps to support the health of a patient. They break health problems down into doable, trackable actions. They serve as the source of truth for all the individuals involved in the care of a patient. Therefore, option A is correct. Option B is incorrect, because both care programs and care plans can be exposed in a community. Option C is incorrect, because both care programs and care plans can be used by providers, payers, and life sciences companies. Option D is incorrect, because care programs are not a different type of care plan, but a separate object in Health Cloud. Option E is incorrect, because care programs are not an extension of care plans, but a related object in Health Cloud.

C is correct because Integration Procedures are components that can be used to update an existing field on a custom SObject. Integration Procedures are reusable processes that can perform various actions on data, such as reading, writing, transforming, or validating. Integration Procedures can be invoked from an OmniScript or a DataRaptor, and can accept input parameters and return output values.

D is correct because DataRaptors are components that can be used to update an existing field on a custom SObject. DataRaptors are data transformation tools that can extract, load, or transform data from any Salesforce object or external data source. DataRaptors can be invoked from an OmniScript or an Integration Procedure, and can accept input parameters and return output values.

References: : Integration Procedure : DataRaptor

The FHIR-Aligned Data Model org preference is the preference that Bloomington Caregivers’ administrator should ensure is enabled to use the objects for the Clinical data model as part of its new Health Cloud implementation. This preference enables the Clinical data model, which is a FHIR R4-aligned data model that captures information from an Electronic Health Record (EHR) system via integration middleware1. The Clinical data model is built on Salesforce core, with no reference to package entities, and supports only the attributes that Health Cloud users need, not all attributes in every FHIR R4 resource2. The Clinical data model is the successor to the original EHR Data Model, which was built on the managed package and followed the FHIR R1 standard2.

References:

1: Clinical Data Model | Salesforce Health Cloud Developer Guide | Salesforce Developers 2: Explore the Clinical Data Model Unit | Salesforce Trailhead

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

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

According to the Salesforce website, The Social Determinants feature in Health Cloud helps providers perform the following activities:

Integrate services such as transportation and meal delivery into their patient care plans and programs. The Social Determinants feature allows providers to connect patients with community resources that can help them overcome nonclinical barriers to care, such as lack of transportation, food insecurity, or social isolation.

Track determinants and barriers to care across their patient populations. The Social Determinants feature allows providers to collect and analyze data on various social factors that affect patients’ health outcomes, such as income, education, housing, or environment.

Plan interventions to help address the barriers to care within their patient populations. The Social Determinants feature allows providers to create and manage action plans that target specific social needs of patients and measure their impact on health indicators.

Reference and details below.

D is correct because Identity Verification Parameter Item is the record that defines the search parameters for identity verification. A consultant can create and configure Identity Verification Parameter Items to add new search parameters or modify existing ones.

References: : Identity Verification Parameter Item : Create a Flow Using the Verify Customer Identity V2 Flow Template

According to the Salesforce documentation1, the Timeline View Configuration is a custom metadata type that defines the appearance and behavior of a timeline in Health Cloud. Each timeline has its own Timeline View Configuration record, which can be accessed and edited from the Health Cloud - Lightning Admin app2. One of the settings that can be changed in the Timeline View Configuration is the Orientation, which controls whether the timeline is displayed horizontally or vertically1. Therefore, to alter the appearance of the timeline so that it displays vertically instead of horizontally, the administrator should find the Timeline View Configuration for each relevant timeline in the Health Cloud - Lightning Admin app and change the Orientation to vertical.

According to the Salesforce documentation, a healthcare facility network is a custom object in Health Cloud that stores information about a network of facilities that are affiliated with each other, such as hospital system, clinic network, or pharmacy chain. A healthcare facility network can be used to track each of the different networks where a provider is affiliated.

Health Cloud does not have a built-in HL7 integration engine, so option A is incorrect. Option B is also incorrect, because Health Cloud does not have prebuilt connections for any EMRs. Option C is incorrect, because there is no such lightning component button automatically configured to export to EMR. Option D is correct, because Health Cloud provides data mappings from commonly used HL7 messages (such as ADT, ORU, and RDE) to the Health Cloud data model, which can help developers and integrators map the data from external systems to Health Cloud objects and fields12.

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.

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.

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.

 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.

The set of objects that the consultant should implement to meet the pharma company’s requirements are Account, Purchaser Plan, Plan Benefit, and Member Plan. These objects are part of the Health Cloud data model and allow the company to track payer organizations, plans, benefits, and patient enrollments.

Medication Management is a Health Cloud add-on product that helps providers and care coordinators manage the medication regimen of their patients, helping to improve patient safety and reduce healthcare costs1. One of the features of Medication Management is the ability to perform medication reconciliation of patients’ medication list and detect potential drug-to-drug interactions1. This feature can help Bloomington Caregivers to view and address any medication issues for their patients and make recommendations based on the data within Health Cloud.

References:

1: Medication Management | Health Cloud Administration | Salesforce Developers

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

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

To modify the out-of-the-box Advanced Patient Card to display the Category, SubjectID, and Date for active Clinical Alerts, a developer should take the following steps:

Create and activate a new child card: This step allows the developer to create a custom card that inherits the properties of the parent card and displays additional information from Clinical Alerts object4.

Create a DataRaptor to extract necessary data: This step allows the developer to create a DataRaptor Extract that queries the Clinical Alerts object and returns the Category, SubjectID, and Date fields for active records5.

Change the child card state to show active: This step allows the developer to change the state of the child card from inactive to active, so that it is visible on the Advanced Patient Card component6. Cloning the parent card, defining session variables, or creating an Integration Procedure are not required steps for this task.

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.

D is correct because leveraging Person Account is the recommended way to model a patient in Health Cloud. A Person Account is a special type of account that combines the attributes of an account and a contact. It allows users to store information about individual people, such as name, address, phone number, email, and health details. Health Cloud uses Person Accounts to represent patients and members, and to enable various features and functionality, such as household data model, clinical data model, care management, and provider network management.

References: : Health Cloud Data Models for Healthcare : Take a Look at the Household Data Model

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.

 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.

To identify pain points and define project requirements for setting up a Contact Center leveraging Health Cloud, a consultant should work with the following group of people:

(Persona) Contact Center agent: This is the end user who interacts with patients through phone calls, emails, chats, or other channels. The Contact Center agent needs to have access to patient information, appointment scheduling, billing inquiries, plan updates, and other tasks in Health Cloud. The consultant should work with the Contact Center agent to understand their needs, challenges, and expectations from the system.

(Stakeholder) Salesforce administrator: This is the person who configures and maintains the Health Cloud system for the Contact Center. The Salesforce administrator needs to set up user profiles, permissions, page layouts, workflows, reports, dashboards, and other features in Health Cloud. The consultant should work with the Salesforce administrator to understand the technical requirements, limitations, and best practices for setting up the system.

(Stakeholder) Integration architect: This is the person who designs and implements the integration between Health Cloud and other external systems, such as EHRs, billing systems, or third-party applications. The integration architect needs to ensure that data is exchanged securely and accurately between Health Cloud and other systems. The consultant should work with the integration architect to understand the integration requirements, challenges, and solutions for the system. General physician, Marketing Cloud administrator, Care coordinator, Tableau developer or MuleSoft developer are not relevant people for this use case.

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.