• Cert++
  • Practice
  • Certle
  • Review
  • Tracks
  • Checklist
  • Guides
  • Upgrade
Cert++
  1. Home
  3. Salesforce Accredited Agentforce Health Professional

Salesforce Accredited Agentforce Health Professional

Checklist progress

0/156Learned

Salesforce Accredited Agentforce Health Professional

Study Checklist

  • 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
  • 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 Consumer Goods AP
  • Agentforce Financial Services AP
  • Agentforce Health AP
  • Agentforce Manufacturing AP
  • 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 Architect

Checklist progress

0/156Learned

  • Choosing clinical-outcome KPIs (for example care gap closure rate or readmission reduction targets) appropriate to stated Health Cloud outcomes
  • Choosing experience and payer-administration KPIs (for example CAHPS/HEDIS proxies or authorization turnaround)
  • Documenting upstream EHR/EMR footprint and interoperability expectations for a Health Cloud program
  • Documenting FHIR or HL7 interface requirements and latency or batch expectations for clinical data exchange into Health Cloud
  • Gathering functional requirements for care plan authoring and care gap identification
  • Gathering functional requirements for care team task assignment, escalation paths, and collaboration
  • Sizing data volumes and user concurrency for integration and Salesforce platform planning
  • Recording HIPAA and 21st Century Cures-style interoperability mandates as technical/compliance intake for integration design
  • Separating engagement-channel requirements (portal, campaigns, reminders) from care coordination adherence and gap closure requirements
  • Choosing Intelligent Appointment Management versus standard Salesforce scheduling or a custom solution from scheduling-related requirements
  • Deciding whether Health Cloud replaces legacy EHR workflows or coordinates around an EHR that remains the clinical system of record
  • Determining HIPAA covered entity versus business associate roles during discovery and how they affect contracting and safeguards expectations
  • Deciding when Shield capabilities (encryption, auditing, Field Audit Trail) are in scope based on contractual and regulatory obligations
  • Determining when customer requirements imply OmniStudio capabilities (guided OmniScripts, FlexCards, Integration Procedures) instead of standard declarative Salesforce alone
  • Selecting which capability areas (care coordination, referral management, utilization management, member engagement, provider directory, home health) discovery must cover given stated problems
  • Surfacing applicable state-level healthcare privacy obligations during discovery and how they constrain Health Cloud design
  • Translating HIPAA, Part 2, and state constraints into concrete Health Cloud implications for sharing, integrations, retention, and consent
  • Distinguishing clinical stakeholders (physicians, nurses, care managers) from operational/IT stakeholders (compliance, admins, integration architects) and how each affects Health Cloud requirements
  • Determining whether third-party payers, community health organizations, external specialists, or pharmacies need Health Cloud access or integration
  • Identifying which Health Cloud personas apply to a scenario (patient/member, caregiver, care coordinator, care team member, provider, payer administrator, case manager)
  • Selecting the payer, provider, pharma/life sciences, or medical device vertical that fits the customer's business model and primary Health Cloud use case
  • Mapping each persona to the Health Cloud access they need: regulated data they must view, actions they must perform, and external systems they collaborate with
  • Adopting Home Health when bedside logistics require field tech flows beyond generic Field Service
  • Adopting Remote Monitoring when device telemetry thresholds must trigger clinician interventions
  • Choosing Intelligent Appointment Management when IAM-specific policies beat generic Scheduler constructs
  • Choosing packaged Referral Management over custom Cases when longitudinal referral SLAs dominate
  • Defining lifecycle stages creation through closure for routed referrals tracked in Health Cloud
  • Determining when Crisis Support Center workflows, objects, and escalation patterns are required for behavioral health crisis response rather than general Case Management patterns alone
  • Determining when native Health Cloud consent modeling replaces ad hoc fields or an external consent platform
  • Determining when packaged Benefits Verification fits the integration strategy versus stitching custom eligibility integrations
  • Engaging Advanced Therapy Management for pharma patients needing wraparound longitudinal therapy journeys
  • Determining when Social Determinants of Health screening plus community resource referral features fit the population health goals versus clinical-only programs alone
  • Driving OCR-to-record mapping fidelity for insurance cards versus referral narratives versus UM packets
  • Relying on Unified Health Scoring or Risk Stratification versus bespoke formulas fed from warehouse exports
  • Selecting Intelligent Document Reader or Automation versus manual keyed intake from documents
  • Selecting Utilization Management versus manual approvals when prior auth and inter-rater reliability matter
  • Using Care Gap Closure features instead of reinventing preventive outreach with unrelated campaigns
  • Surfacing payer responses at point-of-care versus batch clearance for coordinators
  • Aligning Health Cloud objects to FHIR R4 resource types (Patient → Person Account, Practitioner → Provider, Encounter → Episode of Care, Condition → Clinical Condition) for interoperability design
  • Choosing between FHIR R4 API, custom REST/SOAP API, and third-party middleware (e.g., MuleSoft) for EHR integration given data format, latency, volume, and organizational capability constraints
  • Designing bi-directional EHR integration: identifying which clinical data domains (demographics, diagnoses, medications, allergies, lab results, encounters) flow to Health Cloud and in which direction
  • Determining when Salesforce Connect with External Objects is appropriate for surfacing EHR data in Health Cloud vs. full ETL-based replication into Salesforce objects
  • Selecting the correct integration pattern (real-time event-driven, near-real-time CDC, scheduled batch, or on-demand API call) for a given clinical data synchronization use case
  • Applying External Sharing so portal users only see sanctioned patient-owned Health Cloud subsets
  • Choosing an Experience Cloud template and provisioning model suited to HIPAA-sensitive patient portals on Health Cloud
  • Configuring the Health Cloud Timeline so encounters, medications, and care-plan changes appear consistently from Salesforce and integrated EHR feeds
  • Defining HIPAA-aligned Data Use Purposes categories for lawful marketing, treatment, operations, or research communications
  • Designing consent capture journeys for intake versus ongoing preference updates spanning portal, call center, and back-office corrections
  • Designing persona-specific Lightning layouts for care coordinators, case managers, and providers so consoles show the right Health Cloud widgets
  • Determining when Health Cloud's Individual object underpins privacy governance and consent lineage versus relying on basic contact-level preference fields
  • Recording Communication Consent by channel (email, SMS, phone) aligned to permissible outreach workflows
  • Segmenting cohorts via risk tiers, gap flags, enrollment, or configurable clinical filters for population-health plays
  • Routing segment membership into coordinator queues powering proactive outreach and gap-closure workloads
  • Selecting which authenticated patient-facing objects (plans, appointments, teams, summaries) migrate from internal Health Cloud consoles into Experience layers
  • Separating EHR system-of-record boundaries from Health Cloud coordination responsibilities in solution architecture
  • Using Individual to unify privacy stance and attaching Communication Consents to Persons or Contacts
  • Choosing between big-bang and phased data migration approaches for a Health Cloud implementation given data volume, business continuity requirements, and cutover risk tolerance
  • Defining data quality and validation rules for migrated patient records: required field completeness, referential integrity between related clinical objects, and PHI validation
  • Designing a Health Cloud data migration plan: source-to-target field mapping for patient records, care plans, clinical conditions, and provider records; deduplication strategy; and rollback plan
  • Choosing between standard sharing rules, Apex Managed Sharing, and the External Sharing Model to control patient data visibility for external care partners and community providers
  • Designing a Health Cloud security model to meet HIPAA minimum necessary standard: org-wide defaults, role hierarchy, sharing rules, and field-level security for PHI
  • Designing Health Cloud permission set and permission set group assignments to match clinical role requirements without over-provisioning access to sensitive clinical data
  • Determining when Salesforce Shield components (Platform Encryption, Event Monitoring, Field Audit Trail) are required for a healthcare customer's compliance and audit requirements
  • Choosing Person Accounts versus Contact-only modeling for Health Cloud patients and implications for relationships, sharing, and reporting
  • Choosing Episode of Care versus Care Plan when the scenario is episodic boundaries versus ongoing longitudinal coordination
  • Deciding whether specific observations belong in replicated Health Cloud objects versus authoritative EHR storage only
  • Designing Patient duplicate detection matching rules keyed on identifiers such as MRN, birth date names, or SSN
  • Modeling Care Programs, Enrollees, Products, and Providers for wellness or chronic care programs
  • Modeling allergy and intolerance information in Health Cloud and tying it correctly to patient context
  • Representing longitudinal care plans with Care Plan, Care Plan Goals, Problems, and Tasks and how records relate
  • Selecting among Medication, Medication Dispense, Medication Request, and Administration for a patient's medication storyline
  • Selecting parent objects when modeling Clinical Conditions, Health Conditions, and Symptoms for a patient in Health Cloud
  • Selecting Member Plan, Insurance Policy, Coverage Benefit, and Benefit Assignment for payer-style insurance data in Health Cloud
  • Selecting merge survivor field logic and safeguarding related care-plan and clinical history after a Patient merge
  • Understanding Care Observation parent-child placement and linkage to Patient and Episode for vitals or measurements
  • Using Contact for individual providers and Account for provider groups plus Care Provider Facility associations to facilities
  • Using Account-Contact Relationships to represent care roles (such as primary care physician versus specialist) for a patient
  • Defining and mapping HEDIS/CAHPS-aligned KPIs (care gap closure rate, readmission rate, member satisfaction score) to Salesforce report types and Health Cloud data objects
  • Designing a reporting strategy for care team performance metrics: open care plan tasks by care manager, SLA adherence for prior authorizations, average days to care plan completion
  • Designing a future-state care transition process in Health Cloud: discharge from hospital to post-acute care, warm handoff between care teams, and follow-up task automation
  • Designing a future-state prior authorization process in Health Cloud Utilization Management: request intake, clinical documentation capture, review routing, decision communication, and appeals
  • Designing a care coordination workflow using Health Cloud: intake, assessment, care plan creation, care gap identification, care team task assignment, and escalation
  • Designing a provider credentialing and network management process: provider record creation, credentialing status tracking, network tier assignment, and directory updates
  • Designing a member onboarding business process for a payer in Health Cloud: eligibility verification, plan assignment, welcome communications, and care program enrollment
  • Designing a medical device customer solution: device implant tracking, patient/device registry, field service coordination, complaint management, and post-market surveillance
  • Designing a payer (health insurance) solution in Health Cloud: member management, benefit verification, prior authorization, utilization review, and care management program enrollment
  • Designing a pharmaceutical or life sciences patient support program: patient enrollment, therapy initiation, adherence monitoring, hub services, and specialty pharmacy coordination
  • Designing a provider (hospital or clinic) solution in Health Cloud: patient care coordination, discharge planning, care transitions, care team collaboration, and post-acute follow-up
  • Selecting the correct Health Cloud modules and managed package add-ons required for a specific vertical use case (e.g., Home Health, Advanced Therapy Management, Intelligent Appointment Management, Utilization Management)
  • Applying OCR extraction confidence thresholds, automatic posting versus analyst review queues, and exception remediation for Intelligent Document Automation in Health Cloud
  • Assembling Lightning and OmniStudio-hosted portal pages so members see sanctioned care summaries, bookings, reminders, or benefit widgets without unintended PHI bleed-through
  • Configuring a Crisis Support Center in Health Cloud for a behavioral health or crisis intervention use case: enabling crisis intervention record types, configuring escalation workflows from crisis event trigger to care team notification, setting up crisis hotline call logging integrated with the patient timeline, and defining crisis resolution and follow-up care plan triggers
  • Configuring Benefits Verification integrations in Health Cloud: wiring benefit verification requests to Member Plans, payer connections or clearinghouses, and consuming real-time eligibility responses
  • Configuring Care Observation records in Health Cloud to capture vital signs, lab results, and clinical measurements: creating observations linked to patient accounts and episodes of care, configuring reference range thresholds for alert generation, and surfacing observation data on the Health Cloud Timeline for care coordinator review
  • Configuring Advanced Therapy Management in Health Cloud: setting up treatment protocol milestones, configuring site-of-care assignments, enrolling patients in patient support programs, tracking specialty pharmacy coordination steps and hub services case management workflows, and monitoring key therapy journey milestones from prescription through administration
  • Configuring Care Programs and enrollment: defining enrollment criteria, enrollment steps, and program product associations for a disease management program
  • Configuring Care Plan templates: creating care plan goal templates, problem templates, and task templates for a specific chronic condition management program
  • Configuring Home Health visit scheduling: setting up technician territories, defining visit types, enabling offline mobile access for field workers, and integrating with work order management
  • Configuring Health Cloud Assessments and survey forms for patient intake, clinical screening, and risk stratification — choosing between Health Cloud Assessment objects vs. Salesforce Surveys
  • Configuring Intelligent Appointment Management: setting up service territories, operating hours, appointment types, scheduling policies, and provider availability rules
  • Configuring Member Plan and insurance benefit information for a payer use case: linking member plans to patient accounts, capturing benefit details, and surfacing benefit verification information
  • Configuring Intelligent Document Reader and Intelligent Document Automation in Health Cloud: supported document archetypes such as insurance cards, referral packets, prior authorization correspondence, plus OCR-to-field mappings into Member Plan and Care Request records
  • Configuring Referral Management intake in Health Cloud: internal versus external referrals, routing by specialty or network, required clinical dossier fields, SLA clocks, escalation notifications
  • Configuring Medication Management: creating medication records, configuring medication reconciliation workflows, setting up adherence monitoring alerts, and linking medications to care plans
  • Configuring Utilization Management prior authorization workflow: creating authorization request types, defining clinical review criteria, setting up reviewer assignment rules, and configuring approval routing
  • Configuring Social Determinants of Health screening: setting up SDOH assessment templates, capturing screening responses, and routing referrals to community resource organizations
  • Configuring the Provider Search and Provider Directory: setting up provider records, network tiers, search filter criteria, and distance-based search parameters
  • Configuring the Health Cloud Timeline component to display clinical events from Salesforce records and external data sources, including controlling which object types appear and their date mapping
  • Configuring Utilization Management Concurrent Review and Retrospective Review workflows in Health Cloud: setting up care request types for concurrent (ongoing authorization) and retrospective (post-service) review use cases, defining clinical criteria checklists for each review type, configuring reviewer assignment rules, and setting up approval decision notification workflows to providers and members
  • Designing omnichannel intake, preference-change, reconciliation, and audit-friendly corrections that keep Communication Consents current throughout the lifecycle in Health Cloud
  • Publishing Health Cloud data to authenticated Experience Cloud portals: provisioning Customer or Partner Communities, aligning supported objects with sharing sets, and pairing sharing sets with reciprocal internal sharing logic
  • Implementing Communication Consent records across outreach channels, defining HIPAA-aligned Data Use Purposes, and binding consent snapshots to Individuals and Patient Person Accounts for auditability
  • Setting up Care Teams in Health Cloud: creating care team roles, assigning team members to a patient account, and configuring team collaboration and task visibility
  • Surfacing payer-confirmed eligibility, benefit, and patient cost-share information to care coordinators at the point of care using Benefits Verification data in Health Cloud
  • Tracking referral disposition from submission through completion, documenting closure rationales and outcomes leveraged by coordinators and UM stakeholders in Health Cloud
  • Assigning Health Cloud permission sets and permission set groups to users following the principle of least privilege, and verifying access by persona type
  • Configuring Health Cloud post-installation setup: enabling Health Cloud features in Setup, configuring the Health Cloud app, assigning the correct user licenses and permission sets
  • Identifying the correct installation sequence for Health Cloud: prerequisites, managed package installation order (base Health Cloud package, OmniStudio, industry add-on packages), and org edition requirements
  • Identifying which Health Cloud add-on managed packages are required for specific features: Home Health, Intelligent Appointment Management, Advanced Therapy Management, Utilization Management
  • Building Health Cloud custom report types joining Care Plan, Care Plan Task, and Account (Patient) objects to report on care coordinator workload and care plan task completion rates
  • Configuring dashboards to display population health KPIs for care management leadership: care gap closure rate by population segment, average care plan duration, at-risk patient counts
  • Configuring list views and filter criteria in Health Cloud to create patient population segments (e.g., patients with open care gaps, high-risk members, members missing annual wellness visits)
  • Building an OmniScript for a guided clinical intake workflow: collecting patient demographics, screening responses, and triggering care plan creation from a single guided experience
  • Configuring a FlexCard to display a patient summary panel aggregating data from multiple Health Cloud objects (Account, Clinical Conditions, Care Plans, open Tasks, Member Plan)
  • Deploying and activating OmniStudio components (FlexCards, OmniScripts) across Salesforce environments and understanding version management, activation requirements, and deployment order
  • Selecting the correct OmniStudio component for a Health Cloud use case: OmniScript for guided step-by-step workflows, FlexCard for contextual data display, DataRaptor for data read/write, Integration Procedure for multi-system orchestration
  • Using a DataRaptor Extract to read Health Cloud patient data and a DataRaptor Load to write updated care plan status back to Salesforce objects in an OmniScript-driven workflow
  • Using an Integration Procedure to orchestrate multi-step API calls to an external EHR and Salesforce Health Cloud objects within a single OmniScript step, minimizing user wait time
  • Configuring and using Health Cloud's FHIR R4 API endpoints to allow external applications (patient portals, EHR systems) to query and write clinical data using standard FHIR resources
  • Configuring Named Credentials and Auth Providers to securely authenticate Health Cloud API calls to external EHR systems using OAuth 2.0 or certificate-based authentication
  • Implementing Salesforce Connect with an external OData or custom adapter to surface EHR patient encounter data as External Objects in Health Cloud without full data replication
  • Using Platform Events or Change Data Capture (CDC) to trigger near-real-time synchronization of Health Cloud record changes to downstream clinical or operational systems
  • Configuring duplicate management for Health Cloud patient records: defining matching rules on Person Account using healthcare identifiers (MRN, date of birth and name combinations), setting duplicate rules to alert or block on likely duplicates at record creation, and establishing procedures for care coordinators to review and merge duplicate patient records while preserving related clinical object history
  • Customizing Health Cloud Lightning app pages and record page layouts per user profile or permission set using the Lightning App Builder, including embedding OmniStudio FlexCards
  • Determining when to extend the Health Cloud data model with custom objects or custom fields on Health Cloud standard objects vs. using existing managed package objects to avoid upgrade conflicts
  • Extending Health Cloud Clinical Condition and Care Plan objects with custom fields to capture organization-specific clinical data without disrupting managed package upgradability
  • Implementing custom list views and filtered patient population segments in Health Cloud for care managers to identify high-risk patients or patients with specific care gaps
  • Using Salesforce Flow vs. Apex triggers to automate Health Cloud business processes (care plan task creation, care gap flag updates, escalation) given complexity and long-term maintenance constraints
  • Configuring Field-Level Security (FLS) on Health Cloud clinical objects to restrict access to sensitive PHI fields (SSN, diagnosis codes, financial information) to authorized clinical roles only
  • Configuring Health Cloud Guest User access for a patient portal or unauthenticated external access scenario while maintaining HIPAA-compliant access controls
  • Configuring org-wide defaults (OWDs) and sharing rules for Health Cloud patient records to enforce minimum necessary access while enabling care team collaboration
  • Configuring Salesforce Shield Platform Encryption for sensitive Health Cloud PHI fields: selecting encryption schemes, identifying which fields to encrypt, and understanding query limitations
  • Implementing patient/member record visibility controls using manual sharing or Apex Managed Sharing so that providers can only access records of their assigned patients
  • Using the External Sharing Model to control how internal Health Cloud patient records are shared with Experience Cloud (community portal) users such as patients or external care partners

