Can this addendum be signed electronically?

Yes. Electronic signatures are enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA in most states provided intent, consent, attribution, and record retention requirements are met. Exceptions that may require wet signatures include certain court filings and documents specifically excluded by statute.

Is signNow HIPAA-ready for this use?

signNow supports HIPAA-compliant workflows when a Business Associate Agreement (BAA) is in place. Ensure a signed BAA and proper configuration of access controls and audit logging before using the platform for protected health information.

When is notarization required?

Notarization depends on the document’s legal purpose and state law. Some jurisdictions require notarized health attestations or witness statements; check state rules and, where remote notarization is used, verify RON authority and retention requirements.

What happens if fields are mismatched?

Mismatched names, dates, or missing provider details often prompt manual verification and may delay onboarding or credentialing. Standardize formats and require supporting documentation to reduce rework.

How long must I retain signed addenda?

Retention varies: follow HIPAA’s 6-year minimum for covered entities (45 CFR §164.530(j)), retain HR-related records per IRS and labor rules (typically 3+ years), and check state-specific requirements for longer periods.

How do I correct an error after signing?

If data entry errors are found, complete a formal amendment or create a new addendum noting the correction, include signer attestations, and maintain both versions in the audit trail to preserve an evidentiary history.

Electronic Signature
Templates
Healthcare
Healthcare Immunization Addendum

Healthcare Immunization Addendum

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

HEALTHCARE IMMUNIZATION ADDENDUM

This Immunization Addendum supplements the existing patient record and authorizes administration and documentation of immunizations as set forth below. Patient Name: Date of Birth: Medical Record No.:

Patient Information

Address Phone Gender Emergency Contact

Insurance Information

Insurance Provider Policy / ID Number Group Number Subscriber Name

Medical History

Current Medications Allergies Prior Surgeries / Hospitalizations Chronic Conditions

I am currently pregnant or suspect I may be pregnant.

I have a weakened immune system or am taking immunosuppressive medication.

I have a history of severe allergic reaction to a vaccine or vaccine component (describe below).

Immunization Details (Record of Administration)

Immunization Entry 1

Vaccine Name

Date Administered

Manufacturer

Lot Number

Route

Site

Administrator

Immediate adverse reaction observed

Immunization Entry 2 (if applicable)

Vaccine Name

Date Administered

Manufacturer

Lot Number

Route

Site

Administrator

Immediate adverse reaction observed

Risks, Benefits and Acknowledgment

I acknowledge that the administering healthcare provider has explained the purpose, benefits, potential common side effects and rare but serious risks associated with the vaccine(s) listed above. I have had the opportunity to ask questions and received answers that I understand.

I understand that no warranty or guarantee has been made that the immunization will prevent illness in all cases. I understand I should remain in the facility for the period recommended by staff following vaccination for observation of immediate reactions.

I acknowledge that I have been informed of risks and benefits and consent to the administration of the vaccine(s) as documented on this form.

Authorization and Release

By signing below I authorize the licensed healthcare professional attending to administer the vaccine(s) listed on this Addendum and to record the immunization(s) in my medical record and in public health registries as required by law. I authorize release of relevant health information related to this immunization to my insurer for claims processing and to public health authorities for reporting.

This authorization is valid until: unless earlier revoked in writing. I understand that I may withdraw this authorization at any time by providing written notice to the facility; withdrawal will not affect actions already taken based on this authorization.

I acknowledge receipt of the facility's privacy practices and understand my health information will be used and disclosed as described above for immunization documentation and reporting.

Declination (If Refusing Immunization)

I decline the vaccine(s) listed on this Addendum at this time.

Reason for Declination (optional)

Certifications

I certify that the information provided on this Immunization Addendum is true and accurate to the best of my knowledge. I understand that knowingly providing false information may affect my care and that of others.

Patient Printed Name:

Signature:

Date:

If signing as legal guardian, relationship:

What the Healthcare Immunization Addendum Is

A Healthcare Immunization Addendum is a supplemental form appended to employment, contractor, volunteer, or student agreements to document immunization status, vaccine dates, provider information, medical or religious exemptions, and any declination. It creates a clear record of immunization-related conditions tied to workplace or program requirements and supports compliance with institutional policies, public health directives, and privacy rules. The addendum may be retained with personnel or medical files and can be completed on paper or electronically when ESIGN/UETA requirements are met and applicable privacy safeguards are in place.

