HIPAA BAA Agreement Template (Free Download)

An attorney-vetted Business Associate Agreement (BAA) contract template compliant with 45 CFR § 164.502(e) and § 164.504(e). Preview the full legal text below or download the customizable Microsoft Word (.docx) and PDF bundle.

DV
David Vance (CISSP, HCISPP (Former Healthcare Audit Contractor))
Last Audited: 5 Nov 2026 • Verified Against 45 CFR § 164
Vendor-Neutral Review Policy

What a BAA Must Legally Include (Statutory Checklist)

Under 45 CFR § 164.504(e), a valid Business Associate Agreement cannot be a generic non-disclosure agreement (NDA). It must contain specific federal provisions to shield both the Covered Entity and the Business Associate from statutory penalties:

  • 1 Explicitly define permitted and required uses and disclosures of protected health information (PHI).
  • 2 Prohibit the Business Associate from using or disclosing PHI other than as permitted by the contract or required by law.
  • 3 Mandate appropriate technical, physical, and administrative safeguards to prevent unauthorized use or disclosure (45 CFR § 164.314).
  • 4 Require immediate reporting to the Covered Entity of any security incident or breach within a defined timeline (e.g. 5–10 business days).
  • 5 Ensure all subcontractors that create, receive, or transmit PHI agree to the same restrictions and conditions.
  • 6 Authorize immediate termination of the agreement if the Business Associate breaches a material term.
  • 7 Mandate return or destruction of all PHI upon termination of the contract, or extend protections if return is infeasible.

3 Costly BAA Mistakes That Trigger OCR Fines

AUDIT RISK WARNING

✖ Relying on standard generic SaaS Terms of Service without a dedicated BAA addendum

Regulatory Impact: An immediate willful neglect violation punishable by OCR fines ranging from $13,785 to $68,928+ per violation day.

✓ How to Fix: Always execute an independent, countersigned BAA document before any ePHI is ingested, uploaded, or transmitted.

✖ Omitting downstream subcontractor liability clauses

Regulatory Impact: If your vendor's subprocessor (e.g., cloud hosting or email relay) suffers a breach, your covered entity may remain directly liable.

✓ How to Fix: Verify that Section 3 of your BAA mandates identical downstream safeguards across all third-party subprocessors.

✖ Failing to establish a specific breach notification SLA

Regulatory Impact: HIPAA statutes allow up to 60 days, but your state law or insurance policy may require notification within 72 hours.

✓ How to Fix: Contractually specify that the Business Associate must report potential breaches within 5 business days or fewer.

210 KB

Download the Formatted .DOCX & .PDF Template

Includes clean Microsoft Word formatting, attorney bracketed fill-in fields, and execution signature blocks.

Instant file download · No vendor calls · Unsubscribe anytime

Includes 2026 HITECH Omnibus Updates

FORMAT: DOCX, PDF, TXT
STATUTORY BASIS: 45 CFR § 164.504(e)

Complete Plain-Text BAA Agreement Preview

You may copy the raw text directly below or use the download form above for the formatted Microsoft Word document.

Standard Federal HIPAA Business Associate Agreement (Plain-Text Preview) STATUTORY COMPLIANT: 45 CFR § 164.504(e)
BUSINESS ASSOCIATE AGREEMENT (BAA)
[Standard Federal HIPAA/HITECH Compliance Addendum]

This Business Associate Agreement ("Agreement") is entered into as of [EFFECTIVE DATE], by and between:

COVERED ENTITY:
Name of Organization: [COVERED ENTITY LEGAL NAME]
Address: [COVERED ENTITY ADDRESS]
Representative: [AUTHORIZED OFFICER NAME & TITLE]

and

BUSINESS ASSOCIATE:
Name of Organization: [BUSINESS ASSOCIATE LEGAL NAME]
Address: [BUSINESS ASSOCIATE ADDRESS]
Representative: [AUTHORIZED OFFICER NAME & TITLE]

RECITALS:
WHEREAS, Covered Entity is a "Covered Entity" as defined under the Health Insurance Portability and Accountability Act of 1996, as amended by the HITECH Act ("HIPAA"), codified at 45 CFR Parts 160 and 164; and
WHEREAS, Business Associate provides certain services to Covered Entity pursuant to an underlying Master Services Agreement that involves the creation, receipt, maintenance, or transmission of Protected Health Information ("PHI" or "ePHI");

NOW, THEREFORE, the parties agree as follows:

