Download signNow app
4.7 / 5 rating on

Health Care Directive Nd Gov Form

Use a Health Care Directive ND gov template to make your document workflow more streamlined.

What the directive does and records

Health Care Directive Nd Gov Form records a person’s healthcare wishes and identifies the people who may help communicate or carry out those wishes when the person cannot express them. The exact signing, witness, notarization, revocation, and delivery rules depend on the governing state law and the form’s official instructions. With signNow, a sender uploads the directive, reviews detected fields, assigns patient, agent, witness, and date fields, sends it for completion, and retains the signed document with its audit trail. HIPAA-covered organizations must apply their privacy, access, and retention controls.

Who uses this health care directive

Patients and healthcare providers

Patients use the directive to record healthcare choices, treatment preferences, and authorized decision-maker information. Healthcare providers and designated agents use the completed document during care decisions, while compliance teams verify signatures, access, and audit evidence under applicable HIPAA and state requirements.

Healthcare organizations and care teams

Hospitals, clinics, assisted-living organizations, and family-care teams use the workflow to collect patient-specific directives, witness acknowledgments, and agent signatures. They can route the document through signNow, preserve the signed copy, and limit access to authorized personnel handling protected health information.

Business types using health care directives

Healthcare practices and organizations use this directive when patient instructions, signer identity, and controlled records must remain connected.

  • Solo physicians and independent care practices use the directive to collect patient instructions, agent details, and signatures without repeatedly scheduling paper-based appointments.
  • Hospitals and clinics use controlled templates to route patient-specific directives to patients, healthcare agents, witnesses, and authorized records staff.
  • Enterprise health systems use role-based sending, audit trails, and protected archives to coordinate directive workflows across multiple facilities and compliance teams.

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

How the directive workflow works

The signNow workflow connects the directive file, its required participants, signing events, and final record in sequence.

  • Upload: Upload the directive
  • Review: Detect and review fields
  • Send: Route to signers
  • Archive: Store signed evidence

How to complete the directive

Use this signNow sequence to prepare, route, complete, and retain the Health Care Directive Nd Gov Form.

  • Upload:

    Upload directive
  • Check fields:

    Review detected fields
  • Add recipients:

    Assign patient and agent
  • Send:

    Send for signatures
  • Archive:

    Store signed 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.

Ways to send and sign the directive

  1. Use the signNow web app when staff need to upload the directive, review fields, assign recipients, and monitor completion from a desktop browser.
  2. Use the signNow mobile app when patients, agents, or clinicians need to review and sign the directive from an iOS or Android device.
  3. Use kiosk mode for supervised in-person completion at a clinic, allowing staff to present the directive while keeping each signer’s actions in one workflow.
  4. Create a shareable signing link when an authorized organization needs to distribute the same approved directive template without sending individual email invitations.

Security for directive records

Encryption at rest:

AES-256 at rest

Encryption in transit:

TLS 1.2 and 1.3

Healthcare compliance:

HIPAA with BAA

Security certification:

SOC 2 Type II

Information security:

ISO 27001 certified

Signature legality:

ESIGN and UETA

Platform requirements for completing the directive

Complete the Health Care Directive Nd Gov Form in a current browser using TLS 1.2 or TLS 1.3; signNow supports Chrome, Firefox, Safari, Edge, Windows, macOS, iOS, and Android.

  • Browser support Chrome, Firefox, Safari, and Edge support secure form completion.
  • Operating systems Windows 10, macOS 12, iOS 15, and Android 10.
  • Supported devices Desktop, tablet, and smartphone access through a current browser.

Organizations handling protected health information should use managed Windows, macOS, iOS, or Android devices with current security updates. Confirm browser compatibility, identity controls, and retention settings with your privacy or compliance team before deploying the directive workflow.

Integrations for directive workflows

Connect directive workflows with healthcare records, collaboration, storage, and enterprise systems while preserving controlled routing and document access.

Salesforce
Procore
Zapier
Microsoft Teams
Hub spot
Box
Microsoft

What the directive audit trail records

The signNow audit trail preserves evidence around authentication, signing activity, document history, completion, and later retrieval.

