Practice Free Health-Cloud-Accredited-Professional Salesforce Health Cloud Accredited Professional AP-211 Exam Exam Questions Answers With Explanation

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

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-by-Step Explanation:

Discovery Framework for PROMs Surveys:The Discovery Framework in Health Cloud supports question banks, standardized survey templates, and version control.

Exact Extract:

“Use the Discovery Framework to create assessments with question banks, reusable questions, and versioning to manage standardized surveys such as PROMs.”

? FHIR R4 Standard:

Exact Extract:

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

Out-of-the-box caller authentication in Health Cloud is primarily supported through Identity Verification Flow Templates. These flow templates are designed to help organizations comply with HIPAA and other regulatory requirements by standardizing the caller verification process for contact center agents.

Step-by-Step Reference:

Health Cloud provides Identity Verification Flow Templates that streamline the authentication of callers, reducing manual processes and ensuring regulatory compliance.

Extract:

“Use the Health Cloud Identity Verification Flow Templates to verify a caller’s identity based on information you select, such as date of birth, phone number, or other criteria.”

(Source: Administer Health Cloud)

These templates can be deployed as standard flows and easily customized for the organization's authentication requirements.

Extract:

“Leverage out-of-the-box Identity Verification Flow Templates to quickly set up and deploy identity verification processes in your contact center.”

(Source: Administer Health Cloud - Identity Verification)

This approach is preferred over FlexCards, OmniScripts, or ad-hoc processes, as it provides a compliant and guided experience.

The issue is that the FlexCard is displaying an extra line whenever Address Line 2 has data. The requirement is to fix the display formatting without changing the underlying data model.

In OmniStudio DataRaptors, you can add formula fields during data extraction.

By concatenating Address Line 1 + Address Line 2 into a single formatted field inside the Extract DataRaptor, you can pass the clean, properly formatted address to the FlexCard.

This approach ensures:

No changes to underlying data structure.

No need to create new fields.

Controlled formatting at the data transformation layer.

Why not the others?

A. Add a Load DataRaptor to write the data into one new custom field.

This changes the data model by writing into a new custom field, which the requirement prohibits.

B. Replace the Extract DataRaptor with a Transform DataRaptor.

Transform DataRaptors are typically used for complex JSON-to-JSON mapping or orchestration, not needed here since a simple formula in the Extract DataRaptor suffices.

D. Create a new Turbo Extract DataRaptor to trim the Address data in both fields.

Turbo Extracts are used for high-performance, single-object extracts but do not support formulas or transformations.

They wouldn’t solve the concatenation/formatting issue.

Salesforce OmniStudio Reference:

???? OmniStudio DataRaptor Guide:

“Use formulas in Extract DataRaptors to concatenate or transform fields before passing data to a UI component.”

“Turbo Extract DataRaptors don’t support formulas or transformations.”

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:

COPPA Requirements in Healthcare Applications:

Disclose privacy policy and obtain parental consent:

“Organizations must provide clear privacy notices to parents and obtain their consent before collecting any personal information from children under 13.”

— Reference: Salesforce Security Guide, COPPA Compliance

Obtain verified parental consent before collection/storage:

“Verified parental consent is a core requirement for COPPA, prior to collection and storage of children’s personal data.”

Implement security measures:

“Appropriate security controls and safeguards must be in place to protect children’s data as mandated by COPPA.”

Encryption:

While encryption is a best practice (option D), COPPA explicitly requires appropriate security but does not mandate encryption at rest and in transit as a specific requirement, though it is recommended.

Partner Compliance:

Option E refers to the implementation partner, but regulatory responsibility remains with the covered entity (Bloomington Caregivers), not the partner.

In Salesforce Health Cloud Advanced Therapy Management (ATM), the enrollment process for associating patients to Care Programs is driven by OmniStudio OmniScripts.

Salesforce provides out-of-the-box OmniScripts for patient enrollment.

