Free Salesforce Accredited Agentforce Health Professional AP-211 Exam Questions

Step 1: Requirement Analysis

Payer needs to manage healthcare expenses while ensuring quality, affordable care.

Seeks to streamline approval processes for care requests.

Step 2: Utilization Management in Health Cloud

Utilization Management (UM) provides workflows and automation for reviewing, approving, or denying care requests. This supports balancing cost controls with quality care through evidence-based review processes.

Extract:

''Utilization Management helps payers manage costs and ensure members receive appropriate care by streamlining the review and approval process for pre-authorizations and care requests.''

Administer Health Cloud -- Utilization Management

Step 3: Review of Options

A . Utilization Management: Directly addresses care request review, cost, and quality balance.

B . Provider Network Management: Focuses on managing provider networks, not utilization/cost review.

C . Intelligent Appointment Management: For scheduling only.

D . Integrated Care Management: Focuses on care coordination, not cost/approval workflow.

In OmniStudio FlexCards, when you want to change the visual styling of a field element (e.g., font type, font color, formatting), you have two main options:

A . Write custom CSS

OmniStudio FlexCards allow applying custom CSS classes for fine-grained control of styles.

This is how you can specify a font like Times New Roman or apply a red color.

B . Make edits to Field Style

The Field Style editor within the FlexCard Designer lets you directly configure basic styling properties (like text color, background, alignment, etc.) without needing custom CSS.

Why not the others?

C . Make edits to Setup Panel -- The Setup Panel is for data source, conditions, and layout configuration, not for styling individual fields.

D . Make edits to Field Properties -- Field Properties are used to configure which data is displayed and how it behaves (like label, formatting rules, or conditional display), but styling is handled through Field Style or CSS, not properties.

Salesforce OmniStudio Reference:

Salesforce OmniStudio FlexCard Designer Guide

''You can use the Field Style editor to set basic styles, such as font color and alignment.''

''For advanced customization, apply custom CSS classes to field elements.''

When implementing Intelligent Appointment Management to eliminate reliance on external scheduling systems, a consultant should leverage two connectivity options as the scheduling engine:

• Salesforce Health Cloud Scheduling Engine: The native Health Cloud scheduling engine can be used directly as the primary scheduling system, eliminating the need to switch to external tools
• Third-Party Scheduling System API: Alternatively, Health Cloud can integrate with existing third-party scheduling systems via their APIs, allowing the organization to leverage their current scheduling infrastructure while managing appointments through Health Cloud

These two options provide flexibility: organizations can either adopt the native Health Cloud scheduling capabilities or integrate with their existing scheduling systems. The choice depends on the organization's current technology stack and business requirements. Intelligent Appointment Management can work with either approach to consolidate scheduling within Health Cloud and eliminate swivel-chairing between systems.

Step-by-Step Explanatio n:

Health Cloud Best Practice for Displaying Internal and External Data:

FlexCards (part of OmniStudio) can display data from multiple sources in a unified view on a patient record.

Integration Procedures connect to external systems and bring in data (e.g., from EHRs or other sources).

DataRaptors extract and transform Salesforce data for display and use in FlexCards.

Salesforce Documentation Reference:

''FlexCards can display internal Salesforce data and call Integration Procedures or DataRaptors to bring in external or standard object data.''

--- OmniStudio Standard Guide

''Integration Procedures are used to retrieve and update data from external systems and can be invoked directly from FlexCards or OmniScripts.''

--- OmniStudio Integration Procedures

''DataRaptors map Salesforce data to and from FlexCards and Integration Procedures, enabling seamless display of patient information.''

--- OmniStudio DataRaptors

Other Options:

Salesforce Flows: Good for automation but not for real-time display of combined external and internal data on record pages.

Visualforce Pages: Legacy solution, not recommended for modern Health Cloud patient page display, and does not natively integrate with OmniStudio tools.

OmniStudio Standard Guide

OmniStudio Integration Procedures

OmniStudio DataRaptors

To manage run rate business and ensure contract compliance in Health Cloud, a consultant should recommend two key features:

• Run Rate Contracts: This feature specifically tracks and manages contract run rates, enabling the company to monitor ongoing contract performance and revenue recognition aligned with contract terms
• Contract Lifecycle Management: This feature provides comprehensive contract management capabilities including tracking contract milestones, compliance requirements, renewal dates, and contract obligations to ensure the company meets all contractual commitments with customers

