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

The Discovery Framework in Health Cloud supports:

Question Bank: Central repository of reusable questions for assessments.

Branching: Dynamic branching logic based on patient responses.

Scoring: Automatic scoring for assessments/intakes.

Extract:

“The Discovery Framework supports Question Bank, branching logic, and scoring for dynamic, reusable clinical assessments.”

( Source: Administer Health Cloud – Discovery Framework )

Encrypted Text and Image Analysis are not functions of the Discovery Framework.

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

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

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.

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.

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

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

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.

The use case mentions:

Plan and track surgical case visits

Manage device inventory

Run cycle counts

These requirements directly align with the Health Cloud Inventory Management data model .

Inventory Management in Health Cloud is designed for MedTech and Life Sciences companies to track:

Surgical case planning and scheduling

Medical device and implant inventory management

Cycle counts and stock levels across facilities

It supports end-to-end surgical case tracking , ensuring the right devices are available at the right place and time.

Why not the others?

A. Life Sciences – Broader model used for clinical trials, patient programs, and pharma engagement, but not focused on surgical case + device inventory.

B. Provider Engagement – Used for managing provider relationship data (e.g., physician affiliations, facilities), not inventory or surgical planning.

C. Intelligent Sales – Focused on sales optimization and customer engagement, not surgical case or inventory management.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud – Inventory Management Guide:

“Use the Inventory Management data model to manage device inventory, surgical case planning, cycle counts, and medical device tracking across healthcare facilities.”

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.

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

The Advanced Patient Card in Health Cloud is a FlexCard-based UI component that can be extended to show more patient context, such as Clinical Alerts . To display additional fields (Category, SubjectID, Date for active alerts), the developer should:

A. Clone the parent card

Best practice is to clone the delivered parent Patient Card rather than edit it directly, so you preserve the Salesforce-provided baseline functionality.

B. Create and activate a new child card

Child cards display specific contextual data (such as Clinical Alerts ).

To customize which fields show, you create a new child card and activate it.

C. Create a DataRaptor to extract necessary data

Clinical Alert data must be pulled from Health Cloud objects.

A DataRaptor Extract retrieves the required fields (Category, SubjectID, Date) for use in the FlexCard child component.

Why not the others?

D. Define session variables to control visibility of clinical data – Session variables can control context in OmniStudio, but they aren’t required just to display fields on the Patient Card.

E. Change the child card state to show active – Card states are used for conditional rendering (loading, error, empty states). Showing active alerts requires data filtering in the DataRaptor , not card state changes.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud – Advanced Patient Card

“Clone the Advanced Patient Card to customize it while preserving the delivered version.”

“Use child cards to display detailed data such as conditions, medications, or clinical alerts.”

“Retrieve data for FlexCards with DataRaptor Extracts .”

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

Experience Builder and Component Access:

Add the Provider Search component to the Experience Cloud site page for external user access.

Extract:

“Use Experience Builder to add Provider Search components to your site to enable external users to search for providers.”

— Provider Search in Experience Cloud

Read Access:

Granting Read access to the Care Provider Searchable Field object is required for site users to access search results.

Extract:

“Grant the site user profile Read access to the Care Provider Searchable Field object to allow them to view provider search results.”

— Provider Search Security

Other Options:

B: Sharing rules not typically required; object-level access is key.

D: Data Pipeline object access is not relevant for provider search results.

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.

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