Configure Action Buttons for Submitting and Inquiring about Authorization Requests
Help your provider users to launch Omniscripts and handle authorization request
submissions and inquiries in an efficient manner by adding Flexcard-based action buttons to
pages.
Each Flexcard contains an action
button that triggers the launch of the integrated Omniscript.
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions with Health
Cloud
User Permissions Needed
To add action buttons:
OmniStudio Admin permission set
AND
Utilization Management Provider User
permission set
AND
Update on cases
Go to your home page.
Click , and then select Edit
Page.
In the Lightning App Builder, place a FlexCard component on the page.
In the Properties pane for the FlexCard, select
HealthCloudUtilizationManagementProviderAuthorizationLaunch as the
FlexCard name.
Activate the settings and save your changes.
Your authorization coordinators now see the Create Authorization
Request action button on their home pages, which launches the
HealthCloudUtilizationManagementProviderAuthorizationRequest OmniScript process.
Go to the Case Lightning record page, and add the
HealthCloudUtilizationManagementProviderInquiryLaunch FlexCard to the
page layout.
Your authorization coordinators now see the Inquire Status action
button, which launches the HealthCloudUtilizationManagementProviderInquiryRequest Omniscript
process.
Note The predefined Omnistudio components represent a default implementation and are
ready to use. However, we recommend you customize these components per your organization's
requirements. To do so, save a new version of each Omniscript and clone the associated Data
Mappers and Integration Procedures. Retain the settings, save the new version or clone with a
different name, activate the new version or the clone, and then relink the components.
Similarly, clone and activate the Flexcards that launch these Omniscripts and relink them to
the corresponding new versions of the Omniscripts. Cloning ensures that you don’t face any
process disruptions when predefined components are updated during automatic upgrades.
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.