To customize the out-of-the-box advanced Patient Card in Health Cloud, a developer must follow the standard procedure for modifying managed OmniStudio components. The first step is to clone the parent FlexCard (HealthCloudPatientCardParent) to create a customizable version, ensuring the original remains intact for future upgrades. Next, a DataRaptor Extract is required to query the ClinicalAlertc object, filtering for active records and retrieving the specified fields (Category, SubjectID, Date). Finally, a new child FlexCard must be created to display this data, configured to use the new DataRaptor as its data source, and then activated so it becomes visible within the cloned parent card.

D. Define session variables to control visibility of clinical data.

Session variables are not the primary mechanism for filtering data records; this logic is correctly handled within the DataRaptor's query filters.

E. Change the child card state to show active.

Activating the card itself makes it visible. A card's "state" is for defining different layouts or conditional UI displays, not for the initial data filtering.

1. Salesforce Health Cloud Developer Guide: Customize the Advanced Patient Card

Reference: The guide explicitly states, "To customize the patient card, first clone the HealthCloudPatientCardParent FlexCard." It then details adding child cards and configuring their properties, which includes setting up a data source. This supports options A and B.

2. Salesforce OmniStudio Documentation: FlexCards Data Source Properties

Reference: This documentation specifies that FlexCards use data sources like DataRaptors, SOQL queries, or Apex to retrieve data. For extracting and filtering records from a Salesforce object as required in the question, a DataRaptor Extract is the standard and recommended method. This supports option C.

3. Salesforce Trailhead: FlexCard Basics > Create a FlexCard

Reference: The "Activate a FlexCard" unit explains that a FlexCard (including child cards) must be activated to be used or displayed within another component or Lightning page. This confirms the "activate" part of option B is a necessary step.

To successfully install the Health Cloud managed package, administrators must enable several foundational features. Person Accounts are required for the patient data model, and the standard procedure is to request enablement via a Salesforce support case. The "Contacts to Multiple Accounts" feature is necessary to model complex patient relationships with various providers and facilities. Finally, Chatter must be enabled to support the collaborative care team features inherent in Health Cloud. These prerequisites ensure the core components that Health Cloud depends on are active in the org before installation.

D: Making data protection details available is a data privacy configuration step, not a technical prerequisite for package installation.

E: The official Health Cloud installation guide specifies logging a support case to enable Person Accounts, making self-enablement from Setup an incorrect step.

1. Salesforce Help. (2023). Health Cloud Administrator Guide: Prerequisites for Installing Health Cloud. Salesforce, Inc. This document explicitly lists the following as prerequisites:

"Enable Person Accounts" and notes, "To enable person accounts, log a case with Salesforce Customer Support." (Supports option C, invalidates E).

"Enable Contacts to Multiple Accounts" (Supports option A).

"Enable Chatter" (Supports option B).

2. Salesforce Help. (2023). Health Cloud Administrator Guide: Install Health Cloud. Salesforce, Inc. This guide reiterates the prerequisites, stating, "Before you install the Health Cloud packages, complete these prerequisites," and then links to the prerequisite list cited above.

Integrated Care Management represents a significant architectural evolution from the legacy care plan model in Salesforce Health Cloud. It is built upon the standard CarePlan object, aligning more closely with healthcare data standards like FHIR and moving away from the legacy implementation that was based on the Case object. This new framework also leverages modern Salesforce platform technologies, specifically OmniStudio and the Discovery Framework. These tools are used to create dynamic assessments that gather patient information, which can then be used to automatically recommend problems, goals, and interventions, streamlining the creation of personalized care plans.

A. Due to the fundamental data model change from the Case object to the standard CarePlan object, legacy templates and data are not directly compatible and require a migration process.

B. The feature is enabled by a setting named "Integrated Care Management" in Health Cloud Settings, not "Enhanced Care Management."

1. Salesforce Health Cloud Developer Guide: Set Up Integrated Care Management. This document explicitly states, "Integrated Care Management uses the Care Plan standard object to represent care plans." It also details the setup process, showing the setting is named "Integrated Care Management."