Why a Formal Addendum Matters

A dedicated immunization addendum standardizes information, reduces ambiguity about vaccine status, and documents consent or declination. It supports public health compliance, internal risk assessments, and consistent onboarding or credentialing procedures across departments or facilities.

Who Typically Prepares and Signs This Addendum

Common preparers and signers include employers, HR or occupational health staff, clinical program administrators, and the individual whose status is being recorded.

Employers and HR teams responsible for workforce safety and compliance, ensuring forms match policy and are retained appropriately.
Occupational health or clinic staff who verify vaccine records, enter provider data, and confirm dates and lot numbers when required.
Employees, contractors, students, or volunteers who provide their immunization history, attest to accuracy, or submit exemption documentation.

Each party’s role should be clear on the form to avoid later disputes and to support accurate recordkeeping and access controls.

Stepwise Completion and Verification

Follow these sequential steps to complete, verify, and store the immunization addendum reliably.

01

Prepare the form: Confirm the correct addendum version and governing policy.
02

Enter details: Fill name, DOB, vaccine name, dose dates, and provider information.
03

Verify records: Attach or confirm official vaccine record or registry match.
04

Sign and retain: Obtain required signatures, record retention location, and any authentication metadata.

Core Components of a Professional Addendum

A robust addendum balances clear data fields with legal attestations and privacy controls to be useful for HR, clinical, and compliance teams.

Identification

Fields for full legal name, date of birth, employee or student ID, and contact details to reliably link the record to the person.

Vaccine Details

Structured fields for vaccine type, manufacturer, lot number, administration site, and one or more dose dates to capture immunization history precisely.

Verification

Section for provider name, clinic contact, and supporting documentation or registry confirmation to substantiate entries.

Attestation

Clear signer attestations for truthfulness, plus checkboxes for medical or religious exemption where applicable and required.

Privacy Notice

A concise statement describing use, disclosure limits, data retention, and reference to applicable privacy laws (HIPAA or FERPA) when relevant.

Signatures and Dates

Designated signature blocks for the individual, verifier, and witness/official where needed, with date and signer role fields.

Minimum Security and Compliance Elements

Encryption: TLS 1.2/1.3; AES-256 at rest

HIPAA BAA: Signed BAA required for PHI

Audit Trail: Timestamps, IP, action log

Access Controls: Role-based permissions

Authentication: Email, SMS, or stronger MFA

Retention Policy: Documented retention schedule

Risks and Legal Consequences to Consider

HIPAA Noncompliance: Civil penalties and corrective action possible under HHS enforcement; secure handling required (45 CFR Part 160)

Falsified Information: Employment action or liability may follow if attestations are knowingly false

Incomplete Records: Missing dates or provider info can invalidate verification and delay onboarding

Improper Disclosure: Unauthorized PHI sharing risks fines and reputational harm

State-specific Violations: State statutes may impose separate penalties for health record mishandling

Operational Impact: Unverified status can lead to exclusion from clinical assignments or facility access

Common Pitfalls to Avoid

Using inconsistent name formats causes record mismatches with state registries and delays verification requests.
Leaving dose dates incomplete or in nonstandard formats (e.g., YYYY-MM-DD vs MM/DD/YYYY) results in rejected records.
Failing to attach or reference supporting documentation forces manual follow-up and increases administrative burden.
Recording exemption claims without required supporting statements or medical notes can render the exemption invalid.

Typical Digital Completion Workflow

A concise workflow clarifies responsibilities and reduces signer friction when the addendum is completed electronically.

Upload: Send the addendum as PDF or DOCX to the signer.
Pre-fill: Populate known fields from HR or registry data to reduce errors.
Sign: Signer authenticates and applies electronic signature.
Store: Save signed copy with audit log in secure records system.

Configuring an Electronic Workflow

Key configuration settings ensure the addendum routes correctly and meets authentication needs for healthcare data.

