Salesforce AP-211 Exam Questions Instant Access

Question 1

A payer needs to manage requests for concurrent review of prior authorizations within Health Cloud and wants to use out-of-the-box record types and page layouts for prior

However, the payer's Salesforce administrator does not see any preconfigured record types or page layouts for prior authorizations in the payer's Salesforce org.

What should a consultant recommend to the Salesforce administrator to expedite implementation?

AInstall the Health Cloud Care Request Extensions package.

BInstall the Health Cloud Claims unmanaged package.

CBuild custom page layouts and record types to support the requirement.

Dinstall an AppExchange prior authorization package.

Answer : A

* 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.''

* Other Options:

Claims unmanaged package is not for prior authorizations.

Building custom layouts is not necessary when a packaged solution exists.

AppExchange prior authorization packages are not officially supported for core Health Cloud prior auth workflows.

Question 2

How should a consultant recommend modeling a physician's locations of service, when the physician practices at multiple hospitals and clinics?

AAccount Contact Relationship

BHealthcare Taxonomy

CHealthcare Practitioner Facility

DHealthcare Provider Relationship

Answer : C

Question 3

Bloomington Caregivers would like to display patient information from both Salesforce standard objects and data from an external system.

Which three Health Cloud features should a consultant recommend the company use to display this on the patient record page?

Choose 3 answers

AFlexCards

BSalesforce Flows

CIntegration Procedures

DDataRaptors

EVisualforce Pages

Answer : A, C, D

Step-by-Step Explanatio n:

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.

OmniStudio Standard Guide

OmniStudio Integration Procedures

OmniStudio DataRaptors

Question 4

Bloomington Caregivers has more than 1 million patients and each patient has an average of 10 claims a year, which are maintained in an external claims system. Management would like their agents to view all the claims of patients in Salesforce on demand when they open the patient's record.

What should a consultant recommend as the appropriate integration pattern to achieve this?

AAdd a nightly job to fetch all the claims from the external system and store them in Salesforce.

BMake a callout on demand to the external system and store the claims data against the patient record.

CConfigure the claims system as an external data source and leverage external objects with the claims data.

DUse an Enterprise Service Bus (ESB) to load all the claims data from the external system into Salesforce.

Answer : B

Question 5

A developer needs to modify the out-of-the-box advanced Patient Card to display the Category, SubjectID, and Date for active Clinical Alerts.

Which three steps should the developer take to accomplish this?

Choose 3 answers

AClone the parent card

BCreate and activate a new child card.

CCreate a DataRaptor to extract necessary data.

DDefine session variables to control visibility of clinical data.

EChange the child card state to show active

Answer : A, B, C

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

Question 6

Which industry data standard should a consultant consider when designing interoperability with electronic health record (EHR) sources with Health Cloud?

AClinical Data Acquisition

BPersonal Health Record (PHR)

CHL7 vi Messaging

DFHIR R4

Answer : D

* FHIR R4 Standard:

Exact Extract:

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

* Other Options:

HL7 v2 is also supported but FHIR R4 is the recommended modern standard.

Clinical Data Acquisition and PHR are not relevant data standards for EHR interoperability in this context.

Question 7

As part of a post-visit summary, a client wants to send patients information documenting their visit and care plan. A patient advocate will select from templates to create personalized documents to send.

Which tool should a developer use to provide the necessary functionality?

AHealth Cloud Email Manager

BSalesforce PDF Generator

COmniStudio Document Generation

DContract Lifecycle Management

Answer : C

Step-by-Step Explanatio n:

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 Reference 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 - Document Generation

Best Practice from Salesforce:

Salesforce recommends OmniStudio Document Generation for any scenario requiring dynamic, patient-specific document creation and distribution.

OmniStudio Document Generation Overview

Administer Health Cloud - Document Generation

Salesforce Health Cloud Accredited Professional AP-211 Exam Questions