Establishing secure connection…Loading editor…Preparing document…

Legal HIPAA Attestation Form

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

Legal HIPAA Attestation Form

This HIPAA Attestation (the "Attestation") is made effective as of Effective Date: by and between Covered Entity Name: with principal address: (hereinafter "Covered Entity") and Business Associate Name: with principal address: (hereinafter "Business Associate").

RECITALS

WHEREAS, Covered Entity engages Business Associate to perform certain services that involve the creation, receipt, maintenance or transmission of protected health information as defined by the Health Insurance Portability and Accountability Act of 1996 and its implementing regulations ("HIPAA");

WHEREAS, the parties maintain obligations under HIPAA and the Health Information Technology for Economic and Clinical Health Act ("HITECH") to implement administrative, physical and technical safeguards designed to protect the confidentiality, integrity and availability of protected health information ("PHI");

WHEREAS, this Attestation documents the parties' mutual representations and commitments regarding Business Associate's compliance with applicable HIPAA requirements and related security and privacy obligations.

NOW, THEREFORE, in consideration of the mutual covenants contained herein and other good and valuable consideration, the receipt and sufficiency of which are acknowledged, the parties agree as follows:

1. DEFINITIONS

Capitalized terms used but not otherwise defined in this Attestation have the meanings assigned to such terms in HIPAA and its implementing regulations. For purposes of this Attestation, "PHI" means protected health information as defined by 45 C.F.R. § 160.103.

2. ATTESTATION OF COMPLIANCE

Business Associate hereby attests, represents and warrants to Covered Entity that, as of the Effective Date and continuing through the term of the parties' underlying agreement, Business Associate has established and maintains administrative, physical and technical safeguards reasonably designed to protect the confidentiality, integrity and availability of PHI, and is in compliance with the applicable provisions of HIPAA and HITECH.

To evidence the foregoing, Business Associate certifies the following (check each applicable statement and provide details where requested):

Risk assessment performed within last 12 months and documented

Written HIPAA policies and procedures established and enforced

Workforce training provided on privacy and security policies

Access controls, unique user IDs and authentication implemented

Encryption of PHI at rest and in transit where technically feasible

Breach and incident response plan established and tested

Business Associate Agreements in effect with all subcontractors handling PHI

Secure disposal and retention policies for PHI implemented

3. REPRESENTATIONS AND WARRANTIES

Business Associate represents and warrants that: (a) it will use and disclose PHI only as permitted by the parties' applicable agreement and HIPAA; (b) it will implement and maintain reasonable and appropriate administrative, physical and technical safeguards to prevent use or disclosure of PHI not permitted by the parties' agreement; and (c) upon discovery of any actual or suspected breach or security incident involving PHI, it will notify Covered Entity in accordance with Section 5 below.

4. SECURITY SAFEGUARDS

Business Associate shall maintain safeguards that are at least as protective as those required by HIPAA, including but not limited to access controls, audit controls, integrity controls, person or entity authentication and transmission security. Business Associate shall document the technical and organizational measures employed and make such documentation available to Covered Entity upon reasonable request for the purpose of auditing compliance.

5. BREACH NOTIFICATION

Business Associate shall notify Covered Entity without unreasonable delay and in no event later than 72 hours after discovery of any security incident or breach involving unsecured PHI. Notification shall include, to the extent known at the time of notification, a description of the nature of the breach, the PHI affected, steps taken to mitigate harm, and corrective action planned or taken. Business Associate shall reasonably cooperate with Covered Entity’s investigation and required notifications to affected individuals and regulators.

6. TRAINING AND WORKFORCE

Business Associate shall ensure that all members of its workforce with access to PHI receive appropriate privacy and security training and are subject to sanctions for violations of policies. Business Associate will maintain training records for a minimum of three years and make those records available to Covered Entity upon request.

7. SUBCONTRACTORS & AGENTS

Business Associate shall require any subcontractor or agent that creates, receives, maintains or transmits PHI on behalf of Business Associate to agree in writing to substantially the same restrictions and conditions that apply to Business Associate under this Attestation and applicable law. Business Associate remains fully liable for any subcontractor's failure to comply.

8. AUDITS; RECORDS

