Is an electronic Health Declaration legally valid?

Yes. Electronic signatures meet legal validity requirements under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided the four ESIGN elements are met: intent, consent, attribution, and retention. Certain exceptions (e.g., wills, some court filings) remain excluded.

How is protected health information secured?

Treat PHI per HIPAA: implement administrative, physical, and technical safeguards, and execute a Business Associate Agreement when a third-party e-sign provider processes PHI. HIPAA retention and safeguard rules apply (45 CFR §164.530(j)).

Do Health Declarations require notarization?

Generally no. Routine screening declarations do not require notarization. If a specific legal purpose or jurisdiction requires notarization, follow state notary rules including Remote Online Notarization where permitted.

What authentication level should be used?

For low-risk screening, email or SMS verification may suffice. Higher-risk uses should apply stronger methods (KBA, two-factor authentication, credential analysis) and record the method in the audit trail to support attribution.

How can a submitted declaration be amended?

Create a new dated amendment or replacement declaration signed by the same individual. Retain both the original and amendment with an audit trail so the full history is preserved for compliance or investigatory purposes.

How long must signed declarations be retained?

Retention depends on use: IRS-relevant records often require 3 years (IRC §6501(a)); HIPAA requires six years from creation or last effective date (45 CFR §164.530(j)); state laws may extend these periods, so adopt the longest applicable retention period.

Health Declaration

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

What a Health Declaration Is and when it’s used

A Health Declaration is a formal statement completed by an individual to disclose current health status, symptoms, recent exposures, and relevant medical history for a specific purpose, such as entry to a facility, participation in an event, travel, or employment. It documents consent to screening and records acknowledgements about contagious conditions or vaccination status when required. Health Declarations are frequently used to manage public-health risk, support contact tracing, and satisfy organizational or regulatory compliance. The form may be brief or detailed depending on the use case and applicable legal requirements.

Why organizations collect Health Declarations

Use a Health Declaration to document health-related disclosures, reduce transmission risk, and create a record for incident response and regulatory review. It provides a clear, reproducible statement of a person's recent symptoms or exposures for workplace, travel, or event screening purposes.

Who typically completes a Health Declaration

Many organizations collect Health Declarations when assessing entry or participation risk; this includes employers, event organizers, schools, and transportation providers.

Employers screening employees for workplace access and return-to-work clearance procedures.
Event organizers managing attendee health controls and contact-tracing records requirements.
Travel operators and venues checking recent exposure or symptom status.

Stepwise process to complete a Health Declaration

Complete the Health Declaration accurately and in order to ensure reliable screening, correct routing, and valid records for downstream review.

01

Start: Enter personal details, contact info, and effective date.
02

Report: Describe symptoms and exposure history in plain language.
03

Review: Confirm entries, attach supporting documents if required.
04

Sign: Provide signature and consent; choose eSign or wet ink.

How e-submission and routing typically work

A typical e-submission workflow captures data, routes for review, and stores a signed record with an audit trail for compliance.

Upload: Attach the Health Declaration PDF or use an online form.
Prepare: Map required fields and set conditional questions.
Send: Distribute to signer via email link or bulk send.
Archive: Store signed record with audit trail and export options.

Configuring an online Health Declaration workflow

Configure an online Health Declaration workflow to validate inputs, enforce required fields, and route signed records to appropriate recipients for review and storage.

Field	Configuration
Form or Workflow Type and Mode	Single-page form or multi-step wizard for conditional flows.
Required Fields and Validation	Enforce name, date, contact, symptom checkbox, signature.
Authentication Method	Email link, SMS code, or stronger KBA as needed.
Routing and Notifications	Send completed records to HR, medical review, and archive.

Technical requirements for secure eSubmission

Digital submission requires a platform supporting secure forms, e-signature, and access logging for compliance and traceability.

Authentication: Email, SMS code, or KBA
Audit Trail: Timestamps, IP, action log
Document Formats: PDF, DOCX, HTML supported

Security and compliance controls to look for

Encryption in Transit: TLS 1.2 and TLS 1.3

Encryption at Rest: AES-256 with secure key management

Certifications: SOC 2 Type II, ISO 27001

HIPAA: Compliant; BAA required for PHI

Legal Frameworks: ESIGN and UETA support for e-signatures

Accessibility: WCAG 2.0 Level AA supported

Risks and potential penalties for incorrect declarations

False Statements: Civil liability or administrative penalties

Incomplete Data: Denial of entry or access

Privacy Breach: HIPAA violations and fines

Delayed Response: Contact tracing slowed

Criminal Exposure: Willful concealment can trigger charges

Operational Impact: Event cancellations or quarantines

Common preparation and processing mistakes

Failing to standardize date formats leads to inconsistent records and complicates data aggregation for contact tracing and regulatory reporting.
Collecting unnecessary health details without a lawful basis increases privacy risk and may breach HIPAA or state privacy requirements.
Using weak signer authentication such as email-only links can reduce evidentiary weight and enable forged submissions.
Not retaining signed declarations per regulatory retention schedules can expose organizations to audit findings and legal challenges.

Essential elements of a professionally drafted Health Declaration

A professional Health Declaration balances brevity with necessary clinical detail, clear consent language, and recording features that support auditability and privacy compliance.

Purpose

State why the declaration is collected (screening, access control, or public health reporting), who will view the information, and how results will affect participation or access decisions.

Scope

Specify the population covered, applicable locations, and time window for disclosures (for example, symptoms or exposures within the previous 14 days), and any follow-up procedures.

Consent

Include a clear consent clause stating agreement to screening, electronic records under ESIGN, and permission for limited contact for follow-up or contact tracing.

Questions

