The Appointment Guidance custom screen flow opens up a range of options for setting
visit type, engagement channel, and provider preferences. There are important considerations to
keep in mind when setting up the data so that you don’t cause errors in the search function for
providers, assets, and appointment slots.
Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions with Health
Cloud
The Service Appointment object records the patient appointment.
The Work Type object records the visit type.
The Engagement Channel Work Type object records the channel of the appointment, such as
in-person, phone, or video.
Workflow
If no visit type is selected in the Intelligent Appointment Management console, you can
set the visit type in the flow but you can't set the channel.
If the visit type is selected in the Intelligent Appointment Management console and then
the appointment guidance flow runs, then you can set the channel.
If the engagement channel is invalid and the work type is correct, then the provider
search runs automatically, but shows an error.
If the appointment guidance flow sets a channel for the visit type, but the data for
channels isn’t set up, the flow shows an error message.
To verify patient prerequisites as part of the scheduling workflow, we recommend you use
a separate flow distinct from your appointment guidance flow. Then link your prerequisites
flow to a work type code set bundle so that it runs before a scheduler books an
appointment for that work type. If a scheduler changes the patient selected on the
appointment confirmation screen, a prerequisites flow linked to a work type runs for the
newly selected patient. For details, see Verify Prerequisites for Appointments.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.