A provider has moved an existing office to a new location and wants to ensure...

In an OmniStudio Integration Procedure, adding an Email Action within a Conditional Block (Execution Conditional Formula) ensures notification emails trigger under specific appointment location criteria. 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 an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. 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 (Add a Conditional Block.) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - OmniStudio; Integration Procedure

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