Salesforce AP-211 - Salesforce Accredited Agentforce Health Professional

To make Provider Search available to external portal users, the admin must place the Provider Search component on an Experience Cloud site page and grant the external profile Read access to Care Provider Searchable Field. Provider Search uses healthcare-specific provider and facility relationships so users can search by criteria such as specialty, location, network, and practice attributes. From a deployment perspective, the configuration must be activated, licensed, permissioned, or migrated in the correct sequence so that the functionality is available to users without weakening the organization ' s existing security and governance controls. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Give the site user profile Read access to the Care Provider Searchable Field object.; Use Experience Builder to add the Provider Search component to a page on the site.) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Deploy - Provider Search

===============

Once configured, the administrator must ensure the Timeline configuration is active and properly placed and saved on the target Lightning record page. Enhanced Timeline displays configured records chronologically while enforcing the user ' s underlying object, field, and record access. From a deployment perspective, the configuration must be activated, licensed, permissioned, or migrated in the correct sequence so that the functionality is available to users without weakening the organization ' s existing security and governance controls. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Add the Timeline component to the Patient Lightning page and activate the Timeline.) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Deploy - Enhanced Timeline

===============

To enable patient self-service scheduling across clinics and specialties, Experience Cloud hosts the patient portal, Provider Search allows filtering physicians by location and specialty, and Intelligent Appointment Management (IAM) handles the appointment booking engine. Provider Search uses healthcare-specific provider and facility relationships so users can search by criteria such as specialty, location, network, and practice attributes. Intelligent Appointment Management coordinates appointment discovery and booking and can use Salesforce Scheduler or an external scheduling system as the scheduling engine. From a solution-design perspective, the selection fits the requirement because it uses the Health Cloud capability or data model that directly represents the business need, rather than introducing a parallel custom structure or a feature intended for a different stage of the patient, member, provider, or payer lifecycle. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach.

Study Guide references/topics:Design - Provider Search; Intelligent Appointment Management

===============

Salesforce Shield Platform Encryption supports encrypting files, attachments, search index files, and custom/standard fields across production and sandbox environments. Salesforce Shield combines Platform Encryption, Event Monitoring, and Field Audit Trail to strengthen protection, monitoring, and auditability for sensitive information. From an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Salesforce Shield) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - Shield

===============

Integrated Care Management leverages Action Plan Templates to structure care plan interventions and tasks with preconfigured task dependencies and sequences. Integrated Care Management structures care plans around reusable problems, goals, interventions, assessments, and care-team activities so care coordination can be standardized and personalized. From an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Action Plan Templates) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - Care Plan

===============

Health Cloud ' s core clinical data architecture is standardized on HL7 FHIR R4 (Fast Healthcare Interoperability Resources), making it the primary interoperability standard. FHIR R4 provides standardized healthcare resources and REST-oriented semantics, reducing dependence on proprietary object structures when clinical data is exchanged with EHRs, payers, or other healthcare systems. From a solution-design perspective, the selection fits the requirement because it uses the Health Cloud capability or data model that directly represents the business need, rather than introducing a parallel custom structure or a feature intended for a different stage of the patient, member, provider, or payer lifecycle. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (FHIR R4) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Design - FHIR

===============

Intelligent Document Automation (IDA) captures, extracts, and digitizes data from received faxes/documents using OCR. Utilization Management (UM) manages the end-to-end clinical review and determination/approval process for care authorizations. Utilization Management structures care requests, authorization review, medical-necessity determination, concurrent review, and related payer-provider approval workflows. Intelligent Document Automation and related document-reading capabilities transform inbound healthcare documents into structured Salesforce information while supporting document review and downstream workflows. From a solution-design perspective, the selection fits the requirement because it uses the Health Cloud capability or data model that directly represents the business need, rather than introducing a parallel custom structure or a feature intended for a different stage of the patient, member, provider, or payer lifecycle. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Utilization Management; Intelligent Document Automation) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Design - Utilization Management; Intelligent Document

===============

OmniStudio FlexCards (UI), Integration Procedures (data orchestrator combining internal and external APIs), and DataRaptors (internal data transform) form the recommended declarative stack for composite data display. OmniStudio separates presentation, guided interaction, Salesforce data access, and server-side orchestration through FlexCards, OmniScripts, DataRaptors/Data Mappers, and Integration Procedures. DataRaptors, now also represented as Data Mappers in current OmniStudio terminology, declaratively extract, transform, and load Salesforce data for OmniStudio components. From an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Integration Procedures; DataRaptors; FlexCards) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - OmniStudio; DataRaptor; Integration Procedure

===============

In OmniStudio, DataRaptor Load is the declarative tool used to update or insert records into Salesforce SObjects. Integration Procedures are used as best practice controller layers behind OmniScripts to orchestrate DataRaptors. OmniStudio separates presentation, guided interaction, Salesforce data access, and server-side orchestration through FlexCards, OmniScripts, DataRaptors/Data Mappers, and Integration Procedures. DataRaptors, now also represented as Data Mappers in current OmniStudio terminology, declaratively extract, transform, and load Salesforce data for OmniStudio components. From an implementation perspective, the configuration should use delivered Health Cloud and Salesforce mechanisms first, preserving standard relationships, security enforcement, and upgrade compatibility while limiting custom code to cases where declarative capabilities are insufficient. The remaining options do not directly satisfy the stated requirement; they either address a different functional domain, provide only part of the required behavior, or introduce unnecessary customization compared with the selected Health Cloud approach. This approach also keeps the solution aligned with the standard Agentforce Health data and process model, which is important for maintainability, reporting, interoperability, and consistent user access. In practical terms, the consultant should configure and validate the selected elements (Integration Procedures; DataRaptors) against the scenario ' s acceptance criteria and confirm that the intended users can access the underlying records and functionality.

Study Guide references/topics:Implement - OmniStudio; DataRaptor; Integration Procedure

===============