Health-Cloud-Accredited-Professional Sample Questions Answers

Step 1: Understanding the Discovery Framework in Health Cloud

The Discovery Framework in Salesforce Health Cloud is designed to streamline intake and clinical assessments by providing reusable, modular, and compliant tools for healthcare organizations. It enables organizations to collect, store, and reuse responses to assessment questions efficiently and securely.

Video Visits for Social Determinants of Health (SDOH):

Exact Extract:

“Use Virtual Care in Health Cloud to enable video visits between care providers and patients, including for conversations about social and economic factors.”

When onboarding Health Cloud into an org that already uses Service Cloud, it’s critical to properly configure Organization-Wide Defaults (OWD) to ensure that protected health information (PHI) remains restricted.

The correct settings are:

A. Set Person Accounts to Private

Patients are modeled as Person Accounts in Health Cloud.

Setting Person Accounts to Private ensures PHI isn’t exposed to users outside the Health Cloud business unit.

B. Set related clinical objects to Controlled by Parent or Private

Clinical objects (e.g., Care Plans, Assessments, Referrals) often relate to patients.

Making them Controlled by Parent (Person Account) or Private ensures only authorized users can see PHI.

E. Set Health Details to Controlled by Parent or Private

Health Details contain sensitive clinical data.

Must be restricted at the OWD level to prevent exposure to non-Health Cloud users.

Why not the others?

C. Set Account and Contract to Private

Regular business Accounts/Contracts are part of Service Cloud, not typically where PHI resides. Restricting them isn’t required for PHI protection.

D. Set Contact to Controlled by Parent

Contacts in Health Cloud are often caregivers or providers, not patients (who are Person Accounts).

PHI protection centers around Person Accounts + Clinical Objects + Health Details, not Contacts.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud Security and Sharing Guide:

“For HIPAA and other PHI compliance, set Person Accounts and Health Cloud clinical objects to Private or Controlled by Parent.”

“Ensure Health Details are not exposed via default sharing.”

 FHIR-Based Interoperability with Transformation:

Exact Extract:

“Middleware solutions enable integration with EHRs using HL7 or FHIR standards and can perform necessary data transformation for compatibility with Health Cloud.”

Step-by-Step Explanation:

Requirement Analysis:

The client wants to send patients a personalized summary document after their visit, including their care plan.

The process involves selecting from templates and generating patient-specific content.

Tool Comparison:

Health Cloud Email Manager:

Used for composing and sending emails, not for generating documents from templates.

Salesforce PDF Generator:

While Salesforce can generate PDFs from reports, it does not offer flexible, template-based document generation suited for post-visit summaries or complex care plans, especially with dynamic fields.

OmniStudio Document Generation:

Specifically designed to enable dynamic, template-based document creation in Health Cloud and other Salesforce verticals.

Allows users to select templates, merge patient/case data, and generate PDFs or DOCX that can be sent to patients or caregivers.

Supports integration within Health Cloud flows, empowering users (like a patient advocate) to initiate document generation with a few clicks.

Contract Lifecycle Management:

Focused on legal contracts and workflows, not patient summaries or care plans.

Exact Extracts and References from Salesforce Docs:

Extract from OmniStudio Standard Guide:

“OmniStudio Document Generation lets you generate dynamic documents from templates, such as care plans, patient summaries, or correspondence. Templates can be pre-built and allow for the insertion of Health Cloud data fields, enabling the creation of personalized documents for patients or members.”

— OmniStudio Document Generation Overview

From Health Cloud Admin Guide, under Patient Correspondence:

“Patient advocates can use OmniStudio Document Generation to select templates and create personalized care documents for patients based on their Health Cloud data.”

— Reference: Administer Health Cloud - Document Generation

Best Practice from Salesforce:

Salesforce recommends OmniStudio Document Generation for any scenario requiring dynamic, patient-specific document creation and distribution.

Step-by-Step Explanation:

Advanced Therapy Management (ATM):For personalized medicine programs, such as those involving apheresis and infusion, Salesforce Health Cloud offers Advanced Therapy Management (ATM), specifically designed for complex therapy coordination.

