AP-211 Practice Questions

Salesforce Health Cloud's Care Plans are built upon the core Action Plans framework. To create a standardized set of tasks for care coordination, including tasks that are dependent on one another, a consultant must configure an Action Plan Template. This template allows for the definition of problems, goals, and tasks. Crucially, it is within the Action Plan Template that dependencies between tasks can be established, ensuring that certain "intervention tasks" only become available after prerequisite tasks are completed.

A. Industry Template Library: This is a repository of pre-built templates. While it might contain care plan templates, it is not the feature used to configure the dependencies themselves.
B. Intervention Templates: This is not a standard Salesforce feature name. Interventions are represented as problems, goals, and tasks within a Care Plan, which is structured by an Action Plan Template.
D. Care Plan Task Templates: While tasks are a component of a care plan, the overarching template that defines the tasks and their relationships (including dependencies) is the Action Plan Template.

1. Salesforce Help Documentation, "Care Plans in Health Cloud": This document explicitly states, "Care plans use action plan templates to create a set of goals and tasks for a patient." This establishes the direct link between Care Plans and the underlying Action Plan Template framework. (Salesforce Help, Document ID: hlpcareplanswhatis.htm)

2. Salesforce Help Documentation, "Create Action Plan Templates": This guide details the configuration process. In the section "Define Task Dependencies in Action Plan Templates," it states, "Set up dependent tasks to guide your users to complete tasks in a specific order. A dependent task can start only after the task it depends on is complete." This directly confirms that Action Plan Templates are the correct feature for the requirement. (Salesforce Help, Document ID: tasksactionplantemplatescreate.htm)

3. Salesforce Health Cloud Developer Guide, "ActionPlanTemplate": The developer guide describes the ActionPlanTemplate object as the mechanism to "Create templates for plans that you use often." It is the foundational object for templating tasks and is leveraged by the Care Plan functionality. (Salesforce Developer Documentation, Object Reference for Salesforce and Lightning Platform, ActionPlanTemplate object description).

Salesforce Shield Platform Encryption is the comprehensive solution for encrypting sensitive data at rest within Salesforce. It supports the encryption of a wide range of standard and custom fields, as well as files and attachments. This functionality is available in both production and sandbox environments, including full sandboxes. For a Health Cloud implementation, which handles protected health information (PHI), using Shield Platform Encryption is a critical step to help meet compliance requirements like HIPAA by protecting data, including files, in all environments.

A. Classic Encryption: This feature is limited to encrypting custom text fields only; it does not support the encryption of files or attachments.
C. Salesforce Data Mask: This tool is designed to obfuscate or anonymize data in sandboxes for development and testing purposes, not to encrypt live data files at rest for security.
D. Industry Data Security: This is a general term for security practices within an industry and not a specific Salesforce product or encryption solution. ---

1. Salesforce Help Documentation, "What Is Shield Platform Encryption?": This document explicitly states, "You can also encrypt files and attachments stored in Salesforce, such as those attached to records or stored in Salesforce Files, Files Sync, and Chatter." This confirms its capability to encrypt files.

2. Salesforce Help Documentation, "Shield Platform Encryption in Sandboxes": This section clarifies the use in non-production environments: "Shield Platform Encryption is available in sandboxes. When you create a sandbox from a production org that has Shield Platform Encryption, encryption settings are copied to the sandbox."

3. Salesforce Help Documentation, "Encrypt Custom Fields with Classic Encryption": This source details the limitations of the older encryption method: "Classic encryption allows you to encrypt a special type of custom text field." It makes no mention of file encryption capabilities.

4. Salesforce Help Documentation, "Salesforce Data Mask": This document defines the tool's purpose: "Salesforce Data Mask is a powerful tool for Salesforce admins and developers to obscure sensitive data in sandboxes... Data Mask uses platform-native obfuscation technology to mask the data." This distinguishes its function from encryption for data protection at rest.

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.

