Establishing secure connection…Loading editor…Preparing document…

Legal HIPAA Compliance Agreement

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

LEGAL HIPAA COMPLIANCE AGREEMENT

This Legal HIPAA Compliance Agreement ("Agreement") is entered into as of by and between Covered Entity Name: with principal address: (hereafter "Covered Entity"), and Business Associate Name: with principal address: (hereafter "Business Associate").

RECITALS

WHEREAS: Covered Entity creates, receives, maintains or transmits Protected Health Information ("PHI") as defined under the Health Insurance Portability and Accountability Act of 1996 and its implementing regulations ("HIPAA Rules"), including the Privacy Rule and Security Rule; and

WHEREAS: Business Associate performs certain services for Covered Entity, and in connection with such services, Business Associate will create, receive, maintain or transmit PHI on behalf of Covered Entity; and

WHEREAS: The parties desire to set forth their respective rights and obligations with respect to PHI and to ensure that Business Associate complies with applicable HIPAA Rules.

NOW, THEREFORE, in consideration of the mutual covenants and agreements contained herein, the parties agree as follows:

1. DEFINITIONS

Capitalized terms used but not otherwise defined in this Agreement shall have the meanings given in the HIPAA Rules. For purposes of this Agreement, the following definitions apply: "Protected Health Information" or "PHI" means individually identifiable health information that is transmitted or maintained in any form or medium, whether electronic, paper, or oral, that relates to the past, present or future physical or mental health condition of an individual, the provision of health care to an individual, or payment for the provision of health care to an individual.

2. PERMITTED USES AND DISCLOSURES

Business Associate may use and disclose PHI only as necessary to perform the services described in the underlying services agreement between the parties, and as otherwise permitted by this Agreement. Business Associate shall not use or disclose PHI in a manner that would violate the HIPAA Rules if done by Covered Entity. Business Associate may use PHI for its proper management and administration or to carry out its legal responsibilities, provided that such uses are permitted by the HIPAA Rules and only to the extent permitted by this Agreement.

3. OBLIGATIONS OF BUSINESS ASSOCIATE

Business Associate shall:

a. Implement appropriate administrative, physical and technical safeguards to prevent the use or disclosure of PHI other than as permitted by this Agreement and to protect the confidentiality, integrity and availability of Electronic PHI in accordance with the HIPAA Security Rule;

b. Ensure that any agent, including a subcontractor, to whom it provides PHI agrees in writing to the same restrictions and conditions that apply to Business Associate under this Agreement;

c. Not de-identify PHI except in accordance with the HIPAA Rules and only upon prior written authorization from Covered Entity;

d. Use appropriate sanctions against workforce members who fail to comply with the privacy and security policies required by this Agreement; and

e. Make available to Covered Entity such information as Covered Entity may require to satisfy its obligations under the HIPAA Rules, including but not limited to accounting of disclosures, access, and amendment requests, to the extent Business Associate maintains such information.

4. SAFEGUARDS; RISK MANAGEMENT

Business Associate shall implement administrative, physical and technical safeguards sufficient to reasonably and appropriately protect the confidentiality, integrity, and availability of PHI in its possession, including but not limited to:

a. Conducting and documenting periodic risk analyses and applying risk management updates;

b. Implementing access controls, authentication mechanisms, encryption where appropriate, audit controls and secure disposal procedures;

c. Maintaining written policies and providing workforce training addressing the handling of PHI and security incidents.

5. BREACH NOTIFICATION

Business Associate shall report to Covered Entity any use or disclosure of PHI not permitted by this Agreement, any security incident affecting Electronic PHI, and any actual or suspected breach of unsecured PHI. Such notification shall be made without unreasonable delay and in any event no later than 60 calendar days after discovery of the breach. The notification shall include, to the extent known, the nature of the breach, the PHI involved, steps taken to mitigate harm, and steps to prevent future occurrences.

6. SUBCONTRACTORS

Business Associate shall require each subcontractor or agent that creates, receives, maintains, or transmits PHI on behalf of the Business Associate to execute a written agreement obligating the subcontractor to comply with the same restrictions and conditions that apply through this Agreement to Business Associate with respect to such PHI.

7. ACCESS, AMENDMENT AND ACCOUNTING

Business Associate shall make available to Covered Entity such PHI in a designated record set as is necessary for Covered Entity to fulfill its obligations to provide access or make amendments to PHI and to account for disclosures, within the timeframes required by the HIPAA Rules. Business Associate shall, at Covered Entity's direction, provide access directly to the individual when applicable.

8. RETURN OR DESTRUCTION

