Free Practice Questions for the Salesforce Health Cloud Health-Cloud-Accredited-Professional Exam (2026 Updated)

The best answer is to leverage the FHIR R4 Patient API. Salesforce Healthcare API is designed to securely connect and interact with systems that use FHIR APIs, and FHIR is the healthcare standard for representing and exchanging electronic health records. The Healthcare API includes Administration resources such as Patient, Practitioner, Encounter, Organization, Location, and RelatedPerson, making the Patient API the correct out-of-the-box method for sharing patient information. Salesforce also documents that the API URL format aligns with the FHIR standard. MuleSoft accelerators and third-party AppExchange tools can be valid integration approaches, but they are not the most cost-effective out-of-the-box choice when the FHIR API already supports standardized healthcare data exchange. Building a custom API is unnecessary and increases cost, complexity, and maintenance.

To ensure a provider can create and view Salesforce reports analyzing patient outcomes and referrals , the following steps are required:

A. Create custom report types for clinical objects.

Health Cloud clinical data (e.g., patient outcomes, referrals, care plans) resides in custom objects .

To report on them, you must create custom report types .

D. Enable the enhanced Analytics for Healthcare setting in Setup.

This setting provides preconfigured reports and dashboards tailored for healthcare, such as referrals, utilization, and outcomes reporting .

E. Assign appropriate permissions to internal users.

Providers need the correct Health Cloud and reporting permissions to access and run these reports.

Without appropriate object-level and FLS permissions , reports won’t display the necessary data.

Why not the others?

B. Leverage the Patient Referral Management unmanaged package – Referral management is now native in Health Cloud . The unmanaged package was used in early versions but is deprecated and not recommended.

C. Adjust template care management reports and dashboards – These are useful but do not provide referral and outcome reporting by themselves. Customization and proper report type setup are still required.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud Implementation Guide – Reports and Dashboards:

“Enable Enhanced Analytics for Healthcare to access out-of-the-box reports and dashboards for referrals, utilization management, and patient outcomes.”

“Create custom report types for Health Cloud clinical objects to extend reporting capabilities.”

“Ensure users have the appropriate object and field permissions to run reports.

Step-by-Step Explanation:

Understanding the Scenario:

The provider aims to build a Contact Center using Health Cloud for patients to:

Set up appointments

Get billing answers

Update plan information

Salesforce’s Best Practices for Requirements Gathering:

Salesforce Health Cloud documentation emphasizes collaborating with end users and technical stakeholders to uncover pain points and define requirements.

Extract from Health Cloud Admin Guide:

“Successful Health Cloud projects start with workshops that bring together key personas, such as contact center agents and care coordinators, with technical stakeholders including Salesforce admins and integration architects. These sessions surface pain points, business needs, and integration requirements.”

— Reference: Administer Health Cloud – Imple mentation Best Practices

Who Should Be Involved?

Contact Center agent (Persona):

Directly understands patient needs and pain points during calls and chats.

Can highlight workflow, usability, and feature needs.

Salesforce administrator (Stakeholder):

Understands platform capabilities, permissions, and how features will be implemented or configured.

Integration architect (Stakeholder):

Critical for connecting Health Cloud to other systems (e.g., EHR, billing, insurance).

Ensures technical feasibility for integrations (e.g., real-time eligibility checks, appointment scheduling with external systems).

Why Other Answers Are Not Correct:

B: General physician and Marketing Cloud admin are not core to Contact Center workflows or technical design for scheduling/billing.

C: Sales administrator and Tableau developer focus on sales or analytics, not operational or integration workflows for Contact Centers.

D: Tableau developer and MuleSoft developer are more technical roles but not typically involved in initial workflow and requirements gathering at the Contact Center user level.

Official Document Extract:

From Salesforce Implementation Guides:

“It is essential to involve actual end users (such as agents) and platform administrators in requirements workshops, and to include an integration architect for designing connected experiences.”

— Reference: Administer Health Cloud – Implementation Best Practices

Health Cloud supports Utilization Management (UM) through the Service Request object, which tracks prior authorization requests, and through integration with electronic prior authorization systems using MuleSoft.

Customize the Service Request object:

Extract:

“The Service Request object is at the core of the Utilization Management process in Health Cloud. You can customize fields, page layouts, and automation to match your business processes for prior authorization.”

( Source: Administer Health Cloud – Utilization Management )

Integrate using MuleSoft Direct for ePA:

Extract:

“Integrate Health Cloud Utilization Management with external systems using MuleSoft Direct, enabling electronic submission and tracking of prior authorizations.”

( Source: Administer Health Cloud – Utilization Management Integration )

Why not B or D?

There is no standard custom setting called UtilizationManagementSettings for this process.

Support Process is more for standard Salesforce Cases and not directly linked to Utilization Management flows in Health Cloud.

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

To access a patient’s insurance coverage, co-pay, and deductible information in the Benefit Verification component of Health Cloud, you need to integrate with external systems (e.g., payers or clearinghouses). Health Cloud provides the Benefit Verification component, which relies on secure API integrations for real-time eligibility and benefits checks.

Step-by-Step Reference:

Configure the Connection Label with the source system ' s API details:

Extract:

“In Benefit Verification setup, specify the Connection Label and configure the external endpoint and API details to connect to the benefit verification source system.”

( Source: Administer Health Cloud – Benefit Verification Setup )

Create a named credential to support authenticated callouts:

Extract:

“Use Named Credentials to securely store authentication settings and endpoint information for callouts to external services (such as clearinghouses or payers) required for benefit verification.”

