Salesforce Docs Portal

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

Available in: Lightning Experience

Available in: Enterprise and Unlimited Editions with Health Cloud
User Permissions Needed
To customize Omnistudio components:
  • OmniStudio Admin permission set
  • Health Cloud Utilization Management permission set

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
    Note Go to the home page of the Utilization Management for Payers app for adding the cloned HealthCloudUMPriorAuthIntakeLaunch FlexCard.
  9. Select Gear icon, 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.