Intelligent Appointment Management is configured in a Health Cloud org, not installed as a standalone product. You enable the prerequisites, choose your scheduling engine or engines, then assemble the console and patient flow from OmniStudio components. The high-level path is below; exact screens vary by release, so confirm against the current Health Cloud setup help.
- Confirm licensing and permissions
Verify the org has Health Cloud plus any Salesforce Scheduler entitlement you need, and assign the relevant permission sets to schedulers and integration users before you build anything.
- Enable OmniStudio
Install the OmniStudio managed package and confirm the IAM FlexCards and OmniScripts load, since the console is assembled from them rather than hardcoded.
- Connect your scheduling engines
Set up Salesforce Scheduler objects, or connect the EHR engine through the HealthCloudExt interface and Integration Procedures, or both if you are aggregating sources.
- Model visit types and rules
Configure visit types, prerequisites, and provider availability so the console returns only real, eligible slots to agents and patients.
- Publish the booking experiences
Roll out the scheduler console to agents and the patient self-service flow on Experience Cloud, then test both against the same availability to confirm they agree.
Choose Salesforce Scheduler, an EHR scheduling engine, or both. This decision sets whether Salesforce or the EHR is the system of record for availability.
Install and enable the OmniStudio managed package so the FlexCards, OmniScripts, and Integration Procedures that build the console are available.
For EHR engines, wire the connection using the HealthCloudExt Apex interface and the prebuilt OmniStudio Integration Procedures, then map your source systems.
Define the bookable visit types, their prerequisites, and provider availability so the console only offers valid slots.
Stand up the Experience Cloud booking experience and enable guest access if patients should book without signing in.
- IAM is Health Cloud only. It is not a generic Field Service feature, and it does not ship the same way inside Financial Services Cloud or Public Sector Solutions.
- Decide which system owns availability up front. If both Salesforce Scheduler and an EHR think they are authoritative, you get double bookings and reconciliation pain.
- The console depends on OmniStudio. Teams new to FlexCards and OmniScripts should budget learning time before they customize the shipped flow.
- Keep the patient self-service flow short. Every extra step or required field raises the chance a guest abandons the booking before it is confirmed.