Salesforce Health Cloud Accredited Professional Exam Questions

To enable an external provider to retrieve a patient's allergy information from Bloomington Caregivers' Health Cloud system, the Clinical Summary Healthcare API is the appropriate choice. This API facilitates access to clinical data, including allergies, in a standardized format.

Understanding the Clinical Summary Healthcare API:

Purpose: Provides endpoints to access a patient's clinical summary, encompassing various health records such as conditions, procedures, and allergies.

FHIR Compliance: Aligns with the Fast Healthcare Interoperability Resources (FHIR) standards, ensuring compatibility with other healthcare systems and promoting interoperability.

Retrieving Allergy Information:

Endpoint: To fetch a patient's allergy records, utilize the following endpoint:

GET /clinical-summary/fhir-r4/v1/AllergyIntolerance

Parameters:

Patient ID: Specify the unique identifier of the patient whose allergy information is being requested.

Advanced Therapy Management (ATM) in Salesforce Health Cloud is specifically designed to support complex workflows and scheduling requirements, particularly for therapies involving multiple interdependent appointments. For a gene therapy program, ATM provides these features:

Key Scheduling Capabilities of ATM:

Reschedule Part of the Appointment Chain (Option A):

In complex workflows where multiple steps are involved (e.g., collection, processing, infusion), ATM allows administrators to reschedule individual appointments within the chain without disrupting the entire workflow.

This flexibility is crucial for accommodating unexpected delays or changes in the therapy process.

Book Multi-Step Appointments (Option B):

ATM supports the scheduling of interdependent, multi-step appointments that are a common feature of advanced therapies such as gene therapy.

For example, steps like apheresis, manufacturing, and infusion can be scheduled in sequence, ensuring coordination across various stakeholders.

Other Options:

Optimize Appointment Chain with Einstein (Option C):

While optimization using Einstein is a broader Salesforce capability, it is not directly tied to Advanced Therapy Management's out-of-the-box scheduling features.

Schedule a Telehealth Appointment (Option D):

Telehealth appointments are not the focus of ATM, which is designed for in-person and complex therapy workflows.

Advanced Therapy Management Overview

Scheduling in Advanced Therapy Management

The FHIR R4 (Fast Healthcare Interoperability Resources) standard is the most suitable industry data standard for designing interoperability with Electronic Health Record (EHR) systems in Salesforce Health Cloud.

Why FHIR R4?

Widespread Adoption:

FHIR R4 is the industry standard for modern EHR systems, supported by regulatory bodies like the ONC (Office of the National Coordinator for Health IT).

Compatibility:

Salesforce Health Cloud's Clinical Data Model and FHIR-compliant APIs are built to align with FHIR R4 standards.

Data Interoperability:

Facilitates seamless exchange of clinical data (e.g., medications, conditions, and encounters) between Health Cloud and EHR systems.

Why Other Options Are Less Relevant:

A . Clinical Data Acquisition: A generic concept rather than a specific standard.

B . Personal Health Record (PHR): Focuses on patient-controlled data, not interoperability.

C . HL7 v1 Messaging: An outdated standard superseded by FHIR for modern systems.

Salesforce FHIR Integration Guide

To enable the Clinical Data Model in Salesforce Health Cloud, the FHIR-Aligned Data Model org preference must be activated. This preference ensures compatibility with the Fast Healthcare Interoperability Resources (FHIR) standard, which is widely used for managing healthcare data.

FHIR-Aligned Data Model:

Supports the representation of clinical data such as medications, conditions, procedures, and encounters in a format compliant with the FHIR standard.

Aligns Health Cloud's data structure with industry standards, facilitating interoperability with Electronic Health Record (EHR) systems and other healthcare platforms.

Why Not the Other Options?

B . Clinical R4 Model org preference: This is not a valid preference in Salesforce Health Cloud.

C . FHIR-Aligned EHR Data Model org preference: While EHR data models align with FHIR, this specific preference does not exist.

D . Clinical Data Model org preference: This is not specific to the FHIR-aligned framework and may not meet interoperability requirements.

Implementation Steps:

Navigate to Setup Health Cloud Settings.

Enable the FHIR-Aligned Data Model org preference.

Configure the required objects and fields for the Clinical Data Model.

FHIR-Aligned Data Model Overview

Clinical Data Model in Health Cloud

When onboarding a new business unit to Health Cloud while protecting sensitive data for the existing Service Cloud users, adjusting Organization-Wide Defaults (OWD) is critical.

Recommended Settings:

Health Details to Controlled by Parent or Private:

Ensures that only users with appropriate access to parent records (e.g., Person Accounts or Cases) can view sensitive health-related information.

Person Accounts to Private:

Restricts visibility of patient data at the account level, limiting access to users within the appropriate Health Cloud business unit.

Related Clinical Objects to Controlled by Parent or Private:

Applies restricted access to clinical objects like care plans, conditions, and encounters to ensure that PHI is not accessible to Service Cloud users.

Why Other Options Are Less Suitable:

B . Account and Contract to Private: Relevant for managing non-healthcare data but not directly tied to PHI protection.

D . Contact to Controlled by Parent: While this helps manage access to contact data, it does not address broader clinical objects or PHI.

Salesforce Health Cloud Security Best Practices