---
schema_version: "1"
id: b9db495b7c129bcdcb94751dcdc1243d73b270b50f85c2a16d3c9b892f6f8bf0
title: Configure Action Buttons for Processing Authorization Request Reviews
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/admin_utlization_management_action_buttons.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.admin_utlization_management_action_buttons.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 184efe1ca97f632387566ffd6ef9587a412ae9ec4fb952a584b0c35c81d683b5
description: 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 or the Home page in the Utilization Management for Payers app. Conditionalize the visibility of the buttons based on the case status, case substatus, and request type.
products:
  - Health
release: "264"
---
# 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 or the Home page in the Utilization Management for Payers app. Conditionalize the visibility of the buttons based on the case status, case substatus, and request type.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
        <colgroup>
          <col>
        </colgroup>
        <tbody>
          <tr class="">
            <td class="slds-cell-wrap" style="vertical-align:top;">
              <p>Available in: Lightning Experience</p>
              <p style="margin-bottom:0;">Available in: <strong>Enterprise</strong> and <strong>Unlimited</strong> Editions with Health Cloud</p>
            </td>

          </tr>
        </tbody>
      </table> <table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
        <colgroup>
          <col style="width:50%">
          <col style="width:50%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d144402e66">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d144402e66 ">To add action buttons:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d144402e66 ">Update on Case object</td>

          </tr>
        </tbody>
      </table>

Each Flexcard contains an action button that triggers the launch of the integrated Omniscript based on how you configure the 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.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-health-264-0-0-production-enus/90a9f828-79ab-49cd-ac8c-86e58ef7478e/images/icon_note.png)

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

1. From the App Launcher, go to the Utilization Management for Payers app, select the Cases tab and then select a case record.
2. Select ![Gear icon](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-health-264-0-0-production-enus/90a9f828-79ab-49cd-ac8c-86e58ef7478e/health/images/gear_icon.png), and then select **Edit Page**.
3. In the Lightning App Builder, drag Flexcard components onto the page to add action buttons for each case status:
    1. Place Flexcard components on the record page layout.
    2. 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 |
        
        ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-health-264-0-0-production-enus/90a9f828-79ab-49cd-ac8c-86e58ef7478e/images/icon_note.png)
        
        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.
4. Save and activate your changes.
    
    Now, when your users access the Case record page, the page shows the action button that matches with the current status and substatus of the case.
    
    ![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-ind-health-264-0-0-production-enus/90a9f828-79ab-49cd-ac8c-86e58ef7478e/images/icon_note.png)
    
    Note Edit the home page of the Utilization Management for Payers app to add a Flexcard component for the Add Authorization Request Details button.