Update the Credentialing Omniscript to Use Your DocuSign Template
Help your credentialing specialists generate a credentialing application form when
providers complete the credentialing process. Add the provider credentialing DocuSign template
that you uploaded to your DocuSign account to the Credentialing Omniscript. The Omnistudio
Data Mapper in the Omniscript saves all the input given by providers and generates the
credentialing application based on this template.
Required Editions
Available in: Lightning Experience
Available in: Enterprise and Unlimited Editions with Health Cloud
User Permissions Needed
To update an Omniscript:
OmniStudio Admin permission set
From the App Launcher, find and select OmniScripts.
Select the HealthCloudPNMProviderCredentialingApplicationPortalUser Omniscript, and
click New Version.
Go to the Consent step and select the Sign your application
electronically button.
In the Properties pane, go to DocuSign Templates, and click Add
Template.
Provide the details of the credentialing application DocuSign template that’s uploaded to
your DocuSign account.
Template: Provider App Template
Data Mapper Interface: HealthCloudPNMTransformCredentialingDocusign
Signer Name: %FirstName% %LastName%
Signer Email: %ProviderInformation:OfficeEmail%
Template Role: Provider
Save your changes.
Back on the Consent step, select the consent terms text block.
In the Properties pane, edit the Text field and replace the sample terms of use with the
actual terms of your organization.
Save your changes.
Activate the Omniscript.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.