Question 11
Choose 1
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?
Correct answer:
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.
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.
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.
