Download signNow app
4.7 / 5 rating on

Declarant, Executed An Advance Directive For Health Care On The Day Of Form

Use a Declarant, Executed An Advance Directive For Health Care On The Day Of template to make your document workflow more streamlined.

What this advance directive does

This form records a person’s healthcare wishes for circumstances in which the person cannot communicate or make treatment decisions. The declarant identifies personal instructions, treatment preferences, and, where the form provides for it, an authorized healthcare representative. The completed document is reviewed for state-law requirements, signed by the declarant, and witnessed or notarized when the applicable state form requires those steps. A signNow workflow can upload the form, detect fillable fields, route it for signature, and preserve the completed record with an audit trail. State law controls execution and clinical use; ESIGN and UETA do not override exclusions or state-specific formalities.

Who uses this advance directive

Healthcare providers

Healthcare providers use this directive to record a patient’s treatment preferences and authorized decision-maker instructions for future care.

Patients and agents

Patients and designated agents review, sign, and retain the directive so care teams can locate the patient’s stated preferences.

Which healthcare organizations benefit

The form is most useful where patients, representatives, and care teams must coordinate documented treatment preferences securely.

  • Solo medical practices can collect patient directives remotely, preserve signed copies, and make the declarant’s instructions available to authorized care teams when needed.
  • Hospitals and hospice organizations can route directives through controlled templates, require stronger authentication, and maintain audit trails for patient-record workflows involving protected health information.
  • Enterprise health systems can connect directive workflows to storage and business systems while applying HIPAA safeguards, role controls, and retention policies across multiple facilities.

These tasks are executed by both individual contributors and centralized administrators depending on organizational policy and required controls.

How the signNow workflow works

Follow the document from upload through field review, signing, and controlled archival.

  • Upload document: Upload the directive PDF to signNow.
  • Review fields: Confirm detected fields and add missing ones.
  • Assign signers: Assign the declarant, witnesses, or representative.
  • Store record: Complete signing and retain the audit trail.

Complete the directive in signNow

Use this sequence to prepare the healthcare directive while checking state-specific witness and notarization requirements.

  • Upload form:

    Upload the completed directive PDF.
  • Check fields:

    Confirm declarant and witness fields.
  • Add recipients:

    Add signer email addresses or links.
  • Complete signing:

    Send, sign, and download the record.
be ready to get more
Get legally-binding signatures now!
  • Best ROI. Our customers achieve an average 7x ROI within the first six months.
  • Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
  • Intuitive UI and API. Sign and send documents from your apps in minutes.

Configure the advance directive workflow

Use controlled authentication, auditable signing, and secure retention when processing this healthcare directive.

SettingRecommendation
Authentication methodTwo-factor authentication for healthcare signers
Signature typeIntent-based electronic signature with signer consent
Audit trailDetailed audit trail with timestamps and action history
Document retentionSix years when HIPAA applies (45 CFR 164.530(j))
EncryptionTLS 1.2 or 1.3 in transit and AES-256 at rest

Review the directive audit trail

Inspect authentication, timestamps, document history, and completion records before placing the directive in the patient’s authorized record.

01

Authenticate signer:

signNow records the signer authentication event.
02

Capture timestamp:

The audit trail captures date and time.
03

Protect document:

The completed document receives integrity protection.
04

Record history:

Signer actions remain available for review.
05

Export certificate:

The sender retrieves the completion certificate.
06

Archive record:

Authorized staff archive the signed directive.

Security for directive records

Health information:

HIPAA-compliant workflow

Independent controls:

SOC 2 Type II certified

Security management:

ISO 27001 certified

Stored documents:

AES-256 encryption at rest

Data in transit:

TLS 1.2 or 1.3

Signer verification:

Two-factor authentication

Connect the directive to existing systems

Route completed healthcare directives into controlled workflows using Salesforce, Microsoft 365, Google Drive, Box, Egnyte, NetSuite, or direct API connections where the deployment requires it.

Salesforce
Procore
Zapier
Microsoft Teams
Hub spot
Box
Microsoft

Avoid privacy and execution mistakes

  • Patient names, diagnoses, and treatment preferences can be exposed when directive recipients or storage permissions are configured too broadly.
  • A missing witness, notary acknowledgment, or state-required declaration can prevent the executed directive from satisfying local law.
  • Using an old template may omit representative instructions, revocation language, or signature fields required by the applicable state form.
  • Sending the directive to the wrong representative can create a privacy incident and leave the intended healthcare decision-maker without notice.

Check state-specific execution rules

State formalities

May not satisfy state execution rules

Wills and codicils

Excluded from ESIGN and UETA

Family law documents

Requires separate legal process

Real-estate deeds

Recording rules vary by state

Retention rules for directive records

Retention depends on the record’s legal category and the organization’s state and healthcare obligations; do not apply an unrelated schedule automatically.

01

Three years for tax records

IRC §6501(a) generally limits federal tax assessment to three years from filing; this applies only if the directive also supports tax records.
02

Six years for HIPAA records

HIPAA requires six years from creation or the last effective date under 45 CFR 164.530(j).
03

Five years for injury records

OSHA requires five years following the year for injury records under 29 CFR §1904.33.
04

Thirty years for exposure records

OSHA requires thirty years for exposure records under 29 CFR §1910.1020.
05

Seven years for audit records

Sarbanes-Oxley requires seven years for covered audit records under 15 U.S.C. §7245.

Features that support directive completion

signNow combines field preparation, signer routing, authentication, audit history, and storage controls for this healthcare directive workflow.

Field detection

Upload the directive and confirm detected fields before assigning the declarant, witnesses, representative, or notary workflow.

Signer routing

Route the document to each required participant in the intended order, reducing missed signature and acknowledgment fields.

Audit trail

Capture timestamps, actions, and completion history so authorized staff can review how the directive was executed.

Access controls

Use two-factor authentication and controlled access when the directive contains protected health information or sensitive treatment preferences.

Secure storage

Keep the signed directive and completion record together for later retrieval by authorized healthcare personnel.

System connections

Connect completed records with Google Drive, Box, Egnyte, or healthcare systems through supported integrations and API options.

Troubleshooting this directive workflow

Resolve field, authentication, retention, and state-law issues before treating the signed directive as complete.

Upload the original directive as a PDF, then use signNow’s field detection and editor to confirm each declarant, representative, witness, date, and acknowledgment field. If detection misses a field, place it manually and compare the final layout with the source document before sending.

Business includes legally binding eSignatures, templates, audit trails, and mobile apps at $8 per user per month when billed annually. However, state law may require witnesses or notarization for an advance directive, so confirm those requirements before selecting a signing route.

signNow supports HIPAA-compliant workflows when a business associate agreement is required. Configure access controls, limit recipients, and avoid sending unnecessary protected health information. HIPAA retention is six years from creation or the last effective date under 45 CFR 164.530(j).

Use SMS OTP or another configured authentication control when identity assurance matters. The audit trail records signer actions, timestamps, and document history, but authentication settings do not replace state-required witnesses, notarization, or clinical review.

Business Premium costs $15 per user per month annually and adds bulk send, kiosk mode, request payments, and quick invite links. Bulk send is useful for repeated workflows, but each directive still requires accurate patient-specific data and review.

ESIGN and UETA generally recognize electronic records and signatures when intent, consent, attribution, and retention are established. They do not override excluded documents or state execution rules. Review the applicable state statute or Secretary of State guidance before relying on electronic execution.

ROI at a Glance

Key performance indicators that demonstrate SignNow's proven track record.

28M+Documents signed
13+Years in business
4.6/5Average G2 rating

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.