2. Salesforce Health Cloud Developer Guide: Assessments in Integrated Care Management. This section confirms, "Assessments in Integrated Care Management are powered by Discovery Framework and OmniStudio." It describes how these tools are used to gather information to add to a care plan.

3. Salesforce Health Cloud Developer Guide: Migrate from Legacy to Integrated Care Management. This guide clarifies the need for migration: "The legacy care plan model is built on the Case object, while Integrated Care Management uses the Care Plan standard object. Because of this difference in data models, you must migrate your legacy care plan data to the new data model." This directly refutes the claim in option A.

Intelligent Appointment Management in Health Cloud is designed to provide a unified scheduling experience. It offers two primary architectural models for the scheduling engine. The first model uses the native Salesforce Scheduler to manage appointments, resources, and availability directly within Salesforce. The second model allows for integration with an external system of record, such as an Electronic Health Record (EHR) System, where the EHR continues to act as the master scheduling engine. Health Cloud then serves as the engagement layer, reading from and writing to the EHR via APIs, thus eliminating the need for users to switch between systems.

A. Business Rules Engine: This engine is used to automate complex decision-making and business logic, not to manage calendars, resources, or time slots, which are core functions of a scheduling engine.

D. Scheduler for Industries: While related, "Salesforce Scheduler" is the specific foundational product name. The official documentation explicitly names Salesforce Scheduler as the native engine option for Intelligent Appointment Management.

1. Salesforce Help Documentation, Health Cloud: Set Up Intelligent Appointment Management.

Reference: In the introductory section, the documentation states, "Intelligent Appointment Management gives you the flexibility to use Salesforce Scheduler as your scheduling engine or connect to any external EHR or patient management system." This directly supports the selection of both Salesforce Scheduler and an EHR system as valid scheduling engine options.

2. Salesforce Health Cloud Developer Guide: Chapter: Intelligent Appointment Management.

Reference: The architectural overview section explains the two primary configuration patterns. It details how to configure the system to either use the objects and logic of the Salesforce Scheduler package or to use the provided APIs to connect to an external scheduling system, with EHRs being the primary example in a healthcare context. This confirms that both are valid, distinct options for the core scheduling functionality.

The Health Cloud Interoperability APIs are specifically designed to facilitate the exchange of healthcare data between Health Cloud and external systems, such as an external provider's EMR. These APIs are aligned with the Fast Healthcare Interoperability Resources (FHIR) R4 standard. To retrieve a patient's allergy information, the external system would call the endpoint corresponding to the FHIR AllergyIntolerance resource, which is part of the Interoperability API suite. This provides a standardized, secure method for the required data exchange.

A. Clinical Summary Healthcare API: This is not an official name for a Health Cloud API. A clinical summary is a type of document (like a CCDA), not the API used for the data transaction.

C. AllergyMedication API: This is a fabricated name and not a recognized Health Cloud API. It incorrectly combines two separate clinical data concepts.

D. Patient Healthcare API: This term is too generic. While the data is about a patient, the "Interoperability API" is the specific suite designed for standardized clinical data exchange with external entities.

1. Salesforce Health Cloud Developer Guide: "Integrate External Data with Health Cloud". This section details the use of FHIR-aligned APIs for interoperability. It states, "Health Cloud provides APIs that are aligned with Fast Healthcare Interoperability Resources (FHIR) to help you integrate data from external health systems." The AllergyIntolerance resource is a key part of this framework.

2. Salesforce Help: "What Are the Health Cloud APIs?". This document explicitly defines the purpose of these APIs: "The Health Cloud APIs are a set of MuleSoft-powered APIs that help you integrate clinical data from external sources into Health Cloud in a standardized way. The APIs are aligned with Fast Healthcare Interoperability Resources (FHIR) and let you quickly connect with EMRs and other clinical systems."

3. Salesforce Health Cloud API Reference: The API reference documentation lists the available FHIR resources that can be accessed. This includes the AllergyIntolerance resource, which is used to "record a clinical assessment of a propensity, or potential risk to an individual, of a specific substance." Access to this resource is managed through the Interoperability API gateway.