1. DEFINITIONS
Capitalized terms used, but not otherwise defined, in this Agreement shall have the same meaning as those terms in 45 CFR §§ 160.103, 164.402, and 164.501.
(a) Breach shall have the same meaning given under 45 CFR § 164.402.
(b) Designated Record Set shall have the same meaning given under 45 CFR § 164.501.
(c) Protected Health Information (PHI) shall have the meaning given under 45 CFR § 160.103.

2. OBLIGATIONS AND ACTIVITIES OF BUSINESS ASSOCIATE
(a) Permitted Uses and Disclosures. Business Associate agrees not to use or disclose PHI other than as permitted or required by this Agreement, the underlying Master Services Agreement, or as Required by Law.
(b) Safeguards. Business Associate shall implement administrative, physical, and technical safeguards that reasonably and appropriately protect the confidentiality, integrity, and availability of Electronic Protected Health Information (ePHI) in accordance with the HIPAA Security Rule (45 CFR §§ 164.308, 164.310, and 164.312).
(c) Encryption Standards. Business Associate agrees that all ePHI shall be encrypted both at rest (using NIST-validated AES-256 or equivalent) and in transit (using TLS 1.2 or higher).
(d) Reporting Unauthorized Disclosures and Breaches. Business Associate shall report to Covered Entity any acquisition, access, use, or disclosure of PHI not provided for by this Agreement, including Breaches of Unsecured PHI as required by 45 CFR § 164.410, within five (5) business days of becoming aware of such incident.
(e) Subcontractors. Business Associate agrees to ensure that any agent, including a subcontractor, that creates, receives, maintains, or transmits PHI on behalf of Business Associate agrees in writing to the same restrictions, conditions, and requirements that apply to Business Associate with respect to such information (45 CFR § 164.504(e)(1)(i)).

3. PERMITTED USES AND DISCLOSURES BY BUSINESS ASSOCIATE
Except as otherwise limited in this Agreement, Business Associate may:
(a) Use or disclose PHI to perform functions, activities, or services for, or on behalf of, Covered Entity as specified in the underlying Master Services Agreement;
(b) Use PHI for the proper management and administration of Business Associate or to carry out legal responsibilities;
(c) Provide data aggregation services relating to the health care operations of Covered Entity if authorized in writing.

4. TERM AND TERMINATION
(a) Term. This Agreement shall take effect on the Effective Date and shall terminate when all PHI provided by Covered Entity to Business Associate is destroyed or returned.
(b) Termination for Cause. If Covered Entity determines that Business Associate has breached a material term of this Agreement, Covered Entity shall provide written notice giving Business Associate thirty (30) calendar days to cure the breach. If Business Associate fails to cure, Covered Entity may immediately terminate the agreement.
(c) Effect of Termination. Upon termination, Business Associate shall return or destroy all PHI received from Covered Entity, or created or received by Business Associate. If return or destruction is not feasible, Business Associate shall extend the protections of this Agreement to such PHI and limit further uses.

IN WITNESS WHEREOF, the parties hereto have caused this Agreement to be executed by their duly authorized representatives.

COVERED ENTITY:                           BUSINESS ASSOCIATE:
Signature: ______________________        Signature: ______________________
Printed Name: ___________________        Printed Name: ___________________
Title: __________________________        Title: __________________________
Date: ___________________________        Date: ___________________________
Formatted with standard legal clauses (Permitted Uses, Safeguards, Breach SLA, Subcontractor Obligations). Ready for Legal Review

Related Compliance Guides & Software Hubs:

BAA Agreement Template FAQs

Legal and regulatory questions answered by healthtech compliance specialists.

01. Who needs to sign a Business Associate Agreement (BAA)?

Under 45 CFR § 160.103, any third party (vendor, contractor, cloud platform, software provider, or billing agency) that creates, receives, maintains, or transmits Protected Health Information (PHI) on behalf of a Covered Entity must execute a BAA.

02. Can a vendor refuse to sign a BAA and still be HIPAA compliant?

No. A vendor cannot be HIPAA compliant without executing a formal BAA. If a vendor handles PHI and refuses to sign a BAA, using their services is an automatic violation of federal law for the covered entity.

03. Is this BAA template valid in all 50 US states?

This template is based on federal HIPAA/HITECH Act regulations (45 CFR Parts 160 and 164). While federal regulations apply nationwide, certain states (such as Texas HB 300 or California CMIA) enforce stricter state-level privacy and breach reporting deadlines. Always have your healthcare legal counsel review state-specific riders.