Salesforce Updated Health-Cloud-Accredited-Professional Exam Questions and Answers by sasha

The scenario is about sending patients’ visit information from Health Cloud to an ERP system on a weekly billing cycle.

This is a scheduled, bulk-data transfer requirement (not real-time, not request/response).

The correct integration pattern here is a batch extract using an ETL tool.

ETL tools (like Informatica, Mulesoft, Talend) are best for handling scheduled bulk data movement between Salesforce and external systems, especially for billing cycles.

The process can be scheduled nightly/weekly to pull visit data and send it to the ERP system.

Why not the others?

A. Fire and Forget with ESB – Used for real-time event-driven messaging (e.g., when an event happens, send a message immediately). Not needed here since the requirement is weekly batch.

C. ERP system to call the FHIR Billing API in Health Cloud – This would make sense if the ERP were pulling billing records via FHIR APIs, but here the need is sending visit data from Salesforce → ERP in bulk.

D. Request and Reply with ESB – Used when an external system calls Salesforce and expects an immediate response. Not applicable for scheduled, large-scale billing exports.

Salesforce Health Cloud Reference:

???? Salesforce Health Cloud Integration Guide:

“For billing, claims, or other periodic back-office processes, use a batch integration pattern with an ETL tool to extract large volumes of patient and encounter data from Salesforce on a scheduled basis.”

Salesforce Integration Patterns and Practices

Salesforce Health Cloud Data Exchange

Video Visits for Social Determinants of Health (SDOH):

Exact Extract:

“Use Virtual Care in Health Cloud to enable video visits between care providers and patients, including for conversations about social and economic factors.”