Together, these features enable MedTech companies to effectively manage contract compliance, track financial performance against contract terms, and ensure all contractual obligations are met throughout the contract lifecycle.

In Salesforce Health Cloud, when a customer wants to view and navigate to critical patient information such as insurance, clinical, and primary care physician details, the right feature to implement is the Advanced Patient Card.

The Advanced Patient Card provides a configurable panel that displays key patient information at a glance directly on the patient's profile.

It allows quick navigation to related records (insurance coverage, care team/PCP, clinical info, etc.) without switching pages.

It's specifically designed to give providers and service representatives a 360-degree view of the patient's most important details.

Why not the others?

A . Enhanced Highlights Panel -- This is a general Salesforce feature to show record highlights, but it's not tailored to healthcare-specific patient insights.

B . Enhanced Timeline -- Useful for viewing chronological events (interactions, activities, encounters), but not for quick access to insurance/PCP details.

D . Patient Path -- This is a visual guide for patient journeys or care programs, not for surfacing key profile details.

Salesforce Health Cloud Reference:

Salesforce Health Cloud Implementation Guide -- Advanced Patient Card:

''Use the Advanced Patient Card to display a patient's most critical information---such as coverage, conditions, medications, and care team members---directly on the patient profile for easy reference and navigation.''

Salesforce Help: Advanced Patient Card

Step-by-Step Explanatio n:

CRM Analytics for Health Cloud:

Exact Extract:

''CRM Analytics for Health Cloud delivers prebuilt dashboards and extended analytics for monitoring care plans, outcomes, and adherence across networks and facilities.''

Why Not Other Options?

Insights for Health Cloud: Not a standard reporting/analytics product for care plan adherence.

Reporting unmanaged package: Not mentioned in the latest Health Cloud documentation.

Care Management Extension: Refers to process automation, not analytics.

Two out-of-the-box permission sets that should be assigned to users to give them access to Health Cloud are:

• Health Cloud User: This is the primary permission set for full Health Cloud users, granting access to all major Health Cloud features, objects, and functionality including care management, appointments, assessments, and patient records
• Health Cloud Limited User: This permission set provides a more restricted level of access for users who need to access Health Cloud but with limited functionality, such as viewing-only access or access to specific Health Cloud features

The choice between these two depends on the user's role and responsibilities. Most clinical and operational staff would receive the Health Cloud User permission set for full functionality, while support staff, administrators, or users with specific limited roles may receive the Health Cloud Limited User permission set. Additional role-specific permission sets may also be assigned depending on the user's responsibilities. These permission sets should be assigned during user provisioning prior to go-live to ensure all users have appropriate access from day one.

Comprehensive Detailed Step by Step Explanation with exact Extracts from Salesforce Health Cloud documents that you have with Reference

Request Review Types:

Utilization Management processes center around reviewing requests for appropriateness of care, with the three main types being Prior Authorization Review, Concurrent Review, and Retrospective Review.

Extract:

''Utilization Management supports prior authorization, concurrent, and retrospective reviews to evaluate care appropriateness case by case.''

--- Utilization Management in Health Cloud

Care Requests:

Care Requests are the mechanism for providers to seek authorization from payers for drugs, services, or admissions.

Extract:

''Design care request processes to support providers seeking health plan authorization for services, medications, or admissions.''

--- Health Cloud Utilization Management Data Model

Why not the other options?

A: Next Best Action is more for care management recommendations, not utilization review.

C: Intake agent count is an operational consideration, not a UM process.

Utilization Management Overview

Utilization Management Data Model

Step-by-Step Explanatio n:

Requirement:

Encrypt files in a full sandbox instance.

Salesforce Shield Platform Encryption:

Provides encryption of files and attachments at rest across Salesforce environments (including sandboxes).

''Use Shield Platform Encryption to encrypt files and attachments stored in Salesforce, including those in sandbox environments.''

--- Salesforce Shield Platform Encryption Guide

Other Options:

Classic Encryption: Only encrypts a limited set of standard fields, not files or attachments.

Salesforce Data Mask: Masks data for sandbox use, but does not encrypt files for runtime.

Industry Data Security: Not a Salesforce product for file encryption.

Shield Platform Encryption Guide