Field	Configuration
Authentication Level	Email link, SMS code, or MFA depending on sensitivity
Mandatory Fields	Make name, DOB, vaccine, and signature required
Document Retention	Assign storage location and retention tag
Notification	Configure reminders and completion notifications

Technical and Integration Considerations

Ensure the platform supports secure storage, audit logs, and HIPAA-compliant workflows before enabling e-signature for immunization records.

Integrations: Salesforce, NetSuite, Google Workspace supported
File Formats: PDF and DOCX input/output supported
Authentication: Support for SMS, email, and SSO

Comparing eSignature Vendors for Immunization Workflows

Basic pricing and feature posture for common eSignature vendors; signNow is listed first per comparison rules and plan types vary by billing model and feature set.

	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 free trial	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes	Varies	Varies	Varies	Varies
Audit Trail	Yes	Varies	Varies	Varies	Varies
HIPAA Compliant	Yes	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Real-World Examples of Use

These brief examples illustrate how organizations apply an immunization addendum in practice across healthcare and other settings.

Fertility Centers of Illinois

A clinic integrates an immunization addendum into patient-facing intake packets to capture vaccine history efficiently and securely.

This centralizes verification with occupational health and reduces follow-up.
The organization highlights secure storage and API-based exchange with its EHR to keep records current and auditable without repeated patient outreach.

Regional University Health Program

A university requires student immunization addenda for clinical placements and stores signed records in a secure student health portal.

Clinical schools verify records before placements.
Using standardized addenda reduces administrative delays and ensures compliance with placement site requirements.

Practical Tips for Accurate Completion

Adopt consistent practices to minimize rework, support audits, and protect sensitive health data.

Standardize field formats

Require MM/DD/YYYY for dates, full legal names, and a standardized vaccine naming convention to reduce mismatches with registries and clinical systems.

Require supporting documentation

Attach official vaccination records or registry confirmations rather than handwritten notes to streamline verification and reduce follow-up.

Limit access and log activity

Grant access based on role, enable audit logging, and review access logs periodically to detect unauthorized viewing or export of PHI.

Document policy and retention

Publish retention schedules and handling procedures so managers and staff understand storage duration, deletion triggers, and legal hold obligations.

Time-sensitive Submission Points

Certain events trigger immediate or deadline-based submission of immunization records; build these into onboarding and credentialing workflows.

Pre-employment or Enrollment:

Submit immunization addendum before start date or first clinical assignment to permit verification.

Annual or Booster Updates:

Update records annually or when booster doses are required by policy or public health guidance.

Outbreak Response:

Provide updated documentation immediately when local directives or exposure events require proof of vaccination.

Clinical Placement Deadlines:

Meeting placement-specific deadlines avoids loss of assignment privileges.

Request for Audit:

Produce signed records promptly when requested by auditors or regulatory reviewers.

Frequently Asked Questions and Troubleshooting

Answers to common operational and legal questions to help administrators and signers avoid delays and ensure compliant handling.

Need help? Contact support

Can this addendum be signed electronically?
Yes. Electronic signatures are enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and UETA in most states provided intent, consent, attribution, and record retention requirements are met. Exceptions that may require wet signatures include certain court filings and documents specifically excluded by statute.
Is signNow HIPAA-ready for this use?
signNow supports HIPAA-compliant workflows when a Business Associate Agreement (BAA) is in place. Ensure a signed BAA and proper configuration of access controls and audit logging before using the platform for protected health information.
When is notarization required?
Notarization depends on the document’s legal purpose and state law. Some jurisdictions require notarized health attestations or witness statements; check state rules and, where remote notarization is used, verify RON authority and retention requirements.
What happens if fields are mismatched?
Mismatched names, dates, or missing provider details often prompt manual verification and may delay onboarding or credentialing. Standardize formats and require supporting documentation to reduce rework.
How long must I retain signed addenda?
Retention varies: follow HIPAA’s 6-year minimum for covered entities (45 CFR §164.530(j)), retain HR-related records per IRS and labor rules (typically 3+ years), and check state-specific requirements for longer periods.
How do I correct an error after signing?
If data entry errors are found, complete a formal amendment or create a new addendum noting the correction, include signer attestations, and maintain both versions in the audit trail to preserve an evidentiary history.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now