This combination of features directly addresses the pharma company's requirements. Intelligent Document Automation (IDA), powered by Intelligent Document Reader, automates the process of extracting data from an uploaded insurance card to create a Member Plan record. Benefits Verification allows users to check the patient's insurance eligibility and coverage details. Finally, Intelligent Appointment Management provides the tools to schedule appointments with providers on behalf of the patient. Together, these capabilities form a cohesive intake and scheduling business process within Health Cloud.

A: This option is incorrect because it lacks the required Benefits Verification capability and includes Utilization Management and Care Management, which are not relevant to the specified business process. B: This option is incorrect as it is missing the essential Benefits Verification feature. Virtual Care is also not a requirement described in the scenario. C: This option is incorrect because it includes eFax Integration, which is not required by the scenario, and omits Intelligent Document Reader, the underlying OCR technology for document processing.

1. Intelligent Document Automation & Intelligent Document Reader: Salesforce Help, Health Cloud Administrator Guide, "Automate Document Processing with Intelligent Document Automation". This section states, "Intelligent Document Automation helps you extract data from faxed or uploaded documents and route it to the right place... For example, you can create a flow that automatically creates a Member Plan record when a patient’s insurance card is received." It also clarifies that it uses an OCR service like Intelligent Document Reader.

2. Benefits Verification: Salesforce Help, Health Cloud Administrator Guide, "Verify Insurance Benefits in Health Cloud". This section details the feature used to "Check patient eligibility and benefits information with a few clicks... to help patients understand their health plan coverage and financial responsibility."

3. Intelligent Appointment Management: Salesforce Help, Health Cloud Administrator Guide, "Intelligent Appointment Management". This documentation explains, "Intelligent Appointment Management gives your users a simple, guided flow to schedule appointments," which directly supports the requirement to schedule on behalf of a patient.

A critical consideration when implementing patient or member lists in Health Cloud is the impact of Field-Level Security (FLS). If a list's filter criteria include a field that a specific user does not have permission to view, that user will be completely unable to see or access the list. This security-by-design feature prevents users from seeing potentially incomplete or misleading data. Administrators must ensure that care coordinators have the necessary FLS for all fields used in the filters of the lists assigned to them to guarantee accessibility and proper function.

B: Filter logic for lists is configured using a declarative filter builder, similar to standard Salesforce list views, not exclusively controlled by formula fields. C: The concept of an "override filter field" on the person account is not a standard feature for controlling patient list logic in Health Cloud. D: While it is true that patient lists are built using the Campaign and Campaign Member objects, option A highlights a more critical operational constraint and potential point of failure that must be considered during implementation to ensure users can access the lists.

1. Salesforce Health Cloud Administrator Guide, "Considerations for Patient or Member Lists".

Reference: The guide explicitly states, "If a user doesn’t have access to a field that’s used in a filter on a patient or member list, they can’t see the list." This directly supports the correct answer (A).

2. Salesforce Health Cloud Administrator Guide, "Create and Manage Patient or Member Lists".

Reference: This section details the underlying architecture: "Health Cloud uses campaigns to help you create and manage patient or member lists... When you create a list, you can filter it to show only the records that meet your criteria." This confirms that lists use Campaigns (refuting D as the most important consideration) and a declarative filter builder (refuting B).

3. Salesforce Help, "Field-Level Security".

Reference: General Salesforce documentation on FLS explains its function: "Field-level security settings let you restrict users' access to view and edit specific fields." The behavior described in option A is a specific application of this core platform security principle within the Health Cloud managed package.

The standard patient enrollment process for Advanced Therapy Management in Health Cloud is built using an out-of-the-box OmniScript. OmniScripts are designed to create guided, multi-step user interactions and processes. To customize this enrollment flow to meet specific business needs, such as associating patients with Care Programs, the official and recommended best practice is to clone the standard OmniScript. This allows for modifications while preserving the original component and leveraging the core functionality provided by Health Cloud.

A. FlexCard: FlexCards are used to display contextual information and launch actions, but they do not encompass the entire multi-step logic of an enrollment process.
B. Flow: While Flows are used for automation, the specific guided user interface for Advanced Therapy Management enrollment is built with OmniScript, which is part of the OmniStudio suite.
C. Apex Class: Apex is for custom backend logic. The user-facing, guided enrollment path is configured using OmniScript, not by directly cloning and modifying Apex code.

