While running user acceptance testing (UAT) for a customer, an end user is unable to view certain
data on the Enhanced Timeline for Contact Center.
What should be the first step in troubleshooting this issue?
A
A provider wants to set up a Contact Center leveraging Health Cloud to enable its patients to set up
appointments, get answers to their billing questions, and update their plan information.
Which group of people should a consultant work with to identify pain points and define project
requirements?
A
Explanation:
Step-by-Step
Understanding the Scenario:
The provider aims to build a Contact Center using Health Cloud for patients to:
Set up appointments
Get billing answers
Update plan information
Salesforce’s Best Practices for Requirements Gathering:
Salesforce Health Cloud documentation emphasizes collaborating with end users and technical
stakeholders to uncover pain points and define requirements.
Extract from Health Cloud Admin Guide:
“Successful Health Cloud projects start with workshops that bring together key personas, such as
contact center agents and care coordinators, with technical stakeholders including Salesforce admins
and integration architects. These sessions surface pain points, business needs, and integration
requirements.”
— Reference: Administer Health Cloud – Implementation Best Practices
Who Should Be Involved?
Contact Center agent (Persona):
Directly understands patient needs and pain points during calls and chats.
Can highlight workflow, usability, and feature needs.
Salesforce administrator (Stakeholder):
Understands platform capabilities, permissions, and how features will be implemented or
configured.
Integration architect (Stakeholder):
Critical for connecting Health Cloud to other systems (e.g., EHR, billing, insurance).
Ensures technical feasibility for integrations (e.g., real-time eligibility checks, appointment
scheduling with external systems).
Why Other Answers Are Not Correct:
B: General physician and Marketing Cloud admin are not core to Contact Center workflows or
technical design for scheduling/billing.
C: Sales administrator and Tableau developer focus on sales or analytics, not operational or
integration workflows for Contact Centers.
D: Tableau developer and MuleSoft developer are more technical roles but not typically involved in
initial workflow and requirements gathering at the Contact Center user level.
Official Document Extract:
From Salesforce Implementation Guides:
“It is essential to involve actual end users (such as agents) and platform administrators in
requirements workshops, and to include an integration architect for designing connected
experiences.”
— Reference: Administer Health Cloud – Implementation Best Practices
Reference:
Administer Health Cloud – Implementation Best Practices
A pharma company is implementing Health Cloud and trying to track insurance details related to its
patients. The company wants to track:
A list of all payer organizations
The plans offered by a given payer
The standard benefits available under a plan
Which plan a given patient is enrolled in and their specific insurance details
Which set of objects should a consultant implement to meet these requirements?
C
While working with a received document using Intelligent Document Automation, which three
capabilities should a consultant leverage with Health Cloud out-of-the-box?
Choose 3 answers
A, C, D
Explanation:
Step-by-Step
Health Cloud Intelligent Document Automation (IDA) Capabilities:
IDA automates processing of incoming documents (like insurance cards or clinical records).
Out-of-the-box features allow:
Document Rotation: For correcting the orientation of scanned/received documents.
Record Type Association: For matching documents to appropriate Salesforce record types (such as
associating a document with a Patient or Encounter).
Automated Document Checklist Item Creation: Automatically creating checklist items for actions
(e.g., missing forms or needed verifications).
Supported and Unsupported Features:
Barcode Scanning: Not an out-of-the-box feature of Health Cloud IDA (may require third-party
solutions).
eFax Connection: While Health Cloud supports document management, direct eFax integration is not
out-of-the-box.
Official Document Extracts:
From Salesforce Help:
“You can rotate, associate, and automate checklist items for documents received in Health Cloud
using Intelligent Document Automation.”
— Administer Health Cloud – Document Automation
Reference:
Intelligent Document Automation Overview
Bloomington Caregivers is implementing Home Health scheduling with Health Cloud. It must ensure
that those who need to schedule the visits have the right permission set license.
Which permission set license should a consultant assign in this scenario?
B
A consultant is preparing to install Health Cloud in a production org for the first time.
Which three tasks should the consultant ensure are completed prior to installing Health Cloud?
Choose 3 answers
A, C, E
Explanation:
Step-by-Step
Salesforce Health Cloud Prerequisites:
Enable Person Accounts:
Required for representing patients and healthcare contacts.
“Person Accounts must be enabled before installing Health Cloud.”
— Reference: Health Cloud Installation Prerequisites
Enable Chatter:
Health Cloud uses Chatter for collaboration between care teams.
“Chatter must be enabled to use Health Cloud features like care coordination and notes.”
— Reference: Health Cloud Installation Prerequisites
Enable Contacts to Multiple Accounts:
Necessary to relate patients to multiple organizations/providers.
“Enable Contacts to Multiple Accounts to relate contacts (patients) to more than one account (e.g.,
provider, payer).”
— Reference: Health Cloud Installation Prerequisites
Other Options:
B . Enable Shield Event Monitoring: Not required for Health Cloud installation (but is a best practice
for auditing and compliance in some orgs).
D . Enable Health Cloud Installation Monitor: Not a standard Salesforce setting or prerequisite.
Reference:
Health Cloud Installation Prerequisites
Bloomington Caregivers is implementing Health Cloud for managing the healthcare data of children
under the age of 13.
Which three considerations should the company take into account to ensure compliance with the
Children's Online Privacy Protection Act (COPPA)?
Choose 3 answers
A, B, C
Explanation:
Step-by-Step
COPPA Requirements in Healthcare Applications:
Disclose privacy policy and obtain parental consent:
“Organizations must provide clear privacy notices to parents and obtain their consent before
collecting any personal information from children under 13.”
— Reference: Salesforce Security Guide, COPPA Compliance
Obtain verified parental consent before collection/storage:
“Verified parental consent is a core requirement for COPPA, prior to collection and storage of
children’s personal data.”
Implement security measures:
“Appropriate security controls and safeguards must be in place to protect children’s data as
mandated by COPPA.”
Encryption:
While encryption is a best practice (option D), COPPA explicitly requires appropriate security but
does not mandate encryption at rest and in transit as a specific requirement, though it is
recommended.
Partner Compliance:
Option E refers to the implementation partner, but regulatory responsibility remains with the
covered entity (Bloomington Caregivers), not the partner.
Reference:
Salesforce Security Implementation Guide – COPPA Compliance
Health Cloud Security and Compliance
When accessing a person account record within Health Cloud, the user must have access to the
entire account.
What should a consultant do in this scenario, according to Health Cloud implementation best
practice?
B
Explanation:
Step-by-Step
Salesforce Health Cloud Best Practice for Person Accounts Access:
Person Accounts in Salesforce are a combination of an Account and a Contact.
To ensure that access to the person account (patient record) gives access to all data on the record,
Salesforce recommends setting the Contact sharing setting to "Controlled by Parent".
This means the sharing and visibility of the Contact (patient details) will follow the sharing settings of
the parent Account (the Person Account).
Salesforce Documentation Reference:
“For Person Account sharing and access, set the Contact object sharing setting to Controlled by
Parent. This ensures that users with access to the Account (Person Account) also have access to the
associated Contact data.”
— Reference: Health Cloud Implementation Guide, Sharing and Access
Why Not the Other Options?
A . Set Modify All on the Account object at the Profile level: Too broad; not recommended due to
least privilege principle.
C . Set Private for the Contact object: Would prevent access to the Contact, even if user has access to
the Account.
D . Set the organization-wide default to Public Read Write for the Account object: Not best practice
for healthcare, as it risks overexposing sensitive data.
Reference:
Health Cloud Implementation Guide – Sharing and Access
Bloomington Caregivers would like to display patient information from both Salesforce standard
objects and data from an external system.
Which three Health Cloud features should a consultant recommend the company use to display this
on the patient record page?
Choose 3 answers
A, C, D
Explanation:
Step-by-Step
Health Cloud Best Practice for Displaying Internal and External Data:
FlexCards (part of OmniStudio) can display data from multiple sources in a unified view on a patient
record.
Integration Procedures connect to external systems and bring in data (e.g., from EHRs or other
sources).
DataRaptors extract and transform Salesforce data for display and use in FlexCards.
Salesforce Documentation Reference:
“FlexCards can display internal Salesforce data and call Integration Procedures or DataRaptors to
bring in external or standard object data.”
— OmniStudio Standard Guide
“Integration Procedures are used to retrieve and update data from external systems and can be
invoked directly from FlexCards or OmniScripts.”
— OmniStudio Integration Procedures
“DataRaptors map Salesforce data to and from FlexCards and Integration Procedures, enabling
seamless display of patient information.”
— OmniStudio DataRaptors
Other Options:
Salesforce Flows: Good for automation but not for real-time display of combined external and
internal data on record pages.
Visualforce Pages: Legacy solution, not recommended for modern Health Cloud patient page display,
and does not natively integrate with OmniStudio tools.
Reference:
OmniStudio Standard Guide
OmniStudio Integration Procedures
OmniStudio DataRaptors
An administrator for Health Cloud wants to ensure that the files in their full sandbox instance are
encrypted.
Which encryption solution supports the encryption of files in this scenario?
B
Explanation:
Step-by-Step
Requirement:
Encrypt files in a full sandbox instance.
Salesforce Shield Platform Encryption:
Provides encryption of files and attachments at rest across Salesforce environments (including
sandboxes).
“Use Shield Platform Encryption to encrypt files and attachments stored in Salesforce, including
those in sandbox environments.”
— Salesforce Shield Platform Encryption Guide
Other Options:
Classic Encryption: Only encrypts a limited set of standard fields, not files or attachments.
Salesforce Data Mask: Masks data for sandbox use, but does not encrypt files for runtime.
Industry Data Security: Not a Salesforce product for file encryption.
Reference:
Shield Platform Encryption Guide
An external provider wants to get a patient's allergy information from Bloomington Caregivers'
Health Cloud system.
Which Health Cloud API should a consultant recommend?
B
Explanation:
Step-by-Step
Requirement:
External provider needs access to patient allergy information.
Interoperability API:
Salesforce Health Cloud provides FHIR-based Interoperability APIs that expose clinical data, including
AllergyIntolerance resources.
“Use the Health Cloud Interoperability API (FHIR R4) to retrieve AllergyIntolerance resources and
other clinical data for a patient.”
— Health Cloud Interoperability API Guide
Other Options:
Clinical Summary Healthcare API: Provides a summary but not structured, granular allergy data.
AllergyMedication API: Not a standard Salesforce API.
Patient Healthcare API: Broader resource, but allergies specifically are available through the
Interoperability API.
Reference:
Health Cloud Interoperability API Guide
What are three requirements for implementing patients or members in Health Cloud?
Choose 3 answers
A, C, D
Bloomington Caregivers needs to use the objects for the Clinical data model as part of its new Health
Cloud implementation.
Which preference should Bloomington Caregivers' administrator ensure is enabled?
D
A MedTech company needs to manage its run rate business to ensure contract compliance for its
customers.
Which two features of Health Cloud should a consultant recommend the company use?
Choose 2 answers
A, B
A pharma company wants the ability to:
Upload a patient's insurance card, including automatic Member Plan record creation
Run a benefits verification check
Schedule on behalf of the patient with a provider
Cloud Accredited Professional
Which set of Health Cloud capabilities should enable the company to build this business process?
D
Explanation:
Step-by-Step
Business Process Capabilities:
Intelligent Document Automation: Upload and process patient insurance cards.
Intelligent Document Reader: OCR and extract information to automatically create Member Plan
records.
Benefits Verification: Check and verify patient insurance benefits.
Intelligent Appointment Management: Schedule on behalf of the patient with providers.
Salesforce Documentation Reference:
“Use Intelligent Document Automation and Intelligent Document Reader to upload and extract
insurance card details, with automated Member Plan creation. Use Benefits Verification and
Intelligent Appointment Management to enable scheduling and eligibility checks.”
— Health Cloud: Intelligent Document Automation
— Health Cloud: Benefits Verification
— Health Cloud: Intelligent Appointment Management
Why not the other options?
Only D includes all needed automation for insurance card processing, Member Plan record creation,
benefits verification, and scheduling.
Reference:
Intelligent Document Automation
Intelligent Document Reader
Benefits Verification
Intelligent Appointment Management