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
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.
Currently there are no comments in this discussion, be the first to comment!