1. Salesforce Health Cloud Developer Guide: Customize the Enrollment Process for Advanced Therapy Management. This section explicitly states, "The enrollment process for Advanced Therapy Management uses an OmniScript that you can clone and customize to suit your business needs. The OmniScript is called Enrollment." It then provides detailed steps for cloning and activating the customized OmniScript.

2. Salesforce Health Cloud Developer Guide: Advanced Therapy Management Data Model. This section describes the objects involved, such as Care Program and Care Program Enrollee, which the customized OmniScript would interact with to fulfill the requirement of associating patients to care programs.

3. Salesforce OmniStudio Documentation: OmniScripts. This documentation defines OmniScripts as the tool for creating guided paths to complete a business process, confirming its role as the correct component for a guided enrollment journey. The documentation states, "An OmniScript is a guided path to complete a business process."

Data Processing Engine (DPE) is the designated Health Cloud tool for enhancing the performance and scalability of Provider Search. DPE jobs are used to extract, transform, and load provider data from various source objects into a single, denormalized object named Care Provider Searchable Field. By pre-processing and flattening the data into this dedicated search object, the system avoids complex, real-time queries across multiple objects. This architecture significantly improves search speed and efficiency, ensuring a scalable solution for large provider networks.

A. Pipeline Analytics is a tool for visualizing and analyzing data in a sequential process, such as a sales funnel, and is not used for optimizing data search performance.
C. Business Rules Engine is used to automate complex decisions and calculations based on defined criteria; it does not handle the data transformation required for scalable search.
D. Flow for Industries is a process automation tool used to guide users through workflows; it does not perform the large-scale data processing needed to optimize search performance.

1. Salesforce Health Cloud Developer Guide: "Set Up Provider Search". This section explicitly states, "To make provider data available for search, create Data Processing Engine definitions that extract provider data from various objects and load it into the Care Provider Searchable Field object... Using this denormalized object makes searching for providers faster and more efficient."

2. Salesforce Help Documentation: "Data Processing Engine". This document describes DPE as a tool to "transform data that's available in your Salesforce org and write back the results as new records or update existing records," which is precisely its function in the Provider Search context.

3. Salesforce Health Cloud Administrator Guide: "Provider Relationship Management Data Model". The guide details the CareProviderSearchableField object and its purpose, explaining it stores a "flattened, denormalized version of provider data" to support efficient searching, a process managed by the Data Processing Engine.

Complying with HIPAA using Salesforce Shield involves a multi-faceted approach addressing key tenets of the HIPAA Security Rule.
1. Encryption (A): A primary technical safeguard is protecting electronic Protected Health Information (ePHI). Salesforce Shield Platform Encryption encrypts data at rest, complementing Salesforce's default Transport Layer Security (TLS) for data in transit.
2. Audit Controls (D): HIPAA requires mechanisms to record and examine activity in systems containing ePHI. Shield Event Monitoring provides detailed audit trails, enabling organizations to monitor for unauthorized access or suspicious behavior.
3. Data Retention (E): HIPAA mandates retaining documentation and records for specific periods. Shield Field Audit Trail extends the tracking of data changes for up to 10 years, helping organizations implement and prove adherence to their data retention policies.

B. Providing direct system access to auditors is a specific procedural choice, not a foundational compliance requirement. Audits can be conducted by reviewing reports and exported logs.
C. While a backup plan is required by HIPAA, mandating a third-party off-site solution is overly prescriptive and not a direct consideration for implementing Shield itself.

1. U.S. Department of Health & Human Services (HHS). The Security Rule, 45 C.F.R. § 164.302-318.

§ 164.312(a)(2)(iv): Recommends implementing a mechanism to encrypt and decrypt ePHI (supports option A).

§ 164.312(b): Requires implementation of "hardware, software, and/or procedural mechanisms that record and examine activity in information systems" (supports option D).

§ 164.316(b)(1): Mandates retention of required documentation for six years, which necessitates data retention policies and tools to support them (supports option E).

