Design Custom OmniStudio Components for Authorizations
Use the OmniStudio Designer to customize the default OmniScripts and components so that
they match your internal process and fulfill operational requirements for
authorizations.
|
Available in: Lightning Experience Available in: Enterprise and Unlimited Editions with Health Cloud |
| User Permissions Needed | |
|---|---|
| To customize OmniStudio components: |
|
We have already defined custom rules for automating authorization workflows. Now, let’s 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, DataRaptors, Integration Procedures, and FlexCards. By customizing and fine-tuning these components, you can offer your users a guided interaction that helps to optimize various procedures.
- From the App Launcher, find and select OmniScripts.
-
Select the OmniScript to update, and click New Version.
- HealthCloudUM/AuthorizationRequest
- HealthCloudUM/AdminReview
- HealthCloudUM/UMNurse
- HealthCloudUM/MedicalDirectorReview
- HealthCloudUM/P2PScheduling
- HealthCloudUM/P2PReview
-
Use a different name for the OmniScript and update it to suit your business needs:
- Make changes to the logical flow, actions, steps, and elements, and more.
- Use the custom expression sets that you created earlier for applying the rules.
- (Optional) If you want to make changes to the Integration Procedures or Data Raptors, clone the corresponding record, update it to suit your needs, activate, and use it in the cloned OmniScript.
- After you’ve updated the OmniScript, activate the settings and save your changes.
- Now, from the App Launcher, find, and select OmniStudio FlexCards.
-
Select the FlexCard to update:
- Click New Version.
- Use a different name for the FlexCard.
- In the Properties pane, select the corresponding cloned OmniScript as shown:
Clone of FlexCard Clone of OmniScript HealthCloudUMPriorAuthIntakeLaunch HealthCloudUM/AuthorizationRequest HealthCloudUMAdminFlowLaunch HealthCloudUM/AdminReview HealthCloudUMNurseFlowLaunch HealthCloudUM/UMNurse HealthCloudUMAuthReviewsLaunch HealthCloudUM/MedicalDirectorReview HealthCloudUMAuthReviewsLaunch HealthCloudUM/P2PScheduling HealthCloudUMAuthReviewsLaunch HealthCloudUM/P2PReview HealthCloudUMConcurrentReviewLaunch HealthCloudUM/AuthorizationRequest - After you’ve updated the FlexCard, activate the settings and save your changes.
-
Go to the Case Lightning record page.
-
Select
, and then select
Edit Page.
-
In the Lightning App Builder, add action buttons for each case status using the cloned
FlexCard components and set visibility rules.
- Place FlexCard components on the page layout.
- 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. -
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.