Step 1: Requirement Analysis
Bloomington Caregivers wants to share a patient's medical condition details with a local hospital through integration. The recommended method must leverage Health Cloud functionality for standardized, interoperable health data sharing.
Step 2: Salesforce Health Cloud FHIR API
Health Cloud provides native support for the FHIR (Fast Healthcare Interoperability Resources) APIs to facilitate seamless and standardized clinical data exchange (including medical conditions, allergies, medications, etc.) with external systems.
Extract:
"Health Cloud supports the FHIR standard and provides FHIR APIs for accessing and sharing clinical data such as conditions, observations, and encounters with external health systems." Administer Health Cloud - FHIR APIs Step 3: Review of Options A . Expose the MedicalCondition object through an Apex class: Not standards-based; not recommended for clinical interoperability.
B . Use the FHIR Patient API through DataRaptor: DataRaptor is an OmniStudio tool for extracting data, but not specifically for FHIR API access.
C . Leverage the MedicalCondition Integration Procedure: Integration Procedures are used for orchestrating APIs but are not directly the mechanism for sharing FHIR data externally.
D . integrate using the FHIR Clinical API: Correct - aligns with healthcare interoperability standards and Health Cloud's FHIR support.
Reference:
Health Cloud FHIR API Documentation
Omnistudio Standard Guide

To ensure a provider can create and view Salesforce reports analyzing patient outcomes and referrals, the following steps are required:
A . Create custom report types for clinical objects.
Health Cloud clinical data (e.g., patient outcomes, referrals, care plans) resides in custom objects.
To report on them, you must create custom report types.
D . Enable the enhanced Analytics for Healthcare setting in Setup.
This setting provides preconfigured reports and dashboards tailored for healthcare, such as referrals, utilization, and outcomes reporting.
E . Assign appropriate permissions to internal users.
Providers need the correct Health Cloud and reporting permissions to access and run these reports.
Without appropriate object-level and FLS permissions, reports won't display the necessary data.
Why not the others?
B . Leverage the Patient Referral Management unmanaged package - Referral management is now native in Health Cloud. The unmanaged package was used in early versions but is deprecated and not recommended.
C . Adjust template care management reports and dashboards - These are useful but do not provide referral and outcome reporting by themselves. Customization and proper report type setup are still required.
Salesforce Health Cloud Reference:
Salesforce Health Cloud Implementation Guide - Reports and Dashboards:
"Enable Enhanced Analytics for Healthcare to access out-of-the-box reports and dashboards for referrals, utilization management, and patient outcomes."
"Create custom report types for Health Cloud clinical objects to extend reporting capabilities."
"Ensure users have the appropriate object and field permissions to run reports.

The Patient Medication Manager component in Salesforce Health Cloud surfaces data from FHIR-aligned medication objects. When customers request field updates on this UI component, the consultant can configure fields from the underlying objects.
A . Medication Details → Stores key information about a patient's medications. Fields from this object can be exposed or customized on the Patient Medication Manager.
C . Medication Request → Represents a provider's request or order for a medication. Fields from this object are also available to configure in the Patient Medication Manager.
Together, these two objects form the basis of what's displayed and editable in the Patient Medication Manager.
Why not the others?
B . Medication Dispense - Tracks when and how a medication was dispensed. It is not directly configurable for field-level updates in the Patient Medication Manager component.
D . Medication Strength - Captures clinical details about dosage strength, but it isn't one of the configurable objects in the Patient Medication Manager UI.
Salesforce Health Cloud Reference:
Salesforce Health Cloud Medication Management:
"The Patient Medication Manager component displays information from Medication Details and Medication Request objects. Administrators can add or remove fields from these objects to tailor the component."

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

Out-of-the-box caller authentication in Health Cloud is primarily supported through Identity Verification Flow Templates. These flow templates are designed to help organizations comply with HIPAA and other regulatory requirements by standardizing the caller verification process for contact center agents.
Step-by-Step Reference:
Health Cloud provides Identity Verification Flow Templates that streamline the authentication of callers, reducing manual processes and ensuring regulatory compliance.
Extract:
"Use the Health Cloud Identity Verification Flow Templates to verify a caller's identity based on information you select, such as date of birth, phone number, or other criteria." (Source: Administer Health Cloud) These templates can be deployed as standard flows and easily customized for the organization's authentication requirements.
Extract:
"Leverage out-of-the-box Identity Verification Flow Templates to quickly set up and deploy identity verification processes in your contact center." (Source: Administer Health Cloud - Identity Verification) This approach is preferred over FlexCards, OmniScripts, or ad-hoc processes, as it provides a compliant and guided experience.