Given a scenario, determine the post-deployment steps for a specific use case or capability within Health Cloud.

0/5

  • Completing post-deployment steps for a new Health Cloud module activation (e.g., enabling Home Health, Utilization Management, or Advanced Therapy Management) including feature flag enablement and permission re-assignment
  • Determining post-deployment validation steps after a Health Cloud go-live: smoke testing core workflows (care plan creation, prior auth submission, appointment scheduling), data verification, and integration connectivity checks
  • Designing an end-user training and change management plan for a Health Cloud clinical deployment: creating role-based training curricula for care coordinators, case managers, and clinical system admins, selecting training delivery methods (Trailhead, sandbox hands-on labs, instructor-led sessions), and measuring post-go-live adoption through login metrics, workflow completion rates, and user satisfaction surveys
  • Planning for Health Cloud managed package version upgrades: reviewing Salesforce release notes for breaking changes to Health Cloud objects, flows, and OmniStudio components, testing upgrade impact in a Full Copy sandbox, identifying custom configurations that require remapping after an upgrade, and executing a low-risk upgrade in production with a defined rollback procedure
  • Designing a hypercare plan for the weeks following a Health Cloud deployment: monitoring error logs, support ticket triage process, user adoption tracking, and configuration adjustment procedures

Given a scenario, determine the pre-deployment steps for a specific use case.

