# DocuSign Implementation Checklist

Use this checklist to track the steps for implementing the DocuSign integration in Welkin Health. The integration enables electronic signature collection within the care workflow.

## Pre-implementation

* [ ] Confirm DocuSign integration is included in your Welkin contract
* [ ] Identify which documents will require eSignature (consent forms, treatment agreements, releases, etc.)
* [ ] Determine who sends documents for signature (care coordinators, clinicians, administrators)
* [ ] Confirm whether signatures are collected in-person (on a device) or remotely (via email link)
* [ ] Gather existing document templates you want to convert to DocuSign templates

## DocuSign account setup

* [ ] Create or confirm your DocuSign account (your Welkin CSM can assist with enterprise provisioning)
* [ ] Set up your DocuSign organization with the correct branding (logo, email sender name)
* [ ] Configure DocuSign user accounts for staff who will send documents
* [ ] Create signature field templates in DocuSign for each document type
* [ ] Test DocuSign templates independently before connecting to Welkin

## Welkin configuration

* [ ] Complete [DocuSign Authorization](/integrations/docusign/docusign-authorization.md) – connect your DocuSign account to Welkin
* [ ] Complete [DocuSign Setup (Admin)](/integrations/docusign/docusign-setup-admin.md) – configure integration settings in the Admin portal
* [ ] Complete [DocuSign Setup (Designer)](/integrations/docusign/docusign-setup-designer.md) – add DocuSign components to patient templates
* [ ] Map document fields to Welkin patient data for auto-population
* [ ] Configure role permissions so only appropriate staff can send signature requests

## Template creation

* [ ] Create all required document templates (see [DocuSign Creating Templates](/integrations/docusign/docusign-creating-templates.md))
* [ ] Test each template to confirm fields auto-populate correctly from Welkin patient data
* [ ] Review templates with legal/compliance team for approval

## Testing

* [ ] Send a test document to a test patient record
* [ ] Confirm the patient can sign remotely via email link
* [ ] Confirm in-person signing works on a tablet (if applicable)
* [ ] Verify completed documents are stored in Welkin after signing
* [ ] Confirm completed documents are accessible in the patient's document history

## Go-live

* [ ] Complete [DocuSign Go-Live Process](/integrations/docusign/docusign-go-live-process.md)
* [ ] Train staff who will send signature requests
* [ ] Communicate the new eSignature process to patients if applicable
* [ ] Monitor first week of usage for any issues

## Notes

For issues during implementation, contact your Welkin Customer Success Manager or open a [support ticket](https://github.com/welkincloud-io/welkin-docs/blob/master/kb/support/support-tickets.md).


---

# 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/docusign-implementation-checklist.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.