Health-Cloud-Accredited-Professional Salesforce Health Cloud Accredited Professional AP-211 Exam Questions and Answers

Step 1: Requirement Analysis

After deploying a care plan template (including problems, goals, and tasks) via Data Loader to the final environment, users must be able to use the new template for creating care plans in production.

Step 2: Salesforce Health Cloud Documentation Guidance

According to the official Health Cloud administration guide, two key post-deployment steps are required:

1. Confirm User Access to Care Plan Objects

Users must have the correct permissions to view, create, and use care plan templates and related records. This involves assigning the appropriate permission sets or profiles to allow access to the Care Plan, Care Plan Template, and related objects.

Extract:

“Ensure users have the necessary permissions to access care plan templates and related objects so they can view and apply templates to patients’ care plans.”

Administer Health Cloud – Care Plans and Permissions

2. Activate the New Care Plan Template

Templates (and their related records) must be activated after being deployed to make them available for use by end users. Care plan templates in Salesforce Health Cloud have an “Active” status that must be set to “True” or “Activated” before users can select them when creating new care plans.

Extract:

“After importing care plan templates and related data, administrators must activate the template to make it available to care coordinators and clinicians.”

Administer Health Cloud – Deploying and Activating Care Plan Templates

Other Options:

B. Activate the problems, goals, and tasks associated with the template:Not required as a separate step. When you activate the care plan template, its associated problems, goals, and tasks become available.

D. Conduct end-user training:While important, it is not a required technical step for enabling the template after deployment.

Verified Answers:

A. Confirm User access to Care Plan objects.

C. Activate the new care plan template.

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.

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.

Step-by-Step Explanation:

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.

 Preconfigured Prior Authorization Objects:

Exact Extract:

“The Health Cloud Care Request Extensions package provides out-of-the-box record types, page layouts, and flows for prior authorizations and other payer workflows.”

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:

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.

In Salesforce Health Cloud, when dealing with prior authorizations, the correct data model objects are:

Service Preauth → Represents the overall prior authorization request (at the header level).

Preauth Detail → Captures the individual service line items or outcomes associated with the prior authorization.

This structure allows Health Cloud to integrate with an external utilization management system that handles the full prior authorization process. The Service Preauth object acts as the container for the request, while Preauth Detail records capture outcomes, decisions, and details returned from the external system.

This is exactly suited to the requirement:

“The provider requires a display of preauthorization outcomes from its external system which manages the end-to-end prior authorization process.”

Why not the others?

A. Plan Benefit and Plan Benefit Item – These are used to model insurance plan coverage and benefits, not authorization workflows.

B. Care Preauth and Care Preauth Item – These are older, deprecated objects in favor of the Service Preauth data model.

D. Care Request and Care Request Item – These are used to track referrals and service requests (e.g., a doctor requesting lab work), but not prior authorization outcomes.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud Developer Guide – Utilization Management Data Model:

“The Service Preauth object represents the prior authorization request and its details. The Preauth Detail object contains service line items and outcomes for the prior authorization request.”

Salesforce Help: Utilization Management Data Model

Salesforce Health Cloud Implementation Guide – Prior Authorizations

To access a patient’s insurance coverage, co-pay, and deductible information in the Benefit Verification component of Health Cloud, you need to integrate with external systems (e.g., payers or clearinghouses). Health Cloud provides the Benefit Verification component, which relies on secure API integrations for real-time eligibility and benefits checks.

Step-by-Step Reference:

Configure the Connection Label with the source system's API details:

Extract:

“In Benefit Verification setup, specify the Connection Label and configure the external endpoint and API details to connect to the benefit verification source system.”

(Source: Administer Health Cloud – Benefit Verification Setup)

Create a named credential to support authenticated callouts:

Extract:

“Use Named Credentials to securely store authentication settings and endpoint information for callouts to external services (such as clearinghouses or payers) required for benefit verification.”

(Source: Salesforce Security Guide and Administer Health Cloud – Benefit Verification)

Why not A or B?

The HCBenVerConnect custom setting is not part of the standard configuration for the out-of-the-box Benefit Verification component.

Configuring a URI path alone (without API details and credentials) does not enable secure, authenticated communication.

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

Provider Search and Performance:

The Data Processing Engine (DPE) in Health Cloud enables fast, scalable searches across large provider directories. It is specifically designed for performance and scalability in Provider Search scenarios.

Extract:

“Health Cloud leverages the Data Processing Engine to deliver scalable, high-performance Provider Search for finding care locations and providers based on patient preferences and proximity.”

— Health Cloud: Provider Search

