Explanation:

A. Install the Health Cloud Care Request Extensions unmanaged package ❌
This is outdated. Earlier pilots used unmanaged Care Request Extensions, but the supported setup today uses Utilization Management Extensions, not Care Request Extensions.

B. Assign PSLs to Salesforce Classic users ❌
UM is supported only in Lightning Experience. Assigning PSLs to Classic users won’t meet requirements.

C. Assign PSLs to Salesforce Lightning users ✅
To access UM features, users need:
Health Cloud Permission Set License
Health Cloud Platform Permission Set License
And then the Health Cloud Utilization Management Permission Set.
This is required for Lightning users (UM does not run in Classic).

D. Install the Utilization Management Extensions ✅
The UM package must be installed to enable features like authorizations, review processes, determinations, and appeals.
This is a key part of setup.

Reference:
Salesforce Help: Set Up Utilization Management
Steps include installing the Utilization Management Extensions and assigning Health Cloud + Platform PSLs to users in Lightning.

⚡ Exam Tip:
If you see Classic users in UM questions → wrong (UM is Lightning only).
If you see Care Request Extensions → outdated, correct answer is Utilization Management Extensions.

Explanation:

To successfully implement Utilization Management in Health Cloud, the admin must complete both feature activation and user access configuration steps. Here's why the correct answers are essential:
✅ C. Assign the Health Cloud Permission Set License and the Health Cloud Platform Permission Set License to Salesforce Lightning users
Utilization Management is only supported in Lightning Experience, and users must be provisioned with the correct licenses to access features like:
Prior authorization workflows
OmniStudio-based guided processes
Care request record types and layouts
Assigning both the Health Cloud PSL and Health Cloud Platform PSL ensures users can interact with all necessary components.

✅ D. Install the Utilization Management Extensions
This package includes the OmniStudio flows, record types, and support processes required for Utilization Management. Without it, the org won’t have access to:
Concurrent review and appeal workflows
Preauthorization intake forms
Guided decisioning and SLA tracking
Installing this extension is a foundational setup step.

🛑 Why not the others?
A. Health Cloud Care Request Extensions unmanaged package:
This is used for basic care request workflows, not Utilization Management-specific functionality.
B. Assigning licenses to Salesforce Classic users:
Utilization Management is not supported in Classic, so this step is irrelevant.

📚 References:
Salesforce Help: Utilization Management Setup Checklist
Salesforce Trailhead: Set Up Utilization Management
Salesforce Developer Guide: Health Cloud Utilization Management

Explanation:

To enable care providers at a provider system to conduct video visits with patients to discuss socioeconomic factors impacting their care within Salesforce Health Cloud, the consultant should recommend the Virtual Care capability. Here’s why:
D. Virtual Care:
This feature in Health Cloud is specifically designed to support secure video consultations between providers and patients. It integrates with patient records and care plans, allowing providers to discuss critical factors like socioeconomic determinants of health (e.g., housing, income, or access to care) during virtual visits. Virtual Care includes tools for scheduling, conducting, and documenting these interactions, making it the most suitable capability for this use case.
Why the other options are incorrect:
A. Integrated Care Management:
This feature focuses on coordinating care across a care team, managing care plans, and tracking patient progress, not on enabling video visits or direct patient-provider communication.
B. Intelligent Appointment Management:
While this capability supports scheduling appointments, it is focused on automating appointment booking and resource allocation, not on facilitating video visits or discussing socioeconomic factors.
C. Telehealth:
Although telehealth is a general term for remote healthcare delivery, it is not a specific feature within Health Cloud. The platform uses "Virtual Care" as the designated capability for video-based consultations.

Reference:
Salesforce Health Cloud documentation on Virtual Care (Salesforce Help).
Health Cloud Accredited Professional exam resources, which highlight Virtual Care for enabling remote patient interactions.

Explanation:

A. Enable Discovery Framework in Setup ✅
Health Cloud Assessments are built on Salesforce’s Discovery Framework.
To use them, the Discovery Framework must be enabled in Setup.

B. Add the Assessment component to the Patient page ✅
The Assessment Lightning component must be added to the Patient (Person Account) page layout so that end users can access and complete assessments.

C. Download and Install OmniStudio ❌
OmniStudio (formerly Vlocity) powers OmniScripts, DataRaptors, Integration Procedures, etc.
Assessments do not require OmniStudio to function.

D. Update sharing settings in Setup ❌
Not a specific setup step for enabling Assessments. Sharing/security settings are standard Salesforce config but not unique to this feature.

E. Enable users to view and complete Assessments ✅
Admins must assign the right permissions (Discovery Framework + Health Cloud Assessment permissions) so that users can view and complete Assessments.

Reference:
Salesforce Help: Set Up Health Cloud Assessments
Key steps: Enable Discovery Framework → Add Assessment component → Assign user permissions.

⚡ Exam Tip:
If you see Assessments in Health Cloud → always think:
Discovery Framework ON
Component on Patient page
User permissions enabled

Explanation:

The most cost-effective and out-of-the-box method for Bloomington Caregivers to send patient clinical data to an external payer is to leverage the FHIR R4 Patient API.

B. Leverage the FHIR R4 Patient API:
This is the most efficient and cost-effective out-of-the-box solution. Salesforce Health Cloud is built with a FHIR (Fast Healthcare Interoperability Resources)-aligned data model. It provides native FHIR R4 APIs that allow for the secure and standardized exchange of clinical data with other systems, like those of a payer. This eliminates the need to build a custom integration from scratch, which saves significant development time and money. It's a standard feature of the Health Cloud platform, meaning it doesn't require purchasing additional products.

A. Build a custom remote call-in API into Salesforce:
This option is highly custom and expensive. Building a custom API requires significant development effort, maintenance, and potentially additional licensing costs for API calls. It also carries the risk of not being compliant with healthcare data standards like FHIR, making it less desirable and more costly in the long run.

C. Use MuleSoft Accelerator with HL7 API:
While MuleSoft is a powerful integration platform and the Accelerator for Healthcare provides pre-built templates for common healthcare use cases, it is not an out-of-the-box feature of Health Cloud. It's an additional product that requires a separate license and implementation effort, making it more expensive than the native FHIR API. It's used for complex, enterprise-level integration projects, not for a simple, single-use case.

D. Use a third-party tool from AppExchange:
This option would require purchasing and implementing a separate, paid solution from the AppExchange. While some of these tools may offer a quick solution, they would likely involve an additional cost and might not be as natively integrated or as cost-effective as the built-in FHIR API.

In summary, for a direct and cost-effective method to share data with a payer, the consultant should recommend using the platform's native FHIR R4 Patient API, as it is a core, built-in capability designed for this exact purpose.