Salesforce Health-Cloud-Accredited-Professional Salesforce Health Cloud Accredited Professional AP-211 Exam Exam Practice Test

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

Step-by-Step Explanation:

Feature Overview: The Actionable Relationship Center (ARC) in Salesforce Health Cloud is specifically designed to give healthcare organizations a graphical and interactive way to visualize, manage, and act on complex relationships among people (patients, caregivers, practitioners) and organizations.

Source: Administer Health Cloud – Actionable Relationship Center

Complex Associations: ARC supports multiple relationship types, including personal, clinical, and organizational connections, enabling users to easily view and manage these associations in a single, unified interface.

Exact Extract:

“With Actionable Relationship Center, care coordinators and other users can view, create, and manage the relationships between patients, their care teams, household members, and service providers. The ARC visualization tool shows complex relationships between people and organizations.”

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

Step 1: Requirement Analysis

After deploying a care plan template (including problems, goals, and tasks) via Data Loader to the final environment, users must be able to use the new template for creating care plans in production.

Step 2: Salesforce Health Cloud Documentation Guidance

According to the official Health Cloud administration guide, two key post-deployment steps are required:

1. Confirm User Access to Care Plan Objects

Users must have the correct permissions to view, create, and use care plan templates and related records. This involves assigning the appropriate permission sets or profiles to allow access to the Care Plan , Care Plan Template , and related objects.

Extract:

“Ensure users have the necessary permissions to access care plan templates and related objects so they can view and apply templates to patients’ care plans.”

Administer Health Cloud – Care Plans and Permissions

2. Activate the New Care Plan Template

Templates (and their related records) must be activated after being deployed to make them available for use by end users. Care plan templates in Salesforce Health Cloud have an “Active” status that must be set to “True” or “Activated” before users can select them when creating new care plans.

Extract:

“After importing care plan templates and related data, administrators must activate the template to make it available to care coordinators and clinicians.”

Administer Health Cloud – Deploying and Activating Care Plan Templa tes

Other Options:

B. Activate the problems, goals, and tasks associated with the template: Not required as a separate step. When you activate the care plan template, its associated problems, goals, and tasks become available.

D. Conduct end-user training: While important, it is not a required technical step for enabling the template after deployment.

Verified Answers:

A. Confirm User access to Care Plan objects.

C. Activate the new care plan template.

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

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

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.

When configuring security, sharing, and visibility in Salesforce Health Cloud , consultants must consider healthcare-specific requirements such as HIPAA, GDPR, and organizational policies . Two critical considerations are:

B. Understand customer needs, data security, privacy concerns, regulatory compliance, and sharing or visibility restrictions.

Healthcare data involves PHI (Protected Health Information) , which requires strict compliance with HIPAA and regional regulations .

Consultants must tailor security models to meet specific privacy and compliance requirements .

C. Regularly review and update security, sharing, and visibility settings in Health Cloud to align with evolving needs, regulations, and organizational policies.

Regulations change, and so do organizational needs. Security and sharing rules must be reviewed and updated periodically to ensure ongoing compliance and relevance.

Why not the others?

A. Ensure that data mask is used in production to appropriately manage PHI.

Salesforce Data Mask is a tool for sandbox data anonymization , not for production . PHI in production should be secured using encryption, field-level security, and sharing rules—not Data Mask.

D. Review Salesforce documentation and implement a standardized security and visibility model.

While documentation is helpful, healthcare organizations require tailored security models that fit unique compliance and data access needs , not a one-size-fits-all model.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud Security and Compliance Guidance:

“When configuring Health Cloud, ensure security models reflect customer needs, privacy concerns, and regulatory compliance (HIPAA, GDPR, etc.). ”

“ Review and update security, sharing, and visibility models regularly to address evolving business, regulatory, and compliance requirements.”

Step-by-Step Explanation:

Requirement:

Encrypt files in a full sandbox instance.

Salesforce Shield Platform Encryption:

Provides encryption of files and attachments at rest across Salesforce environments (including sandboxes).

“Use Shield Platform Encryption to encrypt files and attachments stored in Salesforce, including those in sandbox environments.” — Salesforce Shield Platform Encryption Guide

Other Options:

Classic Encryption: Only encrypts a limited set of standard fields, not files or attachments.

Salesforce Data Mask: Masks data for sandbox use, but does not encrypt files for runtime.

Industry Data Security: Not a Salesforce product for file encryption.

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.

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.

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: Administe r Health Cloud – Enhanced Timeline )

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.

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.

In Salesforce Health Cloud , the Remote Monitoring capability enables healthcare providers to capture and analyze patient-generated health data (from devices such as glucose monitors, blood pressure cuffs, or fitness trackers).

To implement this functionality, the following records must be populated:

Units of Measure – Defines the measurement units (e.g., mmHg, bpm, mg/dL) for device readings.

Remote Monitoring Device Types – Represents the categories of patient devices (e.g., heart rate monitor, glucose meter).

Care Observations – Stores the actual readings (vital signs, measurements) coming from the devices.

Code Sets – Provides standardized medical coding (e.g., LOINC, SNOMED, ICD) for interoperability and classification of device data.

Together, these records form the Remote Monitoring data model .

Why not the others?

B. Units of Measure, Code Sets, Remote Monitoring Device Types, Care Episodes

Care Episodes are for tracking episodes of care , not device data.

C. Code Sets, Units of Measure, Care Metric Targets, Care Observations

Care Metric Targets are for goal setting , not required for capturing device data.

D. Code Sets, Biometrics, Care Observations, Chart Metrics

" Biometrics " and " Chart Metrics " are not the correct Health Cloud objects for Remote Monitoring; instead, Remote Monitoring Device Types + Care Observations are used.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud – Remote Patient Monitoring:

“Use Remote Monitoring Device Types, Units of Measure, Code Sets, and Care Observations to capture and store data from connected health devices.”

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.

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.

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

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

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

The requirement is:

Push patient medication updates to an external pharmacy immediately → This is an event-driven use case.

Receive immediate confirmation about medication interactions from the pharmacy → This requires a synchronous call/response pattern.

The correct integration patterns are:

A. Platform Event

Best for real-time, event-driven notifications when medication information is updated in Health Cloud.

Ensures the pharmacy receives updates as soon as they occur.

D. Apex HTTP Callout

Supports synchronous communication with external systems.

Allows Health Cloud to send a request and receive an immediate confirmation/response about medication interactions from the pharmacy.

Why not the others?

B. Industries ETL – This is for batch, large-volume data movement , not real-time event-driven updates or immediate confirmations.

C. OmniStudio Integration Procedure – Great for orchestrating data retrieval/manipulation across systems, but it’s not designed for event-driven updates with confirmation requirements.

Salesforce Health Cloud Reference:

???? Salesforce Integration Patterns and Practices:

“Use Platform Events for event-driven, near real-time messaging between Salesforce and external systems.”

“Use Apex callouts when Salesforce must send a request and wait for an immediate response.”

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 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 and 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 Expres sion 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.