In Salesforce Health Cloud , when a customer wants to view and navigate to critical patient information such as insurance, clinical, and primary care physician details , the right feature to implement is the Advanced Patient Card .
* The Advanced Patient Card provides a configurable panel that displays key patient information at a glance directly on the patient's profile.
* It allows quick navigation to related records (insurance coverage, care team/PCP, clinical info, etc.) without switching pages.
* It's specifically designed to give providers and service representatives a 360-degree view of the patient's most important details .
Why not the others?
* A. Enhanced Highlights Panel - This is a general Salesforce feature to show record highlights, but it's not tailored to healthcare-specific patient insights.
* B. Enhanced Timeline - Useful for viewing chronological events (interactions, activities, encounters), but not for quick access to insurance/PCP details.
* D. Patient Path - This is a visual guide for patient journeys or care programs , not for surfacing key profile details.
Salesforce Health Cloud Reference:
# Salesforce Health Cloud Implementation Guide - Advanced Patient Card:
"Use the Advanced Patient Card to display a patient's most critical information-such as coverage, conditions, medications, and care team members-directly on the patient profile for easy reference and navigation."
* Salesforce Help: Advanced Patient Card

* Expanding Access to Auditors:
* Exact Extract:
"Use criteria-based sharing rules to grant additional access to Person Account (patients) records for users or groups who do not own the records, such as auditors." Reference:Salesforce Security Guide - Sharing Rules Other Options:
Restriction rule:Restricts, not expands, access.
User access policy:Not a Salesforce standard for sharing data.
Changing org-wide default to Public Read-Only:Not best practice for PHI and patient data-should use sharing rules for scoped access.

When onboarding Health Cloud into an org that already uses Service Cloud, it's critical to properly configure Organization-Wide Defaults (OWD) to ensure that protected health information (PHI) remains restricted.
The correct settings are:
A . Set Person Accounts to Private
Patients are modeled as Person Accounts in Health Cloud.
Setting Person Accounts to Private ensures PHI isn't exposed to users outside the Health Cloud business unit.
B . Set related clinical objects to Controlled by Parent or Private
Clinical objects (e.g., Care Plans, Assessments, Referrals) often relate to patients.
Making them Controlled by Parent (Person Account) or Private ensures only authorized users can see PHI.
E . Set Health Details to Controlled by Parent or Private
Health Details contain sensitive clinical data.
Must be restricted at the OWD level to prevent exposure to non-Health Cloud users.
Why not the others?
C . Set Account and Contract to Private
Regular business Accounts/Contracts are part of Service Cloud, not typically where PHI resides. Restricting them isn't required for PHI protection.
D . Set Contact to Controlled by Parent
Contacts in Health Cloud are often caregivers or providers, not patients (who are Person Accounts).
PHI protection centers around Person Accounts + Clinical Objects + Health Details, not Contacts.
Salesforce Health Cloud Reference:
* Salesforce Health Cloud Security and Sharing Guide:
"For HIPAA and other PHI compliance, set Person Accounts and Health Cloud clinical objects to Private or Controlled by Parent."
"Ensure Health Details are not exposed via default sharing."

The requirement is:
* Push patient medication updates to an external pharmacy immediately # This is an event-driven use case.
* Receive immediate confirmation about medication interactions from the pharmacy # This requires a synchronous call/response pattern.
The correct integration patterns are:
* A. Platform Event
* Best for real-time, event-driven notifications when medication information is updated in Health Cloud.
* Ensures the pharmacy receives updates as soon as they occur.
* D. Apex HTTP Callout
* Supports synchronous communication with external systems.
* Allows Health Cloud to send a request and receive an immediate confirmation/response about medication interactions from the pharmacy.
Why not the others?
* B. Industries ETL - This is for batch, large-volume data movement , not real-time event-driven updates or immediate confirmations.
* C. OmniStudio Integration Procedure - Great for orchestrating data retrieval/manipulation across systems, but it's not designed for event-driven updates with confirmation requirements.
Salesforce Health Cloud Reference:
# Salesforce Integration Patterns and Practices:
* "Use Platform Events for event-driven, near real-time messaging between Salesforce and external systems."
* "Use Apex callouts when Salesforce must send a request and wait for an immediate response."