Salesforce Health-Cloud-Accredited-Professional Salesforce Health Cloud Accredited Professional Exam (SU24) Exam Practice Test

D is correct because Patient Provider Relationship is the standard object in Health Cloud that is used to track patient relationships to healthcare practitioners, such as cardiologist, primary care physician, and oncologist. Patient Provider Relationship represents the association between a patient and a healthcare practitioner who provides care for the patient. This object can store information such as the practitioner’s specialty, role, contact details, and relationship status.

References: : Patient Provider Relationship : Healthcare Practitioner Data Model

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

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.

Shield © is the Salesforce product that allows encryption of Protected Health Information (PHI) data at rest to enhance Health Cloud. Tableau CRM (A), Service Cloud (B), and Health Cloud (D) are not products that provide encryption capabilities.

Reference and details below.

According to the Salesforce documentation3, the following Salesforce and Health Cloud objects can be used to represent providers and their relationships in a provider management data model:

Contact: A contact is a standard object in Salesforce that stores information about an individual person, such as name, phone, email, address, etc. A contact can be used to represent a provider who is a person, such as a physician, nurse, or therapist3.

Healthcare Practitioner Facility: A healthcare practitioner facility is a custom object in Health Cloud that stores information about the relationship between a provider and a facility where they practice, such as hospital, clinic, or pharmacy. A healthcare practitioner facility can be used to track each of the different locations where a provider practices3.

Healthcare Provider: A healthcare provider is a custom object in Health Cloud that stores information about a provider who is an organization or a group of providers, such as hospital system, clinic network, or physician group3.

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.

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.

Reference and details below.

The underlying component that the consultant should customize to achieve this is OmniScript. OmniScript is a component in OmniStudio that allows the consultant to create guided scripts or wizards for users to follow. OmniScript can be used to create the Care Plan creation wizard, and it can be customized using various elements, such as steps, prompts, inputs, outputs, and actions.

According to the Health Cloud Implementation Guide, the recommended best practice for modeling members in Health Cloud for a payer service cloud org that uses accounts and contacts to model health insurance members is to model them as person accounts, whether they are using Health Cloud capabilities or not. 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. Using person accounts for all members can simplify data management and avoid data duplication. Only groups needing Health Cloud capabilities need to use person accounts is not a recommended best practice, as it can create inconsistency and complexity in data modeling. Account record types for existing members can remain as-is is not a recommended best practice, as it can limit the functionality and integration of Health Cloud features. Using the individual model with Health Cloud is not a valid option, as the individual model is not supported by Health Cloud.

Record Alerts can be used to inform agents about changes in information, such as a change in address or phone number. Record Alerts display a banner on the record page with a custom message and an optional link to another record or URL.

Action Launcher can be used to view basic details about a patient’s insurance, such as the plan name, coverage type, and eligibility status. Action Launcher displays a FlexCard component that shows key information from a related record or external data source.

Timeline can be used to have a complete view of all engagement interactions in one place, such as calls, emails, tasks, and events. Timeline displays a chronological list of past and upcoming activities related to the record.

References: : Record Alerts : Action Launcher : Timeline

The FHIR R4 Patient API is a Health Cloud feature that allows users to create, update, and query patient data in Salesforce using the Fast Healthcare Interoperability Resources (FHIR) standard1. FHIR is a widely adopted standard for exchanging healthcare information electronically2. By using the FHIR R4 Patient API, Bloomington Caregivers can make their patient clinical data available to the external payer in a cost-effective and interoperable way, without requiring any custom development or third-party tools. The FHIR R4 Patient API supports the US Core Patient profile, which defines the minimum set of data elements for exchanging patient information3.

References:

1: FHIR Patient Input | Salesforce Health Cloud Developer Guide | Salesforce Developers 

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.

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.

 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.

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.

 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.

According to the [Intelligent Sales for Medical Devices Implementation Guide], to set up a warehouse that serves as a product fulfillment location to salesforce representatives in a specific region, irrespective of the account, a salesforce administrator should complete the following steps:

Create Inventory Location and add Visitor Address as Location Address. This step creates a record for the warehouse location and associates it with a visitor address.

Create Record in Product Fulfillment Location. This step defines the product fulfillment location for the inventory location and assigns it to a specific region.

