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.
Required Editions
Before performing this task: Define Provider Statuses for Authorization Requests
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.