0/4

  • Determining which Health Cloud components require special pre-deployment considerations: managed package version verification, OmniStudio component activation status, custom metadata dependencies, and permission set assignments
  • Defining the sandbox environment strategy for a Health Cloud implementation: selecting appropriate sandbox types (Developer Pro for unit testing, Partial Copy for integration testing, Full Copy for UAT and performance testing), understanding Health Cloud managed package installation requirements per sandbox type, and managing sandbox refresh cadence to maintain environment parity before go-live
  • Choosing the correct deployment mechanism for Health Cloud configuration and customization: change sets, Salesforce DX with source format, unlocked packages — and the constraints of each for managed package orgs
  • Identifying required pre-deployment steps for a Health Cloud go-live: user acceptance testing (UAT) in a full-copy sandbox, data migration dry run, permission set validation, and integration smoke testing

Determine how to manage techs via Mobile app and capabilities.

0/3

Configuring the Salesforce mobile app for Health Cloud field technicians or home health workers: enabling offline access, configuring mobile navigation items, and surfacing Home Health visit schedules and work orders

Learn this concept
Unseen

Identifying which Health Cloud capabilities are supported in the Salesforce mobile app for field technicians vs. which require a desktop browser, and designing workflows accordingly

Learn this concept
Unseen

Managing technician schedules, visit status updates, and patient record access through the Salesforce mobile app in a Home Health or field-based care delivery scenario

