 Medication Management in Health Cloud enables providers to view all of a patient ' s prescription history in one place, supporting medication reconciliation and review for better health outcomes.

Extract:

“Use Medication Management to track and review patient prescriptions, past and present, ensuring a comprehensive view of medication history and supporting care team collaboration.”

( Source: Administer Health Cloud – Medication Management )

 Other options (Intelligent Appointment Management, Virtual Care, Integrated Care Management) do not provide comprehensive medication tracking.

Step-by-Step Explanation:

COPPA Requirements in Healthcare Applications:

Disclose privacy policy and obtain parental consent:

“Organizations must provide clear privacy notices to parents and obtain their consent before collecting any personal information from children under 13.”

— Reference: Salesforce Security Guide, COPPA Compliance

Obtain verified parental consent before collection/storage:

“Verified parental consent is a core requirement for COPPA, prior to collection and storage of children’s personal data.”

Implement security measures:

“Appropriate security controls and safeguards must be in place to protect children’s data as mandated by COPPA.”

Encryption:

While encryption is a best practice (option D), COPPA explicitly requires appropriate security but does not mandate encryption at rest and in transit as a specific requirement, though it is recommended.

Partner Compliance:

Option E refers to the implementation partner, but regulatory responsibility remains with the covered entity (Bloomington Caregivers) , not the partner.

The use case describes:

A UI component to display customer data → FlexCards

A link to start a process (build a new order) → OmniScript

Retrieving and displaying available products → DataRaptors (and often Integration Procedures if orchestration is needed).

Let’s map it step by step:

D. FlexCards → Used to display contextual customer data on the UI and provide clickable actions (like " Create New Order " ).

E. OmniScript → Guides the user through the order creation process , step by step (product selection, details, confirmation).

A. DataRaptors → Extract and load Salesforce data (e.g., retrieving available products, saving the order).

???? These three are the core capabilities needed .

Why not the others?

B. Integration Procedures – Helpful if the solution requires multiple data sources or orchestration , but the question doesn’t explicitly state external integration or complex orchestration. If data is all within Salesforce, DataRaptors are enough .

C. Document Generation – Used to create documents (PDFs, Word, etc.) , which isn’t part of this order creation flow.

Salesforce Health Cloud / OmniStudio Reference:

???? Salesforce OmniStudio Developer Guide

“ FlexCards present contextual information and actions in a UI component.”

“Use OmniScripts to guide users through business processes such as creating orders.”

“ DataRaptors retrieve, transform, and save Salesforce data for use in OmniScripts and FlexCards.”

To improve appointment scheduling and provide patient self-service, these three Health Cloud features should be configured:

Experience Cloud for Health Cloud :

Allows creation of patient-facing portals for self-service appointment booking and information access.

Extract:

“Experience Cloud enables self-service portals for patients, supporting appointment scheduling and other interactions.”

( Source: Administer Health Cloud – Experience Cloud )

Intelligent Appointment Management :

Offers advanced scheduling features and automation to reduce wait times and manual booking.

Extract:

“Intelligent Appointment Management in Health Cloud supports both self-service and agent-assisted scheduling workflows.”

( Source: Administer Health Cloud – Intelligent Appointment Management )

Provider Search :

Lets patients find the right clinic or provider based on specialty, availability, and other criteria.

Extract:

“Provider Search empowers patients to search for providers and book appointments online through self-service portals.”

( Source: Administer Health Cloud – Provider Search )

Why not A or D?

Intelligent Form Reader is used for document capture, not for scheduling or self-service.

Assessments and Recommendations are used for care management, not scheduling.

Step-by-Step Explanation:

Health Cloud Best Practice for Displaying Internal and External Data:

FlexCards (part of OmniStudio) can display data from multiple sources in a unified view on a patient record.

Integration Procedures connect to external systems and bring in data (e.g., from EHRs or other sources).

DataRaptors extract and transform Salesforce data for display and use in FlexCards.

Salesforce Documentation Reference:

“FlexCards can display internal Salesforce data and call Integration Procedures or DataRaptors to bring in external or standard object data.” — OmniStudio Standard Guide

“Integration Procedures are used to retrieve and update data from external systems and can be invoked directly from FlexCards or OmniScripts.” — OmniStudio Integration Procedures

“DataRaptors map Salesforce data to and from FlexCards and Integration Procedures, enabling seamless display of patient information.” — OmniStudio DataRaptors

Other Options:

Salesforce Flows : Good for automation but not for real-time display of combined external and internal data on record pages.

Visualforce Pages : Legacy solution, not recommended for modern Health Cloud patient page display, and does not natively integrate with OmniStudio tools.

The best answer is to leverage the FHIR R4 Patient API. Salesforce Healthcare API is designed to securely connect and interact with systems that use FHIR APIs, and FHIR is the healthcare standard for representing and exchanging electronic health records. The Healthcare API includes Administration resources such as Patient, Practitioner, Encounter, Organization, Location, and RelatedPerson, making the Patient API the correct out-of-the-box method for sharing patient information. Salesforce also documents that the API URL format aligns with the FHIR standard. MuleSoft accelerators and third-party AppExchange tools can be valid integration approaches, but they are not the most cost-effective out-of-the-box choice when the FHIR API already supports standardized healthcare data exchange. Building a custom API is unnecessary and increases cost, complexity, and maintenance.

The scenario involves collecting structured information (series of questions) from patients and automatically assigning a personalized care plan based on their answers.

Step-by-Step Reference:

Salesforce Surveys can be used to gather responses from patients post-discharge.

Extract:

“With Salesforce Surveys, care managers can send and record responses directly within Health Cloud, allowing structured data capture from patients.”

( Source: Administ er Health Cloud - Surveys )

Discovery Framework processes responses and triggers automated care plan assignments based on responses.

Extract:

“The Discovery Framework in Health Cloud enables dynamic question flows and recommendations, such as assigning care plans based on patient answers.”

( Source: Administer Health Cloud - Discovery Framework )

Combining these, care managers can capture structured data (Surveys) and drive workflow automation and personalization (Discovery Framework).