( Source: Salesforce Security Guide and Administer H ealth Cloud – Benefit Verification )

Why not A or B?

The HCBenVerConnect custom setting is not part of the standard configuration for the out-of-the-box Benefit Verification component.

Configuring a URI path alone (without API details and credentials) does not enable secure, authenticated communication.

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

Provider Search and Performance:

The Data Processing Engine (DPE) in Health Cloud enables fast, scalable searches across large provider directories. It is specifically designed for performance and scalability in Provider Search scenarios.

Extract:

“Health Cloud leverages the Data Processing Engine to deliver scalable, high-performance Provider Search for finding care locations and providers based on patient preferences and proximity.”

— Health Cloud: Provider Search

Other Options:

Pipeline Analytics: Used for data insights, not real-time search.

Business Rules Engine: Handles rules/logic, not high-volume search.

Flow for Industries: Automates processes, but DPE is the correct scalable search tool.

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

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

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

Step-by-Step Explanation:

Salesforce Health Cloud Prerequisites:

Enable Person Accounts:

Required for representing patients and healthcare contacts.

“Person Accounts must be enabled before installing Health Cloud.”

— Reference: Health Cloud Installation Prerequisites

Enable Chatter:

Health Cloud uses Chatter for collaboration between care teams.

“Chatter must be enabled to use Health Cloud features like care coordination and notes.”

— Reference: Health Cloud Installation Prerequisites

Enable Contacts to Multiple Accounts:

Necessary to relate patients to multiple organizations/providers.

“Enable Contacts to Multiple Accounts to relate contacts (patients) to more than one account (e.g., provider, payer).”

— Reference: Health Cloud Installation Prerequisites

Other Options:

B. Enable Shield Event Monitoring: Not required for Health Cloud installation (but is a best practice for auditing and compliance in some orgs).

D. Enable Health Cloud Installation Monitor: Not a standard Salesforce setting or prerequisite.

To improve appointment scheduling and provide patient self-service, these three Health Cloud features should be configured:

Experience Cloud for Health Cloud :

Allows creation of patient-facing portals for self-service appointment booking and information access.

Extract:

“Experience Cloud enables self-service portals for patients, supporting appointment scheduling and other interactions.”

( Source: Administer Health Cloud – Experience Cloud )

Intelligent Appointment Management :

Offers advanced scheduling features and automation to reduce wait times and manual booking.

Extract:

“Intelligent Appointment Management in Health Cloud supports both self-service and agent-assisted scheduling workflows.”

( Source: Administer Health Cloud – Intelligent Appointment Management )

Provider Search :

Lets patients find the right clinic or provider based on specialty, availability, and other criteria.

Extract:

“Provider Search empowers patients to search for providers and book appointments online through self-service portals.”

( Source: Administer Health Cloud – Provider Search )

Why not A or D?

Intelligent Form Reader is used for document capture, not for scheduling or self-service.

Assessments and Recommendations are used for care management, not scheduling.

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

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

Step 1: Understanding the Requirement

A payer organization needs to recruit, credential, and onboard providers into its network. This requires features that manage provider information, credentialing processes, onboarding workflows, and network directory maintenance.

Step 2: Official Salesforce Health Cloud Capability

Salesforce Health Cloud offers an add-on called Provider Network Management (PNM) that is specifically designed for payers to recruit, credential, and onboard providers.

Extract:

“Provider Network Management streamlines recruiting, credentialing, onboarding, and network directory maintenance for payers. It provides tools to manage the provider lifecycle from initial recruitment through onboarding and network management.”

Administer Health Cloud – Provider Network Management

Step 3: Review of Options

A. Contact Center for Payers : Focused on member and provider service center functionality, not recruiting or credentialing.

B. Utilization Management : Focused on authorization and medical necessity reviews, not onboarding or credentialing.

C. Provider Network Management : Specifically built for recruiting, credentialing, and onboarding providers.

D. Provider Relationship Management : Focuses on relationship management post-onboarding, but not credentialing/onboarding workflows.

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

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.

Step-by-Step Explanation:

CRM Analytics for Health Cloud:

Exact Extract:

“CRM Analytics for Health Cloud delivers prebuilt dashboards and extended analytics for monitoring care plans, outcomes, and adherence across networks and facilities.”

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

In Salesforce Health Cloud, when dealing with prior authorizations, the correct data model objects are:

Service Preauth → Represents the overall prior authorization request (at the header level).

Preauth Detail → Captures the individual service line items or outcomes associated with the prior authorization.

This structure allows Health Cloud to integrate with an external utilization management system that handles the full prior authorization process. The Service Preauth object acts as the container for the request, while Preauth Detail records capture outcomes, decisions, and details returned from the external system.

This is exactly suited to the requirement:

“The provider requires a display of preauthorization outcomes from its external system which manages the end-to-end prior authorization process.”

Why not the others?

A. Plan Benefit and Plan Benefit Item – These are used to model insurance plan coverage and benefits, not authorization workflows.

B. Care Preauth and Care Preauth Item – These are older, deprecated objects in favor of the Service Preauth data model.

D. Care Request and Care Request Item – These are used to track referrals and service requests (e.g., a doctor requesting lab work), but not prior authorization outcomes.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud Developer Guide – Utilization Management Data Model:

“The Service Preauth object represents the prior authorization request and its details. The Preauth Detail object contains service line items and outcomes for the prior authorization request.”

Salesforce Help: Utilization Management Data Model

Salesforce Health Cloud Implementation Guide – Prior Authorizations