Health-Cloud-Accredited-Professional Exam Dumps - Salesforce Health Cloud Accredited Professional AP-211 Exam

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

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

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.