Exact Extract:

“Advanced Therapy Management supports cell and gene therapy processes by coordinating multiple steps such as collection, manufacturing, apheresis, and infusion.”

DataRaptors are best for extracting, transforming, and loading Salesforce data, especially when handling data from related SObjects.

Single DataRaptor for related SObjects:

Extract:

“Use a DataRaptor Extract when you need to read Salesforce data, such as retrieving fields from multiple related SObjects in a single read.”

(Source: Omnistudio Standard Guide – DataRaptors)

Why not B, C, or D?

SendMail tasks, complex multi-step logic, or external data connections are handled by Integration Procedures, not DataRaptors.

Step-by-Step Explanation:

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.

After deploying Enhanced Timeline, you must register the custom object to the Timeline before it will appear in the Timeline component on the Lightning page.

Extract:

“Add new objects to the Timeline after deployment in setup, then update the Timeline component to include them.”

(Source: Administer Health Cloud – Enhanced Timeline)

Step-by-Step Explanation:

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.

The requirement is:

Encryption at rest → Handled by Salesforce Shield Platform Encryption.

Notification of activities (user monitoring, data access) → Provided by Event Monitoring in Salesforce Shield.

Extensive field tracking → Achieved with Field Audit Trail, also part of Salesforce Shield.

That’s why the correct answer is the Salesforce Shield bundle, which directly addresses all three compliance needs.

Why not the others?

A. Role Hierarchy, Password Policies, IP Restrictions → These are basic Salesforce security features, but they don’t provide encryption at rest or activity monitoring.

B. Field Audit Trail + Encryption + 2FA → Close, but Field Audit Trail and Encryption require Shield anyway, and 2FA is important but doesn’t meet the monitoring requirement.

D. Security Health Check + DLP policies → Useful for improving org security posture, but Salesforce does not have native DLP policies like in other security platforms. This doesn’t satisfy the encryption + monitoring requirement.

Salesforce Health Cloud / Security Reference:

???? Salesforce Shield Overview:

“Use Shield Platform Encryption for encryption at rest.”

“Use Event Monitoring to monitor and track user activity across apps.”

“Use Field Audit Trail to retain field value changes for compliance requirements.”

In Salesforce Health Cloud’s Identity Verification framework, you can configure which search parameters (such as date of birth, SSN, phone number, etc.) are used by customer service representatives to verify a member or patient’s identity.

To add a new search parameter, you configure an Identity Verification Parameter Item record.

Identity Verification Parameter Item → Defines the actual search fields that will be used in the verification process.

These parameter items are tied to the Identity Verification Process Detail to determine how the verification is performed.

Why not the others?

A. Verification Search Feature – This controls whether identity verification search is enabled, but not the specific search parameters.

B. Identity Verification Process Detail – This defines the steps and rules of the verification process, but doesn’t store the search fields themselves.

D. Linked Identity Search Detail – Used to configure linked identities across systems, not to add new search parameters.

Salesforce Health Cloud Reference:

???? Salesforce Help – Identity Verification in Health Cloud

“To configure the search fields that agents use for member or patient identity verification, create and manage Identity Verification Parameter Item records.”

Salesforce Health Cloud Identity Verification Documentation

Step 1: Requirement Analysis

Birth Date should be a result field and an optional verifier (not required).

Bloomington ID (a custom field) should appear in search results and be a required verifier.

Step 2: Salesforce Health Cloud Identity Verification Process Configuration

The Identity Verification Process Field object in Health Cloud determines which fields are used for search results, required verification, or optional verification during the identity verification process.

You can add multiple records for a field with different purposes (e.g., one as Result Field and another as Required/Optional Verifier).

Extract:

“You can add or modify Identity Verification Process Field records to control which fields are shown as search results, required verifiers, or optional verifiers. For example, to make a field a required verifier, set Field Type to ‘Required Verifier’. To make a field show in results, set Field Type to ‘Result Field’. You can have more than one record for the same field with different Field Types.”

