Which two data exchange standards support clinical data in Health Cloud?

Health Cloud natively aligns with HL7 FHIR R4 (Fast Healthcare Interoperability Resources) and supports legacy HL7 v2 messaging standards through MuleSoft accelerators. FHIR R4 provides standardized healthcare resources and REST-oriented semantics, reducing dependence on proprietary object structures when clinical data is exchanged with EHRs, payers, or other healthcare systems. 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 (HL7 v2; FHIR R4) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Design - FHIR

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