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

Step-by-Step Explanation:

Feature Overview: The Actionable Relationship Center (ARC) in Salesforce Health Cloud is specifically designed to give healthcare organizations a graphical and interactive way to visualize, manage, and act on complex relationships among people (patients, caregivers, practitioners) and organizations.

Source: Administer Health Cloud – Actionable Relationship Center

Complex Associations: ARC supports multiple relationship types, including personal, clinical, and organizational connections, enabling users to easily view and manage these associations in a single, unified interface.

Exact Extract:

“With Actionable Relationship Center, care coordinators and other users can view, create, and manage the relationships between patients, their care teams, household members, and service providers. The ARC visualization tool shows complex relationships between people and organizations.”

Step 1: Requirement Analysis

Payer needs to manage healthcare expenses while ensuring quality, affordable care.

Seeks to streamline approval processes for care requests.

Step 2: Utilization Management in Health Cloud

Utilization Management (UM) provides workflows and automation for reviewing, approving, or denying care requests . This supports balancing cost controls with quality care through evidence-based review processes.

Extract:

“Utilization Management helps payers manage costs and ensure members receive appropriate care by streamlining the review and approval process for pre-authorizations and care requests.”

Administer Health Cloud – Utilization Management

Step 3: Review of Options

A. Utilization Management: Directly addresses care request review, cost, and quality balance.

B. Provider Network Management: Focuses on managing provider networks, not utilization/cost review.

C. Intelligent Appointment Management: For scheduling only.

D. Integrated Care Management: Focuses on care coordination, not cost/approval workflow.

The Patient Medication Manager component in Salesforce Health Cloud surfaces data from FHIR-aligned medication objects . When customers request field updates on this UI component, the consultant can configure fields from the underlying objects.

A. Medication Details → Stores key information about a patient’s medications. Fields from this object can be exposed or customized on the Patient Medication Manager.

C. Medication Request → Represents a provider’s request or order for a medication. Fields from this object are also available to configure in the Patient Medication Manager.

Together, these two objects form the basis of what’s displayed and editable in the Patient Medication Manager .

Why not the others?

B. Medication Dispense – Tracks when and how a medication was dispensed. It is not directly configurable for field-level updates in the Patient Medication Manager component.

D. Medication Strength – Captures clinical details about dosage strength, but it isn’t one of the configurable objects in the Patient Medication Manager UI.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud Medication Management:

“The Patient Medication Manager component displays information from Medication Details and Medication Request objects. Administrators can add or remove fields from these objects to tailor the component.”

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

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

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

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 - Docu ment 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:

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 1: Requirement Analysis

The payer wants to use predefined rules for prior authorization request reviews, seeking out-of-the-box Health Cloud functionality for speed to value.

Step 2: Health Cloud Prior Authorization and Rules Engine

The Expression Set Templates in Health Cloud provide a prebuilt, configurable framework to automate and standardize prior authorization request reviews. These templates contain reusable logic and criteria that can be easily tailored and applied to common authorization scenarios.

Extract:

“Use Health Cloud’s prebuilt Expression Set Templates to accelerate prior authorization configuration. These templates enable payers to implement standardized review criteria and automate decision logic without building rules from scratch.”

Administer Health Cloud – Utilization Management and Expres sion Sets

Integration Procedures , FlexCards , and OmniScript Templates are OmniStudio tools for integration, UI, and guided processes, but Expression Set Templates are the feature specifically designed for rules automation in Utilization Management.

 Tracking Socioeconomic and Cultural Barriers:

Exact Extract:

“The Social Determinants of Health data model in Health Cloud enables organizations to document and track social, cultural, and economic barriers affecting patients.”

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

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.

Step-by-Step Explanation:

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.

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 R4 Standard:

Exact Extract:

“Health Cloud supports FHIR R4 as an industry data standard for EHR interoperability.”

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

Business Rules Engine (BRE):

Enables you to define, automate, and manage approval criteria for prior authorizations.

Extract:

“Use Business Rules Engine to automate decisions and apply approval criteria for utilization management and prior authorizations.”

— OmniStudio: Business Rules Engine

Utilization Management Data Model:

Provides standard Health Cloud objects to manage prior authorizations, including requests, approvals, and denials.

Extract:

“Health Cloud Utilization Management provides a complete data model for tracking prior authorization requests and decisions.”

— Health Cloud: Utilization Management Data Model

Out-of-the-box Process Libraries:

Prebuilt processes for common healthcare workflows, including prior authorizations.

Extract:

“Out-of-the-box process libraries provide reusable flows for utilization management, including authorizations, appeals, and notifications.”

— Administer Health Cloud: Process Libraries

Incorrect Options:

A. Claims data model: Related to claims, not prior authorizations.

B. Intelligent Appointment Management: Focused on scheduling, not utilization management or prior authorization.

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.

Step-by-Step Explanation:

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.

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

Record Alerts:

Notify agents of important or recent changes in patient information.

Extract:

“Use Record Alerts to keep agents informed of changes and critical updates on the patient’s record.”

— Contact Center fo r Health Cloud Overview

Timeline:

Provides a single, unified view of all engagement interactions, encounters, and activities with a patient.

Extract:

“Timeline shows a consolidated history of patient interactions and engagement, giving agents a complete view in one place.”

— Health Cloud: Enhanced Timeline

Member Plan FlexCard:

Displays key patient insurance information directly on the record page.

Extract:

“The Member Plan FlexCard displays essential details about the patient’s insurance coverage for agents.”

— OmniStudio: FlexCards

Other Options:

A. Identity Verification: Used for verifying caller identity, not information display.

D. Action Launcher: Launches actions/processes, not for displaying info or alerts.

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.

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

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 Templa tes

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.