Create a product item entry inventory, a single entry for each product that will be replenished from industry. This step adds the products that will be available in the warehouse location and specifies their quantity and expiration date. Setting up Product Transfer and Product Request are not required steps for setting up a warehouse location. Selecting inventory location while creating visit is not a step for setting up a warehouse location, but for creating a visit record.

To launch a patient portal with contact tracing functionality as part of its Health Cloud implementation, a consultant should recommend Experience Cloud for Health Cloud license for the external patient users. This license allows patients to access an Experience Cloud site that is integrated with Health Cloud and provides features such as self-service appointment scheduling, provider search, contact tracing surveys, chat support, and more7. Experience Cloud for Health Cloud license also supports advanced sharing and customizable dashboards for patient users8. External Apps for Health Cloud, Customer Community for Health Cloud, or Customer Community Plus for Health Cloud are not licenses that can fulfill this requirement.

The approach that a consultant should use to set up this integration is a middleware integration solution that can handle data transformation if necessary. A middleware integration solution is a software layer that connects different systems and applications and facilitates data exchange between them. A middleware integration solution can also perform data transformation, which is the process of converting data from one format or structure to another. This is useful when the source system and the target system have different data models or standards.

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.

Reference and details below.

According to the Salesforce documentation3, there are two ways to support the health department so that the team can efficiently assess the individual, enroll them in a program, and monitor them during emergency:

Install Emergency Response Management unmanaged package, which provides prebuilt objects, fields, apps, tabs, reports, dashboards, and more to help health organizations manage emergency response3.

Leverage pre-configured flows provided with Health Cloud, such as Assess Individual Risk Level flow and Enroll in Program flow, which help health workers quickly assess and enroll individuals in emergency programs3. Therefore, options B and C are correct. Option A is incorrect, because there is no such thing as a healthcare provider enrollment flow in Health Cloud. Option D is incorrect, because there is no such thing as a patient enrollment console in Health Cloud.

Expression Set Templates are the prebuilt feature that the payer should leverage to implement predefined rules for its prior authorization request review process. Expression Set Templates are reusable sets of expressions that can be used to evaluate business logic and trigger actions based on the results.

The best approach is to define a PGI Library and care plan templates using the library. This will enable the care coordinators to track PGIs in a standardized way, and also leverage best practices and evidence-based guidelines.

According to the Salesforce documentation2, the following standard objects are used in the workflow to manage utilization data:

Care Request Plan: A care request plan is an object that stores information about the plan of care for a member. It includes details such as the diagnosis, the service type, the start and end dates, and the status of the plan2.

Care Authorization: A care authorization is an object that stores information about the approval or denial of a service or payment by a payer. It includes details such as the authorization number, the decision date, the decision reason, and the status of the authorization2.

Care Request: A care request is an object that stores information about the request for a service or payment by a provider or a member. It includes details such as the request type, the request date, the priority, and the status of the request2.

To extend the reporting capability of Health Cloud, a consultant should recommend CRM Analytics for Health Cloud. This is a feature that provides pre-built dashboards and reports that help users analyze various aspects of health care delivery, such as care plan adherence, patient outcomes, referral management, network performance, and more12. CRM Analytics for Health Cloud also allows users to customize and create their own dashboards and reports based on their specific needs13. Care Management Extension, Insights for Health Cloud, or Reporting unmanaged package are not features that can extend the reporting capability of Health Cloud.

HL7v2 and FHIR R4 are two data exchange standards that support clinical data in Health Cloud. HL7v2 is a widely used standard for exchanging healthcare information electronically, such as patient demographics, orders, results, and billing1. FHIR R4 is the latest version of the Fast Healthcare Interoperability Resources standard, which defines a set of resources for representing and sharing healthcare data in a granular and interoperable way2. Health Cloud supports both HL7v2 and FHIR R4 data exchange through its Clinical Data Model, which maps various FHIR resources to Salesforce standard objects3.

References:

1: Review the Data Exchange Standards Unit | Salesforce Trailhead 2: FHIR R4 Support for Better Interoperability - Salesforce 3: Mapping FHIR v4.0 to Salesforce Standard Objects | Salesforce Health …

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.

