Parties
Full legal names and contact details for consenting parties and any representative or guardian responsible for signing on behalf of another.
A well-drafted Legal MCAN Consent Form reduces ambiguity about rights granted, limits liability, and supports regulatory compliance by producing a dated, attributable record of agreement under ESIGN and applicable state UETA or ESRA frameworks.
Full legal names and contact details for consenting parties and any representative or guardian responsible for signing on behalf of another.
A precise description of the action or authorization being consented to, including any limits, duration, and specific conditions or exclusions.
Explicit effective date and, if applicable, expiration or review dates to avoid ambiguity about when rights commence or terminate.
Clear signature, printed name, title, and date fields; if executed electronically, include the audit trail and method of authentication used.
Language describing how consent can be withdrawn, any notice requirements, and the effect of revocation on ongoing activities.
A statement naming the governing state law and venue for disputes, chosen consistently with parties' expectations and applicable statute.
Organizations and individuals use this consent form to document legal authorization, including providers, counsel, and authorized agents.
The responsible signer depends on the consent context: an adult party, a parent/guardian, an authorized representative, or corporate signatory may be required.
A hospital administrator or clinical manager completes and maintains the form when MCAN consent relates to patient care protocols, ensuring HIPAA compliance and retention under 45 CFR §164.530(j). They coordinate identity verification and record storage.
In-house or outside counsel prepares and reviews the consent language for business transactions to limit exposure, confirm governing law selection, and verify that the electronic process meets ESIGN (15 U.S.C. ch. 96) standards.
| Field | Configuration |
|---|---|
| Signature Field | Required; include printed name and date |
| Authentication | Email link, SMS code, or knowledge-based verification |
| Attachment | Allow upload of ID or supporting documents |
| Retention Policy | Enable audit trail retention and exportable PDF |
Ensure your chosen platform supports required authentication, audit trails, and secure storage to meet legal and industry obligations.
Choose a platform that provides exportable signed PDFs, a complete audit trail, and configurable authentication options consistent with ESIGN and any industry-specific rules.
Obtain signed consent prior to the activity it authorizes
Provide the signer with a copy at execution or promptly afterward
Retain signed records per applicable retention rules
Specify notice periods and effect dates for revocation
Ensure signed PDF and audit trail are exportable on demand
| Criteria | Legal MCAN Consent Form | Comparable Consent |
|---|---|---|
| E-sign Allowed | depends on parties | |
| Notarization Required | no (usually) | sometimes required |
| State Variations | present | present |
| Typical Industry Use | healthcare/legal | administrative or clinical |
| signNow | DocuSign | Adobe Sign | PandaDoc | HelloSign | |
|---|---|---|---|---|---|
| Starting Price | $8/user/mo | $15/user/mo | $14/user/mo | $19/user/mo | $15/user/mo |
| Free Trial | 7-day trial | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes | Yes | Yes | Yes | Varies |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| Envelope Cap | No envelope cap | 100 envelopes/user/year | Varies | Varies | Varies |