DocuSign: Authorization

Docusign Configuration: Authorization 

To start using e-signing within Welkin, we need to complete the following 3 steps:

In this article, we’ll cover Step 3: Authorization. You can then click through to the other two links to see the prerequisites to this step. 

This step enables API access for performing signing operations through DocuSign. This authorization must be completed for both the Developer and Production account (for Go-Live)  – please see the appropriate instructions below

Authorization

Developer Account

To authorize the integration app, please complete the following:

Welkin Admin > Integrations > Docusign > Environment Configuration

  • Copy the integration key from the Configuration
  • Enter the integration key into the URL below

https://account-d.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=integration_key&redirect_uri=https://care.live.welkincloud.io/signin

  • In a new tab – paste the above URL (with the integration key which was entered) and navigate to the site
  • This will lead to an authorization screen. Click “Accept”.
  • After this signing operations can be done.

Production Account

If Go-Live process is completed, follow these steps:

  • Login to Docusign production account at account.docusign.com.
  • In another tab – navigate to the following location within Welkin Admin

Welkin Admin > Integrations > Docusign > Environment Configuration

  • Copy the integration key from the Configuration
  • Enter the integration key into the URL below

https://account.docusign.com/oauth/auth?response_type=code&scope=signature%20impersonation&client_id=integration_key&redirect_uri=https://care.live.welkincloud.io/signin

  • In a new tab – paste the above URL (with the integration key which was entered) and navigate to the site

Both workflows above will redirect to the authorization screen. Click “Accept”.

After this signing operations can be done.

Note: Authorization step needs to be done separately for Developer and Production Accounts.

More Questions? If you have any questions regarding the Docusign Integration or its implementation, please visit the Welkin Health Knowledge-Base or contact your Implementation/CSM for more information.

 

Generating Auth Token

After the patient has signed the document, in order to receive the signed document in welkin, an auth token must be generated in the admin portal. To do that, follow the steps:

  1. In the admin portal, go to Integrations > Docusign
  2. Edit the configuration for the instance where docusign is being used.
  3. Click on the “Generate Token” button and a 36 digit token (a GUID) will be generated.
  4. Save the configuration.

Also advised to generate the token for “Default Config” of Docusign Integration, as well as for any other instances under Docusign Integration where docusign is configured.

Go-Live

Go Live is DocuSign’s process for migrating an integration created in the demo environment to the production environment. Go Live is necessary before you can perform real transactions in your integration through the DocuSign APIs.

For detailed information on how to Go-Live, check out these links visit our Knowledge Base: DocuSign: Go-Live article. 

Post Go-Live

We can verify whether our integration is live or not by:

  1. Logging into Docusign developer Account, go to Settings > Apps & Keys. The status of our integration should have changed to Live.
  2. Logging into Docusign production Account, go to Settings > Apps & Keys. A new integration should be seen in the list of integrations. This app, and the integration app in the developer account will have the same integration key.