# Configure eSignature

Welkin supports electronic signatures through the DocuSign integration. This page covers how to enable and configure eSignature for your organization, including the key decisions you need to make before setup.

## What is eSignature in Welkin?

eSignature allows care team members to send documents (consent forms, treatment agreements, program enrollment documents) to patients for electronic signature directly from the patient record. Completed, signed documents are stored in Welkin alongside the patient's other records.

Welkin's eSignature capability is powered by DocuSign. You must have a DocuSign account to use eSignature.

## Step 1: Choose your DocuSign plan

If your organization does not already have a DocuSign account:

* **DocuSign eSignature** is the standard plan for basic electronic signatures
* **DocuSign for Healthcare** offers additional HIPAA-compliant features and may be required depending on your compliance requirements

Contact your Welkin Customer Success Manager for guidance on the appropriate DocuSign plan.

## Step 2: Complete the implementation checklist

Follow the [DocuSign Implementation Checklist](/integrations/docusign/docusign-implementation-checklist.md) to track all setup steps.

## Step 3: Authorize and configure

Complete these setup steps in order:

1. [DocuSign Authorization](/integrations/docusign/docusign-authorization.md) – connect your DocuSign account to Welkin
2. [DocuSign Setup (Admin)](/integrations/docusign/docusign-setup-admin.md) – configure sender settings, document storage, and user permissions
3. [DocuSign Setup (Designer)](/integrations/docusign/docusign-setup-designer.md) – add DocuSign components to patient templates

## Step 4: Create document templates

Before care team members can send documents, you must create them as DocuSign templates:

* See [DocuSign Creating Templates](/integrations/docusign/docusign-creating-templates.md) for instructions
* Common documents to create as templates: intake consent forms, HIPAA authorization, telehealth consent, program enrollment agreements

## Step 5: Test and go live

* Test the complete workflow: sending a document, signing it, and confirming it appears in the patient record
* Follow the [DocuSign Go-Live Process](/integrations/docusign/docusign-go-live-process.md) to switch from sandbox to production

## eSignature compliance considerations

Electronic signatures in healthcare must meet specific regulatory requirements:

* **ESIGN Act** (federal) – establishes the legal validity of electronic signatures in the US
* **UETA** (state laws) – most states recognize electronic signatures under the Uniform Electronic Transactions Act
* **HIPAA** – if signed documents contain PHI, ensure your DocuSign plan includes a Business Associate Agreement (BAA)

Consult your legal or compliance team before using eSignature for documents that have specific witnessing or notarization requirements, as those may not be satisfied by standard electronic signatures.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.welkinhealth.com/integrations/docusign/how-to-configure-esignature.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.