Use simple, specific questions with checkbox options and space for brief explanations; avoid ambiguous phrasing and include date fields for onset information.

Attachments

Allow upload of supporting documents such as test results, vaccination records, or clinician notes; define accepted formats, file size limits, and submission deadlines.

Audit Trail

Record signer identity, timestamps, IP addresses, and action logs; preserve a machine-readable certificate of completion and storage location to support legal admissibility.

Practical best practices for accurate, efficient completion

Adopt practices that reduce errors, protect privacy, and speed processing of Health Declarations across workflows.

Use clear and consistent question wording

Phrase symptom and exposure questions in plain language, offer checkbox options, and provide examples of acceptable answers. Consistent phrasing across forms reduces caller confusion and eases automated data aggregation for reporting and contact tracing.

Limit data collection to necessities

Collect only information required to make health decisions and meet legal obligations. Avoid unnecessary medical history. Minimizing data reduces privacy risk and simplifies compliance with HIPAA and state privacy laws.

Document consent for e-records per ESIGN

Include a clear electronic-consent clause, ensure the signer can access records in the chosen format, and record affirmative consent to e-records to satisfy 15 U.S.C. §7001 requirements.

Apply appropriate access controls and retention

Restrict access to signed declarations to authorized personnel, encrypt data at rest and in transit, and implement retention schedules aligned with HIPAA, IRS, or state requirements.

Timing expectations for submission and processing

Understand timing expectations for submitting and processing Health Declarations to ensure valid screening and timely follow-up across use cases.

Submission Window:

Submit within 24–72 hours before entry or event.

Event Entry:

Provide upon arrival or via pre-event online submission.

Travel:

Complete declarations per carrier or destination rules before departure.

Return-to-Work:

Employees must submit up-to-date declarations before workplace reentry.

Processing Time:

Allow 24–48 hours for review and verification in typical workflows.

Key milestones in the Health Declaration lifecycle

Key milestones outline form preparation, collection, verification, and retention steps for each Health Declaration lifecycle.

01

Form Prepared

Define fields, consent language, and required attachments.

02

Distribution Live

Publish form link or distribute paper copies to participants.

03

Verification Complete

Review responses and follow up on flagged items promptly.

04

Records Archived

Export signed records to secure storage and apply retention.

Illustrative examples of operational use

Examples of how organizations use Health Declarations show operational variety across sectors and compliance needs.

Martin Properties

A regional property management firm used a digital Health Declaration to screen attendees at showings and manage tenant access without in-person forms.

Enabled mobile signing onsite and offline.
Tim Martin, Founder of Martin Properties, noted online processing maintained compliance and allowed fast return of completed forms, reducing administrative handoffs and preserving audit records for each transaction.

Fertility Centers of Illinois

A healthcare clinic integrated Health Declarations into patient intake to capture symptom screening and consent before appointments.

Supported HIPAA-aligned secure intake workflows.
John Butler, Founder of Fertility Centers of Illinois, emphasized responsive support and API integration that made it easier to collect signed declarations while preserving patient privacy and auditability.

Who signs and administers Health Declarations

Clinic Administrator

Oversees patient intake and requires Health Declarations to triage appointments, document consent for telehealth, and coordinate with medical staff. Must ensure data handling meets HIPAA and that e-sign consents are documented for each patient visit.

Event Organizer

Manages attendee screening, uses Health Declarations to enforce entry rules, track potential exposures, and coordinate notifications. Needs configurable questions, bulk send capability, and retention policies aligned with local public-health guidance.

eSignature pricing and plan features for Health Declaration workflows

Compare starting prices and common plan features across vendors to estimate eSignature costs for Health Declaration workflows.

	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	Yes, 7-day free trial, no credit card required	Varies by vendor	Varies by vendor	Varies by vendor	Varies by vendor
Bulk Send	Yes (plan dependent)	Yes (plan dependent)	Yes (plan dependent)	Yes (plan dependent)	Varies
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Frequently asked questions about Health Declarations

Answers to common questions about legal validity, privacy, authentication, notarization, updates, and record retention for Health Declarations.

Need help? Contact support

Is an electronic Health Declaration legally valid?
Yes. Electronic signatures meet legal validity requirements under the ESIGN Act (15 U.S.C. §7001) and UETA where adopted, provided the four ESIGN elements are met: intent, consent, attribution, and retention. Certain exceptions (e.g., wills, some court filings) remain excluded.
How is protected health information secured?
Treat PHI per HIPAA: implement administrative, physical, and technical safeguards, and execute a Business Associate Agreement when a third-party e-sign provider processes PHI. HIPAA retention and safeguard rules apply (45 CFR §164.530(j)).
Do Health Declarations require notarization?
Generally no. Routine screening declarations do not require notarization. If a specific legal purpose or jurisdiction requires notarization, follow state notary rules including Remote Online Notarization where permitted.
What authentication level should be used?
For low-risk screening, email or SMS verification may suffice. Higher-risk uses should apply stronger methods (KBA, two-factor authentication, credential analysis) and record the method in the audit trail to support attribution.
How can a submitted declaration be amended?
Create a new dated amendment or replacement declaration signed by the same individual. Retain both the original and amendment with an audit trail so the full history is preserved for compliance or investigatory purposes.
How long must signed declarations be retained?
Retention depends on use: IRS-relevant records often require 3 years (IRC §6501(a)); HIPAA requires six years from creation or last effective date (45 CFR §164.530(j)); state laws may extend these periods, so adopt the longest applicable retention period.

Explore Templates

Notice of Name Correction Kids' World Parental Agreement Equipment Purchase and Security Agreement Chapter 13 Bankruptcy Overview Reaffirmation Agreement Verification of Creditor Matrix

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now