2. Salesforce Developer Documentation. Shield Platform Encryption.

"Encrypt Data" section: "Shield Platform Encryption gives your data a whole new layer of security while preserving critical platform functionality. It enables you to encrypt sensitive data at rest...without modifying existing custom fields, or custom objects." This directly supports the "at rest" component of option A.

3. Salesforce Help. Monitor Login and User Activity with Event Monitoring.

"Event Monitoring" article: "Event Monitoring is one of many tools that Salesforce provides to help keep your data secure... You can see who is accessing critical business data, when they are accessing it, and from where." This directly supports the audit trail requirement in option D.

4. Salesforce Help. Field Audit Trail.

"Field Audit Trail" article: "With Field Audit Trail, you can know the state and value of your data for any date, at any time... You can use it to create a forensic data-level audit trail, which can be useful for regulatory compliance..." This directly supports the data retention and policy requirements in option E.

Health Cloud provides out-of-the-box Identity Verification Flow Templates specifically designed to streamline caller authentication in contact centers. These templates can be cloned and customized to create guided, step-by-step flows for agents. By using these flows, agents can consistently and efficiently verify a caller's identity against information stored in Salesforce, such as date of birth or address. This directly addresses the company's goal of reducing manual processes and leveraging a standard Health Cloud feature for a more streamlined agent experience.

A. Reusable Verification FlexCards are primarily used to display contextual information to the user, not to orchestrate the multi-step process of identity verification.
C. While OmniScript can create guided interactions, the standard, out-of-the-box Health Cloud feature for this specific use case is the set of pre-built Flow Templates.
D. "Verify Customer Identity Process Flow" is a generic description of a business process, not the name of a specific, configurable feature within Health Cloud.

1. Salesforce Help Documentation, Health Cloud Administrator Guide, "Identity Verification in Health Cloud" section. This section explicitly states, "Health Cloud provides flow templates that you can clone and customize to create your own identity verification flows." This confirms that flow templates are the designated out-of-the-box feature for this purpose.

2. Salesforce Help Documentation, Health Cloud Administrator Guide, "Verify a Caller’s Identity" section. This page details the end-user experience and administrative setup, noting, "To help your users verify a caller’s identity, you can define identity verification process flows based on your company’s policies." It then directs administrators to use Flow Builder with the provided templates.

The Health Cloud Clinical data model is specifically designed to represent a patient's clinical information, including medications, conditions, allergies, and immunizations. This data model is architected to align with the Fast Healthcare Interoperability Resources (FHIR) R4 standard. It provides standard objects such as Medication, MedicationStatement, and MedicationRequest that directly map to corresponding FHIR resources. This alignment ensures that clinical data from external systems like EHRs can be represented in a standardized, interoperable format within Salesforce, making it the correct model for viewing medication data leveraging FHIR.

A. Virtual Care data model: This model supports remote patient interactions and telehealth services, not the foundational storage of standardized clinical data like medications.
B. Integrated Care Management data model: This model focuses on care plans, problems, goals, and tasks for coordinating patient care, rather than storing the core clinical data itself.
D. Electronic health record (EHR) data model: This is a general term for an external system's data structure. Health Cloud's specific, FHIR-aligned implementation for this data is the Clinical data model.

1. Salesforce Help, Health Cloud Data Models, "The Clinical Data Model": "The clinical data model in Health Cloud is aligned with the FHIR (Fast Healthcare Interoperability Resources) specification... Use the clinical data model to represent a patient's medical history, such as conditions, medications, and immunizations."

2. Salesforce Help, Health Cloud Data Models, "Map Your EHR Data to Health Cloud Objects": This document explicitly shows the mapping of medication-related data from an EHR to Health Cloud objects like MedicationStatement and MedicationRequest, which are core components of the Clinical data model.

3. Salesforce Health Cloud Developer Guide, "Understand the Health Cloud Data Models", Section: "Clinical Data Model": "The clinical data model is based on the FHIR standard... It includes objects to manage information about a patient's conditions, medications, allergies, immunizations, and more." (Refer to the latest version of the guide for specific section titles).