Salesforce Accredited Agentforce Health Professional AP-211 Exam Questions

Answer : C

Expanding Access to Auditors:

Exact Extract:

''Use criteria-based sharing rules to grant additional access to Person Account (patients) records for users or groups who do not own the records, such as auditors.''

Other Options:

Restriction rule: Restricts, not expands, access.

User access policy: Not a Salesforce standard for sharing data.

Changing org-wide default to Public Read-Only: Not best practice for PHI and patient data---should use sharing rules for scoped access.

Answer : D

Answer : A, D, E

When complying with HIPAA using Salesforce Shield, Bloomington Caregivers must:

Encrypt sensitive data in transit and at rest:

Shield Platform Encryption ensures encryption at rest; Salesforce uses TLS for encryption in transit.

Extract:

''Salesforce Shield encrypts sensitive data at rest. Salesforce also encrypts data in transit using TLS.''

(Source: Salesforce Security Guide, Shield Platform Encryption Guide)

Implement and regularly review audit trails:

Shield Event Monitoring and Field Audit Trail help monitor data access and modifications.

Extract:

''Implement audit trails and monitor them to detect unauthorized or suspicious activities.''

([Source: Salesforce Security Guide, Shield Platform Encryption Guide])

Configure data retention policies:

Retain records for legally required periods to comply with HIPAA.

Extract:

''Data retention policies must comply with legal and regulatory requirements, including HIPAA.''

([Source: Salesforce Security Guide])

Why not B or C?

Providing access to third-party auditors is not a Salesforce Shield requirement; such reviews are typically handled internally.

Using third-party backup solutions is not a core Shield/HIPAA control within Salesforce, and data residency must be managed with care.

Answer : A, B, C

The Advanced Patient Card in Health Cloud is a FlexCard-based UI component that can be extended to show more patient context, such as Clinical Alerts. To display additional fields (Category, SubjectID, Date for active alerts), the developer should:

A . Clone the parent card

Best practice is to clone the delivered parent Patient Card rather than edit it directly, so you preserve the Salesforce-provided baseline functionality.

B . Create and activate a new child card

Child cards display specific contextual data (such as Clinical Alerts).

To customize which fields show, you create a new child card and activate it.

C . Create a DataRaptor to extract necessary data

Clinical Alert data must be pulled from Health Cloud objects.

A DataRaptor Extract retrieves the required fields (Category, SubjectID, Date) for use in the FlexCard child component.

Why not the others?

D . Define session variables to control visibility of clinical data -- Session variables can control context in OmniStudio, but they aren't required just to display fields on the Patient Card.

E . Change the child card state to show active -- Card states are used for conditional rendering (loading, error, empty states). Showing active alerts requires data filtering in the DataRaptor, not card state changes.

Salesforce Health Cloud Reference:

Salesforce Health Cloud -- Advanced Patient Card

''Clone the Advanced Patient Card to customize it while preserving the delivered version.''

''Use child cards to display detailed data such as conditions, medications, or clinical alerts.''

''Retrieve data for FlexCards with DataRaptor Extracts.''

Answer : C

Step-by-Step Explanatio n:

Requirement Analysis:

The client wants to send patients a personalized summary document after their visit, including their care plan.

The process involves selecting from templates and generating patient-specific content.

Tool Comparison:

Health Cloud Email Manager:

Used for composing and sending emails, not for generating documents from templates.

Salesforce PDF Generator:

While Salesforce can generate PDFs from reports, it does not offer flexible, template-based document generation suited for post-visit summaries or complex care plans, especially with dynamic fields.

OmniStudio Document Generation:

Specifically designed to enable dynamic, template-based document creation in Health Cloud and other Salesforce verticals.

Allows users to select templates, merge patient/case data, and generate PDFs or DOCX that can be sent to patients or caregivers.

Supports integration within Health Cloud flows, empowering users (like a patient advocate) to initiate document generation with a few clicks.

Contract Lifecycle Management:

Focused on legal contracts and workflows, not patient summaries or care plans.

Exact Extracts and Reference from Salesforce Docs:

Extract from OmniStudio Standard Guide:

''OmniStudio Document Generation lets you generate dynamic documents from templates, such as care plans, patient summaries, or correspondence. Templates can be pre-built and allow for the insertion of Health Cloud data fields, enabling the creation of personalized documents for patients or members.''

--- OmniStudio Document Generation Overview

From Health Cloud Admin Guide, under Patient Correspondence:

''Patient advocates can use OmniStudio Document Generation to select templates and create personalized care documents for patients based on their Health Cloud data.''

--- Reference: Administer Health Cloud - Document Generation

Best Practice from Salesforce:

Salesforce recommends OmniStudio Document Generation for any scenario requiring dynamic, patient-specific document creation and distribution.

OmniStudio Document Generation Overview

Administer Health Cloud - Document Generation

Answer : D

Step-by-Step Explanatio n:

Business Process Capabilities:

Intelligent Document Automation: Upload and process patient insurance cards.

Intelligent Document Reader: OCR and extract information to automatically create Member Plan records.

Benefits Verification: Check and verify patient insurance benefits.

Intelligent Appointment Management: Schedule on behalf of the patient with providers.

Salesforce Documentation Reference:

''Use Intelligent Document Automation and Intelligent Document Reader to upload and extract insurance card details, with automated Member Plan creation. Use Benefits Verification and Intelligent Appointment Management to enable scheduling and eligibility checks.''

--- Health Cloud: Intelligent Document Automation

--- Health Cloud: Benefits Verification

--- Health Cloud: Intelligent Appointment Management

Why not the other options?

Only D includes all needed automation for insurance card processing, Member Plan record creation, benefits verification, and scheduling.

Intelligent Document Automation

Intelligent Document Reader

Benefits Verification

Intelligent Appointment Management

Answer : A

* Preconfigured Prior Authorization Objects:

Exact Extract:

''The Health Cloud Care Request Extensions package provides out-of-the-box record types, page layouts, and flows for prior authorizations and other payer workflows.''

* Other Options:

Claims unmanaged package is not for prior authorizations.

Building custom layouts is not necessary when a packaged solution exists.

AppExchange prior authorization packages are not officially supported for core Health Cloud prior auth workflows.