Salesforce Health Cloud Accredited Professional Practice Exams
Last updated on Oct 22,2026- Exam Code: Health Cloud Accredited Professional
- Exam Name: Salesforce Health Cloud Accredited Professional
- Certification Provider: Salesforce
- Latest update: Oct 22,2026
Question #81
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
- A . Set Health Details to Controlled by Parent or Private.
- B . Set Account and Contract to Private.
- C . Set Person Accounts to Private.
- D . Set Contact to Controlled by Parent.
- E . Set related clinical objects to Controlled by Parent or Private.
Correct Answer: A, C, E
A, C, E
Explanation:
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.
Reference: Salesforce Health Cloud Security Best Practices
A, C, E
Explanation:
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.
Reference: Salesforce Health Cloud Security Best Practices
Question #81
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
- A . Set Health Details to Controlled by Parent or Private.
- B . Set Account and Contract to Private.
- C . Set Person Accounts to Private.
- D . Set Contact to Controlled by Parent.
- E . Set related clinical objects to Controlled by Parent or Private.
Correct Answer: A, C, E
A, C, E
Explanation:
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.
Reference: Salesforce Health Cloud Security Best Practices
A, C, E
Explanation:
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.
Reference: Salesforce Health Cloud Security Best Practices
Question #83
A consultant is implementing Identity Verification for their customer’s customer service representatives and needs to add a new search parameter.
Which record should the consultant configure to accomplish this?
- A . Identity Verification Process Detail
- B . Identity Verification Parameter Item
- C . Verification Search Feature
- D . Linked Identity Search Detail
Correct Answer: B
B
Explanation:
To implement Identity Verification in Salesforce and add a new search parameter, the consultant needs to configure the Identity Verification Parameter Item record.
Key Details:
Identity Verification Parameter Item:
Purpose: Defines the parameters used in the identity verification process, such as name, email, phone, or custom attributes.
Configuration Steps:
Navigate to Identity Verification Parameter Item in Setup or the appropriate Health Cloud app.
Create or modify a record to include the new parameter, such as a specific field or custom attribute.
Link it to the corresponding Identity Verification Process Detail to ensure it’s utilized during verification.
Supporting Documentation:
Salesforce Health Cloud Admin Guide (help.salesforce.com)
Identity Verification Configuration Overview (developer.salesforce.com)
B
Explanation:
To implement Identity Verification in Salesforce and add a new search parameter, the consultant needs to configure the Identity Verification Parameter Item record.
Key Details:
Identity Verification Parameter Item:
Purpose: Defines the parameters used in the identity verification process, such as name, email, phone, or custom attributes.
Configuration Steps:
Navigate to Identity Verification Parameter Item in Setup or the appropriate Health Cloud app.
Create or modify a record to include the new parameter, such as a specific field or custom attribute.
Link it to the corresponding Identity Verification Process Detail to ensure it’s utilized during verification.
Supporting Documentation:
Salesforce Health Cloud Admin Guide (help.salesforce.com)
Identity Verification Configuration Overview (developer.salesforce.com)
Question #84
Bloomington Caregivers would like to share patient medication Information with an external pharmacy as soon as It Is updated in Bloomington Caregivers’ Health Cloud system. It would also like to receive an Immediate confirmation about any medication Interactions from the pharmacy.
Which two integration patterns should a consultant recommend? Choose 2 answers
- A . Industries ETL
- B . Platform Event
- C . OmniStudio Integration Procedure
- D . Apex HTTP Callout
Correct Answer: B, D
B, D
Explanation:
Bloomington Caregivers requires real-time integration for sharing medication updates with an external pharmacy and receiving immediate feedback. The recommended integration patterns are:
Platform Event:
Used for real-time, event-driven communication between Salesforce and external systems. Enables asynchronous updates, ensuring the pharmacy receives medication updates as they occur. Apex HTTP Callout:
Used for synchronous, real-time communication with external systems.
Allows Salesforce to call the pharmacy’s API to receive immediate feedback, such as medication interactions or confirmations.
How These Work Together:
Platform Events push medication updates from Health Cloud to the pharmacy system.
The pharmacy system processes the updates and uses an API endpoint in Salesforce, invoked through Apex HTTP Callouts, to send feedback on medication interactions.
Why Other Options Are Incorrect:
Industries ETL: Used for batch data processing, not real-time interactions.
OmniStudio Integration Procedure: While it supports complex integration scenarios, it is not optimized for real-time event-driven communication.
Reference: Platform Events in Salesforce
Apex Callouts Documentation
B, D
Explanation:
Bloomington Caregivers requires real-time integration for sharing medication updates with an external pharmacy and receiving immediate feedback. The recommended integration patterns are:
Platform Event:
Used for real-time, event-driven communication between Salesforce and external systems. Enables asynchronous updates, ensuring the pharmacy receives medication updates as they occur. Apex HTTP Callout:
Used for synchronous, real-time communication with external systems.
Allows Salesforce to call the pharmacy’s API to receive immediate feedback, such as medication interactions or confirmations.
How These Work Together:
Platform Events push medication updates from Health Cloud to the pharmacy system.
The pharmacy system processes the updates and uses an API endpoint in Salesforce, invoked through Apex HTTP Callouts, to send feedback on medication interactions.
Why Other Options Are Incorrect:
Industries ETL: Used for batch data processing, not real-time interactions.
OmniStudio Integration Procedure: While it supports complex integration scenarios, it is not optimized for real-time event-driven communication.
Reference: Platform Events in Salesforce
Apex Callouts Documentation
Question #85
An administrator at Bloomington Caregivers has received a change request to alter the appearance of the timeline so that it displays vertically instead of horizontally.
Which step should the administrator take when implementing this change request?
- A . Enable Timeline in Salesforce Setup, then configure and activate new timeline and add to the relevant Lightning record.
- B . Enable Timeline in Salesforce Setup, then set the toggle for vertical orientation to true to set all timeline orientations as vertical.
- C . Find the Timeline View Configuration for each relevant timeline in the Health Cloud – Lightning Admin app and change the orientation to vertical.
- D . Find the Timeline Orientation setting in Custom Metadata, which controls the orientation of all timelines, and change the value to vertical.
Correct Answer: C
C
Explanation:
To modify the timeline orientation in Health Cloud, administrators can adjust the Timeline View Configuration to display the timeline vertically.
Steps:
Access Timeline View Configuration:
Open the Health Cloud – Lightning Admin app in Salesforce. Locate Timeline View Configuration records. Edit the Configuration:
Select the relevant configuration for the timeline you wish to update. Change the orientation setting to Vertical. Save and activate the updated configuration. Verify the Changes:
Check the timeline in the respective Lightning record pages to ensure the vertical layout is applied.
Why Other Options Are Incorrect:
C
Explanation:
To modify the timeline orientation in Health Cloud, administrators can adjust the Timeline View Configuration to display the timeline vertically.
Steps:
Access Timeline View Configuration:
Open the Health Cloud – Lightning Admin app in Salesforce. Locate Timeline View Configuration records. Edit the Configuration:
Select the relevant configuration for the timeline you wish to update. Change the orientation setting to Vertical. Save and activate the updated configuration. Verify the Changes:
Check the timeline in the respective Lightning record pages to ensure the vertical layout is applied.
Why Other Options Are Incorrect:
Question #86
Bloomington Caregivers currently has the organization-wide default controlling patient access set to Private. A new respiratory therapist is being added to support a patient at Bloomington Caregivers,
and the therapist needs access to the patient’s data.
How should an administrator grant access to the respiratory therapist using out-of-the-box Health Cloud features?
- A . Add the respiratory therapist to the patient’s Account Team and default access will be automatically granted.
- B . Add the respiratory therapist to the patient’s Care Team and grant Read or Read/Write access as needed.
- C . Add the respiratory therapist to the patient’s Account Team and grant Read or Read/Write access as needed.
- D . Add the respiratory therapist to the patient’s Care Team and default access will be automatically granted.
Correct Answer: B
B
Explanation:
In Salesforce Health Cloud, granting access to patient data for healthcare providers or supporting personnel is efficiently managed through Care Teams.
Key Details:
Care Teams in Health Cloud:
A Care Team represents the group of professionals supporting a patient.
Access levels (Read or Read/Write) can be explicitly granted to Care Team members.
Implementation Steps:
Navigate to the patient’s record in Health Cloud.
Open the Care Team section and add the respiratory therapist.
Assign the appropriate Role (e.g., Respiratory Therapist).
Specify the required access level (Read or Read/Write).
Why Care Teams Are Preferred:
Specific Roles: Clearly defines the roles of individuals supporting the patient.
Access Flexibility: Provides fine-grained control over access to patient data.
Why Other Options Are Incorrect:
A and C (Account Team): Account Teams are not designed for patient care management and lack the granularity required for healthcare scenarios.
D (Care Team with Default Access): Default access is not automatically granted; permissions must be explicitly defined.
Supporting Documentation:
Manage Care Teams in Health Cloud (help.salesforce.com)
Role-Based Access in Health Cloud (developer.salesforce.com)
By leveraging Care Teams and assigning appropriate permissions, administrators can efficiently manage access to sensitive patient data while maintaining compliance with privacy regulations.
B
Explanation:
In Salesforce Health Cloud, granting access to patient data for healthcare providers or supporting personnel is efficiently managed through Care Teams.
Key Details:
Care Teams in Health Cloud:
A Care Team represents the group of professionals supporting a patient.
Access levels (Read or Read/Write) can be explicitly granted to Care Team members.
Implementation Steps:
Navigate to the patient’s record in Health Cloud.
Open the Care Team section and add the respiratory therapist.
Assign the appropriate Role (e.g., Respiratory Therapist).
Specify the required access level (Read or Read/Write).
Why Care Teams Are Preferred:
Specific Roles: Clearly defines the roles of individuals supporting the patient.
Access Flexibility: Provides fine-grained control over access to patient data.
Why Other Options Are Incorrect:
A and C (Account Team): Account Teams are not designed for patient care management and lack the granularity required for healthcare scenarios.
D (Care Team with Default Access): Default access is not automatically granted; permissions must be explicitly defined.
Supporting Documentation:
Manage Care Teams in Health Cloud (help.salesforce.com)
Role-Based Access in Health Cloud (developer.salesforce.com)
By leveraging Care Teams and assigning appropriate permissions, administrators can efficiently manage access to sensitive patient data while maintaining compliance with privacy regulations.
Question #86
Bloomington Caregivers currently has the organization-wide default controlling patient access set to Private. A new respiratory therapist is being added to support a patient at Bloomington Caregivers,
and the therapist needs access to the patient’s data.
How should an administrator grant access to the respiratory therapist using out-of-the-box Health Cloud features?
- A . Add the respiratory therapist to the patient’s Account Team and default access will be automatically granted.
- B . Add the respiratory therapist to the patient’s Care Team and grant Read or Read/Write access as needed.
- C . Add the respiratory therapist to the patient’s Account Team and grant Read or Read/Write access as needed.
- D . Add the respiratory therapist to the patient’s Care Team and default access will be automatically granted.
Correct Answer: B
B
Explanation:
In Salesforce Health Cloud, granting access to patient data for healthcare providers or supporting personnel is efficiently managed through Care Teams.
Key Details:
Care Teams in Health Cloud:
A Care Team represents the group of professionals supporting a patient.
Access levels (Read or Read/Write) can be explicitly granted to Care Team members.
Implementation Steps:
Navigate to the patient’s record in Health Cloud.
Open the Care Team section and add the respiratory therapist.
Assign the appropriate Role (e.g., Respiratory Therapist).
Specify the required access level (Read or Read/Write).
Why Care Teams Are Preferred:
Specific Roles: Clearly defines the roles of individuals supporting the patient.
Access Flexibility: Provides fine-grained control over access to patient data.
Why Other Options Are Incorrect:
A and C (Account Team): Account Teams are not designed for patient care management and lack the granularity required for healthcare scenarios.
D (Care Team with Default Access): Default access is not automatically granted; permissions must be explicitly defined.
Supporting Documentation:
Manage Care Teams in Health Cloud (help.salesforce.com)
Role-Based Access in Health Cloud (developer.salesforce.com)
By leveraging Care Teams and assigning appropriate permissions, administrators can efficiently manage access to sensitive patient data while maintaining compliance with privacy regulations.
B
Explanation:
In Salesforce Health Cloud, granting access to patient data for healthcare providers or supporting personnel is efficiently managed through Care Teams.
Key Details:
Care Teams in Health Cloud:
A Care Team represents the group of professionals supporting a patient.
Access levels (Read or Read/Write) can be explicitly granted to Care Team members.
Implementation Steps:
Navigate to the patient’s record in Health Cloud.
Open the Care Team section and add the respiratory therapist.
Assign the appropriate Role (e.g., Respiratory Therapist).
Specify the required access level (Read or Read/Write).
Why Care Teams Are Preferred:
Specific Roles: Clearly defines the roles of individuals supporting the patient.
Access Flexibility: Provides fine-grained control over access to patient data.
Why Other Options Are Incorrect:
A and C (Account Team): Account Teams are not designed for patient care management and lack the granularity required for healthcare scenarios.
D (Care Team with Default Access): Default access is not automatically granted; permissions must be explicitly defined.
Supporting Documentation:
Manage Care Teams in Health Cloud (help.salesforce.com)
Role-Based Access in Health Cloud (developer.salesforce.com)
By leveraging Care Teams and assigning appropriate permissions, administrators can efficiently manage access to sensitive patient data while maintaining compliance with privacy regulations.
Question #88
Bloomington Caregivers would like to bulk upload information to support Provider Search and Provider Relationship Card.
What are the two best practice recommendations to upload this information? Choose 2 answers
- A . Use Provider Relationship API.
- B . Use Provider Card API.
- C . Use Composite API Request.
- D . Use Data Loader.
Correct Answer: C, D
C, D
Explanation:
Bloomington Caregivers aims to bulk upload information to support Provider Search and the Provider Relationship Card in Salesforce Health Cloud. Implementing this requires populating various provider-related objects efficiently.
Two best practice methods for achieving this are:
C, D
Explanation:
Bloomington Caregivers aims to bulk upload information to support Provider Search and the Provider Relationship Card in Salesforce Health Cloud. Implementing this requires populating various provider-related objects efficiently.
Two best practice methods for achieving this are:
Question #89
During a design session, the client asks for best practices around when to use DataRaptors vs.
Integration Procedures.
For which scenario should a consultant advise the client to use a single DataRaptor?
- A . The dataset squired needs to read two SObjects with a clearly defined
- B . relationship.
- C . Q The action must perform a SendMail task and check for any errors.
- D . The task requires both a read and write of SObject data.
- E . The dataset requires connecting to an external data source, such as CSV or REST API,
Correct Answer: A
A
Explanation:
In Salesforce OmniStudio, DataRaptors and Integration Procedures are both tools designed to handle data operations, but they serve different purposes and are suited to distinct scenarios.
DataRaptors:
DataRaptors are declarative tools used to extract, transform, and load data to and from Salesforce objects. They are ideal for straightforward data operations involving a limited number of objects.
Integration Procedures:
Integration Procedures are server-side processes that execute multiple actions in a single server call. They are designed for complex data operations, especially those involving multiple data sources or requiring orchestration of various steps.
Scenario Analysis:
Option A: The dataset required needs to read two SObjects with a clearly defined relationship.
Approach: A single DataRaptor Extract can efficiently handle this scenario by utilizing relationship queries to retrieve data from two related SObjects. DataRaptors support extracting data from multiple objects, provided there is a defined relationship between them, such as a parent-child relationship.
Option B: The action must perform a SendMail task and check for any errors.
Approach: This scenario involves sending an email and handling error checking, which goes beyond simple data extraction or loading. An Integration Procedure would be more appropriate here, as it can orchestrate multiple actions, including sending emails and managing error handling.
Option C: The task requires both a read and write of SObject data.
Approach: While DataRaptors can perform both read (Extract) and write (Load) operations, if the task involves complex logic or multiple steps, an Integration Procedure might be more suitable to manage the orchestration of these actions.
Option D: The dataset requires connecting to an external data source, such as CSV or REST API.
Approach: Connecting to external data sources typically requires capabilities beyond DataRaptors. Integration Procedures can handle REST API calls and integrate external data, making them the appropriate choice for this scenario.
Best Practices:
Use DataRaptors When:
You need to perform simple CRUD operations on Salesforce data.
The data operations involve a limited number of related objects. Minimal transformation or processing logic is required. Use Integration Procedures When:
The process involves multiple steps or complex logic.
You need to integrate with external systems or APIs.
Error handling and conditional processing are necessary.
Reference: **OmniStudio
A
Explanation:
In Salesforce OmniStudio, DataRaptors and Integration Procedures are both tools designed to handle data operations, but they serve different purposes and are suited to distinct scenarios.
DataRaptors:
DataRaptors are declarative tools used to extract, transform, and load data to and from Salesforce objects. They are ideal for straightforward data operations involving a limited number of objects.
Integration Procedures:
Integration Procedures are server-side processes that execute multiple actions in a single server call. They are designed for complex data operations, especially those involving multiple data sources or requiring orchestration of various steps.
Scenario Analysis:
Option A: The dataset required needs to read two SObjects with a clearly defined relationship.
Approach: A single DataRaptor Extract can efficiently handle this scenario by utilizing relationship queries to retrieve data from two related SObjects. DataRaptors support extracting data from multiple objects, provided there is a defined relationship between them, such as a parent-child relationship.
Option B: The action must perform a SendMail task and check for any errors.
Approach: This scenario involves sending an email and handling error checking, which goes beyond simple data extraction or loading. An Integration Procedure would be more appropriate here, as it can orchestrate multiple actions, including sending emails and managing error handling.
Option C: The task requires both a read and write of SObject data.
Approach: While DataRaptors can perform both read (Extract) and write (Load) operations, if the task involves complex logic or multiple steps, an Integration Procedure might be more suitable to manage the orchestration of these actions.
Option D: The dataset requires connecting to an external data source, such as CSV or REST API.
Approach: Connecting to external data sources typically requires capabilities beyond DataRaptors. Integration Procedures can handle REST API calls and integrate external data, making them the appropriate choice for this scenario.
Best Practices:
Use DataRaptors When:
You need to perform simple CRUD operations on Salesforce data.
The data operations involve a limited number of related objects. Minimal transformation or processing logic is required. Use Integration Procedures When:
The process involves multiple steps or complex logic.
You need to integrate with external systems or APIs.
Error handling and conditional processing are necessary.
Reference: **OmniStudio
Question #90
An administrator for Health Cloud wants to ensure that the files in their full sandbox instance are encrypted.
Which encryption solution supports the encryption of files in this scenario?
- A . Classic Encryption
- B . Salesforce Shield
- C . Industry Data Security
- D . Salesforce Data Mask
Correct Answer: B
B
Explanation:
Salesforce Shield is a robust security suite designed to ensure data encryption, monitoring, and auditing compliance for sensitive data, including files stored in Salesforce. In a full sandbox environment where data encryption is crucial, Shield’s Platform Encryption is the ideal solution.
Features of Salesforce Shield Platform Encryption:
Encrypts files and attachments stored in Salesforce.
Protects sensitive data such as personally identifiable information (PII) to comply with regulations like HIPAA.
Ensures encryption persists even when files are exported or shared outside the Salesforce environment.
Why Other Options Are Incorrect:
Classic Encryption: Limited to custom text fields, lacks support for files or advanced use cases. Industry Data Security: Focused on data classification and access control, not encryption. Salesforce Data Mask: Used to mask data in sandboxes for testing, not encrypt files.
Reference: Salesforce Shield Platform Encryption Guide
Salesforce Security Guide
B
Explanation:
Salesforce Shield is a robust security suite designed to ensure data encryption, monitoring, and auditing compliance for sensitive data, including files stored in Salesforce. In a full sandbox environment where data encryption is crucial, Shield’s Platform Encryption is the ideal solution.
Features of Salesforce Shield Platform Encryption:
Encrypts files and attachments stored in Salesforce.
Protects sensitive data such as personally identifiable information (PII) to comply with regulations like HIPAA.
Ensures encryption persists even when files are exported or shared outside the Salesforce environment.
Why Other Options Are Incorrect:
Classic Encryption: Limited to custom text fields, lacks support for files or advanced use cases. Industry Data Security: Focused on data classification and access control, not encryption. Salesforce Data Mask: Used to mask data in sandboxes for testing, not encrypt files.
Reference: Salesforce Shield Platform Encryption Guide
Salesforce Security Guide