Configure Action Buttons for Processing Authorization Request Reviews

Help your users to launch OmniScripts and handle authorization requests in an efficient and timely manner by adding FlexCard-based action buttons to the Case record page. Visibility of the buttons is based on the case status, case substatus, and request type.

Each FlexCard contains an action button that triggers the launch of the integrated OmniScript based on the configured visibility rules. For example:

The HealthCloudUMAdminFlowLaunch FlexCard contains the Start Admin Review button.
The Start Admin Review button launches the HealthCloudUM/AdminReview OmniScript, which initiates an admin review of the authorization request.
The Start Admin Review button is available only when the case status is Admin Review. Setting visibility rules using case status helps you to achieve this conditional display.

Before adding the buttons, make sure you’ve configured the necessary case status values.

Note

Available in: Lightning Experience

Available in: Enterprise and Unlimited Editions with Health Cloud

User Permissions Needed
To add action buttons:	Update on Case object

Go to the Case Lightning record page.

Go to the home page of the Utilization Management for Payers app for adding the FlexCard for the Add Authorization Request Details button.
Note
Select , and then select Edit Page.

In the Lightning App Builder, add action buttons for each case status using FlexCard components:

Place FlexCard components on the page layout.

In the Properties pane for each FlexCard, select the FlexCard name and configure visibility rules, as shown.

FlexCard Name	Visibility Rule	Shows This Action Button	Launches This OmniScript
HealthCloudUMPriorAuthIntakeLaunch	No action is required to set the visibility rules.	Add Authorization Request Details	HealthCloudUM/AuthorizationRequest
HealthCloudUMAdminFlowLaunch	Record Field > Status Equal Admin Review	Start Admin Review	HealthCloudUM/AdminReview
HealthCloudUMNurseFlowLaunch	Record Field > Status Equal Nurse Review	Start Utilization Management Nurse Review	HealthCloudUM/UMNurse
HealthCloudUMAuthReviewsLaunch	No action is required to set the visibility rules as they’re predefined based on Case Status equals MD Review and Substatus doesn’t equal Peer to Peer Review Scheduled.	Start Medical Director Review	HealthCloudUM/MedicalDirectorReview
HealthCloudUMAuthReviewsLaunch	No action is required to set the visibility rules as they’re predefined based on Case Status equals Nurse Review and Substatus equals Schedule Peer to Peer Review.	Schedule Peer-to-Peer Review	HealthCloudUM/P2PScheduling
HealthCloudUMAuthReviewsLaunch	No action is required to set the visibility rules as they’re predefined based on Case Status equals MD Review and Substatus equals Peer to Peer Review Scheduled.	Start Peer-to-Peer Review	HealthCloudUM/P2PReview
HealthCloudUMConcurrentReviewLaunch	No action is required to set the visibility rules as they’re predefined based on Request Type equals Inpatient - Physical Health Review or Outpatient - Physical Health Review.	Create Concurrent Review	HealthCloudUM/AuthorizationRequest

These OmniScripts and FlexCards are ready to use, however, we recommend using a cloned version of them. Simply clone each of the above OmniScript and FlexCard, retain the settings, save with a different name, and activate the cloned version. Go to each cloned FlexCard and relink it to the corresponding cloned OmniScript. Cloning ensures that you don’t face any process disruptions when predefined OmniScripts are updated during automatic upgrades.

Note

Activate the settings and save your changes.
Now, when your users access the Case record page, the action button that matches with the current status and substatus of the case is shown.

Health Cloud Administration

Configure Action Buttons for Processing Authorization Request Reviews