Best practice: Instead of building from scratch, you clone the delivered OmniScript and then customize it to align with your customer’s unique enrollment process.

This approach ensures you continue to leverage Health Cloud’s standard functionality while tailoring the process flow.

Why not the others?

A. FlexCard – Displays patient/care program info but doesn’t handle the guided enrollment process.

B. Flow – Standard Salesforce Flows are not used for ATM enrollment; Health Cloud leverages OmniScripts for these guided workflows.

C. Apex Class – Only needed for custom logic; cloning Apex is not recommended for configuration/customization here.

Salesforce Health Cloud Reference:

Salesforce Health Cloud Implementation Guide – Advanced Therapy Management:

“Enrollment processes for patients into Care Programs are delivered as OmniScripts. To customize these processes, clone the standard OmniScript and modify it to meet your business needs.”

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

? 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:

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.

The use case describes:

A UI component to display customer data ? FlexCards

A link to start a process (build a new order) ? OmniScript

Retrieving and displaying available products ? DataRaptors (and often Integration Procedures if orchestration is needed).

Let’s map it step by step:

D. FlexCards ? Used to display contextual customer data on the UI and provide clickable actions (like "Create New Order").

E. OmniScript ? Guides the user through the order creation process, step by step (product selection, details, confirmation).

A. DataRaptors ? Extract and load Salesforce data (e.g., retrieving available products, saving the order).

???? These three are the core capabilities needed.

Why not the others?

B. Integration Procedures – Helpful if the solution requires multiple data sources or orchestration, but the question doesn’t explicitly state external integration or complex orchestration. If data is all within Salesforce, DataRaptors are enough.

C. Document Generation – Used to create documents (PDFs, Word, etc.), which isn’t part of this order creation flow.

Salesforce Health Cloud / OmniStudio Reference:

???? Salesforce OmniStudio Developer Guide

“FlexCards present contextual information and actions in a UI component.”

“Use OmniScripts to guide users through business processes such as creating orders.”

“DataRaptors retrieve, transform, and save Salesforce data for use in OmniScripts and FlexCards.”

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.

? Dependent Intervention Tasks:

Exact Extract:

“Action Plan Templates allow you to define and manage dependent intervention tasks for integrated care management workflows, enabling conditional task sequencing.”

In Salesforce Health Cloud, when an organization needs to track account information along with geographical details (like facilities, addresses, and locations), the following objects are used:

A. Location

A standard object in Salesforce used to store physical location data such as addresses, latitude/longitude, and site details.

Useful for mapping and onsite representative visits.

B. Healthcare Facility

Represents the organization’s clinical facilities (hospitals, clinics, labs, etc.).

Connected to Accounts to model the healthcare network.

C. Facility Address

Stores detailed address information for a healthcare facility.

Provides geographical data needed by onsite reps.

Why not D. Clinic Location?

Clinic Location is not a standard Health Cloud object. The correct objects are Healthcare Facility + Facility Address + Location to track facility and geographical details.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud Provider Data Model:

“Use the Healthcare Facility object to represent hospitals, clinics, and other care sites.”

“Use the Facility Address object to store location-specific details about healthcare facilities.”

“The Location object stores standardized address and geographic information.”

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)

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 ensure that the new office address is sent to patients via email after booking, you need logic in the Integration Procedure that checks the office location and triggers the correct email template.

Conditional Blocks in Integration Procedures allow developers to execute actions (like sending a specific email) only when certain conditions are met—such as the new office location.

Extract:

“Use a Conditional Block in an Integration Procedure to execute logic based on data values or conditions. For example, send a specific notification when a record matches certain criteria.”

(Source: Omnistudio Standard Guide – Integration Procedures)

Why not A, B, or C?

Removing Try-Catch, building If-Elself logic, or only updating test conditions do not leverage the maintainable and declarative power of Conditional Blocks in Integration Procedures.

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.

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.