According to the Health Cloud Data Model Developer Guide, Case is the Salesforce object that is used to model a Care Plan. Case is a standard object that represents an issue or request that requires resolution or action. Cases can be used to model care plans by adding custom fields and related objects such as problems, goals, tasks, and timeline events. Account, Lead, Opportunity, and Task are not objects that are used to model a Care Plan.

The three key considerations when complying with HIPAA regulations using Salesforce Shield in conjunction with Bloomington Caregivers’ data strategy are ensuring that sensitive data is encrypted both in transit and at rest, configuring data retention policies to ensure that records are retained for the appropriate length of time, and implementing audit trails and regularly reviewing them to detect unauthorized access attempts. Salesforce Shield provides these features as part of its platform encryption, event monitoring, and field audit trail capabilities.

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.

To solve the use case of creating a new order and displaying available products for purchase, a developer should leverage the following OmniStudio capabilities:

OmniScript: This is a capability that allows developers to create guided flows that capture user inputs and execute business logic. OmniScript can be used to create a process that builds a new order based on customer data and product selection9.

FlexCards: This is a capability that allows developers to create reusable UI components that display data from various sources. FlexCards can be used to create a component that shows customer data and contains a link to start the OmniScript flow10.

Document Generation: This is a capability that allows developers to create documents based on templates and data from various sources. Document Generation can be used to create an order confirmation document that shows the details of the order and products purchased11. DataRaptors or Integration Procedures are not required capabilities for this use case.

According to the Health Cloud Implementation Guide, the two steps that need to be taken during the set-up process for Utilization Management are:

Install the Health Cloud Care Request Extensions unmanaged package. This package contains custom objects, fields, layouts, tabs, and components for Utilization Management.

Assign the Health Cloud Permission Set License and the Health Cloud Platform Permission Set License to Salesforce Lightning users. These licenses enable access to Health Cloud features and functionalities for Lightning Experience. Assigning the Health Cloud Permission Set License and Health Cloud Platform Permission Set License to Salesforce Classic users is not necessary for Utilization Management. Installing the Utilization Management Extensions is not a valid step for Utilization Management.

Reference and details below.

According to the Health Cloud Implementation Guide, the best practice when transitioning an org from Service Cloud to Health Cloud is to approach it depending on how each customer uses their org. There is no one-size-fits-all solution for migrating from Service Cloud to Health Cloud, as each customer may have different requirements, use cases, and data models. Therefore, any of the other options may be used depending on the customer’s needs and preferences.

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.

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.

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

According to the Salesforce documentation3, to leverage the health cloud utilization management capabilities, you need to install the health cloud managed package and the health cloud care request extensions managed package. 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 care request extensions managed package contains additional objects, fields, tabs, apps, components, and more that are specific to utilization management3.

Reference and details below.

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 request reviews (B), Care request drug ©, and Care request diagnosis (D) are three types of ancillary information that can be included in a single care request. Care request providers (A) and Care request facility (E) are not types of ancillary information, but types of related records that can be associated with a care request.

To show end users highlighted information about providers that work at specific facilities, a consultant should implement the Provider Relationship Card feature. This feature allows end users to view information such as provider name, contact details, specialty, role, facility name, and relationship status on a card-like interface on the Facility record page. Provider Network Management, Facility Relationship Center, or HCProvider360 FlexCard are not features that can fulfill this requirement.

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.

Reference and details below.

Graphical user interface, text, application Description automatically generated

According to the Health Cloud Data Model Developer Guide, Program Management is a feature in Health Cloud that allows life science companies to track and manage care programs that offer products and services to patients and providers. With Program Management, life science companies can track the following three items about a care program:

The multiple marketing campaigns that enrollees are subjected to as part of the care program. This item can be tracked by using the CareProgramEnrolleeCampaign object, which represents a marketing campaign that targets a specific care program enrollee.

The products that are associated with a given care program. This item can be tracked by using the CareProgramEnrolleeProduct object, which represents a product or service that is offered to a care program enrollee.

The plans that enrollees have been engaged in as part of the care program. This item can be tracked by using the CareProgramEnrolleePlan object, which represents a plan or package that contains one or more products or services for a care program enrollee. The budget and expenses of the company’s associated care program is not an item that can be tracked by using Program Management. The clinical indicators that need to be monitored in the care programs is not an item that can be tracked by using Program Management.

 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 Salesforce documentation3, when setting up a new care request record, you need to choose a case record type to identify the care request type. The care request type determines what fields and values are available on the care request record. There are four predefined care request types in Health Cloud: Physician Request, Drug Request, Admission Request, and Appeal Request. You can also create custom care request types to suit your business needs3.

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.

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

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