Business Associate shall maintain records necessary to demonstrate compliance with this Attestation and HIPAA. Covered Entity may, upon reasonable notice and during normal business hours, audit Business Associate's relevant policies, procedures and records or require independent third-party audit reports prepared in accordance with generally accepted standards.

9. TERM; TERMINATION

This Attestation shall commence on the Effective Date and shall remain in effect for the duration of the parties' underlying service agreement or until terminated pursuant to that agreement. Upon termination, Business Associate shall return or securely destroy PHI in accordance with the parties' agreement and applicable law.

10. INDEMNIFICATION

Each party shall indemnify, defend and hold harmless the other party from and against any third-party claim, liability, loss or expense arising from its own breach of this Attestation or violation of HIPAA. The indemnifying party shall have the right to control the defense and settlement of any such claim, provided that the indemnifying party shall not settle any claim that imposes liability on the indemnified party without the indemnified party's prior written consent.

11. NOTICES

Any notice required or permitted under this Attestation shall be in writing and delivered to the parties at the addresses set forth below or to such other address as either party may designate by written notice in accordance with this section. Notices shall be deemed effective upon receipt.

12. AMENDMENT; WAIVER

No amendment or modification of this Attestation will be effective unless in writing and signed by both parties. Failure by either party to enforce any provision shall not constitute a waiver of that provision or the right to enforce it in the future.

13. GOVERNING LAW

This Attestation shall be governed by and construed in accordance with the laws of the state specified below without regard to conflict of law principles. The parties consent to the exclusive jurisdiction of the state and federal courts located therein.

14. ENTIRE AGREEMENT; SEVERABILITY

This Attestation, together with any underlying services agreement between the parties, constitutes the entire agreement between the parties with respect to the subject matter herein and supersedes all prior and contemporaneous agreements and understandings. If any provision of this Attestation is held invalid or unenforceable by a court of competent jurisdiction, the remaining provisions shall remain in full force and effect.

CERTIFICATION

The undersigned, as an authorized representative of the party for which they sign, certifies that the statements in this Attestation are true, complete and accurate to the best of their knowledge as of the Effective Date and that the signing party will comply with the representations, warranties and obligations set forth herein. The undersigned further acknowledges that false statements may result in contractual remedies and other penalties permitted by law.

Covered Entity:

By:

Date:

Business Associate:

By:

Date:

Enter text✕

What the Legal HIPAA Attestation Form Is and when it's used

The Legal HIPAA Attestation Form is a written statement used by covered entities, business associates, vendors, or contractors to confirm compliance with HIPAA privacy and security requirements when handling protected health information (PHI). It documents assertions about administrative, physical, and technical safeguards, data sharing purposes, and any limited authorizations for PHI use. The form can accompany a Business Associate Agreement but does not replace a BAA; it functions as an operational attestation to support due diligence and recordkeeping under HIPAA and related organizational policies.

Why this attestation matters for compliance and risk control

A clear attestation creates an auditable record that the signer understands and accepts HIPAA-related responsibilities, supports vendor assessments, and helps satisfy documentation expectations during audits or breach investigations.

Why this attestation matters for compliance and risk control

Who completes or receives this attestation

Recipients typically include privacy officers, compliance teams, procurement, and contracting officers who retain the attestation with contractual records.

  • Healthcare vendor: A third-party software or service provider that processes PHI on behalf of a covered entity.
  • Business associate: An organization performing services requiring PHI access under a Business Associate Agreement.
  • Internal compliance team: Security or privacy officers who collect attestations for vendor risk registries.

Key elements to include in a professional HIPAA attestation

A complete attestation combines identity, scope, specific safeguards, certifications, signature data, and retention instructions so reviewers can verify obligations and the evidence trail during audits.

Signer identity

Full legal name, title, organization, and contact details to attribute responsibility and support verification of authority.

Scope of access

Clear description of PHI types, systems, and purposes for access so obligations are matched to actual data flows.

Safeguards attested

Specific administrative, physical, and technical measures (encryption, access controls, training) the signer certifies are in place.

Regulatory reference

Citation to HIPAA obligations and any controlling state privacy law that frame the attestation’s legal context.

Signature metadata

Date, signing method (electronic or wet), and authentication evidence recorded for auditability and ESIGN/UETA compliance.

