Salesforce AP-211 Exam Questions

Step-by-Step Explanatio n:

Intelligent Document Automation:

Exact Extract:

''Intelligent Document Automation in Health Cloud automatically extracts data from incoming documents, including faxes, and creates structured data for downstream workflows.''

Utilization Management:

Exact Extract:

''Utilization Management provides workflows and automation to support end-to-end approval processes, including clinical review and authorizations.''

Why Not Other Options?

Integrated Care Management: Focuses on care plans and assessments, not document automation or clinical approval processes.

Care Authorizations: Part of Utilization Management but not the capability for document ingestion and process automation.

Step-by-Step Explanatio n:

Health Cloud Intelligent Document Automation (IDA) Capabilities:

IDA automates processing of incoming documents (like insurance cards or clinical records).

Out-of-the-box features allow:

Document Rotation: For correcting the orientation of scanned/received documents.

Record Type Association: For matching documents to appropriate Salesforce record types (such as associating a document with a Patient or Encounter).

Automated Document Checklist Item Creation: Automatically creating checklist items for actions (e.g., missing forms or needed verifications).

Supported and Unsupported Features:

Barcode Scanning: Not an out-of-the-box feature of Health Cloud IDA (may require third-party solutions).

eFax Connection: While Health Cloud supports document management, direct eFax integration is not out-of-the-box.

Official Document Extracts:

From Salesforce Help:

''You can rotate, associate, and automate checklist items for documents received in Health Cloud using Intelligent Document Automation.''

--- Administer Health Cloud -- Document Automation

Intelligent Document Automation Overview

Step 1: Understanding the Discovery Framework in Health Cloud

The Discovery Framework in Salesforce Health Cloud is designed to streamline intake and clinical assessments by providing reusable, modular, and compliant tools for healthcare organizations. It enables organizations to collect, store, and reuse responses to assessment questions efficiently and securely.

''Discovery Framework provides a way to design, distribute, and reuse forms and assessments for clinical and non-clinical scenarios. It leverages reusable question banks, digital data capture, and integration with Health Cloud objects.''

Administer Health Cloud -- Assessments and Discovery Framework

Step 2: FHIR Question Bank

Capability: The use of a FHIR-based Question Bank allows healthcare organizations to standardize questions and reuse them across multiple assessments. This ensures consistency and regulatory compliance in data collection.

Extract:

''The Question Bank leverages the FHIR Questionnaire resource, making it easy to define, store, and reuse question sets for various clinical assessments.''

Administer Health Cloud -- Discovery Framework: Question Bank

Step 3: Digital Signature Capture

Capability: Digital Signature Capture is supported natively in Health Cloud assessments, ensuring consent, authenticity, and regulatory compliance.

Extract:

''Out-of-the-box support for digital signature capture in assessment forms allows for secure, auditable consent capture, which is often required for clinical or legal compliance.''

Administer Health Cloud -- Discovery Framework Features

Step 4: Using Previously Submitted Responses

Capability: The ability to use previously submitted responses enhances user experience and speeds up the intake process by pre-populating assessments with earlier responses where relevant.

Extract:

''You can configure assessments to pre-fill questions with responses from prior assessments, supporting both efficiency and patient engagement.''

Administer Health Cloud -- Reuse of Data in Assessments

Step 5: Options Not Natively Supported Out-of-the-Box

A . Adding a QR Code: Not natively supported in Health Cloud Discovery Framework out-of-the-box for assessments. This would require custom development or external integrations.

B . SMS Assessment Completion: Not supported out-of-the-box; may require integration with Marketing Cloud or external SMS services and customization.

Reference for non-supported features:

''Features such as QR code generation or SMS completion notifications are not available out of the box and would require customizations or integrations.''

Administer Health Cloud

Video Visits for Social Determinants of Health (SDOH):

Exact Extract:

''Use Virtual Care in Health Cloud to enable video visits between care providers and patients, including for conversations about social and economic factors.''

Other Options:

Telehealth: A generic term; Salesforce feature is specifically named ''Virtual Care.''

Intelligent Appointment Management: Focuses on scheduling, not video.

Integrated Care Management: For care plans and interventions, not video visits.

When onboarding Health Cloud into an org that already uses Service Cloud, it's critical to properly configure Organization-Wide Defaults (OWD) to ensure that protected health information (PHI) remains restricted.

The correct settings are:

A . Set Person Accounts to Private

Patients are modeled as Person Accounts in Health Cloud.

Setting Person Accounts to Private ensures PHI isn't exposed to users outside the Health Cloud business unit.

B . Set related clinical objects to Controlled by Parent or Private

Clinical objects (e.g., Care Plans, Assessments, Referrals) often relate to patients.

Making them Controlled by Parent (Person Account) or Private ensures only authorized users can see PHI.

E . Set Health Details to Controlled by Parent or Private

Health Details contain sensitive clinical data.

Must be restricted at the OWD level to prevent exposure to non-Health Cloud users.

Why not the others?

C . Set Account and Contract to Private

Regular business Accounts/Contracts are part of Service Cloud, not typically where PHI resides. Restricting them isn't required for PHI protection.

D . Set Contact to Controlled by Parent

Contacts in Health Cloud are often caregivers or providers, not patients (who are Person Accounts).

PHI protection centers around Person Accounts + Clinical Objects + Health Details, not Contacts.

Salesforce Health Cloud Reference:

Salesforce Health Cloud Security and Sharing Guide:

''For HIPAA and other PHI compliance, set Person Accounts and Health Cloud clinical objects to Private or Controlled by Parent.''

''Ensure Health Details are not exposed via default sharing.''