To grant users access to Health Cloud functionalities, two specific permission set licenses (PSLs) must be assigned. The Health Cloud Foundation PSL provides access to the core Health Cloud data model, objects, and features common to all customers, such as care plans and patient timelines. The Health Cloud Platform PSL unlocks additional platform capabilities, including features like care programs, remote monitoring, and advanced therapy management. Assigning both is a fundamental and required step in the user setup process for a Health Cloud implementation.

A. "Health Cloud permission set license" is a generic term describing a category of licenses, not the specific, assignable license name required for setup.

D. "Health Cloud Standard permission set license" is not a valid or recognized name for a permission set license within the Salesforce Health Cloud product structure.

1. Salesforce Help Documentation, Assign Health Cloud Permission Set Licenses to Users: "To give users access to Health Cloud, assign them the Health Cloud Foundation and the Health Cloud Platform permission set licenses." This document explicitly names the two required licenses. (Document ID: sf.adminassignhcpermsetlicenses)

2. Salesforce Health Cloud Developer Guide, Post-Installation Tasks for Health Cloud, Section: "Assign Permission Set Licenses for Health Cloud": "Assign the Health Cloud Foundation and Health Cloud Platform permission set licenses to give your users access to Health Cloud features." (Document ID: healthclouddevguide, Chapter: Set Up Health Cloud)

The Patient Medication Manager is a standard Lightning component in Salesforce Health Cloud designed to display a patient's medication history. Its user interface is configurable, allowing administrators to control which fields are visible. This customization is achieved by modifying the field sets on the specific objects that the component uses. According to official Salesforce documentation, the fields displayed for a patient's medications within this component are controlled directly by the field sets on the Medication Request and Medication Dispense objects.

A. Medication Details: While related, the fields for this object are not directly configured in the Patient Medication Manager component's primary view via its designated field sets.

D. Medication Strength: This object provides supporting information, but the component's configurable columns are pulled from the Medication Request and Medication Dispense objects, not Medication Strength.

1. Salesforce Health Cloud Administrator Guide: "Configure the Patient Medication Manager Component". This document explicitly states, "You can customize the fields that are shown for the Medication Request and Medication Dispense objects... From the management settings for the Medication Request object, go to Field Sets... Edit the PatientMedicationManagerFS field set." The same instruction is provided for the Medication Dispense object.

2. Salesforce Health Cloud Developer Guide: "Patient Medication Manager Component". This guide describes the component's purpose, which is to show "a patient’s current and past medications," reinforcing that it is built upon the core medication-related objects. The configuration details point back to the field sets on Medication Request and Medication Dispense.

3. Salesforce Health Cloud Data Models Documentation: The "Medication Management" data model section illustrates that Medication Request and Medication Dispense are the central objects for tracking a patient's medication orders and fulfillment, which aligns with them being the primary configurable objects in the UI component.

Salesforce Health Cloud's clinical data model is specifically designed and aligned with the Fast Healthcare Interoperability Resources (FHIR) R4 standard. This modern standard provides a consistent, API-based framework for representing and exchanging electronic health information. By leveraging the FHIR R4 specification, consultants can ensure seamless and standardized interoperability between Health Cloud and external systems like Electronic Health Records (EHRs). This alignment simplifies integration, promotes data consistency, and enables a comprehensive view of the patient by mapping EHR data to corresponding Health Cloud objects.

A. Clinical Data Acquisition: This describes a process or a category of functions for gathering clinical data, not a specific industry data standard for interoperability.

B. Personal Health Record (PHR): A PHR is a type of health record controlled by the patient, not a technical standard for data exchange between provider systems.

C. HL7 v2 Messaging: While HL7 v2 is a widely used legacy standard, Health Cloud's core data model is built upon the more modern, flexible, and API-friendly FHIR standard.

1. Salesforce Help Documentation, Health Cloud Data Models: "The Health Cloud clinical data model is aligned with the FHIR (Fast Healthcare Interoperability Resources) R4 standard. This alignment makes it easier to integrate Health Cloud with external systems, such as electronic health records (EHR)." (Section: Clinical Data Model)

2. Salesforce Health Cloud Developer Guide, Understand the Health Cloud Data Models: "The clinical data model in Health Cloud is based on the Fast Healthcare Interoperability Resources (FHIR) standard. FHIR is a standard for exchanging healthcare information electronically... Health Cloud supports a subset of FHIR R4 resources." (Chapter: Data Models)

3. Trailhead, Health Cloud Data Model Module, Get to Know the Health Cloud Data Models Unit: "The Health Cloud data model is based on the Fast Healthcare Interoperability Resources (FHIR) specification. FHIR is a standard for exchanging healthcare information electronically."

The Benefits Verification feature in Health Cloud is specifically designed to allow payer agents to look up a member's insurance benefits and eligibility. This feature is typically implemented as a flow that can be launched from a component on the Member (Person Account) record page. It enables agents to view detailed coverage information, including deductibles, copayments, and coinsurance, directly addressing the need to answer member inquiries about their benefits coverage using the populated data.

A. Coverage Confirmation: This is a generic term describing the outcome of a process, not the name of a specific Health Cloud component or feature.

B. Eligibility Validation: This is only one aspect of the process. Benefits Verification is more comprehensive, as it includes both eligibility status and detailed benefit information.

C. Benefits Coverage: While this term accurately describes the information being viewed, it is not the official name of the standard Health Cloud feature or component used for this function.

1. Salesforce Health Cloud Administrator Guide, Chapter: Verify Insurance Benefits and Eligibility. The guide states, "Use the Benefits Verification flow to let your users quickly verify a patient’s insurance benefits and eligibility." This confirms that "Benefits Verification" is the correct feature name for this use case.

2. Salesforce Help, Article: Benefits Verification. This article explicitly mentions, "Benefits Verification helps you get details about a member's health benefits and share them with the member." This directly aligns with the scenario of an agent answering member questions.

3. Salesforce Health Cloud Developer Guide, Section: Connect API, Namespace: ConnectApi.BenefitsInquiry. The guide details the BenefitsInquiry API, which is the underlying technology that powers the Benefits Verification feature, demonstrating that this is a formally defined capability within Health Cloud.

The Patient Card in Health Cloud is a specialized and highly configurable highlights panel designed to provide a consolidated, at-a-glance view of a patient's most critical information. It can be customized to pull data from various related objects to display key details such as insurance plans, clinical summaries (like conditions or allergies), and members of the care team, including the primary care physician. This component also provides direct navigation links to these related records, fulfilling the customer's requirement to both view and navigate to essential information from the patient's profile.

A. Enhanced Highlights Panel: This is a generic term. The "Patient Card" is the specific Health Cloud component that functions as an advanced, purpose-built highlights panel for patient profiles.

B. Enhanced Timeline: The Timeline component displays a chronological view of a patient's past and future events, such as appointments and tasks, not a static summary of their core data.

D. Patient Path: The Patient Path component visually represents a patient's progression through the stages of a care program or process, not a summary of their critical profile information.

1. Salesforce Health Cloud Developer Guide: "The Patient Card" section. The guide describes the patient card as the highlights panel on the patient's record page, which provides "at-a-glance information like the patient’s age, medical record number, and key medical conditions." It details how to customize this component to add information about the patient's care team and other important details. (Reference: Health Cloud Developer Guide, Chapter: "Set Up the Health Cloud Console", Section: "Customize the Patient Card").

2. Salesforce Help & Training: "Customize the Patient Card". This document explicitly states, "The patient card is the highlights panel on the patient’s record page... You can also add information about the patient’s care team and other important details." This confirms its role in displaying information like the primary care physician. (Reference: Salesforce Help, Article #000389203, "Customize the Patient Card").

3. Salesforce Health Cloud Administration Guide: "Patient Card Configuration". This section details the steps to modify the compact layout for the Account object to control the fields displayed on the patient card, including pulling in information from related objects to create a comprehensive summary. (Reference: Health Cloud Administration Guide, Chapter: "Configure Health Cloud", Section: "Customize Patient and Member Details").