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

When organization-wide default access to patient data is set to Private, Care Team functionality in Health Cloud is the standard, out-of-the-box method to manage individual access to patient records.

Step-by-Step Reference:

Health Cloud uses Care Teams to manage access to patient records.

Extract:

“Add care team members (users, contacts, or person accounts) to the patient’s care team and assign appropriate access (Read or Read/Write) to patient records.”

(Source: Administer Health Cloud - Manage Care Teams)

Administrators can specify the access level (Read or Read/Write) for each care team member, allowing for precise control as per role requirements.

Extract:

“Assign record access levels for care team members when adding them to a patient’s care team. This is especially important when the OWD is set to Private.”

(Source: Administer Health Cloud - Care Team Access)

This ensures compliance and proper segmentation of data, as required by healthcare regulations.

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.

 Enhanced Timeline Functionality:

The Enhanced Timeline in Health Cloud displays a sequence of clinical events (e.g., health conditions and encounters) on a patient’s Person Account.

Exact Extract:

“To configure the Enhanced Timeline component to show custom event types and adjust the event display, create a Timeline View Configuration record.”

Comprehensive Detailed Step by Step Explanation with exact Extracts from Salesforce Health Cloud documents that you have with References

Record Alerts:

Notify agents of important or recent changes in patient information.

Extract:

“Use Record Alerts to keep agents informed of changes and critical updates on the patient’s record.”

— Contact Center for Health Cloud Overview

Timeline:

Provides a single, unified view of all engagement interactions, encounters, and activities with a patient.

Extract:

“Timeline shows a consolidated history of patient interactions and engagement, giving agents a complete view in one place.”

— Health Cloud: Enhanced Timeline

Member Plan FlexCard:

Displays key patient insurance information directly on the record page.

Extract:

“The Member Plan FlexCard displays essential details about the patient’s insurance coverage for agents.”

— OmniStudio: FlexCards

Other Options:

A. Identity Verification: Used for verifying caller identity, not information display.

D. Action Launcher: Launches actions/processes, not for displaying info or alerts.

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

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

DataRaptors are best for extracting, transforming, and loading Salesforce data, especially when handling data from related SObjects.

Single DataRaptor for related SObjects:

Extract:

“Use a DataRaptor Extract when you need to read Salesforce data, such as retrieving fields from multiple related SObjects in a single read.”

(Source: Omnistudio Standard Guide – DataRaptors)

Why not B, C, or D?

SendMail tasks, complex multi-step logic, or external data connections are handled by Integration Procedures, not DataRaptors.

Comprehensive Detailed Step by Step Explanation with exact Extracts from Salesforce Health Cloud documents that you have with References

Healthcare Practitioner and Healthcare Provider Objects:

Salesforce recommends using the Healthcare Practitioner object for modeling individual doctors and the Healthcare Provider object for organizations/facilities.

Extract:

“Model physicians using the Healthcare Practitioner object and relate them to organizations or facilities using the Healthcare Provider object.”

— Provider Network Management Data Model

Other Options:

A. Contact and B. Person Account are not the recommended approach for modeling licensed clinical professionals in the Health Cloud provider data model.

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

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

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

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

Bloomington Caregivers wants to share a patient’s medical condition details with a local hospital through integration. The recommended method must leverage Health Cloud functionality for standardized, interoperable health data sharing.

Step 2: Salesforce Health Cloud FHIR API

Health Cloud provides native support for the FHIR (Fast Healthcare Interoperability Resources) APIs to facilitate seamless and standardized clinical data exchange (including medical conditions, allergies, medications, etc.) with external systems.

Extract:

“Health Cloud supports the FHIR standard and provides FHIR APIs for accessing and sharing clinical data such as conditions, observations, and encounters with external health systems.”

Administer Health Cloud – FHIR APIs

Step 3: Review of Options

A. Expose the MedicalCondition object through an Apex class: Not standards-based; not recommended for clinical interoperability.

B. Use the FHIR Patient API through DataRaptor: DataRaptor is an OmniStudio tool for extracting data, but not specifically for FHIR API access.

C. Leverage the MedicalCondition Integration Procedure: Integration Procedures are used for orchestrating APIs but are not directly the mechanism for sharing FHIR data externally.

D. integrate using the FHIR Clinical API: Correct – aligns with healthcare interoperability standards and Health Cloud's FHIR support.

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 & 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 Expression 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.

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

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

— Health 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.

Step 1: Requirement Analysis

The provider’s office needs to verify a patient’s insurance plan information and coverage when a patient calls to book an appointment.

This means checking whether the patient’s insurance is active, what services are covered, and any applicable copays or eligibility details.

Step 2: Health Cloud Out-of-the-Box Capability

Benefits Eligibility and Verification is the dedicated Health Cloud capability that allows provider offices and payers to verify a patient’s insurance coverage, eligibility, and benefit details in real time, either through integration with payers or using Health Cloud workflows.

Extract:

“Health Cloud offers Benefits Eligibility and Verification, enabling providers and payers to confirm a patient’s plan information and coverage eligibility, reducing the risk of denied claims and improving the patient experience.”

Administer Health Cloud – Benefits Eligibility and Verification

Step 3: Review of Options

A. Benefits Eligibility and Verification: Directly addresses insurance plan and coverage verification.

B. Intelligent Appointment Management: For scheduling, not insurance verification.

C. Utilization Management: For prior authorizations and care request reviews.

D. Identity Verification: For confirming patient identity, not insurance coverage.

In OmniStudio FlexCards, when you want to change the visual styling of a field element (e.g., font type, font color, formatting), you have two main options:

A. Write custom CSS

OmniStudio FlexCards allow applying custom CSS classes for fine-grained control of styles.

This is how you can specify a font like Times New Roman or apply a red color.

B. Make edits to Field Style

The Field Style editor within the FlexCard Designer lets you directly configure basic styling properties (like text color, background, alignment, etc.) without needing custom CSS.

Why not the others?

C. Make edits to Setup Panel – The Setup Panel is for data source, conditions, and layout configuration, not for styling individual fields.

D. Make edits to Field Properties – Field Properties are used to configure which data is displayed and how it behaves (like label, formatting rules, or conditional display), but styling is handled through Field Style or CSS, not properties.

Salesforce OmniStudio Reference:

???? Salesforce OmniStudio FlexCard Designer Guide

“You can use the Field Style editor to set basic styles, such as font color and alignment.”

“For advanced customization, apply custom CSS classes to field elements.”