Total 117 Questions
Last Updated On : 9-Oct-2026
Implement
Bloomington Caregivers wants to use patient or member lists for its care coordinators in its current implementation. What is an important consideration when implementing this in Health Cloud?
A. If a user cannot access a field used in a filter on a patient or member list, they will not be able to see the list.
B. An administrator can create lists or add records to existing lists from the Campaign object.
C. An administrator can create an override filter field on the person account.
D. Filter logic for patient or member lists is controlled by formula fields on records.
Explanation
Health Cloud's patient lists and member lists (used by care coordinators in console views) are built with filter criteria against fields on the Person Account and related records. A critical — and commonly tested — consideration is that list filters respect field-level security (FLS):
Field-Level Security (FLS) Considerations
If a list's filter uses a field that a given user doesn't have at least read access to (via FLS on their profile or permission set), that user cannot see the list at all. The list simply won't render for them — it doesn't gracefully degrade to showing all records or ignoring the filter.
This means administrators must carefully design list filters using fields that are visible to all intended audiences, or maintain different lists per user persona. It's both a functionality issue and a data-governance issue in a healthcare context.
Why the Other Options Are Wrong
B — Campaign Object
Patient/member lists are managed within the Health Cloud console/admin experience, not through the standard Campaign object. Campaigns are a marketing feature; conflating the two is a distractor.
C — Override Filter Field on the Person Account
There is no "override filter field" concept you create on the Person Account to control list behavior. Filters are defined in the list configuration itself.
D — Formula Fields Controlling Filter Logic
List filter criteria are configured directly in the list definition (field, operator, value) — they are not driven by formula fields on records. Formulas may be used as filterable fields, but they don't control the filter logic of the list.
Key Takeaway for the Exam
For Health Cloud patient/member list questions, the standout best-practice or consideration answer is usually about field-level security interplay — filters run in the context of the running user, and inaccessible filter fields hide the list. Keep FLS in mind whenever the question mentions coordinators, nurses, or other personas viewing shared lists.
A bug is assigned to a developer stating that when an address contains data in the Address Line 2 field, the FlexCard display adds an additional line, causing formatting issues. How should the developer handle this in a DataRaptor without changing the underlying data structures?
A. Add a Load DataRaptor to write the data into one new custom field.
B. Modify the Extract DataRaptor to concatenate the address fields by using a formula.
C. Replace the Extract DataRaptor with a Transform DataRaptor to convert the data as needed.
D. Create a new Turbo Extract DataRaptor to trim the Address data in both fields.
Explanation
The FlexCard is displaying an extra blank line when Address Line 2 contains data (or is blank), which breaks the layout.
The cleanest solution that does not change the underlying Salesforce data model is to adjust the Extract DataRaptor that feeds the FlexCard:
Step 1: Open the Existing Extract DataRaptor
Go to the Formulas tab of the existing Extract DataRaptor.
Step 2: Create a Formula to Concatenate the Address Fields
Create a formula that concatenates the address fields (e.g., Street + Address Line 2), handling blank values so no extra line or extra comma appears.
Example Formula Using CONCAT and ISNOTBLANK / IF Functions:
CONCAT(
%Address:Street%,
IF(ISNOTBLANK(%Address:AddressLine2%), CONCAT(" ", %Address:AddressLine2%), "")
)
Step 3: Map the Formula ResultWhile setting up Advanced Therapy Management, a consultant wants to have patients associated to Care Programs during enrollment. They need to customize the Health Cloud enrollment process to match their customer ' s process. What should the consultant clone to customize for the customer, while leveraging out-ofthe- box Health Cloud functionality?
A. FlexCard
B. Apex Class
C. OmniScript
D. Flow
Explanation
The question asks what a consultant should clone to customize the Health Cloud enrollment process while leveraging out-of-the-box functionality. The correct answer is OmniScript because Health Cloud's standard patient/care program enrollment experiences are built using OmniStudio components, specifically OmniScripts.
Salesforce documentation consistently recommends cloning prebuilt OmniScripts (and their associated FlexCards) rather than modifying them directly. Cloning ensures you don't face process disruptions when predefined components are updated during automatic upgrades. The consultant should find the relevant enrollment OmniScript (such as the Care Program Enrollment or Member Enrollment flow), clone it, and then customize the cloned version to match the customer's process.
Why the Other Options Are Incorrect
A. FlexCard
FlexCards are used for displaying data and launching OmniScripts (e.g., an action button on a record page). They are not the component that contains the enrollment process logic itself. FlexCards are cloned to launch cloned OmniScripts, but the FlexCard alone does not represent the enrollment workflow.
B. Apex Class
Apex is custom code, not an out-of-the-box declarative component. Using Apex would not be leveraging standard Health Cloud functionality and is not the recommended approach for customizing enrollment flows.
D. Flow
While Flow Builder is used for some Health Cloud automation (such as the Program Enrollment Flow), the OmniScript is the specific OmniStudio component that drives guided enrollment experiences in Health Cloud's advanced therapy and care program management features. The question specifically references Advanced Therapy Management, whose enrollment processes are built on OmniStudio components.
References
Salesforce Health Cloud Implementation Guide: Customize Predefined OmniScripts and FlexCards
Recommends cloning each prebuilt OmniScript and FlexCard, then relinking cloned FlexCards to corresponding cloned OmniScripts to avoid disruptions during upgrades.
Trailhead: Advanced Therapy Management in Health Cloud
Documents that therapy workflows (from enrollment through infusion) are orchestrated using Flow and OmniStudio components, with enrollment as a key stage in the therapy journey.
Bloomington Caregivers has set up Health Cloud and needs to analyze patient referrals through Salesforce reports and dashboards. Which Health Cloud unmanaged package should a consultant recommend to deliver a prebuilt dashboard and reports?
A. Health Cloud Reports for Patient Referral Management
B. Health Cloud Member Referral Management Reports
C. Health Cloud Referral Management Reports
D. Health Cloud Network Management Reports
Explanation
Salesforce provides an unmanaged package called Health Cloud Reports for Patient Referral Management that delivers a prebuilt dashboard and sample reports for analyzing patient or member referrals. The package is specifically designed to help organizations track and report on referral management metrics without requiring administrators to build reports and dashboards from scratch.
According to Salesforce Health Cloud documentation, administrators can install this optional unmanaged package to provide users with a referral management dashboard and reports for analyzing referrals.
Why the Other Options Are Incorrect
B. Health Cloud Member Referral Management Reports
Incorrect. This is not the name of the Salesforce unmanaged package documented for referral analytics.
C. Health Cloud Referral Management Reports
Incorrect. Although the name sounds plausible, Salesforce specifically identifies the package as Health Cloud Reports for Patient Referral Management.
D. Health Cloud Network Management Reports
Incorrect. Network Management focuses on provider network-related functionality and is not the package used for referral reporting dashboards.
Exam Tip
For AP-211 questions related to Referral Management reporting, remember:
Referral analytics + prebuilt dashboard = Health Cloud Reports for Patient Referral Management
It is delivered as an optional unmanaged package that contains reports and dashboards for referral analysis.
Answer: A. Health Cloud Reports for Patient Referral Management
Bloomington Caregivers would like to send patient clinical data to an external payer. How should a consultant advise Bloomington Caregivers to make this information available to the payer using the most costeffective method in out-of-the-box Health Cloud?
A. Use a third-party tool from AppExchange.
B. Leverage the FHIR R4 Patient API.
C. Use MuleSoft Accelerator with HL7 API.
D. Build a custom remote call-in API into Salesforce.
Explanation
Salesforce Health Cloud supports healthcare interoperability through Fast Healthcare Interoperability Resources (FHIR) APIs. FHIR R4 is a healthcare data exchange standard that enables systems to exchange structured clinical and patient information.
For Bloomington Caregivers, using the out-of-the-box FHIR API avoids the additional expense and development effort associated with third-party integration tools, custom APIs, or a separate MuleSoft implementation.
However, there is an important distinction: the FHIR R4 Patient API primarily handles patient-resource data. If the payer needs broader clinical information, the integration must also support the relevant FHIR resources and APIs for that data.
Why the Other Options Are Incorrect
A. Use a third-party tool from AppExchange
May introduce additional licensing costs and unnecessary complexity.
C. Use MuleSoft Accelerator with HL7 API
Useful for more complex integrations, but requires additional integration infrastructure and licensing.
D. Build a custom remote call-in API into Salesforce
Requires custom development and ongoing maintenance.
References
Salesforce Help — The Clinical Data Model and FHIR
Explains how Health Cloud aligns its clinical data model with FHIR R4.
Salesforce Developers — Healthcare API
Documents the standard healthcare API and its FHIR resource endpoints.
Salesforce Developers — Healthcare API FAQ
Explains API access and licensing considerations.
Exam Tip
When a question emphasizes out-of-the-box Health Cloud and the most cost-effective method, look for a standard FHIR API before choosing custom development or a separately licensed integration platform.
An administrator is configuring security for a patient list. Which three considerations should the administrator take into account to ensure proper access to the list?
A. Administrators can restrict access using HCP/IdentListSecurity custom settings.
B. If a user ' s field-level security restricts access to a field used as a display column, the column does not appear in the list.
C. Administrators can create restriction rules to offset a private organisation-wide default setting.
D. Users with profile or permission sets that restrict access to an object cannot create a list using that object.
E. Administrators can restrict access to patient or member lists using standard Salesforce sharing settings on the list.
Explanation
When configuring security and access controls for patient and member lists in Health Cloud, administrators must consider standard Salesforce security enforcement principles and list-specific behaviors:
Field-Level Security & Display Columns (Option B)
Patient lists respect standard Salesforce Field-Level Security (FLS). If a user does not have read access to a specific field included as a display column in the list configuration, that column will simply be omitted from their view.
Restriction Rules for Private OWD (Option C)
Organizations with Private OWD settings can utilize Restriction Rules to refine and secure record access dynamically (e.g., ensuring users only see specific patient records based on criteria), working alongside sharing rules.
Object-Level Permissions (Option D)
A user must have baseline object-level access (Create/Read via Profile or Permission Set) on the underlying object to build or generate a patient/member list based on that object.
Why the Other Options Are Incorrect
Option A — Custom Settings (HCP/IdentListSecurity)
This option references custom settings that are not the standard mechanism for governing Health Cloud patient list access.
Option E — Sharing Settings on the List Object
Patient/member lists in Health Cloud do not use standard Salesforce sharing settings applied directly on the list object itself. Instead, user visibility is governed by underlying record-level sharing (OWD, sharing rules, Care Teams) and list permissions.
References
Salesforce Help: Manage Patient and Member Lists Security in Health Cloud
Salesforce Help: Restriction Rules Overview
An external provider wants to get a patient ' s allergy information from Bloomington Caregivers ' Health Cloud system. Which Health Cloud API should a consultant recommend?
A. Clinical Summary Healthcare API
B. Interoperability API
C. AllergyMedication API
D. Patient Healthcare API
Explanation
Salesforce's Healthcare APIs are organized into FHIR R4-aligned families, and allergy data maps to the AllergyIntolerance resource, which sits squarely in the Clinical Summary API family. Salesforce's own documentation states: "Use the Clinical Summary APIs to manage a patient's clinically assessed allergy or intolerance, condition, or procedure."
You can see this in the API endpoint structure as well: requests go to api.healthcloud.salesforce.com/clinical-summary/fhir-r4/v1/AllergyIntolerance.
Why the Other Options Are Wrong
B — Interoperability API
This is a distractor. Salesforce has interoperability features (the HC Interoperability module, Integration User for connecting to external FHIR endpoints, MuleSoft), but there is no product called the "Interoperability API" that you would point an external provider at to retrieve allergy data.
C — AllergyMedication API
This is fabricated. There's no such API. Allergies live in Clinical Summary; medications live in the separate Medication API family (Medication, MedicationRequest, MedicationStatement, etc.). The two are distinct domains, and this option combines them incorrectly.
D — Patient Healthcare API
The Patient API family exposes Patient and RelatedPerson — administrative and demographic information (name, identifiers, contacts), not clinical content like allergies. It's the wrong domain even though the request concerns a patient.
Key Takeaway for the Exam
Match the data type to the FHIR resource, then to the API family:
Patient demographics and related persons: Patient API
Allergies, conditions, and procedures: Clinical Summary API
Medications, prescriptions, and immunizations: Medication API
Appointments and slots: Scheduling API
Coverage and eligibility: Coverage API
Consent: Consent API
Remember: Allergies = AllergyIntolerance = Clinical Summary. This exact mapping shows up repeatedly on the exam.
Bloomington Caregivers is implementing Health Cloud to streamline the process to register patients to care programs while capturing their consent. The company plans to leverage out-of-the-box Health Cloud features. Which Health Cloud feature should a consultant recommend the company use in this scenario?
A. Program Enrollment Flow
B. Care Plan Enrollment Flow
C. Program Eligibility OmniScript
D. Enrollment Consent OmniScript
Explanation
Health Cloud provides an out-of-the-box guided program enrollment process built on Salesforce Flow that lets care coordinators enroll patients into care programs and capture consent in a single, step-by-step experience.
The standard Program Enrollment Flow is designed to handle exactly what Bloomington Caregivers needs:
1. Select a Care Program
Select the care program in which the patient needs to enroll.
2. Add Products and Services
Add products and services associated with the selected program.
3. Add Care Providers
Add the care providers who will participate in the patient's care program.
4. Capture Participant Consent
Capture the participant's consent via eSignature.
This flow is available as a template in Flow Builder (search for "Program Enrollment"), which means the company can leverage out-of-the-box functionality without building the process from scratch. The consent component is a standard part of the flow, satisfying the requirement to capture consent during registration.
Why the Other Options Are Incorrect
B. Care Plan Enrollment Flow
There is no standard "Care Plan Enrollment Flow" in Health Cloud. Care Plans are a separate feature for documenting ongoing care coordination (using the Case object), not for enrolling patients into care programs.
C. Program Eligibility OmniScript
While OmniScripts are used for guided interactions in Health Cloud, eligibility determination is a separate function (using Business Rules Engine or decision matrices). It does not handle enrollment or consent capture.
D. Enrollment Consent OmniScript
This is not a standard out-of-the-box Health Cloud component. Consent capture during program enrollment is handled within the Program Enrollment Flow, not as a separate standalone OmniScript.
References
Salesforce Trailhead: Care Programs
Describes the standard Program Enrollment Flow, which guides coordinators through program selection, product/provider assignment, and consent capture.
Salesforce Release Notes: Enroll Patients in Programs and Capture Their Consent
Confirms this is an out-of-the-box Flow-based feature.
A payer needs to triage provider and care team inquiries around member plan benefits and member care. The agents also need to be informed about changes in records that require attention. Which three permission set licenses should a consultant assign to the security model for these users?
A. Service Cloud User permission set license
B. OmniStudio User permission set license
C. Contact Center for Health Cloud permission set license
D. Health Cloud Platform permission set license
E. CRM Content User permission set license
Explanation
For payer contact-center agents who triage provider and care-team inquiries about member plan benefits and member care, and who also need to receive alerts about record changes, Salesforce requires these three permission set licenses:
1. Health Cloud Platform
Required for all internal Health Cloud users. It provides the base platform capabilities, including the core data model.
2. Contact Center for Health Cloud
Specifically grants access to the Contact Center for Health Cloud app and features. This includes:
- Member identity verification
- Viewing member plan and benefits information
- Capturing engagement interactions
- Record Alerts (the mechanism that notifies agents of changes that require attention)
3. OmniStudio User
Contact Center for Health Cloud relies on OmniStudio components (FlexCards, OmniScripts, etc.). Users therefore need the OmniStudio User permission set license.
Why the Other Options Are Incorrect
A. Service Cloud User
While Service Cloud features (Cases, etc.) are often used, the documentation specifically calls out the Contact Center for Health Cloud license rather than a generic Service Cloud User license for this functionality.
E. CRM Content User
Not required for Contact Center triage or record-alert functionality.
References
Salesforce Help: View and Assign Health Cloud Permission Sets and Permission Set Licenses
Salesforce Help: Assign Permission Sets to Contact Center Users
Salesforce Help: Contact Center for Health Cloud
A consultant is implementing clinical assessments to track intake for a hospital leveraging the Discovery Framework. Which three functions is the consultant able to leverage with Health Cloud?
A. Image Analysis
B. Scoring
C. Encrypted Text
D. Question Bank
E. Branching
Explanation
Salesforce Health Cloud's Discovery Framework supports configurable intake forms and clinical assessments. These capabilities help hospitals collect patient information, standardize assessments, and adapt questions based on responses.
B. Scoring
Allows assessments to calculate scores based on responses, helping evaluate patient needs or assessment outcomes.
D. Question Bank
Provides reusable questions that can be organized and used across assessments, reducing duplication and promoting consistency.
E. Branching
Allows subsequent questions or sections to depend on previous answers, enabling a more relevant and dynamic assessment experience.
Why the Other Options Are Incorrect
A. Image Analysis
Not a core Discovery Framework assessment function.
C. Encrypted Text
A data-security consideration, not a built-in assessment function like branching or scoring.
References
Salesforce Help — Discovery Framework Assessment Questions
Explains reusable question sets and assessment form logic.
Salesforce Help — Assessments vs. Surveys
Confirms that Health Cloud Assessments support branching and scoring.
Exam Tip
Remember Question Bank + Branching + Scoring as key Discovery Framework capabilities for clinical assessments.
| Page 2 out of 12 Pages |
| 1234 |
| Salesforce-Accredited-Agentforce-Health-Professional Practice Test Home |
Our new timed 2026 Salesforce-Accredited-Agentforce-Health-Professional practice test mirrors the exact format, number of questions, and time limit of the official exam.
The #1 challenge isn't just knowing the material; it's managing the clock. Our new simulation builds your speed and stamina.
You've studied the concepts. You've learned the material. But are you truly prepared for the pressure of the real Salesforce Accredited Agentforce Health Professional - AP-211 exam?
We've launched a brand-new, timed Salesforce-Accredited-Agentforce-Health-Professional practice exam that perfectly mirrors the official exam:
✅ Same Number of Questions
✅ Same Time Limit
✅ Same Exam Feel
✅ Unique Exam Every Time
This isn't just another Salesforce-Accredited-Agentforce-Health-Professional practice questions bank. It's your ultimate preparation engine.
Enroll now and gain the unbeatable advantage of:
Copyright © - All Rights Reserved