Salesforce Accredited Agentforce Health Professional Study Guide
- Platform Administrator
- Platform App Builder
- Platform Foundations
- Platform Developer
- Platform Administrator II
- Agentforce Sales Consultant
- Agentforce Service Consultant
- Platform Data Architect
- Platform Development Lifecycle and Deployment Architect
- Platform Identity and Access Management Architect
- Platform Integration Architect
- Platform Sharing and Visibility Architect
- Heroku Architect
- B2C Solution Architect
- Experience Cloud Consultant
- Agentforce Field Service and Operations Consultant
- Agentforce Nonprofit Consultant
- Data 360 Consultant
- Omnistudio Consultant
- CRM Analytics and Einstein Discovery Consultant
- Platform User Experience Designer
- Platform Strategy Designer
- B2C Commerce Developer
- JavaScript Developer
- Omnistudio Developer
- Platform Developer II
- Marketing Cloud Engagement Administrator
- Marketing Cloud Engagement Specialist
- Marketing Cloud Engagement Consultant
- Marketing Cloud Account Engagement Specialist
- Marketing Cloud Next Consultant
- Agentforce Sales Foundations
- Business Analyst
- Marketing Cloud Engagement Developer
- Marketing Cloud Engagement Foundations
- Agentforce Specialist
- Agentforce Life Sciences Consultant
- B2B Commerce Administrator AP
- B2B Commerce Developer AP
- Agentforce Communications AP
- Agentforce Consumer Goods AP
- Agentforce Financial Services AP
- Agentforce Health AP
- Agentforce Manufacturing AP
- Public Sector Solutions AP
- Revenue Cloud Consultant
- MuleSoft Integration Foundations
- MuleSoft Developer
- MuleSoft Developer II
- MuleSoft Platform Integration Architect
- MuleSoft Platform Architect
- Tableau Desktop Foundations
- Tableau Data Analyst
- Tableau Consultant
- Tableau Server Administrator
- Tableau Next Consultant
- Tableau Architect
- Slack Administrator
- Slack Consultant
- Slack Developer
Checklist progressProgress
0/167Learned
Checklist progressProgress
0/167Learned
Given customer use cases, define the personas and stakeholders
0/8
Given customer requirements, define the capabilities that need to be analyzed for a successful project
0/3
Given a customer's desired outcomes, gather functional and technical requirements to meet customer outcomes
0/10
- Functional versus nonfunctional requirements and project constraints
- Choosing an elicitation technique for clinical and operational stakeholders
- Turning desired health outcomes into measurable requirements and user stories
- Business analysis deliverables for capturing discovery findings
- Care coordination requirements and Integrated Care Management capabilities
- Prior authorization requirements and Utilization Management capabilities
- Gathering EHR integration and interoperability requirements
- Gathering legacy data, provider data and data quality requirements
- Gathering privacy, security and consent requirements for patient data
- Prioritizing competing requirements and reaching stakeholder sign-off
- Core platform features versus the legacy managed package
- Utilization Management for prior authorization and care request review
- Patient and member record modeling
- Modeling caregivers and other supporting people
- Household and relationship objects around a patient
- Individual practitioner records: person and role objects
- Modeling provider organizations and what they do
- Modeling provider branches and healthcare facilities
- Practitioner-to-facility assignments and working hours
- Provider specialty and taxonomy objects
- Provider credential and identifier objects
- Payer network and facility network participation
- Modeling a member's health plan coverage
- Code sets and code set bundles for clinical terminology
- Clinical objects for conditions, medications and diagnostic results
- Linking clinical encounters to providers and facilities
- Declarative-first design with Omnistudio and Flow before custom code
- Patient 360 record page design with timeline and patient card components
- Actionable Relationship Center for patient and provider relationship networks
- Experience Cloud sites for patient, member and caregiver collaboration
- Inbound document automation versus outbound document generation
- Agentforce Health feature groups matched to customer requirements
- Care Programs versus Integrated Care Management care plans
- Assessments for standardized screening and patient data gathering
- Social determinants of health for addressing care barriers
- Provider Network Management across the provider lifecycle
- Provider Search and provider relationship cards
- Intelligent Appointment Management versus Field Service for care visits
- Benefits verification versus prior authorization
- Matching a healthcare vertical to Agentforce Health feature groups
- Payer shop, quote and enrollment experiences for individual and group members
- Payer member service contact center design
- Utilization Management design for payers versus providers
- Pharma patient support program design with care programs
- MedTech commercial design with sales agreements versus account forecasting
- Patient journey stages mapped to Agentforce Health data models
- Patient access and front-office process design with Patient and Member Services
- Care coordination process design with Care Orchestration capabilities
- Provider lifecycle process design with Provider Network Management
- Choosing industry automation tools for a health business process
- Translating health business objectives into measurable success metrics
- Custom report types for FHIR-aligned clinical objects
- Dashboard visibility for PHI with running user and dynamic dashboards
- Tracking KPI trends over time with reporting snapshots
- Standard reports and dashboards versus CRM Analytics and Data 360 for health KPIs
- Record access model for patient and member person accounts
- Field-level protection and classification of sensitive clinical fields
- Shield Platform Encryption for protected health information at rest
- Authentication, session controls and security baseline for health users
- Patient and caregiver data access on Experience Cloud sites
- Identity Verification before disclosing protected health information
- Consent capture for patient communications and data use
- Auditing and monitoring access to patient health data
- Integration pattern selection for health data exchange
- Middleware versus point-to-point integration in a multi-system health landscape
- EHR clinical data integration into the FHIR-aligned clinical data model
- Omnistudio Integration Procedures for server-side calls to external systems
- Salesforce Connect data virtualization versus copying external health data into the org
- Data 360 for unifying patient data across external systems
- Securing integrations that exchange protected health information
- Current-state and future-state process mapping for health customers
- Customer language and stakeholder engagement in process redesign
- Multiple business processes and record types for health case lifecycles
- Action Plans versus care plans and Flow Orchestration for multistep processes
- Systems of record across the legacy and future-state health landscape
- Migration strategy, historical data scope and go-live cutover
- Mapping legacy clinical data to standard FHIR-aligned target objects
- Data cleansing and duplicate prevention for patient and provider loads
- External IDs and upsert for retaining legacy identifiers
- Load sequencing for provider, facility, and clinical record relationships
- Choosing a data load tool for health data volume and complexity
- Integrity controls during bulk legacy loads
- Trial loads, validation, and reconciliation before production migration
- Managed package versus core platform installation path
- Org readiness checks and edition requirements before feature setup
- Person account enablement before Agentforce Health feature setup
- Omnistudio as a setup prerequisite in Agentforce Health orgs
- Enabling the Agentforce Health features a finalized design calls for
- Permission set licenses versus permission sets for Agentforce Health users
- User provisioning, custom profiles and bulk license assignment
- Care program setup and enrollment rules
- Consent capture for care programs with authorization forms
- Integrated Care Management care plans versus managed-package care plans
- Healthcare provider records and provider search setup
- Provider network management for onboarding, credentialing and contracting
- Intelligent Appointment Management configuration
- Benefits verification in patient access workflows
- Utilization Management configuration for payers and providers
- Commercial Excellence features for medtech sales teams
- Omniscripts versus Flexcards for health user experiences
- Integration Procedures versus Data Mappers for health data operations
- Omnistudio standard runtime versus managed package runtime settings
- Omnistudio permission sets for health builders and end users
- Access control for Data Mappers and Integration Procedures
- Customizing standard Omnistudio components versus custom builds
- Advanced Patient Card Flexcard on patient records
- Customizing Intelligent Appointment Management Omniscripts
- Utilization Management prebuilt Omnistudio components
- Integration Procedure blocks, caching and long-running steps
- Patient and provider record types and page layouts on person accounts
- Households and group memberships for related individuals
- Enhanced Timeline configuration for patient and member events
- Customizing the managed-package Agentforce Health console
- Action Plans versus care plans for repeatable task sets
- Lead-to-patient conversion and lead-based referral tracking
- Document Generation and electronic signatures for health records
- Intelligent Document Automation and Document Reader for inbound forms
- Experience Cloud sites for patient and member self-service
- Extending standard health objects versus building custom objects
- Managed package triggers and custom automation coexistence
- Bulk API versus REST and SOAP API for health data volume and timing
- Salesforce Healthcare API (FHIR) versus generic platform APIs for EHR exchange
- When to use Agentforce Health Business APIs
- Event-driven health integrations with Pub/Sub API and platform events
- MuleSoft Direct prebuilt integration apps for Agentforce Health
- Object, field and record-level access layers for health personas
- Field-level security versus page layouts for protected health fields
- Lightning page component visibility rules by user or record criteria
- Org-wide defaults as the baseline for patient and member records
- Role and territory hierarchies for record access in a care organization
- Owner-based versus criteria-based sharing rules
- Teams, queues and manual sharing for collaborative record access
- When to use Apex managed sharing
- Restriction rules for narrowing access to sensitive health records
- Sharing and permission setup for care program and consent objects
- Sharing sets and share groups for patient and member site users
- User sharing and visibility between internal and external users
- Guest and site user access for public-facing health sites
- Source objects for care program, utilization management and appointment KPIs
- Standard versus custom report types for Agentforce Health data
- Report format selection for agreed KPI layouts
- Bucket fields and report formulas for health KPIs
- Dashboard components, filters and running user for care team KPIs
- Report folder access versus record visibility in report results
- Scheduled delivery and subscriptions for agreed reports
- Adoption and business-outcome dashboards for validating success criteria
- Basic org setup before configuring Agentforce Health features
- Capability prerequisites before deploying a specific Agentforce Health feature
- Sandbox-to-production release planning and deployment validation
- Choosing a deployment tool for Omnistudio components between orgs
- Pre-go-live training plan and pilot rollout
- Manual post-deployment tasks in production for an Agentforce Health use case
- Omnistudio component activation, access and upgrades after deployment
- Post-go-live training, refreshers and user feedback
- Field Service and Home Health for mobile clinicians in Agentforce Health
- Mobile app home and navigation setup for mobile care staff
Prepare for the Exam
Study Community
Ask questions and get the latest info from other Salesforce Accredited Agentforce Health Professional studiers. 757 members and growing.
Pick a concept to study
Select any concept from the checklist to read its explainer, sources, and practice question.