Immediate synchronous request-and-reply integrations from Salesforce to an external system are achieved through Apex HTTP Callouts or OmniStudio Integration Procedures using HTTP Actions. OmniStudio separates presentation, guided interaction, Salesforce data access, and server-side orchestration through FlexCards, OmniScripts, DataRaptors/Data Mappers, and Integration Procedures. Integration Procedures provide server-side orchestration for OmniStudio, including calls to DataRaptors, Apex, and external REST services while minimizing client-side processing. From a solution-design perspective, the selection fits the requirement because it uses the Health Cloud capability or data model that directly represents the business need, rather than introducing a parallel custom structure or a feature intended for a different stage of the patient, member, provider, or payer lifecycle. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (OmniStudio Integration Procedure; Apex HTTP Callout) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Design - OmniStudio; Integration Procedure; Medication

===============