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:

Chau
2 months ago
Ah, the classic 'keep the PHI on lockdown' question. A, D, and E are the way to go, no doubt. Gotta make sure that original business unit doesn't accidentally stumble upon any sensitive health data. *chuckles* Wouldn't want them to get a case of the 'snoopy blues,' now would we?
upvoted 0 times
Orville
29 days ago
Yeah, keeping PHI secure is top priority. A, D, and E all the way.
upvoted 0 times
...
Penney
1 months ago
A, D, and E are definitely the right choices. Can't risk any leaks of sensitive health data.
upvoted 0 times
...
...
Jaclyn
2 months ago
Okay, let's think this through. A, D, and E are the way to go. Heck, I'd even throw in a little B just for good measure, just to be on the safe side. Can't be too careful when it comes to PHI, am I right? *laughs* 'Course, I'm probably just overthinking it.
upvoted 0 times
Barrett
29 days ago
Yeah, I think adding B as an extra precaution is a good idea. Can't be too careful with protected health information.
upvoted 0 times
...
Lucy
1 months ago
I agree, A, D, and E seem like the best options to ensure the original business unit doesn't have access to PHI.
upvoted 0 times
...
...
Lucina
2 months 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
Stephanie
1 months ago
Beth: Perfect, that way the Service Cloud team won't have access to protected health information.
upvoted 0 times
...
Sang
1 months ago
User 3: Agreed. And we should set related clinical objects to Controlled by Parent or Private.
upvoted 0 times
...
Beth
1 months ago
User 2: Yeah, that's a good idea. We should also set Contact to Controlled by Parent.
upvoted 0 times
...
Charlene
1 months ago
User 1: I think we should set Health Details to Controlled by Parent or Private.
upvoted 0 times
...
...
Horace
2 months 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
Virgina
1 months ago
E) Set related clinical objects to Controlled by Parent or Private.
upvoted 0 times
...
Arletta
2 months ago
D) Set Contact to Controlled by Parent.
upvoted 0 times
...
Casie
2 months ago
A) Set Health Details to Controlled by Parent or Private.
upvoted 0 times
...
...
Diego
3 months ago
I think setting Contact to Controlled by Parent is also important to ensure privacy.
upvoted 0 times
...
Man
3 months 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
2 months ago
Definitely, it's important to make sure only the necessary people have access to PHI.
upvoted 0 times
...
Diane
2 months ago
I agree, A, D, and E seem like the best options to protect that sensitive health data.
upvoted 0 times
...
...
Anjelica
3 months ago
I agree with that. We also need to set Person Accounts to Private.
upvoted 0 times
...
Armando
3 months ago
I think we should set Health Details to Controlled by Parent or Private.
upvoted 0 times
...

Save Cancel