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 #121
Bloomington Caregivers has replaced its legacy Contact Center application with Health Cloud. During user acceptance testing (UAT), the call center team is reporting differences between current Identity Verification business processes and what was built in Health Cloud.
The call center manager has requested the following changes:
• Birth Date be available in results and as an optional verifier, but no longer required for verification purposes
• Add ‘Bloomington ID’, a custom field on Account, to search results and as a required verifier
What should a consultant do to meet these requirements?
- A . Add ‘Bloomington ID’ to the picklist choices within the Identity Verification flow
and mark it as required. Remove the Birth Date record from the required fields picklist and add Birth Date to the optional verifiers picklist. - B . Add two new Identity Verification Process Field records for ‘Bloomington ID’. Set the Field Type to Result Field and set the Required field to true. Add the new record to the Lightning component parameters in the identity flow screen in Flow Builder.
- C . Add two new Identity Verification Process Field records for ‘Bloomington ID’; one with Field Type set to Result Field and one with Field Type set to Required Verifier. Change the Birth Date record with Field Type value Required Verifier to Optional Verifier.
- D . Add two new Identity Verification Process Field records for ‘Bloomington ID’; one with the Field Type set to Result Field and one with Field Type set to Optional Verifier. Delete the Birth Date record which has the Field Type value Required Verifier.
Correct Answer: C
C
Explanation:
In Salesforce Health Cloud, Identity Verification Processes allow you to configure how patient or contact identities are verified during interactions. The requirements from the call center team involve modifying the verification process to:
Include "Bloomington ID":
This custom field should be added as a required verifier and also included in search results.
Modify "Birth Date":
Remove it as a required verifier while keeping it available as an optional verifier in the process.
Steps to Implement the Solution:
Add Two New Identity Verification Process Field Records for ‘Bloomington ID’:
Field Type: Result Field: Ensures the field appears in the search results.
Field Type: Required Verifier: Makes this field mandatory for identity verification.
Modify Birth Date Record:
Update the existing record for Birth Date by changing its Field Type from "Required Verifier" to "Optional Verifier." This adjustment makes the field optional in the verification process.
This approach ensures the flexibility and compliance requested by the call center manager while aligning with Salesforce Health Cloud’s configurable Identity Verification features.
Reference: Administer Health Cloud
Flow Builder Documentation for Identity Verification
C
Explanation:
In Salesforce Health Cloud, Identity Verification Processes allow you to configure how patient or contact identities are verified during interactions. The requirements from the call center team involve modifying the verification process to:
Include "Bloomington ID":
This custom field should be added as a required verifier and also included in search results.
Modify "Birth Date":
Remove it as a required verifier while keeping it available as an optional verifier in the process.
Steps to Implement the Solution:
Add Two New Identity Verification Process Field Records for ‘Bloomington ID’:
Field Type: Result Field: Ensures the field appears in the search results.
Field Type: Required Verifier: Makes this field mandatory for identity verification.
Modify Birth Date Record:
Update the existing record for Birth Date by changing its Field Type from "Required Verifier" to "Optional Verifier." This adjustment makes the field optional in the verification process.
This approach ensures the flexibility and compliance requested by the call center manager while aligning with Salesforce Health Cloud’s configurable Identity Verification features.
Reference: Administer Health Cloud
Flow Builder Documentation for Identity Verification
Question #122
How should a consultant recommend modeling a physician’s locations of service, when the physician practices at multiple hospitals and clinics?
- A . Healthcare Practitioner Facility
- B . Healthcare Taxonomy
- C . Healthcare Provider Relationship
- D . Account Contact Relationship
Correct Answer: A
A
Explanation:
The Healthcare Practitioner Facility object in Salesforce Health Cloud allows modeling of a physician’s locations of service. It captures relationships between healthcare practitioners and the facilities (hospitals, clinics, etc.) where they practice.
Key Features of Healthcare Practitioner Facility:
Multiple Locations: Tracks all locations where a physician practices.
Relationships: Links practitioners to facilities, ensuring accurate mapping of service areas.
Operational Benefits: Facilitates scheduling, referrals, and care coordination by providing accurate location data.
Why Other Options Are Incorrect:
Healthcare Taxonomy: Used to classify healthcare providers based on specialties and services, not locations.
Healthcare Provider Relationship: Tracks relationships between healthcare organizations or facilities, not individual physician locations.
Account Contact Relationship: Provides a general relationship mapping but lacks the specificity required for modeling service locations.
Reference: Health Cloud Data Model for Practitioners and Facilities
A
Explanation:
The Healthcare Practitioner Facility object in Salesforce Health Cloud allows modeling of a physician’s locations of service. It captures relationships between healthcare practitioners and the facilities (hospitals, clinics, etc.) where they practice.
Key Features of Healthcare Practitioner Facility:
Multiple Locations: Tracks all locations where a physician practices.
Relationships: Links practitioners to facilities, ensuring accurate mapping of service areas.
Operational Benefits: Facilitates scheduling, referrals, and care coordination by providing accurate location data.
Why Other Options Are Incorrect:
Healthcare Taxonomy: Used to classify healthcare providers based on specialties and services, not locations.
Healthcare Provider Relationship: Tracks relationships between healthcare organizations or facilities, not individual physician locations.
Account Contact Relationship: Provides a general relationship mapping but lacks the specificity required for modeling service locations.
Reference: Health Cloud Data Model for Practitioners and Facilities
Question #123
When accessing a person account record within Health Cloud, the user must have access to the entire account.
What should a consultant do in this scenario, according to Health Cloud implementation best practice?
- A . Set Modify All on the Account object at the Profile level.
- B . Set Private for the Contact object.
- C . Set Contacts to Controlled by Parent.
- D . Set the organization-wide default to Public Read Write for the Account object.
Correct Answer: C
C
Explanation:
In Salesforce Health Cloud, Person Accounts represent a combination of Account and Contact records. Ensuring that a user accessing a Person Account has appropriate access to both the Account and associated Contact is essential for seamless functionality.
Controlled by Parent Setting:
When Contacts are set to Controlled by Parent, the access to Contact records is directly inherited from the parent Account. This simplifies access management, ensuring that if a user has access to the Account, they automatically gain equivalent access to its associated Contact records.
This approach aligns with Health Cloud’s best practices for managing Person Accounts, where consistent access to both the Account and Contact components of a Person Account is crucial.
Why Not the Other Options?
C
Explanation:
In Salesforce Health Cloud, Person Accounts represent a combination of Account and Contact records. Ensuring that a user accessing a Person Account has appropriate access to both the Account and associated Contact is essential for seamless functionality.
Controlled by Parent Setting:
When Contacts are set to Controlled by Parent, the access to Contact records is directly inherited from the parent Account. This simplifies access management, ensuring that if a user has access to the Account, they automatically gain equivalent access to its associated Contact records.
This approach aligns with Health Cloud’s best practices for managing Person Accounts, where consistent access to both the Account and Contact components of a Person Account is crucial.
Why Not the Other Options?
Question #123
When accessing a person account record within Health Cloud, the user must have access to the entire account.
What should a consultant do in this scenario, according to Health Cloud implementation best practice?
- A . Set Modify All on the Account object at the Profile level.
- B . Set Private for the Contact object.
- C . Set Contacts to Controlled by Parent.
- D . Set the organization-wide default to Public Read Write for the Account object.
Correct Answer: C
C
Explanation:
In Salesforce Health Cloud, Person Accounts represent a combination of Account and Contact records. Ensuring that a user accessing a Person Account has appropriate access to both the Account and associated Contact is essential for seamless functionality.
Controlled by Parent Setting:
When Contacts are set to Controlled by Parent, the access to Contact records is directly inherited from the parent Account. This simplifies access management, ensuring that if a user has access to the Account, they automatically gain equivalent access to its associated Contact records.
This approach aligns with Health Cloud’s best practices for managing Person Accounts, where consistent access to both the Account and Contact components of a Person Account is crucial.
Why Not the Other Options?
C
Explanation:
In Salesforce Health Cloud, Person Accounts represent a combination of Account and Contact records. Ensuring that a user accessing a Person Account has appropriate access to both the Account and associated Contact is essential for seamless functionality.
Controlled by Parent Setting:
When Contacts are set to Controlled by Parent, the access to Contact records is directly inherited from the parent Account. This simplifies access management, ensuring that if a user has access to the Account, they automatically gain equivalent access to its associated Contact records.
This approach aligns with Health Cloud’s best practices for managing Person Accounts, where consistent access to both the Account and Contact components of a Person Account is crucial.
Why Not the Other Options?
Question #125
Which Health Cloud feature helps ensure compliance with Health Insurance Portability and Accountability Act (HIPAA) regulations?
- A . Data visualization and analytics
- B . Social media integration
- C . User authentication and access control
- D . Real-time monitoring and alerts
Correct Answer: C
C
Explanation:
Salesforce Health Cloud includes several features to ensure compliance with regulations like the Health Insurance Portability and Accountability Act (HIPAA). Among these, user authentication and access control is a key feature that safeguards protected health information (PHI) by controlling and restricting access based on user roles, permissions, and organizational policies.
Why User Authentication and Access Control is Key for HIPAA Compliance:
Role-Based Access Control (RBAC):
Salesforce allows administrators to define and manage access through role hierarchies and sharing rules. Only authorized users can view, edit, or process sensitive health data.
Shield Platform Encryption:
Salesforce Shield provides encryption capabilities for PHI. It ensures data remains secure at rest and during transit, an essential requirement of HIPAA.
Audit Trails and Field Tracking:
Salesforce Health Cloud tracks changes to sensitive data fields, offering detailed logs for auditing purposes.
Two-Factor Authentication (2FA):
2FA ensures only authenticated users access the system, adding an extra layer of security to sensitive health information.
Compliance Policies:
Salesforce’s built-in compliance tools, like health data masking and logging, align with HIPAA requirements.
Why Other Options Are Incorrect:
C
Explanation:
Salesforce Health Cloud includes several features to ensure compliance with regulations like the Health Insurance Portability and Accountability Act (HIPAA). Among these, user authentication and access control is a key feature that safeguards protected health information (PHI) by controlling and restricting access based on user roles, permissions, and organizational policies.
Why User Authentication and Access Control is Key for HIPAA Compliance:
Role-Based Access Control (RBAC):
Salesforce allows administrators to define and manage access through role hierarchies and sharing rules. Only authorized users can view, edit, or process sensitive health data.
Shield Platform Encryption:
Salesforce Shield provides encryption capabilities for PHI. It ensures data remains secure at rest and during transit, an essential requirement of HIPAA.
Audit Trails and Field Tracking:
Salesforce Health Cloud tracks changes to sensitive data fields, offering detailed logs for auditing purposes.
Two-Factor Authentication (2FA):
2FA ensures only authenticated users access the system, adding an extra layer of security to sensitive health information.
Compliance Policies:
Salesforce’s built-in compliance tools, like health data masking and logging, align with HIPAA requirements.
Why Other Options Are Incorrect:
Question #126
A provider wants to get a comprehensive view of a patient’s prescriptions, including history, to improve health outcomes.
Which Health Cloud capability should a consultant leverage to assist the provider?
- A . Virtual Care
- B . Integrated Care Management
- C . Medication Management
- D . Intelligent Appointment Management
Correct Answer: C
C
Explanation:
For a provider to gain a comprehensive view of a patient’s prescriptions and history, Salesforce Health Cloud’s Medication Management capability is the best solution.
Key Features of Medication Management:
Comprehensive Prescription Tracking:
Provides a unified view of a patient’s current medications, prescription history, and dosages.
Facilitates collaboration across care teams to monitor adherence and prevent adverse drug interactions.
Improving Health Outcomes:
Enables providers to assess medication efficacy and make informed adjustments to treatment plans.
Identifies gaps in prescription adherence to improve patient outcomes.
FHIR-Standard Data Compatibility:
Supports FHIR resources like MedicationRequest and MedicationStatement for integrating with EHR systems.
Why Other Options Are Less Relevant:
C
Explanation:
For a provider to gain a comprehensive view of a patient’s prescriptions and history, Salesforce Health Cloud’s Medication Management capability is the best solution.
Key Features of Medication Management:
Comprehensive Prescription Tracking:
Provides a unified view of a patient’s current medications, prescription history, and dosages.
Facilitates collaboration across care teams to monitor adherence and prevent adverse drug interactions.
Improving Health Outcomes:
Enables providers to assess medication efficacy and make informed adjustments to treatment plans.
Identifies gaps in prescription adherence to improve patient outcomes.
FHIR-Standard Data Compatibility:
Supports FHIR resources like MedicationRequest and MedicationStatement for integrating with EHR systems.
Why Other Options Are Less Relevant: