Free AP-211 Practice Test Questions and Answers (2026)

The Provider Relationship Card is a standard Health Cloud Lightning component specifically designed to fulfill this requirement. It displays a provider's details, including their contact information and specialty, within the context of a specific healthcare facility. This component visualizes the relationship stored in the HealthcarePractitionerFacility object, which links a practitioner to a facility and captures their specific role or specialty at that location, presenting the highlighted information in a single, consolidated view on a record page.

A. HCPProvider360 FlexCard: This is a more comprehensive OmniStudio component for a 360-degree provider view, not the specific, standard component for showing the facility-specialty relationship.

B. Facility Relationship Center: This feature shows relationships from the facility's perspective (e.g., all providers at a facility), not a highlighted summary of one provider's details.

C. Provider Network Management: This is a broad set of capabilities for managing provider networks (e.g., credentialing, contracting), not a specific user interface component for displaying information.

---

1. Salesforce Health Cloud Administrator Guide: "Show Provider Details with the Provider Relationship Card". This document explicitly states, "The Provider Relationship card is a Lightning component that shows a provider’s relationship with a facility, including their specialty. Add the component to the Account and Contact record pages so that your users can easily access this information." This directly aligns with the question's requirement.

2. Salesforce Health Cloud Developer Guide: "Provider Data Model". This guide details the HealthcarePractitionerFacility object, which is the junction object that the Provider Relationship Card visualizes. It explains that this object "Represents the relationship between a practitioner and a facility, including details such as the practitioner's specialty and medical privileges at that facility." This confirms the card is the correct UI for this data.

3. Trailhead - Health Cloud Data Models: "Provider and Payer Data Models in Health Cloud". This module explains the purpose of the HealthcarePractitionerFacility object is to "Connect practitioners to facilities where they practice and define their specialty at each location." The Provider Relationship Card is the component used to surface this information.

To grant users access to Health Cloud, an administrator must assign specific out-of-the-box permission sets. The Health Cloud Foundation permission set is the baseline, providing access to core Health Cloud objects, record types, and fundamental features. The Health Cloud Standard permission set is assigned in addition to the Foundation set to grant users access to a broader range of standard Health Cloud features and functionalities, such as care plans and timelines. Together, these two permission sets provide the necessary access for a typical Health Cloud user.

A. Health Cloud permission set license: This is a license that enables the assignment of Health Cloud permission sets; it is not a permission set itself and does not grant permissions directly.

D. Health Cloud User: This is not a standard, out-of-the-box permission set provided by Salesforce for granting general access to Health Cloud features.

E. Health Cloud Platform permission set license: This is a specific type of license, not a permission set. It is intended for users who need Health Cloud access without full CRM functionality.

1. Salesforce Health Cloud Developer Guide: "Assign Health Cloud Permission Sets". The documentation explicitly states, "Assign the Health Cloud Foundation permission set to give users access to Health Cloud objects and features. To give users access to more Health Cloud features, assign the Health Cloud Standard permission set."

Source: Salesforce Help, Health Cloud Developer Guide, Section: "Post-Installation Tasks" > "Set Up Users" > "Assign Health Cloud Permission Sets".

2. Trailhead by Salesforce: "Health Cloud Administration" module, "Set Up Your Health Cloud Org" unit. This module details the setup process, including user configuration.

Source: Trailhead, Health Cloud Administration, Unit: "Set Up Your Health Cloud Org", Section: "Assign Health Cloud Permission Sets". The text confirms the necessity of assigning both the "Health Cloud Foundation" and "Health Cloud Standard" permission sets for user access.

To facilitate electronic requests for care services from a provider to a payer system, the consultant should recommend APIs that map to standard healthcare business processes.

1. Benefit Verification (D): This API is used to request information from the payer to confirm a patient's eligibility and coverage for specific services, which is a foundational step in requesting care.

2. Referral Request (C): This API allows a provider to submit a request for a patient to receive care from another provider (e.g., a specialist), which often requires payer involvement and approval.

3. Prior Authorization (B): This API is used to formally request approval from the payer for specific medical services, procedures, or medications before they are administered to ensure they will be covered.

These three APIs directly support the workflow of requesting and authorizing care services with a payer organization.

A. Care Services: This is a general term, not a specific business-level API in Health Cloud for payer integration. The other options represent specific types of care service requests.

E. Admission, Discharge, and Transfer (ADT): This API is used to send notifications about a patient's status (e.g., hospital admission), not to request a care service from a payer.

1. Salesforce Health Cloud Developer Guide: The "Health Cloud Business APIs" section details the pre-built APIs for common healthcare processes. It explicitly lists and describes the purpose of the Benefit Verification, Prior Authorization, and Referral Request APIs for provider-payer communication.

Reference: Salesforce Help, Health Cloud Developer Guide, "Health Cloud Business APIs". This section outlines the APIs designed to "streamline communication between providers and payers," including those for verifying benefits and submitting authorization or referral requests.

2. Salesforce Health Cloud for Payers Documentation: This documentation describes how payers use Health Cloud to manage member services, including processing incoming requests from providers.

Reference: Salesforce Help, "Health Cloud for Payers", section on "Utilization Management". This area details the workflows for handling prior authorizations, benefit verifications, and referrals, which are initiated via the corresponding business APIs.

The requirement is to send a large volume of data ("all of their patients’ visit information") on a fixed schedule ("weekly") for a back-office process ("billing cycle"). This is a classic use case for the Batch Data Synchronization pattern. An ETL (Extract, Transform, Load) tool is specifically designed to handle such large-scale, scheduled data movements efficiently between systems like Health Cloud and an ERP. This pattern is robust, scalable, and avoids the performance overhead and API limit constraints associated with real-time, transactional patterns.

A. Fire and Forget is for near-real-time, event-driven messages, not for scheduled, large-volume data extracts.

C. Calling an API record-by-record for a bulk weekly extract is highly inefficient and not the intended use of FHIR APIs.

D. Request and Reply is a synchronous pattern for real-time queries, which is inappropriate for a large, asynchronous weekly batch job.

1. Salesforce Architects. (2023). Integration Patterns and Practices. Section: "Batch Data Synchronization". This official guide describes the pattern as ideal for processing records as a group on a scheduled basis, stating, "Data is exported from the source system and imported into the target system in a batch... This pattern is useful when a large number of records need to be transmitted..." This directly matches the scenario.

2. Salesforce Health Cloud Developer Guide. (2024). Health Cloud APIs and Standards. Chapter: "FHIR-Aligned APIs". The documentation details how these APIs are used to create, read, and update specific FHIR resources (e.g., a single patient or encounter). Their design is for transactional, not bulk-extract, purposes, which makes option C unsuitable.

3. MuleSoft Documentation. Batch Processing. As a Salesforce company, MuleSoft's documentation is an authoritative source. It defines batch jobs as the solution for "processing large data sets that can't be processed in a single, real-time transaction," which aligns perfectly with the weekly billing cycle requirement.

This set of objects correctly represents the standard Health Cloud insurance data model.

1. Account: Used to represent the payer organizations (insurance companies).

2. Purchaser Plan: Represents the specific insurance plans offered by a payer (Account).

3. Plan Benefit: This conceptually maps to the PurchaserPlanBenefit object, which links a standard benefit to a specific Purchaser Plan.

4. Member Plan: This object links a patient (Person Account) to a Purchaser Plan, tracking their specific enrollment details like member ID and group number.

This combination provides a structured way to manage the relationships between payers, the plans they offer, the standard benefits of those plans, and the individual patients enrolled in them.

A. Purchaser, Insurance Plan, Insurance Benefit, Plan Detail: These are generic or non-existent object names in the standard Health Cloud insurance data model.

B. Payer, Plan Offering, Coverage Benefit, Member Plan: Plan Offering is not a standard object name. Coverage Benefit tracks a member's specific benefit details, not the standard benefits of a plan.

D. Account, Purchaser Plan, Member Benefit, Insurance Plan: Member Benefit is not a standard object. Insurance Plan is a parent object, but Member Plan is the correct object for tracking a patient's specific enrollment.

1. Salesforce Health Cloud Developer Guide: "Insurance Data Model". This guide details the object relationships. The Account object represents payers. The PurchaserPlan object represents a plan offered by a payer. The PurchaserPlanBenefit object links benefits to a plan. The MemberPlan object links a patient to a PurchaserPlan.

2. Trailhead - Health Cloud Data Models: "Get to Know the Health Cloud Data Models" unit. The "Insurance and Utilization Management" section illustrates how Account (Payer), PurchaserPlan, PurchaserPlanBenefit, and MemberPlan objects work together to model insurance information for a patient. This confirms the object selection in the correct answer.

Salesforce provides a specific unmanaged package designed to help organizations analyze patient referrals. This package, named "Health Cloud Reports for Patient Referral Management," includes a preconfigured dashboard and several reports. These tools enable users to track referral metrics such as the number of referrals by status, priority, and specialty, directly addressing the needs of Bloomington Caregivers to analyze their patient referral data.

B. This is an incorrect name for the official package. The correct name specifically includes the word "Patient" to distinguish its purpose.

C. This package is for analyzing provider networks, such as provider directories and network adequacy, not for tracking patient referrals.

D. This is not the name of the standard unmanaged package. The official package for this purpose is focused on "Patients," not "Members."

1. Salesforce Health Cloud Administrator Guide. "Install Health Cloud Reports for Patient Referral Management". Salesforce Help. Accessed May 2024. The documentation explicitly states, "Install the Health Cloud Reports for Patient Referral Management unmanaged package to get reports and a dashboard that help you track and analyze referrals." This guide details the contents of the package, including reports like "Top Referring Practitioners" and "Referrals by Specialty."

Health Cloud utilizes the Person Account object model to represent patients, which combines account and contact information into a single record. For users to have a complete view of a patient, their access rights to the underlying contact record must be synchronized with their access to the account record. The Salesforce best practice for this scenario is to set the organization-wide default (OWD) for the Contact object to 'Controlled by Parent'. This setting ensures that a user's access to the contact portion of the Person Account is inherited directly from their access to the parent account, providing seamless and unified access to the entire patient record as required.

A. Setting 'Modify All' on the Account object is an excessive permission that bypasses all sharing rules, creating a significant security risk and violating the principle of least privilege.

C. Setting the Contact object OWD to 'Private' would segregate the sharing of the contact from the account, potentially preventing users from seeing the full record even if they have access to the account.

D. Setting the Account OWD to 'Public Read Write' is overly permissive for a healthcare setting, as it would expose all patient data to all users, which is inappropriate and violates privacy standards.

1. Salesforce Health Cloud Administrator Guide, "Set Your Organization-Wide Sharing Defaults". The documentation explicitly states, "For person accounts to work properly, the organization-wide default for contacts must be set to Controlled by Parent." This is listed as a mandatory configuration step for Health Cloud.

2. Salesforce Security Guide, "Sharing Settings". In the section discussing organization-wide sharing defaults, it explains that for objects in a master-detail relationship (or special relationships like Account-Contact for Person Accounts), setting the detail object to 'Controlled by Parent' makes its sharing dependent on the master record's sharing. This is the intended mechanism for Person Accounts.

3. Trailhead, "Prepare for Your Health Cloud Implementation" module, "Set Up Your Org for Health Cloud" unit. This official training material lists the prerequisite org configurations. It instructs administrators to "From Setup, go to Sharing Settings and edit the organization-wide defaults... set Contact to Controlled by Parent." This reinforces it as a foundational implementation best practice.

To enable Provider Search for external users on an Experience Cloud site, two key configurations are required. First, the user interface element, the 'Provider Search' Lightning Web Component, must be added to a page within the Experience Builder so users can interact with it. Second, users must have the necessary data permissions to see the search results. The search functionality queries the CareProviderSearchableField object. Therefore, the external user's profile or an assigned permission set must have 'Read' access to this object to view the indexed provider data.

B. Create a sharing rule on the Care Provider Searchable Field object to share with external users.

Sharing rules grant record-level access, but the primary requirement here is object-level 'Read' permission, which is controlled by profiles and permission sets.

D. Give the site user profile Read access to the Data Pipeline object.

The Data Pipeline object is related to the backend Data Processing Engine jobs that populate the search index, not the end-user search experience itself.

1. Salesforce Health Cloud Developer Guide: Set Up Provider Search for Users. The documentation explicitly states the required steps:

"Make the Provider Search component available to your users by adding it to a page in your org or community." (Supports Answer A)

Under the "Required Permissions" section: "To let users search for providers, give them Read access to the Care Provider Searchable Field object." (Supports Answer C)

2. Salesforce Help: Provider Search. This document outlines the feature and its setup, reinforcing the need for both the UI component placement and the specific object permission. It details that the CareProviderSearchableField object stores the flattened, searchable data and access to it is fundamental for the component to function.

Sales Agreements are designed to manage long-term contracts by tracking planned quantities and revenues against actual orders over a specific period. This directly addresses the need to ensure contract compliance. Advanced Account Forecasting leverages data from sales agreements, orders, and opportunities to generate granular forecasts. This provides the visibility needed to manage the run rate business by predicting future sales volumes and revenue, ensuring the company can proactively manage its performance against contractual obligations. Together, these features provide a comprehensive solution for the MedTech company's requirements.

A. Remote Device Monitoring: This feature is for integrating patient data from medical devices for clinical purposes, not for managing commercial sales contracts or run rate business.

C. MedTech Accelerator: This is a pre-configured set of components and templates to speed up implementation, not a specific feature used for ongoing business management of contracts and forecasting.

1. Salesforce Help, "Sales Agreements": "A sales agreement is a long-term contract between your company and a customer for selling a predefined quantity of products at a predetermined price over a specific period... Track planned quantities and amounts against actuals to maintain compliance." This directly supports the use of Sales Agreements for contract compliance.

2. Salesforce Help, "Advanced Account Forecasting": "Generate forecasts for your business across regions, products, and other custom dimensions. Use sales agreements, orders, and opportunities as source data for your forecasts." This confirms that Advanced Account Forecasting is the correct tool for managing run rate business based on contractual data.

3. Salesforce Help, "What is MedTech in Health Cloud?": This documentation describes the MedTech Accelerator as a tool to "jump-start your implementation and digital transformation" by providing pre-built apps and components. This clarifies its role as an implementation aid rather than an operational feature for run rate management.

4. Salesforce Help, "Integrate Medical Device Data in Health Cloud": This section details how to "bring medical device data into Health Cloud" for patient monitoring and care coordination, confirming that Remote Device Monitoring is a clinical, not a commercial, feature.

To update an SObject field from an OmniScript, the standard and recommended approach involves two key server-side components. A DataRaptor (specifically a DataRaptor Post Action, formerly Load) is the dedicated tool for performing Data Manipulation Language (DML) operations like creating or updating Salesforce records.

An Integration Procedure is used to bundle this and other server-side actions into a single, reusable transaction. The OmniScript calls the Integration Procedure, which in turn calls the DataRaptor to perform the update. This pattern is a best practice as it minimizes client-to-server calls (improving performance) and separates business logic from the user interface.

B. SOQL Query: A SOQL Query is used exclusively for retrieving (reading) data from Salesforce objects, not for modifying or updating records.

C. API Actions: API Actions are primarily designed to call external REST APIs. While you could call the Salesforce API, DataRaptors are the native, more efficient tool for SObject manipulation.

---

1. Salesforce Help, OmniStudio Documentation, "DataRaptor Load": "Use a DataRaptor Load to create, update, or delete Salesforce data... A DataRaptor Load receives data in JSON or XML format, and writes the data to Salesforce objects." This source confirms that DataRaptors are the correct tool for updating SObjects.

2. Salesforce Help, OmniStudio Documentation, "Integration Procedure Actions": The documentation lists "DataRaptor Post Action" as a primary available action within an Integration Procedure. It states this action "Runs a DataRaptor Load or a DataRaptor Turbo Action." This confirms that Integration Procedures are designed to orchestrate DataRaptors for data updates.

3. Salesforce Trailhead, OmniStudio Architecture, "OmniStudio Service Management": "Integration Procedures run on the server and are the recommended way to save data from an OmniScript... An Integration Procedure can call a DataRaptor to load the data into Salesforce." This reference explicitly states the best practice of using an Integration Procedure to call a DataRaptor for saving data.

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").