Other Options:

Pipeline Analytics: Used for data insights, not real-time search.

Business Rules Engine: Handles rules/logic, not high-volume search.

Flow for Industries: Automates processes, but DPE is the correct scalable search tool.

 Enhanced Timeline Functionality:

The Enhanced Timeline in Health Cloud displays a sequence of clinical events (e.g., health conditions and encounters) on a patient’s Person Account.

Exact Extract:

“To configure the Enhanced Timeline component to show custom event types and adjust the event display, create a Timeline View Configuration record.”

Step-by-Step Explanation:

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.

Step-by-Step Explanation:

Person Account as Patient Model:Salesforce Health Cloud is designed to leverage the Person Account model to represent patients, especially for large provider systems.

Exact Extract:

“Health Cloud uses person accounts to represent patients as individuals with whom you do business. Person accounts combine the functionality of accounts and contacts into a single record.”

Expanding Access to Auditors:

Exact Extract:

“Use criteria-based sharing rules to grant additional access to Person Account (patients) records for users or groups who do not own the records, such as auditors.”

The requirement is:

Push patient medication updates to an external pharmacy immediately → This is an event-driven use case.

Receive immediate confirmation about medication interactions from the pharmacy → This requires a synchronous call/response pattern.

The correct integration patterns are:

A. Platform Event

Best for real-time, event-driven notifications when medication information is updated in Health Cloud.

Ensures the pharmacy receives updates as soon as they occur.

D. Apex HTTP Callout

Supports synchronous communication with external systems.

Allows Health Cloud to send a request and receive an immediate confirmation/response about medication interactions from the pharmacy.

Why not the others?

B. Industries ETL – This is for batch, large-volume data movement, not real-time event-driven updates or immediate confirmations.

C. OmniStudio Integration Procedure – Great for orchestrating data retrieval/manipulation across systems, but it’s not designed for event-driven updates with confirmation requirements.

Salesforce Health Cloud Reference:

???? Salesforce Integration Patterns and Practices:

“Use Platform Events for event-driven, near real-time messaging between Salesforce and external systems.”

“Use Apex callouts when Salesforce must send a request and wait for an immediate response.”

In Salesforce Health Cloud, when a customer wants to view and navigate to critical patient information such as insurance, clinical, and primary care physician details, the right feature to implement is the Advanced Patient Card.

The Advanced Patient Card provides a configurable panel that displays key patient information at a glance directly on the patient’s profile.

It allows quick navigation to related records (insurance coverage, care team/PCP, clinical info, etc.) without switching pages.

It’s specifically designed to give providers and service representatives a 360-degree view of the patient’s most important details.

Why not the others?

A. Enhanced Highlights Panel – This is a general Salesforce feature to show record highlights, but it’s not tailored to healthcare-specific patient insights.

B. Enhanced Timeline – Useful for viewing chronological events (interactions, activities, encounters), but not for quick access to insurance/PCP details.

D. Patient Path – This is a visual guide for patient journeys or care programs, not for surfacing key profile details.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud Implementation Guide – Advanced Patient Card:

“Use the Advanced Patient Card to display a patient’s most critical information—such as coverage, conditions, medications, and care team members—directly on the patient profile for easy reference and navigation.”

Salesforce Help: Advanced Patient Card

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

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

To ensure a provider can create and view Salesforce reports analyzing patient outcomes and referrals, the following steps are required:

A. Create custom report types for clinical objects.

Health Cloud clinical data (e.g., patient outcomes, referrals, care plans) resides in custom objects.

To report on them, you must create custom report types.

D. Enable the enhanced Analytics for Healthcare setting in Setup.

This setting provides preconfigured reports and dashboards tailored for healthcare, such as referrals, utilization, and outcomes reporting.

E. Assign appropriate permissions to internal users.

Providers need the correct Health Cloud and reporting permissions to access and run these reports.

Without appropriate object-level and FLS permissions, reports won’t display the necessary data.

Why not the others?

B. Leverage the Patient Referral Management unmanaged package – Referral management is now native in Health Cloud. The unmanaged package was used in early versions but is deprecated and not recommended.

C. Adjust template care management reports and dashboards – These are useful but do not provide referral and outcome reporting by themselves. Customization and proper report type setup are still required.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud Implementation Guide – Reports and Dashboards:

“Enable Enhanced Analytics for Healthcare to access out-of-the-box reports and dashboards for referrals, utilization management, and patient outcomes.”

“Create custom report types for Health Cloud clinical objects to extend reporting capabilities.”

“Ensure users have the appropriate object and field permissions to run reports.