Retention note

Retention period and storage location so records remain available for OCR review or legal discovery.

Required data points at a glance

Legal name: Exact corporate or individual name
Title: Job title or authority level
Organization: Company or department name
Effective date: MM/DD/YYYY
Scope: Systems or PHI categories
Signature method: eSign type or wet signature

Step-by-step: completing the HIPAA attestation

Follow these ordered steps to produce a valid, auditable attestation that aligns with HIPAA documentation expectations.

  • 01
    Prepare details: Gather legal names, scope, and control descriptions.
  • 02
    Fill the form: Enter data carefully with required formats.
  • 03
    Authenticate signer: Confirm identity using chosen authentication method.
  • 04
    Record signature: Capture signature metadata and store securely.

How electronic submission and tracking typically flow

A standard eSubmission workflow reduces friction and preserves an audit trail; these are the usual operational steps.

  • Upload document: Sender uploads the attestation form to the signing platform.
  • Apply fields: Place signature, date, and data fields before sending.
  • Authenticate signer: Use email, SMS, or stronger methods per policy.
  • Archive copy: Store executed form and audit trail in records.

Typical digital workflow settings for online completion

Configure these settings to ensure consistent signer experience, secure authentication, and reliable archival.

Field Configuration
Signing order Sequential or parallel routing
Authentication Email code | SMS code | KBA
Notifications Sender and signer email alerts
Retention Encrypted archive location

Digital signing and platform requirements

Ensure the platform can produce a complete audit trail and meet encryption and retention requirements for HIPAA records.

  • File formats: PDF, DOCX supported
  • Integrations: Salesforce, NetSuite, Google Workspace
  • Authentication: Email, SMS, KBA options

Timelines and processing expectations for attestations

Set internal timelines for review and retention so attestations are available for audits and vendor management processes.

Internal review target:

Complete review within 7–14 days of receipt

BAA execution window:

BAA should be in place before PHI access

Record availability:

Signed copy must be retrievable immediately upon request

Update cadence:

Re-attest annually or on material change

Audit readiness:

Maintain accessible records for six years

Key processing milestones from request to archival

Track these sequential milestones to ensure the attestation is completed, validated, and retained with contractual records.

01

Request issued

Procurement or privacy sends the attestation request.

02

Signer completes

Vendor or business associate completes the form.

03

Compliance review

Privacy officer reviews content and verifies claims.

04

Archive stored

Signed attestation stored in encrypted records repository.

Common mistakes to avoid when preparing attestations

  • Using initials instead of a full signature, which can weaken attribution and complicate audits or legal challenges.
  • Leaving scope vague, for example stating 'access to records' without specifying systems, PHI categories, or business purpose.
  • Failing to authenticate the signer properly, relying solely on an unauthenticated email click for high-risk PHI access.
  • Not pairing the attestation with a signed Business Associate Agreement when PHI processing meets BA criteria.

Penalties and legal risks from incorrect or missing attestations

Regulatory penalties: OCR enforcement possible
Breach liability: Increased civil exposure
Contract exposure: Loss of contract or termination
Reputational harm: Public disclosure risk
Operational disruption: Remediation costs and downtime
Criminal risk: Willful violations may trigger prosecution

Common eSignature vendor pricing and capability snapshot

Comparison of starting price and core capabilities for common eSignature vendors; signNow is listed first for parity.

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

Real-world examples of attestations in use

Practical examples show how organizations record and rely on attestations during operations and audits.

Optica Ventures LLC — Brian Fitzgibbons

Optica standardized attestations for third-party integrations to reduce review time.

  • The approach centralized vendor responses and evidence.
  • As a result, Optica improved document turnaround, simplified procurement checks, and maintained an auditable log for compliance reviews without duplicative legal steps.

Fertility Centers of Illinois — John Butler

The center used attestations alongside BAAs for lab data providers.

  • Attestations clarified technical safeguards.
  • This pairing ensured signed commitments were retrievable for audits, supported incident response decisions, and documented compliance with internal privacy policies and regulatory expectations.

Frequently asked questions about the Legal HIPAA Attestation Form

Answers to common questions about validity, required elements, eSigning, and post-signature handling for attestations.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users