The developer should add a Conditional Block to the existing Create Appointment Integration Procedure to solve the request. A Conditional Block is a component in OmniStudio that allows the developer to define conditional logic based on input values or variables. A Conditional Block can be used to check if the provider has moved to a new location, and if so, send an email with the new address to the patient.

The Advanced Patient Card is a Health Cloud capability that allows users to view and navigate to critical information on a patient’s profile, such as insurance, clinical, and primary care physician information1. The Advanced Patient Card is a customizable component that can be added to the Health Cloud console or the Contact Center app2. It can also display data from external sources, such as EHR systems or medical devices3.

References:

1: Use the Advanced Patient Card - Salesforce 2: Configure the Person Account Page Layout for Contact Center - Salesforce 3: Display Data from External Sources in the Advanced Patient Card - Salesforce

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 documentation1, consent documents are files that capture the enrollee’s consent to participate in a care program. Consent documents can be uploaded as PDF, DOC, DOCX, or JPG files in secure folders of Health Cloud for a care program. The file size limit for consent documents is 2 MB1. Therefore, options C and D are correct. Option A is incorrect, because copy-protected PDF files cannot be uploaded as consent documents. Option B is incorrect, because opt out consent documents are not used to enroll in a care program, but to withdraw from it. Option E is incorrect, because password protected files cannot be uploaded as consent documents.

Reference and details below.

 According to the Salesforce documentation3, there are two ways to restrict access to an entire patient/member list or to specific columns of that list:

Sharing setting: Sharing settings control the access level that users have to records owned by other users. You can use sharing settings to grant or restrict access to an entire list of records based on criteria such as role hierarchy, public groups, or manual sharing3.

Field Level Security: Field level security controls the access level that users have to individual fields within a record. You can use field level security to grant or restrict access to specific columns of a list based on profiles or permission sets3.

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

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

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.

To set up care requests, you need to do the following steps3:

Install the Utilization Management unmanaged package for Health Cloud and assign the Health Cloud Utilization Management permission set to users along with Health Cloud permission set licenses.

Create a new case record type for each care request type.

Choose the Case Care Request record type for each care request configuration.

Reference and details below.

Deterministic encryption is a type of encryption policy that allows you to encrypt fields that are used as search criteria, such as FirstName and LastName fields on the Account object. Deterministic encryption ensures that identical plaintext values always result in identical ciphertext values, which enables searching and filtering on encrypted fields. This is suitable for PHI data that needs to be encrypted at rest but also searchable by users.

To help streamline caller authentication for Contact Center agents, a consultant should recommend Bloomington Caregivers use the Identity Verification Flow Templates feature in Health Cloud. This feature allows agents to launch a flow from the utility bar or a record page to verify a caller’s identity before processing their requests involving sensitive information. The flow prompts the agent to search for the caller in Health Cloud, select a reason for the call, ask verification questions based on predefined rules, and capture engagement details8. Customer Identity OmniScript Templates, Reusable Verification FlexCards, or Verify Customer Identity Process Flow are not features that exist in Health Cloud.

B is correct because giving the site user profile Read access to the Care Provider Searchable Field object is a change that allows an external user to access search results. The Care Provider Searchable Field object stores the searchable data for Provider Search, and users need to have Read access to this object and its fields to perform searches and view results.

D is correct because using Experience Builder to add the Provider Search component to a page on the site is a change that allows an external user to access search results. The Provider Search component is a Lightning web component that enables users to search for providers by various criteria and view their details. Administrators can use Experience Builder to drag and drop the Provider Search component onto any page on their site.

References: : Set Up Data for Provider Search : Let Site Users Search for Providers

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.

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.

The feature that the consultant should configure to leverage dependent intervention tasks as part of their care coordination solution using Integrated Care Management is Action Plan Templates. Action Plan Templates are reusable sets of tasks that can be assigned to patients or members based on their care needs. Action Plan Templates can include dependent tasks that are triggered by the completion of other tasks.

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

 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.