Administer Health Cloud – Identity Verification Process

Step 3: Actions Needed

For Bloomington ID:

Add a record with Field Type = Result Field (to display in search results)

Add another record with Field Type = Required Verifier (to make it a required field for verification)

For Birth Date:

Update the current record so that Field Type is changed from Required Verifier to Optional Verifier (to make it not required but still usable as a verifier)

Ensure there is a record with Field Type = Result Field if Birth Date should show in the results

Step 4: Review of Options

A: Incorrect; it says to delete the Birth Date Required Verifier instead of changing it to optional.

B: Not the right object/method; doesn’t mention the correct object (Identity Verification Process Field).

C: Correct; matches the best practices and object structure in Health Cloud.

D: Incomplete; does not cover all configuration requirements.

Verified Answer:

C. Add two new Identity Verification Process Field records for ‘Bloomington one with Field Type set to Result Field and one with Field Type set to Required Verifier. Change the Birth Date record with Field Type value Required Verifier to Optional Verifier.

The requirement is to identify the Health Cloud feature that helps ensure compliance with the Health Insurance Portability and Accountability Act (HIPAA), which governs the protection of Protected Health Information (PHI). HIPAA compliance requires robust security measures, including access controls and data protection. Let’s evaluate the options.

Option A: Data visualization and analytics

Explanation: Data visualization and analytics in Health Cloud provide insights into patient data and care coordination but do not directly address HIPAA compliance requirements like securing PHI or controlling access. These features are more about operational efficiency than security.

 Medication Management in Health Cloud enables providers to view all of a patient's prescription history in one place, supporting medication reconciliation and review for better health outcomes.

Extract:

“Use Medication Management to track and review patient prescriptions, past and present, ensuring a comprehensive view of medication history and supporting care team collaboration.”

(Source: Administer Health Cloud – Medication Management)

 Other options (Intelligent Appointment Management, Virtual Care, Integrated Care Management) do not provide comprehensive medication tracking.

To improve appointment scheduling and provide patient self-service, these three Health Cloud features should be configured:

Experience Cloud for Health Cloud:

Allows creation of patient-facing portals for self-service appointment booking and information access.

Extract:

“Experience Cloud enables self-service portals for patients, supporting appointment scheduling and other interactions.”

(Source: Administer Health Cloud – Experience Cloud)

Intelligent Appointment Management:

Offers advanced scheduling features and automation to reduce wait times and manual booking.

Extract:

“Intelligent Appointment Management in Health Cloud supports both self-service and agent-assisted scheduling workflows.”

(Source: Administer Health Cloud – Intelligent Appointment Management)

Provider Search:

Lets patients find the right clinic or provider based on specialty, availability, and other criteria.

Extract:

“Provider Search empowers patients to search for providers and book appointments online through self-service portals.”

(Source: Administer Health Cloud – Provider Search)

Why not A or D?

Intelligent Form Reader is used for document capture, not for scheduling or self-service.

Assessments and Recommendations are used for care management, not scheduling.

Step-by-Step Explanation:

Intelligent Document Automation:

Exact Extract:

“Intelligent Document Automation in Health Cloud automatically extracts data from incoming documents, including faxes, and creates structured data for downstream workflows.”

Comprehensive Detailed Step by Step Explanation with exact Extracts from Salesforce Health Cloud documents that you have with References

Request Review Types:

Utilization Management processes center around reviewing requests for appropriateness of care, with the three main types being Prior Authorization Review, Concurrent Review, and Retrospective Review.

Extract:

“Utilization Management supports prior authorization, concurrent, and retrospective reviews to evaluate care appropriateness case by case.”

— Utilization Management in Health Cloud

Care Requests:

Care Requests are the mechanism for providers to seek authorization from payers for drugs, services, or admissions.

Extract:

“Design care request processes to support providers seeking health plan authorization for services, medications, or admissions.”

— Health Cloud Utilization Management Data Model

Why not the other options?

A: Next Best Action is more for care management recommendations, not utilization review.

C: Intake agent count is an operational consideration, not a UM process.