---
schema_version: "1"
id: a91f45de579c8b5ca2402e80c2e99f3e9881d8a2db6d2e25366b80168c0b0b6d
title: Design Custom Omnistudio Components for Authorizations
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/ind/264-0-0/admin_utlization_management_custom_os.md
canonical_url: https://help.salesforce.com/s/articleView?id=ind.admin_utlization_management_custom_os.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 43f69716fe6cba43152bf392dd5759c5a0c996eb646462645c7b2acd63c614aa
description: Use Omnistudio to customize the default Omniscripts and related components so that they match your internal process and fulfill operational requirements for authorizations.
products:
  - Health
release: "264"
---
# Design Custom Omnistudio Components for Authorizations

Use Omnistudio to customize the default Omniscripts and related components so that they match your internal process and fulfill operational requirements for authorizations.

### 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="d228518e66">User Permissions Needed</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d228518e66 ">To customize Omnistudio components:</td>

            <td class="slds-cell-wrap" style="vertical-align:top;" headers="d228518e66 ">
              <ul>
                <li>OmniStudio Admin permission set</li>

                <li>Health Cloud Utilization Management permission set</li>

              </ul>
            </td>

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

After you define custom rules for automating authorization workflows, you can customize the Omnistudio components to refer to those custom rules.

The Omniscript Designer enables you to preview dynamic web forms as you build them using a drag-and-drop interface. You can update all of the Omnistudio components: Omniscripts, Flexcards, Omnistudio Data Mappers, and Integration Procedures. By customizing and fine-tuning these components, you can offer your users a guided interaction that optimizes their procedures.

1. From the App Launcher, find and select the OmniStudio app, and select the Omniscripts tab.
2. Select an Omniscript of type HealthCloudUM to update, and then click **New Version**.
3. Use a different name for the Omniscript per your organization's needs:
    1. Make changes to the logical flow, actions, steps, and elements, and their properties.
    2. Use the custom expression sets that you created earlier for applying the rules.
    3. (Optional) If you want to make changes to the Integration Procedures or Data Mappers, clone the corresponding record, update it to suit your needs, activate, and use it in the customized Omniscript.
4. After you’ve updated the Omniscript, activate the settings and save your changes.
5. From the App Launcher, find and select **OmniStudio FlexCards**.
6. Select a Flexcard to update:
    
    1. Click **New Version**.
    2. Use a different name for the Flexcard.
    3. In the Properties pane, select the corresponding customized Omniscript as shown:
    
    | Clone of Flexcard | New Version of Omniscript |
    | --- | --- |
    | HealthCloudUMPriorAuthIntakeLaunch | HealthCloudUM/AuthorizationRequest |
    | HealthCloudUMAdminFlowLaunch | HealthCloudUM/AdminReview |
    | HealthCloudUMNurseFlowLaunch | HealthCloudUM/UMNurse |
    | HealthCloudUMAuthReviewsLaunch | HealthCloudUM/MedicalDirectorReview |
    | HealthCloudUMAuthReviewsLaunch | HealthCloudUM/P2PScheduling |
    | HealthCloudUMAuthReviewsLaunch | HealthCloudUM/P2PReview |
    | HealthCloudUMConcurrentReviewLaunch | HealthCloudUM/AuthorizationRequest |
7. After you’ve updated the Flexcard, activate the settings and save your changes.
8. Go to the Case Lightning record page.
    
    ![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 Go to the home page of the Utilization Management for Payers app for adding the cloned HealthCloudUMPriorAuthIntakeLaunch FlexCard.
9. 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**.
10. In the Lightning App Builder, add action buttons for each case status using the cloned Flexcard components and set visibility rules.
    
    1. Place Flexcard components on the page layout.
    2. In the Properties pane for each Flexcard, select the Flexcard name and configure visibility rules, as shown.
    
    | Clone of Flexcard | Visibility Rule |
    | --- | --- |
    | HealthCloudUMPriorAuthIntakeLaunch | No action is required to set the visibility rules. |
    | HealthCloudUMAdminFlowLaunch | Record Field > Status Equal Admin Review |
    | HealthCloudUMNurseFlowLaunch | Record Field > Status Equal Nurse Review |
    | 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. |
    | 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. |
    | 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. |
    | 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. |
11. Activate the settings and save your changes.
    
    That’s it! 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. Also, when your users create and review authorization requests, the customized Omnistudio components and rules are used.