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

Step 1: Requirement Analysis

Admin needs to leverage Advanced Therapy Management for complex gene therapy scheduling.

Step 2: Key Capabilities of Advanced Therapy Management

Book multi-step appointments: Supports sequencing and booking complex, interdependent appointments and procedures (e.g., cell collection, manufacturing, infusion).

Reschedule part of the appointment chain: Enables rescheduling one step in a multi-step process without rebooking the entire chain.

Extract:

“Advanced Therapy Management allows for the orchestration of complex, multi-step appointment chains and the flexibility to reschedule individual steps in the chain.”

Administer Health Cloud – Advanced Therapy Management

Other options:

A: Telehealth scheduling is not a specific feature of Advanced Therapy Management.

D: Einstein is not natively used for chain optimization in Advanced Therapy Management as per current documentation.

Verified Answers:

B. Book multi-step appointments.

C. Reschedule part of the appointment chain.

The best answer is to leverage the FHIR R4 Patient API. Salesforce Healthcare API is designed to securely connect and interact with systems that use FHIR APIs, and FHIR is the healthcare standard for representing and exchanging electronic health records. The Healthcare API includes Administration resources such as Patient, Practitioner, Encounter, Organization, Location, and RelatedPerson, making the Patient API the correct out-of-the-box method for sharing patient information. Salesforce also documents that the API URL format aligns with the FHIR standard. MuleSoft accelerators and third-party AppExchange tools can be valid integration approaches, but they are not the most cost-effective out-of-the-box choice when the FHIR API already supports standardized healthcare data exchange. Building a custom API is unnecessary and increases cost, complexity, and maintenance.

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

— He alth 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.

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

Step 1: Understanding the Requirement

A payer organization needs to recruit, credential, and onboard providers into its network. This requires features that manage provider information, credentialing processes, onboarding workflows, and network directory maintenance.

Step 2: Official Salesforce Health Cloud Capability

Salesforce Health Cloud offers an add-on called Provider Network Management (PNM) that is specifically designed for payers to recruit, credential, and onboard providers.

Extract:

“Provider Network Management streamlines recruiting, credentialing, onboarding, and network directory maintenance for payers. It provides tools to manage the provider lifecycle from initial recruitment through onboarding and network management.”

Administer Health Cloud – Provider Network Management

Step 3: Review of Options

A. Contact Center for Payers : Focused on member and provider service center functionality, not recruiting or credentialing.

B. Utilization Management : Focused on authorization and medical necessity reviews, not onboarding or credentialing.

C. Provider Network Management : Specifically built for recruiting, credentialing, and onboarding providers.

D. Provider Relationship Management : Focuses on relationship management post-onboarding, but not credentialing/onboarding workflows.

 The Health Cloud Reports for Patient Referral Management unmanaged package provides prebuilt reports and dashboards to analyze referrals.

Extract:

“The Health Cloud Reports for Patient Referral Management unmanaged package includes reports and dashboards that help track patient referrals in Salesforce.”

( Source: Administer Health Cloud – Reports and Dashboards )

 Other options are either not standard package names or do not match referral reporting.

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.

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.

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

The correct approach is to use the Social Determinants data model in Health Cloud and extend it as needed. Social Determinants of Health represent non-clinical social and environmental factors that affect a patient or member’s wellness, such as food insecurity, transportation barriers, housing instability, and socioeconomic conditions. Salesforce Trailhead explains that the Social Determinants data model gives care teams insight into a patient’s physical environment and socioeconomic status, helping them identify intervention tasks and reduce care barriers. Salesforce developer documentation also describes the model as representing barriers, health determinants, and interventions for a patient or member. A custom entity should not be the first choice because Health Cloud already provides a purpose-built data model. The Care Plan and EHR models address clinical care, not broad non-clinical determinants.

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

The users need both the Provider Network Management permission set and the Health Cloud Foundation permission set. Salesforce documentation states that the Provider Network Management permission set grants access to provider management objects used for recruiting, credentialing, network management, and related provider administration. Salesforce also identifies the Health Cloud Foundation permission set as providing access to additional Health Cloud platform capabilities, including the Provider Network Management data model. The Provider Network Management data model documentation directly indicates that users should be assigned both the Health Cloud Foundation permission set and the Provider Network Management permission set. Health Cloud Standard is too general and is not the required PNM-specific permission set. Health Cloud Utilization Management applies to prior authorization and utilization workflows, not provider network management access.

Step-by-Step Explanation:

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

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.

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.

The scenario involves collecting structured information (series of questions) from patients and automatically assigning a personalized care plan based on their answers.

Step-by-Step Reference:

Salesforce Surveys can be used to gather responses from patients post-discharge.

Extract:

“With Salesforce Surveys, care managers can send and record responses directly within Health Cloud, allowing structured data capture from patients.”

( Source: Administ er Health Cloud - Surveys )

Discovery Framework processes responses and triggers automated care plan assignments based on responses.

Extract:

“The Discovery Framework in Health Cloud enables dynamic question flows and recommendations, such as assigning care plans based on patient answers.”

( Source: Administer Health Cloud - Discovery Framework )

Combining these, care managers can capture structured data (Surveys) and drive workflow automation and personalization (Discovery Framework).

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.

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

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.

The correct capabilities are Provider Search and Intelligent Appointment Management. Provider Search is specifically designed to help users find healthcare providers using search criteria such as location, specialty, subspecialty, plan type, facility name, and patient travel distance. Salesforce Trailhead also identifies call center agents and care coordinators as typical users of Provider Search, which directly matches the scenario. Intelligent Appointment Management is the scheduling capability that lets appointment schedulers and call center representatives view provider availability and schedule appointments for patients. It centralizes appointment scheduling and can use Salesforce Scheduler, EHR scheduling engines, or both. Experience Cloud is mainly for external self-service portals, while Integrated Care Management is for care plan and care coordination workflows, not provider lookup and appointment scheduling.

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

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.

When configuring security, sharing, and visibility in Salesforce Health Cloud , consultants must consider healthcare-specific requirements such as HIPAA, GDPR, and organizational policies . Two critical considerations are:

B. Understand customer needs, data security, privacy concerns, regulatory compliance, and sharing or visibility restrictions.

Healthcare data involves PHI (Protected Health Information) , which requires strict compliance with HIPAA and regional regulations .

Consultants must tailor security models to meet specific privacy and compliance requirements .

C. Regularly review and update security, sharing, and visibility settings in Health Cloud to align with evolving needs, regulations, and organizational policies.

Regulations change, and so do organizational needs. Security and sharing rules must be reviewed and updated periodically to ensure ongoing compliance and relevance.

Why not the others?

A. Ensure that data mask is used in production to appropriately manage PHI.

Salesforce Data Mask is a tool for sandbox data anonymization , not for production . PHI in production should be secured using encryption, field-level security, and sharing rules—not Data Mask.

D. Review Salesforce documentation and implement a standardized security and visibility model.

While documentation is helpful, healthcare organizations require tailored security models that fit unique compliance and data access needs , not a one-size-fits-all model.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud Security and Compliance Guidance:

“When configuring Health Cloud, ensure security models reflect customer needs, privacy concerns, and regulatory compliance (HIPAA, GDPR, etc.). ”

“ Review and update security, sharing, and visibility models regularly to address evolving business, regulatory, and compliance requirements.”