Bloomington Caregivers would like to display patient Information from both Salesforce standard objects and data from an external system. Which three…

To display patient information from both Salesforce standard objects and external systems on the

patient record page in Health Cloud, the most efficient approach involves leveraging declarative tools

from OmniStudio, such as Integration Procedures, FlexCards, and DataRaptors. These tools enable

seamless integration and visualization of data across systems.

1. Integration Procedures (Answer B):

Purpose:

Integration Procedures are server-side processes used to retrieve, transform, and orchestrate data

from Salesforce and external systems. They are ideal for connecting to external APIs or databases to

fetch real-time patient data.

Key Features:

Retrieve data from multiple sources, including Salesforce objects and external APIs.

Perform transformations and calculations before presenting the data.

Execute multiple actions in a single server call for improved performance.

Implementation Steps:

Design Integration Procedure: Configure actions to fetch data from standard Salesforce objects and

external systems via REST or SOAP API.

Connect External Systems: Use the External Services framework or Apex adapters to call external

APIs.

Output Data: Structure the data to be consumed by a FlexCard or a Lightning Web Component (LWC).

Reference:

Integration Procedures Overview

2. FlexCards (Answer D):

Purpose:

FlexCards are reusable, lightweight UI components that display data from Salesforce and external

systems. They provide a framework for creating dynamic and interactive visualizations on record

pages.

Key Features:

Aggregate data from multiple sources into a single, cohesive view.

Include actions like navigation, editing, or triggering Integration Procedures.

Display related data in context using customizable layouts.

Implementation Steps:

Design the FlexCard: Use the FlexCard Designer in OmniStudio to build the component with fields

and actions.

Bind Data Sources: Link the FlexCard to the data fetched by the Integration Procedure.

Deploy on Patient Record Page: Add the FlexCard to the Lightning App Builder for the patient record

page.

Reference:

FlexCards Overview

3. DataRaptors (Answer E):

Purpose:

DataRaptors are declarative tools used to extract, transform, and load data to and from Salesforce

objects. They handle data processing between the database and UI components like FlexCards.

Key Features:

Perform CRUD operations on Salesforce data.

Transform data using formulas, mappings, and default values.

Simplify interactions with Salesforce objects for components like FlexCards.

Implementation Steps:

Configure DataRaptors: Set up DataRaptor Extracts to pull data from Salesforce standard objects and

DataRaptor Loads to save updates.

Integrate with FlexCards: Use the output of DataRaptors as input to FlexCards for dynamic data

presentation.

Reference:

DataRaptors Overview

Why Other Options Are Less Relevant:

A. Salesforce Flows:

While Flows are powerful for automation and guided processes, they are not optimized for

displaying real-time, integrated data from external systems on a record page.

C. Visualforce Pages:

Visualforce is a legacy framework with limited flexibility compared to modern tools like FlexCards

and LWCs. It is not recommended for new implementations in Health Cloud.

Conclusion:

By combining Integration Procedures, FlexCards, and DataRaptors, Bloomington Caregivers can

efficiently display patient information from Salesforce standard objects and external systems on the

patient record page. This approach ensures a seamless user experience and streamlined data

integration.

Reference for Further Reading:

OmniStudio Guide

Data Integration in OmniStudio