01

Authenticate signer:

SignNow records the signer’s authentication event before the directive is completed.
02

Capture timestamp:

Each signing action receives a recorded date and time.
03

Record document history:

The completed directive is associated with document history and signing evidence.
04

Seal completion:

Tamper-evident completion evidence helps show whether the signed record changed.
05

Review audit trail:

The sender can review the completed workflow and audit events.
06

Export evidence:

Export the audit trail with the signed directive for controlled archival.

Privacy and disclosure pitfalls

  • A directive may expose diagnoses, treatment preferences, or family information when copied into unprotected email, downloaded to unmanaged devices, or shared beyond authorized care personnel.
  • A signer may complete fields without a clear electronic-record consent process, creating uncertainty about whether the patient understood and intended the electronic transaction.
  • Incorrect agent or witness permissions can reveal the directive to an unintended recipient or prevent an authorized participant from completing required fields.
  • Replacing a directive without marking the earlier version can leave providers uncertain about which healthcare instructions remain effective.

Retention and record-keeping practices

Preserve the directive, signing evidence, access history, and superseded versions according to healthcare privacy obligations and applicable state law.

Set a documented retention period for completed directives

Retain the completed directive and its audit trail for at least six years when the record is part of a HIPAA-covered designated record set, measured from creation or the last effective date under 45 CFR 164.530(j). Apply any longer state-law or organizational requirement.

Export the audit trail with every signed directive

Export the signNow audit trail with the signed directive after every completed workflow, preserving signer identity, timestamps, actions, and delivery evidence. Store the export with the final PDF so reviewers can connect the signature event to the exact healthcare directive.

Archive directives in a restricted protected repository

Restrict archived directives to authorized care, compliance, and records personnel using role-based access. Encrypt stored files, record access events, and avoid sending unprotected copies by email because directives may contain sensitive health and family information.

Separate current directives from superseded versions

Review archived directives when a patient replaces, revokes, or updates instructions. Mark the superseded copy clearly, preserve its history according to the applicable retention rule, and make the currently effective directive easy for authorized providers to identify.

Legal value of the completed directive

A completed electronic directive can provide an accessible record of healthcare instructions when the signer shows intent, consents to electronic records, and the organization preserves an accurate copy. ESIGN and UETA generally recognize qualifying electronic signatures, but state law may impose additional witness, notarization, revocation, or form requirements.

Why teams look for DocuSign alternatives

State rules and document limits

May invalidate execution

State witness rule

May delay recognition

Notarization requirement

Prior wishes may remain

Directive revocation

ESIGN exception applies

Excluded document type

Health Care Directive troubleshooting

Resolve field, authentication, privacy, and retention questions before relying on a completed Health Care Directive Nd Gov Form.

The Business plan includes legally binding eSignatures, templates, audit trails, mobile apps, ISO 27001, SOC 2, and GDPR support. If the directive requires HIPAA safeguards, signNow identifies HIPAA compliance as requiring a BAA; confirm the needed plan and agreement before sending protected health information.

Use signNow’s auto-detection after uploading the directive, then inspect every detected field before sending. Health Care Directive Nd Gov Form fields may not be recognized perfectly when the source PDF is scanned, so manually add or correct patient, agent, witness, date, and signature fields.

Use signNow’s authentication controls, including email delivery and SMS verification where configured, to connect the signer to the directive. For a higher-assurance workflow, Enterprise adds advanced signer authentication; select the method required by your organization and applicable state law.

A typed or drawn eSignature can be supported by ESIGN and UETA when intent, consent, attribution, and record retention are established. A healthcare organization must also satisfy its disclosure, access, and privacy procedures; signNow’s HIPAA compliance requires a BAA.

Business Premium includes bulk send and kiosk mode, but a single directive should be reviewed for patient-specific fields before distribution. Use separate recipient data and templates carefully; never bulk-send one patient’s health information to another recipient.

The signNow audit trail records signing activity, timestamps, and document history, while completed documents can be stored with the workflow. Export the audit trail and signed PDF together, then apply the organization’s retention and access policy under HIPAA 45 CFR 164.530(j), when applicable.

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.