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 #51
A customer is looking to implement Discovery Framework to manage their intake and clinical assessments.
Which three capabilities should a consultant configure with Health Cloud out-of-the-box to enhance their assessment functionality? Choose 3 answers
- A . Adding a QR Code
- B . SMS Assessment Completion
- C . FHIR Question Bank
- D . Digital Signature Capture
- E . Using Previously Submitted Responses
Correct Answer: C, D, E
C, D, E
Explanation:
The Discovery Framework in Salesforce Health Cloud is designed to streamline intake and clinical assessment processes by leveraging configurable and reusable components.
Below is a detailed explanation of the correct options:
Correct Capabilities:
FHIR Question Bank (C):
Health Cloud supports the integration of FHIR (Fast Healthcare Interoperability Resources) standards for clinical data management.
The FHIR Question Bank allows healthcare organizations to utilize predefined, standards-compliant question sets for assessments. This ensures uniformity and compliance with healthcare regulations.
Digital Signature Capture (D):
Salesforce Health Cloud enables capturing digital signatures to confirm the completion and accuracy of assessments, which is often required for compliance or legal documentation.
Using Previously Submitted Responses (E):
Health Cloud supports dynamic assessments that can reference and reuse responses from previously submitted assessments. This enhances efficiency, prevents redundancy, and reduces patient burden.
Why Other Options Are Incorrect:
C, D, E
Explanation:
The Discovery Framework in Salesforce Health Cloud is designed to streamline intake and clinical assessment processes by leveraging configurable and reusable components.
Below is a detailed explanation of the correct options:
Correct Capabilities:
FHIR Question Bank (C):
Health Cloud supports the integration of FHIR (Fast Healthcare Interoperability Resources) standards for clinical data management.
The FHIR Question Bank allows healthcare organizations to utilize predefined, standards-compliant question sets for assessments. This ensures uniformity and compliance with healthcare regulations.
Digital Signature Capture (D):
Salesforce Health Cloud enables capturing digital signatures to confirm the completion and accuracy of assessments, which is often required for compliance or legal documentation.
Using Previously Submitted Responses (E):
Health Cloud supports dynamic assessments that can reference and reuse responses from previously submitted assessments. This enhances efficiency, prevents redundancy, and reduces patient burden.
Why Other Options Are Incorrect:
Question #52
When implementing Provider Search functionality, which two changes allow an external user to access search results? Choose 2 answers
- A . Use Experience Builder to add the Provider Search component to a page on the site.
- B . Create a sharing rule on the Care Provider Searchable Field object to share with external users.
- C . Give the site user profile Read access to the Care Provider Searchable Field object.
- D . Give the site user profile Read access to the Data Pipeline object.
Correct Answer: A, C
A, C
Explanation:
To enable external users to access Provider Search functionality, you need to make necessary changes to the Experience Cloud site and permissions:
Steps to Enable Provider Search for External Users:
Add the Provider Search Component to the Site (Option A):
Use Experience Builder to include the Provider Search Lightning Web Component on a public-facing page of the Experience Cloud site.
Steps:
Navigate to Experience Builder.
Drag and drop the Provider Search component onto a designated page.
Publish the site to make the component available to external users.
Grant Read Access to the Care Provider Searchable Field Object (Option C):
External users must have appropriate permissions to view the provider search results.
Steps:
Go to Setup > Profiles.
Edit the site user profile associated with the Experience Cloud site.
Grant Read access to the Care Provider Searchable Field object.
Save and assign the profile to the relevant users.
Additional Notes:
Sharing Rules (Not Necessary): Sharing rules are not required if the external user profile already has sufficient object-level access.
Data Pipeline Object (Not Relevant): The Data Pipeline object is not directly involved in enabling Provider Search functionality for external users.
Reference: Enable Provider Search in Health Cloud
Experience Cloud for Health Cloud
A, C
Explanation:
To enable external users to access Provider Search functionality, you need to make necessary changes to the Experience Cloud site and permissions:
Steps to Enable Provider Search for External Users:
Add the Provider Search Component to the Site (Option A):
Use Experience Builder to include the Provider Search Lightning Web Component on a public-facing page of the Experience Cloud site.
Steps:
Navigate to Experience Builder.
Drag and drop the Provider Search component onto a designated page.
Publish the site to make the component available to external users.
Grant Read Access to the Care Provider Searchable Field Object (Option C):
External users must have appropriate permissions to view the provider search results.
Steps:
Go to Setup > Profiles.
Edit the site user profile associated with the Experience Cloud site.
Grant Read access to the Care Provider Searchable Field object.
Save and assign the profile to the relevant users.
Additional Notes:
Sharing Rules (Not Necessary): Sharing rules are not required if the external user profile already has sufficient object-level access.
Data Pipeline Object (Not Relevant): The Data Pipeline object is not directly involved in enabling Provider Search functionality for external users.
Reference: Enable Provider Search in Health Cloud
Experience Cloud for Health Cloud
Question #53
What are three requirements for implementing patients or members in Health Cloud? Choose 3 answers
- A . Ensure the Parent Contact object is blank.
- B . Ensure the Parent Account field is blank.
- C . Ensure the Account is the Parent to Household Accounts.
- D . Ensure the Person Account object is used.
- E . Ensure 1-to-1 Account to Contact relationship.
Correct Answer: C, D, E
C, D, E
Explanation:
Implementing patients or members in Health Cloud requires careful configuration to accurately represent individual relationships and household structures.
C, D, E
Explanation:
Implementing patients or members in Health Cloud requires careful configuration to accurately represent individual relationships and household structures.
Question #54
Bloomington Caregivers has been using the legacy Health Cloud electronic health record (EHR) data model and wants to move to the FHIR R4 clinical data model.
Which two steps should a consultant take to complete this? Choose 2 answers
- A . Use the Health Cloud Clinical Transition tool.
- B . Use Data Loader to load the respective data.
- C . Map objects and Fields to the target objects.
- D . Leverage the Health Cloud FHIR API.
Correct Answer: A C
A C
Explanation:
Bloomington Caregivers is transitioning from the legacy Health Cloud Electronic Health Record (EHR) data model to the FHIR R4-aligned Clinical Data Model. This migration enhances interoperability and aligns with current healthcare data standards. The following steps are essential for a successful transition:
Utilize the Health Cloud Clinical Transition Tool (Answer A):
Purpose: Salesforce provides the Health Cloud Clinical Transition tool to facilitate the migration from the legacy EHR data model to the FHIR R4-aligned Clinical Data Model.
Functionality: This tool automates the migration process by mapping legacy EHR objects to their corresponding FHIR R4-aligned Clinical Data Model objects, ensuring data integrity and consistency.
Implementation Steps:
Preparation: Review existing data to identify the scope of migration and ensure data quality.
Execution: Run the Clinical Transition tool to perform the automated mapping and data migration.
Validation: Verify the migrated data to ensure accuracy and completeness.
Reference: For detailed guidance on using the Clinical Transition tool, refer to Salesforce’s official
documentation: Replacing the EHR Data Model with the Clinical Data Model.
Map Objects and Fields to the Target Objects (Answer C):
Purpose: Accurate mapping of legacy EHR objects and fields to the new Clinical Data Model is crucial for maintaining data integrity and ensuring seamless integration with other healthcare systems.
Implementation Steps:
Analysis: Identify all legacy EHR objects and fields that require migration.
Mapping: Determine the corresponding objects and fields in the FHIR R4-aligned Clinical Data Model.
Configuration: Set up the mappings within Salesforce, ensuring that data flows correctly into the new model.
Reference: Salesforce provides a comprehensive guide on mapping FHIR resources to Salesforce
standard objects: Mapping FHIR v4.0 to Salesforce Standard Objects.
Additional Considerations:
Data Loader Usage (Answer B):
While Data Loader is a powerful tool for bulk data operations, it is not specifically designed for complex data model transitions like this. Using the Clinical Transition tool is recommended for its specialized capabilities in handling such migrations.
Leveraging the Health Cloud FHIR API (Answer D):
The Health Cloud FHIR API is intended for integrating external systems with Salesforce using FHIR standards. It is not designed for internal data model migrations. Therefore, it is not applicable in this context.
Conclusion:
By utilizing the Health Cloud Clinical Transition tool and meticulously mapping objects and fields to the target FHIR R4-aligned Clinical Data Model, Bloomington Caregivers can achieve a seamless and efficient migration, enhancing data interoperability and aligning with modern healthcare standards.
A C
Explanation:
Bloomington Caregivers is transitioning from the legacy Health Cloud Electronic Health Record (EHR) data model to the FHIR R4-aligned Clinical Data Model. This migration enhances interoperability and aligns with current healthcare data standards. The following steps are essential for a successful transition:
Utilize the Health Cloud Clinical Transition Tool (Answer A):
Purpose: Salesforce provides the Health Cloud Clinical Transition tool to facilitate the migration from the legacy EHR data model to the FHIR R4-aligned Clinical Data Model.
Functionality: This tool automates the migration process by mapping legacy EHR objects to their corresponding FHIR R4-aligned Clinical Data Model objects, ensuring data integrity and consistency.
Implementation Steps:
Preparation: Review existing data to identify the scope of migration and ensure data quality.
Execution: Run the Clinical Transition tool to perform the automated mapping and data migration.
Validation: Verify the migrated data to ensure accuracy and completeness.
Reference: For detailed guidance on using the Clinical Transition tool, refer to Salesforce’s official
documentation: Replacing the EHR Data Model with the Clinical Data Model.
Map Objects and Fields to the Target Objects (Answer C):
Purpose: Accurate mapping of legacy EHR objects and fields to the new Clinical Data Model is crucial for maintaining data integrity and ensuring seamless integration with other healthcare systems.
Implementation Steps:
Analysis: Identify all legacy EHR objects and fields that require migration.
Mapping: Determine the corresponding objects and fields in the FHIR R4-aligned Clinical Data Model.
Configuration: Set up the mappings within Salesforce, ensuring that data flows correctly into the new model.
Reference: Salesforce provides a comprehensive guide on mapping FHIR resources to Salesforce
standard objects: Mapping FHIR v4.0 to Salesforce Standard Objects.
Additional Considerations:
Data Loader Usage (Answer B):
While Data Loader is a powerful tool for bulk data operations, it is not specifically designed for complex data model transitions like this. Using the Clinical Transition tool is recommended for its specialized capabilities in handling such migrations.
Leveraging the Health Cloud FHIR API (Answer D):
The Health Cloud FHIR API is intended for integrating external systems with Salesforce using FHIR standards. It is not designed for internal data model migrations. Therefore, it is not applicable in this context.
Conclusion:
By utilizing the Health Cloud Clinical Transition tool and meticulously mapping objects and fields to the target FHIR R4-aligned Clinical Data Model, Bloomington Caregivers can achieve a seamless and efficient migration, enhancing data interoperability and aligning with modern healthcare standards.
Question #54
Bloomington Caregivers has been using the legacy Health Cloud electronic health record (EHR) data model and wants to move to the FHIR R4 clinical data model.
Which two steps should a consultant take to complete this? Choose 2 answers
- A . Use the Health Cloud Clinical Transition tool.
- B . Use Data Loader to load the respective data.
- C . Map objects and Fields to the target objects.
- D . Leverage the Health Cloud FHIR API.
Correct Answer: A C
A C
Explanation:
Bloomington Caregivers is transitioning from the legacy Health Cloud Electronic Health Record (EHR) data model to the FHIR R4-aligned Clinical Data Model. This migration enhances interoperability and aligns with current healthcare data standards. The following steps are essential for a successful transition:
Utilize the Health Cloud Clinical Transition Tool (Answer A):
Purpose: Salesforce provides the Health Cloud Clinical Transition tool to facilitate the migration from the legacy EHR data model to the FHIR R4-aligned Clinical Data Model.
Functionality: This tool automates the migration process by mapping legacy EHR objects to their corresponding FHIR R4-aligned Clinical Data Model objects, ensuring data integrity and consistency.
Implementation Steps:
Preparation: Review existing data to identify the scope of migration and ensure data quality.
Execution: Run the Clinical Transition tool to perform the automated mapping and data migration.
Validation: Verify the migrated data to ensure accuracy and completeness.
Reference: For detailed guidance on using the Clinical Transition tool, refer to Salesforce’s official
documentation: Replacing the EHR Data Model with the Clinical Data Model.
Map Objects and Fields to the Target Objects (Answer C):
Purpose: Accurate mapping of legacy EHR objects and fields to the new Clinical Data Model is crucial for maintaining data integrity and ensuring seamless integration with other healthcare systems.
Implementation Steps:
Analysis: Identify all legacy EHR objects and fields that require migration.
Mapping: Determine the corresponding objects and fields in the FHIR R4-aligned Clinical Data Model.
Configuration: Set up the mappings within Salesforce, ensuring that data flows correctly into the new model.
Reference: Salesforce provides a comprehensive guide on mapping FHIR resources to Salesforce
standard objects: Mapping FHIR v4.0 to Salesforce Standard Objects.
Additional Considerations:
Data Loader Usage (Answer B):
While Data Loader is a powerful tool for bulk data operations, it is not specifically designed for complex data model transitions like this. Using the Clinical Transition tool is recommended for its specialized capabilities in handling such migrations.
Leveraging the Health Cloud FHIR API (Answer D):
The Health Cloud FHIR API is intended for integrating external systems with Salesforce using FHIR standards. It is not designed for internal data model migrations. Therefore, it is not applicable in this context.
Conclusion:
By utilizing the Health Cloud Clinical Transition tool and meticulously mapping objects and fields to the target FHIR R4-aligned Clinical Data Model, Bloomington Caregivers can achieve a seamless and efficient migration, enhancing data interoperability and aligning with modern healthcare standards.
A C
Explanation:
Bloomington Caregivers is transitioning from the legacy Health Cloud Electronic Health Record (EHR) data model to the FHIR R4-aligned Clinical Data Model. This migration enhances interoperability and aligns with current healthcare data standards. The following steps are essential for a successful transition:
Utilize the Health Cloud Clinical Transition Tool (Answer A):
Purpose: Salesforce provides the Health Cloud Clinical Transition tool to facilitate the migration from the legacy EHR data model to the FHIR R4-aligned Clinical Data Model.
Functionality: This tool automates the migration process by mapping legacy EHR objects to their corresponding FHIR R4-aligned Clinical Data Model objects, ensuring data integrity and consistency.
Implementation Steps:
Preparation: Review existing data to identify the scope of migration and ensure data quality.
Execution: Run the Clinical Transition tool to perform the automated mapping and data migration.
Validation: Verify the migrated data to ensure accuracy and completeness.
Reference: For detailed guidance on using the Clinical Transition tool, refer to Salesforce’s official
documentation: Replacing the EHR Data Model with the Clinical Data Model.
Map Objects and Fields to the Target Objects (Answer C):
Purpose: Accurate mapping of legacy EHR objects and fields to the new Clinical Data Model is crucial for maintaining data integrity and ensuring seamless integration with other healthcare systems.
Implementation Steps:
Analysis: Identify all legacy EHR objects and fields that require migration.
Mapping: Determine the corresponding objects and fields in the FHIR R4-aligned Clinical Data Model.
Configuration: Set up the mappings within Salesforce, ensuring that data flows correctly into the new model.
Reference: Salesforce provides a comprehensive guide on mapping FHIR resources to Salesforce
standard objects: Mapping FHIR v4.0 to Salesforce Standard Objects.
Additional Considerations:
Data Loader Usage (Answer B):
While Data Loader is a powerful tool for bulk data operations, it is not specifically designed for complex data model transitions like this. Using the Clinical Transition tool is recommended for its specialized capabilities in handling such migrations.
Leveraging the Health Cloud FHIR API (Answer D):
The Health Cloud FHIR API is intended for integrating external systems with Salesforce using FHIR standards. It is not designed for internal data model migrations. Therefore, it is not applicable in this context.
Conclusion:
By utilizing the Health Cloud Clinical Transition tool and meticulously mapping objects and fields to the target FHIR R4-aligned Clinical Data Model, Bloomington Caregivers can achieve a seamless and efficient migration, enhancing data interoperability and aligning with modern healthcare standards.
Question #56
A payer is implementing Health Cloud and wants to leverage predefined rules for its prior authorization request review process. The payer would like to leverage out-of-the-box Health Cloud functionality to drive speed to value.
Which prebuilt feature should a consultant recommend the payer leverage?
- A . Integration Procedures
- B . Expression Set Templates
- C . FlexCards
- D . OmmScript Templates
Correct Answer: B
B
Explanation:
For a payer implementing Health Cloud, leveraging predefined rules for prior authorization reviews can significantly improve efficiency and speed. Salesforce Health Cloud provides Expression Set Templates as an out-of-the-box feature to achieve this.
Key Features of Expression Set Templates:
Predefined Rules:
Expression Set Templates come with prebuilt rule sets that can evaluate conditions, making them ideal for automating prior authorization request reviews.
Customizable Logic:
While they provide predefined logic, templates can also be customized to align with specific payer policies or regulatory requirements.
Faster Implementation:
Using out-of-the-box templates accelerates time-to-value, as they require minimal configuration compared to building rules from scratch.
Why Other Options Are Less Suitable:
B
Explanation:
For a payer implementing Health Cloud, leveraging predefined rules for prior authorization reviews can significantly improve efficiency and speed. Salesforce Health Cloud provides Expression Set Templates as an out-of-the-box feature to achieve this.
Key Features of Expression Set Templates:
Predefined Rules:
Expression Set Templates come with prebuilt rule sets that can evaluate conditions, making them ideal for automating prior authorization request reviews.
Customizable Logic:
While they provide predefined logic, templates can also be customized to align with specific payer policies or regulatory requirements.
Faster Implementation:
Using out-of-the-box templates accelerates time-to-value, as they require minimal configuration compared to building rules from scratch.
Why Other Options Are Less Suitable:
Question #57
A provider wants to set up a Contact Center leveraging Health Cloud to enable its patients to set up appointments, get answers to their billing questions, and update their plan information.
Which group of people should a consultant work with to identify pain points and define project requirements?
- A . (Persona) Care coordinator
(Stakeholder) Salesforce administrator (Stakeholder) Tableau developer - B . (Persona) Contact Center agent
(Stakeholder) Salesforce administrator (Stakeholder) Integration architect - C . (Persona) Contact Center agent (Stakeholder) Tableau developer (Stakeholder) MuleSoft developer
- D . (Persona) General physician
(Stakeholder) Salesforce administrator (Stakeholder) Marketing Cloud administrator
Correct Answer: B
B
Explanation:
For implementing a Contact Center leveraging Health Cloud, identifying pain points and defining project requirements involves collaborating with:
Contact Center Agent (Persona):
Frontline staff who interact directly with patients.
Provide insights into the day-to-day challenges in appointment scheduling, billing inquiries, and plan updates.
Salesforce Administrator (Stakeholder):
Responsible for configuring Health Cloud and implementing workflows to address identified pain points.
Integration Architect (Stakeholder):
Ensures smooth integration between Health Cloud and external systems like billing platforms or insurance providers.
Why Other Options Are Incorrect:
A: Care coordinators are not directly involved in patient-initiated contact center interactions. Tableau developers focus on reporting, not operational processes.
C: MuleSoft developers are not primary stakeholders for contact center operations.
D: General physicians and Marketing Cloud administrators do not contribute directly to Contact Center workflows.
Reference: Health Cloud Contact Center Overview
Integration Architecture Guide
B
Explanation:
For implementing a Contact Center leveraging Health Cloud, identifying pain points and defining project requirements involves collaborating with:
Contact Center Agent (Persona):
Frontline staff who interact directly with patients.
Provide insights into the day-to-day challenges in appointment scheduling, billing inquiries, and plan updates.
Salesforce Administrator (Stakeholder):
Responsible for configuring Health Cloud and implementing workflows to address identified pain points.
Integration Architect (Stakeholder):
Ensures smooth integration between Health Cloud and external systems like billing platforms or insurance providers.
Why Other Options Are Incorrect:
A: Care coordinators are not directly involved in patient-initiated contact center interactions. Tableau developers focus on reporting, not operational processes.
C: MuleSoft developers are not primary stakeholders for contact center operations.
D: General physicians and Marketing Cloud administrators do not contribute directly to Contact Center workflows.
Reference: Health Cloud Contact Center Overview
Integration Architecture Guide
Question #58
A payer receives faxes for clinical review as part of the determination process. The payer needs Health Cloud to automatically capture the data from the documents received from patients and manage the end-to-end approval process.
Which two Health Cloud capabilities should a consultant recommend as a way to build this process? Choose 2 answers
- A . Utilization Management
- B . Integrated Care Management
- C . Intelligent Document Automation
- D . Care Authorizations
Correct Answer: A, C
A, C
Explanation:
To automate the capture of data from faxes for clinical reviews and manage the approval process in Salesforce Health Cloud, the following capabilities are recommended:
A, C
Explanation:
To automate the capture of data from faxes for clinical reviews and manage the approval process in Salesforce Health Cloud, the following capabilities are recommended:
Question #58
A payer receives faxes for clinical review as part of the determination process. The payer needs Health Cloud to automatically capture the data from the documents received from patients and manage the end-to-end approval process.
Which two Health Cloud capabilities should a consultant recommend as a way to build this process? Choose 2 answers
- A . Utilization Management
- B . Integrated Care Management
- C . Intelligent Document Automation
- D . Care Authorizations
Correct Answer: A, C
A, C
Explanation:
To automate the capture of data from faxes for clinical reviews and manage the approval process in Salesforce Health Cloud, the following capabilities are recommended:
A, C
Explanation:
To automate the capture of data from faxes for clinical reviews and manage the approval process in Salesforce Health Cloud, the following capabilities are recommended:
Question #60
A MedTech company is implementing Health Cloud to better plan and track surgical case visits, manage device inventory, and run cycle counts.
Which data model should a consultant recommend the company use?
- A . Intelligent Sales
- B . Inventory Management
- C . Life Sciences
- D . Provider Engagement
Correct Answer: C
C
Explanation:
The Life Sciences data model in Salesforce Health Cloud is specifically designed to meet the needs of MedTech companies. It includes features for planning and tracking surgical case visits, managing medical device inventory, and conducting cycle counts, making it ideal for this use case.
Key Features of the Life Sciences Data Model:
Surgical Case Management: Tracks and plans surgical procedures, including device requirements and associated logistics.
Device Inventory Management: Manages medical device stock, including availability, usage, and maintenance schedules.
Cycle Counts: Ensures inventory accuracy through routine counting and tracking.
Why Other Options Are Incorrect:
Intelligent Sales: Focuses on sales processes, not surgical or inventory management.
Inventory Management: Generic inventory features lack the healthcare-specific capabilities provided by the Life Sciences model.
Provider Engagement: Centers around provider relationship management rather than surgical and inventory processes.
Reference: Life Sciences Cloud Documentation
Surgical Case Management Features
C
Explanation:
The Life Sciences data model in Salesforce Health Cloud is specifically designed to meet the needs of MedTech companies. It includes features for planning and tracking surgical case visits, managing medical device inventory, and conducting cycle counts, making it ideal for this use case.
Key Features of the Life Sciences Data Model:
Surgical Case Management: Tracks and plans surgical procedures, including device requirements and associated logistics.
Device Inventory Management: Manages medical device stock, including availability, usage, and maintenance schedules.
Cycle Counts: Ensures inventory accuracy through routine counting and tracking.
Why Other Options Are Incorrect:
Intelligent Sales: Focuses on sales processes, not surgical or inventory management.
Inventory Management: Generic inventory features lack the healthcare-specific capabilities provided by the Life Sciences model.
Provider Engagement: Centers around provider relationship management rather than surgical and inventory processes.
Reference: Life Sciences Cloud Documentation
Surgical Case Management Features