Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Salesforce Exam Health Cloud Accredited Professional Topic 2 Question 58 Discussion

Actual exam question for Salesforce's Health Cloud Accredited Professional exam
Question #: 58
Topic #: 2
[All Health Cloud Accredited Professional Questions]

A customer that already has Service Cloud is onboarding a new business unit, which needs to use Health Cloud.

Which three organization-wide default settings should an administrator change to ensure the original business unit that leverages Service Cloud does not have visibility into protected health information (PHI)?

Choose 3 answers

Show Suggested Answer Hide Answer
Suggested Answer: A, C, E

When onboarding a new business unit to Health Cloud while protecting sensitive data for the existing Service Cloud users, adjusting Organization-Wide Defaults (OWD) is critical.

Recommended Settings:

Health Details to Controlled by Parent or Private:

Ensures that only users with appropriate access to parent records (e.g., Person Accounts or Cases) can view sensitive health-related information.

Person Accounts to Private:

Restricts visibility of patient data at the account level, limiting access to users within the appropriate Health Cloud business unit.

Related Clinical Objects to Controlled by Parent or Private:

Applies restricted access to clinical objects like care plans, conditions, and encounters to ensure that PHI is not accessible to Service Cloud users.

Why Other Options Are Less Suitable:

B . Account and Contract to Private: Relevant for managing non-healthcare data but not directly tied to PHI protection.

D . Contact to Controlled by Parent: While this helps manage access to contact data, it does not address broader clinical objects or PHI.


Salesforce Health Cloud Security Best Practices

Contribute your Thoughts:

Lucina
2 days ago
Let's see here... A, D, and E, easy peasy. Wouldn't want the Service Cloud folks snooping around in the Health Cloud, that's for sure. Gotta keep those two worlds separate, you know?
upvoted 0 times
...
Horace
5 days ago
This is a classic case of 'cover your assets.' Gotta make sure that original business unit doesn't get their hands on any of that juicy PHI. A, D, and E are the way to go, no doubt.
upvoted 0 times
...
Diego
20 days ago
I think setting Contact to Controlled by Parent is also important to ensure privacy.
upvoted 0 times
...
Man
23 days ago
Hmm, this is a tricky one. I'd go with A, D, and E to keep those PHI details locked down tight. Can't be too careful with sensitive health data, am I right?
upvoted 0 times
Pete
4 days ago
Definitely, it's important to make sure only the necessary people have access to PHI.
upvoted 0 times
...
Diane
11 days ago
I agree, A, D, and E seem like the best options to protect that sensitive health data.
upvoted 0 times
...
...
Anjelica
28 days ago
I agree with that. We also need to set Person Accounts to Private.
upvoted 0 times
...
Armando
29 days ago
I think we should set Health Details to Controlled by Parent or Private.
upvoted 0 times
...

Save Cancel