Learn this concept
Unseen

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Salesforce Accredited Agentforce Health Professional studiers. 593 members and growing.

Go to Discord

Identifying which Health Cloud capabilities are supported in the Salesforce mobile app for field technicians vs. which require a desktop browser, and designing workflows accordingly

Explainer

Learn More

Practice Question

Keep going

Next conceptManaging technician schedules, visit status updates, and patient record access through the Salesforce mobile app in a Home Health or field-based care delivery scenario

Checklist progress

0/156 (0%)

0 of 156 concepts learned

Tip: You can filter concepts by status.

Prepare for the Exam

Play Today's Certle
Back to track

Study Community

Ask questions and get the latest info from other Salesforce Accredited Agentforce Health Professional studiers. 593 members and growing.

Go to Discord

Explainer

Health Cloud data can be accessed by field technicians through the Salesforce mobile app when Field Service is configured with the Health Cloud Package Extension. This enables care team members to complete tasks and update records while delivering services outside facilities, such as mobile nursing and home health care. Some capabilities require desktop browser access, particularly when using certain Lightning page components without mobile-specific configuration.

Core information
  • The Health Cloud Package Extension for Field Service is an optional package that enables care team members to access Health Cloud data on mobile devices using the Field Service Mobile App.
More details and nuances
  • Field and Field Section components on Lightning record pages are supported on desktop only by default; to enable the same experience on mobile, you must enable Dynamic Forms and Dynamic Highlights on Mobile from Salesforce Mobile App Setup.