Upon termination of this Agreement, Business Associate shall, at Covered Entity's option, return or destroy all PHI received from Covered Entity that Business Associate still maintains in any form. If return or destruction is infeasible, Business Associate shall extend the protections of this Agreement to such PHI and limit further uses and disclosures to those purposes that make the return or destruction infeasible.

9. INDEMNIFICATION

Business Associate shall indemnify, defend and hold harmless Covered Entity from and against any and all claims, liabilities, losses, damages, fines and expenses (including reasonable attorneys' fees) arising from Business Associate's breach of this Agreement or violation of the HIPAA Rules to the extent caused by Business Associate's negligent or willful acts or omissions.

10. AUDIT; RECORDS

Business Associate shall document and retain policies, procedures, records of disclosures, risk assessments and other materials necessary to demonstrate compliance with this Agreement and shall make such records available to Covered Entity and to the Secretary of the relevant regulatory authority upon request as required by law.

11. TERM AND TERMINATION

This Agreement shall commence on the Effective Date and shall remain in effect for the term of the underlying services agreement, unless earlier terminated. Covered Entity may terminate this Agreement and the underlying services agreement upon written notice if Covered Entity determines Business Associate has committed a material breach of this Agreement and such breach is not cured within thirty (30) days following written notice specifying the breach. If termination is not feasible, Covered Entity shall report the problem to the Secretary of the relevant regulatory authority.

12. NOTICES

All notices, demands or communications required or permitted under this Agreement shall be in writing and delivered to the addresses set forth below by hand, registered mail, or certified mail, return receipt requested, or by nationally recognized overnight courier.

13. MISCELLANEOUS

Governing Law: This Agreement shall be governed by and construed in accordance with the laws of the state identified by Covered Entity's principal address, without regard to conflict of law principles.

Entire Agreement: This Agreement contains the entire understanding of the parties with respect to the subject matter hereof and supersedes all prior oral or written agreements between the parties concerning the subject matter.

Severability: If any provision of this Agreement is held to be invalid or unenforceable, the remaining provisions shall remain in full force and effect.

Amendment: This Agreement may be amended only by a written instrument signed by both parties. Any amendment required by changes in applicable law shall be effective as of the date required by law; the parties shall promptly execute a written amendment to reflect such change.

Waiver: No failure or delay by either party in exercising any right under this Agreement shall constitute a waiver of that right.

Counterparts: This Agreement may be executed in counterparts, each of which shall be deemed an original and all of which together shall constitute one instrument. Photocopies or electronic copies of signatures shall be binding.

ADDITIONAL BUSINESS ASSOCIATE REPRESENTATIONS

Covered Entity Printed Name:

By:

Date:

Business Associate Printed Name:

By:

Date:

Enter text✕

What the Legal HIPAA Compliance Agreement Is

A Legal HIPAA Compliance Agreement is a written contract that sets privacy, security, and permitted-use terms for protected health information (PHI) exchanged between covered entities and business associates. It documents responsibilities for safeguarding PHI, breach notification duties, permitted disclosures, and any technical or administrative safeguards required. The agreement supports compliance with HIPAA privacy and security rules and establishes the scope of PHI access and processing, recordkeeping expectations, and how audits, audits responses, and risk mitigation will be handled.

Why a Written HIPAA Agreement Matters

A clear agreement reduces compliance risk by allocating responsibilities for PHI protection, breach handling, and regulatory reporting. It documents controls and provides evidence of required contractual protections under HIPAA and HITECH, helping organizations demonstrate compliance during audits.

Why a Written HIPAA Agreement Matters

Who Typically Completes This Agreement

Covered entities and vendors exchanging PHI must complete or require this agreement before any PHI transfer.

  • Healthcare providers and clinics that share patient data with outsourced service providers for claims processing or analytics.
  • Business associates such as cloud hosting, billing, and transcription vendors that store, access, or process PHI on behalf of covered entities.
  • In-house legal, compliance, or vendor-management teams negotiating terms and verifying technical safeguards and audit rights.

Signing the agreement before PHI exchange and keeping an executed copy supports regulatory defenses and internal compliance workflows.

Step-by-Step: How to Complete and Execute the Agreement

Follow a predictable sequence to prepare, review, sign, and store the agreement to ensure enforceability and traceability.

  • 01
    Prepare: Populate parties, scope, safeguards, and retention fields.
  • 02
    Review: Legal and privacy teams confirm obligations and risk allocation.
  • 03
    Authorize: Obtain signatures from individuals with signing authority.
  • 04
    Store: Save executed copy in secure records with audit trail.

Essential Contract Elements to Include

A professional HIPAA Compliance Agreement should be concise but cover key legal, technical, and operational controls so both parties understand obligations and remedies.

Scope

Define the specific PHI types, permitted uses, and any processing limitations so data handling expectations are clear and auditable.

Permitted Uses

List permitted disclosures and processing activities, including any restrictions on onward transfers or aggregation for analytics.

Security Measures

Specify administrative, physical, and technical safeguards such as encryption, access controls, and incident response procedures.

Breach Notification

Set timelines and reporting channels for suspected breaches, including cooperation obligations for investigations and notifications.

Audit Rights

Establish the right to audit, review logs, and receive evidence of compliance, including frequency and scope limits.

Termination

Detail data return or destruction procedures upon contract end and steps for continued protection of retained records.

Security and Compliance Certifications to Verify

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest
HIPAA: Compliant — BAA required
SOC 2: SOC 2 Type II certified
21 CFR Part 11: Supported for regulated records
ISO: ISO 27001 certified
Accessibility: WCAG 2.0 Level AA

Penalties and Key Legal Risks to Note

HIPAA civil liability: Civil fines, corrective action (45 CFR §§160–164)
Unauthorized disclosure: Regulatory enforcement and reputation harm
Contract breach: Indemnity and damages exposure
Audit failures: Remediation orders and monitoring
Data residence issues: Cross-border transfer restrictions
Recordkeeping lapses: Compliance findings on retention

Common Preparation Mistakes to Avoid

  • Failing to obtain a signed Business Associate Agreement (BAA) before sharing PHI, leaving covered entities exposed to regulatory enforcement.
  • Using vague scope language that permits broad PHI use without specifying permitted processing, making audits and enforcement harder to defend.
  • Relying on weak signer authentication or not documenting consent for electronic execution, which can weaken proof of intent under ESIGN and UETA.
  • Neglecting retention and destruction instructions, resulting in over-retention or premature deletion that jeopardizes legal and regulatory obligations.

How Electronic Execution Typically Works

Digital workflows let parties complete the agreement while capturing evidence required to establish intent, consent, and attribution under U.S. e-signature laws.

  • Upload: Sender uploads the agreement document to the signing platform.
  • Place Fields: Add signature, date, and initial fields where required.
  • Authenticate: Signers authenticate via email, SMS, or stronger methods.
  • Finalize: Platform records timestamps, IP, and audit trail.

Recommended Platform Settings for HIPAA Agreements

Configure your e-signature workflow to balance signer convenience with required authentication and auditability.

Field Configuration
Authentication Method Email + SMS code or KBA for higher assurance
Signature Type Electronic signature with audit trail
Audit Trail Capture IP, timestamp, and action log
BAA Requirement Enforce BAA acceptance before enabling PHI fields

Technical and Integration Considerations

Select a signing platform that supports required security, integrations, and file formats for your workflows.

  • Integrations: Salesforce, NetSuite, Google Workspace support
  • File Formats: PDF, DOCX, and editable templates
  • APIs & Automation: API access for automated routing

Ensure the platform can support retention exports, audit logs, and a signed BAA to meet HIPAA contract and recordkeeping needs.

Key Timing Considerations and Deadlines

Track execution, retention, and disclosure timeframes to meet HIPAA obligations and support audits.

Execute Before PHI Exchange:

Ensure the agreement and any required BAA are signed prior to sharing PHI.

Retention Start Date:

Retention periods typically begin on the document creation or execution date.

ESIGN Consumer Disclosure:

Provide required consent/consumer disclosure before obtaining electronic signatures for consumer-facing records.

Breach Cooperation Timeline:

Contract should require prompt cooperation on breach investigations and notifications.

Record Access Window:

Specify how long audit logs and signed copies remain accessible for inspections.

Typical Contract Lifecycle Milestones

Track milestones from negotiation through post-termination obligations to ensure continuous protection of PHI.

01

Drafting

Complete initial terms, scope, and security requirements.

02

Legal Review

Privacy and contract teams verify obligations and indemnities.

03

Execution

Obtain authorized signatures and capture audit evidence.

04

Post-Termination Steps

Return or securely destroy PHI per agreement terms.

Comparing Electronic vs Paper HIPAA Agreements

A concise comparison of practical differences between electronic and paper execution for HIPAA agreements.

Criteria Electronic Agreement Paper Agreement
Legal validity esign/ueta acceptance common law enforceable
Signature evidence audit trail and metadata wet ink on paper
Storage requirements encrypted digital storage physical filing or safe
HIPAA compatibility yes with baa yes with baa

eSignature Vendor Pricing Snapshot for HIPAA Agreements

Compare starting prices and feature availability for common eSignature vendors. signNow is listed first per vendor-comparison convention.

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

Frequently Asked Questions and Quick Answers

Common practitioner questions about enforceability, BAAs, signatures, and recordkeeping with concise answers to guide practical compliance steps.


Need help? Contact support

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