Establishing secure connection…Loading editor…Preparing document…

HIPAA Business Partner Contract

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

SAMPLE BUSINESS ASSOCIATE CONTRACT PROVISIONS

Statement of Intent

These sample business associate contract provisions are provided in response to numerous requests for guidance. This is only sample language. These provisions are designed to help covered entities more easily comply with the business associate contract requirements of the Privacy Rule. However, use of these sample provisions is not required for compliance with the Privacy Rule. The language may be amended to more accurately reflect business arrangements between the covered entity and the business associate.

These or similar provisions may be incorporated into an agreement for the provision of services between the entities or they may be incorporated into a separate business associate agreement. These provisions only address concepts and requirements set forth in the Privacy Rule and alone are not sufficient to result in a binding contract under state law. They do not include many formalities and substantive provisions that are required or typically included in a valid contract. Reliance on this sample is not sufficient for compliance with state law and does not replace consultation with a lawyer or negotiations between the parties to the contract.

Furthermore, a covered entity may want to include other provisions that are related to the Privacy Rule but that are not required by the Privacy Rule. For example, a covered entity may want to add provisions in a business associate contract in order for the covered entity to be able to rely on the business associate to help the covered entity meet its obligations under the Privacy Rule. In addition, there may be permissible uses or disclosures by a business associate that are not specifically addressed in these sample provisions, for example having a business associate create a limited data set. These and other types of issues will need to be worked out between the parties.

Sample Business Associate Contract Provisions

Definitions (alternative approaches)

Catch-all definition: Terms used, but not otherwise defined, in this Agreement shall have the same meaning as those terms in the Privacy Rule.

Examples of specific definitions:

a. Business Associate. "Business Associate" shall mean

b. Covered Entity. "Covered Entity" shall mean

c. Individual. "Individual" shall have the same meaning as the term "individual" in 45 CFR § 164.501 and shall include a person who qualifies as a personal representative in accordance with 45 CFR § 164.502(g).

d. Privacy Rule. "Privacy Rule" shall mean the Standards for Privacy of Individually Identifiable Health Information at 45 CFR Part 160 and Part 164, Subparts A and E.

e. Protected Health Information. "Protected Health Information" shall have the same meaning as the term "protected health information" in 45 CFR § 164.501, limited to the information created or received by Business Associate from or on behalf of Covered Entity.

f. Required By Law. "Required By Law" shall have the same meaning as the term "required by law" in 45 CFR § 164.501.

g. Secretary. "Secretary" shall mean the Secretary of the Department of Health and Human Services or his designee.

Obligations and Activities of Business Associate

a. Business Associate agrees to not use or disclose Protected Health Information other than as permitted or required by the Agreement or as Required By Law.

b. Business Associate agrees to use appropriate safeguards to prevent use or disclosure of the Protected Health Information other than as provided for by this Agreement.

c. Business Associate agrees to mitigate, to the extent practicable, any harmful effect that is known to Business Associate of a use or disclosure of Protected Health Information by Business Associate in violation of the requirements of this Agreement. This provision may be included if it is appropriate for the Covered Entity to pass on its duty to mitigate damages to a Business Associate.

d. Business Associate agrees to report to Covered Entity any use or disclosure of the Protected Health Information not provided for by this Agreement of which it becomes aware.

e. Business Associate agrees to ensure that any agent, including a subcontractor, to whom it provides Protected Health Information received from, or created or received by Business Associate on behalf of Covered Entity agrees to the same restrictions and conditions that apply through this Agreement to Business Associate with respect to such information.

f. Business Associate agrees to provide access, at the request of Covered Entity, and in the time and manner , to Protected Health Information in a Designated Record Set, to Covered Entity or, as directed by Covered Entity, to an Individual in order to meet the requirements under 45 CFR § 164.524. [Not necessary if business associate does not have protected health information in a designated record set.]

g. Business Associate agrees to make any amendment(s) to Protected Health Information in a Designated Record Set that the Covered Entity directs or agrees to pursuant to 45 CFR § 164.526 at the request of Covered Entity or an Individual, and in the time and manner . [Not necessary if business associate does not have protected health information in a designated record set.]

h. Business Associate agrees to make internal practices, books, and records, including policies and procedures and Protected Health Information, relating to the use and disclosure of Protected Health Information received from, or created or received by Business Associate on behalf of, Covered Entity available to the Covered Entity, or to the Secretary, in a time and manner or designated by the Secretary, for purposes of the Secretary determining Covered Entity's compliance with the Privacy Rule.

i. Business Associate agrees to document such disclosures of Protected Health Information and information related to such disclosures as would be required for Covered Entity to respond to a request by an Individual for an accounting of disclosures of Protected Health Information in accordance with 45 CFR § 164.528.

j. Business Associate agrees to provide to Covered Entity or an Individual, in time and manner , information collected in accordance with Section of this Agreement, to permit Covered Entity to respond to a request by an Individual for an accounting of disclosures of Protected Health Information in accordance with 45 CFR § 164.528.

Permitted Uses and Disclosures by Business Associate

General Use and Disclosure Provisions [(a) and (b) are alternative approaches]

a. Specify purposes:

Except as otherwise limited in this Agreement, Business Associate may use or disclose Protected Health Information on behalf of, or to provide services to, Covered Entity for the following purposes, if such use or disclosure of Protected Health Information would not violate the Privacy Rule if done by Covered Entity or the minimum necessary policies and procedures of the Covered Entity:

b. Refer to underlying services agreement:

Except as otherwise limited in this Agreement, Business Associate may use or disclose Protected Health Information to perform functions, activities, or services for, or on behalf of, Covered Entity as specified in , provided that such use or disclosure would not violate the Privacy Rule if done by Covered Entity or the minimum necessary policies and procedures of the Covered Entity.

Specific Use and Disclosure Provisions [only necessary if parties wish to allow Business Associate to engage in such activities]

a. Except as otherwise limited in this Agreement, Business Associate may use Protected Health Information for the proper management and administration of the Business Associate or to carry out the legal responsibilities of the Business Associate.

b. Except as otherwise limited in this Agreement, Business Associate may disclose Protected Health Information for the proper management and administration of the Business Associate, provided that disclosures are Required By Law, or Business Associate obtains reasonable assurances from the person to whom the information is disclosed that it will remain confidential and used or further disclosed only as Required By Law or for the purpose for which it was disclosed to the person, and the person notifies the Business Associate of any instances of which it is aware in which the confidentiality of the information has been breached.

c. Except as otherwise limited in this Agreement, Business Associate may use Protected Health Information to provide Data Aggregation services to Covered Entity as permitted by 45 CFR § 164.504(e)(2)(i)(B).

d. Business Associate may use Protected Health Information to report violations of law to appropriate Federal and State authorities, consistent with § 164.502(j)(1).

Obligations of Covered Entity

Provisions for Covered Entity to Inform Business Associate of Privacy Practices and Restrictions [provisions dependent on business arrangement]

a. Covered Entity shall notify Business Associate of any limitation(s) in its notice of privacy practices of Covered Entity in accordance with 45 CFR § 164.520, to the extent that such limitation may affect Business Associate's use or disclosure of Protected Health Information.

b. Covered Entity shall notify Business Associate of any changes in, or revocation of, permission by Individual to use or disclose Protected Health Information, to the extent that such changes may affect Business Associate's use or disclosure of Protected Health Information.

c. Covered Entity shall notify Business Associate of any restriction to the use or disclosure of Protected Health Information that Covered Entity has agreed to in accordance with 45 CFR § 164.522, to the extent that such restriction may affect Business Associate's use or disclosure of Protected Health Information.

Permissible Requests by Covered Entity

Covered Entity shall not request Business Associate to use or disclose Protected Health Information in any manner that would not be permissible under the Privacy Rule if done by Covered Entity. [Include an exception if the Business Associate will use or disclose protected health information for, and the contract includes provisions for, data aggregation or management and administrative activities of Business Associate].

Term and Termination

a. Term. The Term of this Agreement shall be effective as of , and shall terminate when all of the Protected Health Information provided by Covered Entity to Business Associate, or created or received by Business Associate on behalf of Covered Entity, is destroyed or returned to Covered Entity, or, if it is infeasible to return or destroy Protected Health Information, protections are extended to such information, in accordance with the termination provisions in this Section. [Term may differ.]

b. Termination for Cause. Upon Covered Entity's knowledge of a material breach by Business Associate, Covered Entity shall either:

1. Provide an opportunity for Business Associate to cure the breach or end the violation and terminate this Agreement [and the ______ Agreement/ sections ______ of the ______ Agreement] if Business Associate does not cure the breach or end the violation within the time specified by Covered Entity;

2. Immediately terminate this Agreement [and the ______ Agreement/ sections ______ of the ______ Agreement] if Business Associate has breached a material term of this Agreement and cure is not possible; or

3. If neither termination nor cure are feasible, Covered Entity shall report the violation to the Secretary.

[Bracketed language in this provision may be necessary if there is an underlying services agreement. Also, opportunity to cure is permitted, but not required by the Privacy Rule.]

c. Effect of Termination.

1. Except as provided in paragraph (2) of this section, upon termination of this Agreement, for any reason, Business Associate shall return or destroy all Protected Health Information received from Covered Entity, or created or received by Business Associate on behalf of Covered Entity. This provision shall apply to Protected Health Information that is in the possession of subcontractors or agents of Business Associate. Business Associate shall retain no copies of the Protected Health Information.

2. In the event that Business Associate determines that returning or destroying the Protected Health Information is infeasible, Business Associate shall provide to Covered Entity notification of the conditions that make return or destruction infeasible. Upon that return or destruction of Protected Health Information is infeasible, Business Associate shall extend the protections of this Agreement to such Protected Health Information and limit further uses and disclosures of such Protected Health Information to those purposes that make the return or destruction infeasible, for so long as Business Associate maintains such Protected Health Information.

Miscellaneous

a. Regulatory References. A reference in this Agreement to a section in the Privacy Rule means the section as in effect or as amended.

b. Amendment. The Parties agree to take such action as is necessary to amend this Agreement from time to time as is necessary for Covered Entity to comply with the requirements of the Privacy Rule and the Health Insurance Portability and Accountability Act of 1996, Pub. L. No. 104-191.

c. Survival. The respective rights and obligations of Business Associate under Section of this Agreement shall survive the termination of this Agreement.

d. Interpretation. Any ambiguity in this Agreement shall be resolved to permit Covered Entity to comply with the Privacy Rule.

Business Associate Signature

Covered Entity Signature

Enter text✕

What the HIPAA Business Partner Contract Is and When It Applies

A HIPAA Business Partner Contract (commonly called a Business Associate Agreement or BAA) is a written agreement between a HIPAA-covered entity and a business associate that will create, receive, maintain, or transmit protected health information (PHI) on behalf of the covered entity. The BAA defines permitted uses and disclosures of PHI, requires implementation of administrative, physical, and technical safeguards, addresses breach notification, and sets responsibilities for subcontractors and return or destruction of PHI at termination. A properly executed BAA helps satisfy HIPAA regulatory requirements and documents each party's compliance obligations.

Why a Clear, Enforceable BAA Matters

A written BAA is required by HIPAA when a vendor handles PHI; it allocates risk, mandates safeguards, and establishes breach reporting timelines to meet federal obligations.

Why a Clear, Enforceable BAA Matters

Who Typically Signs a HIPAA Business Partner Contract

Covered entities and their third-party vendors use BAAs to formalize PHI handling obligations and controls before any PHI exchange.

  • Hospitals and Clinics – Health systems and independent practices engaging vendors for billing, cloud storage, or analytics.
  • Health IT and Cloud Vendors – SaaS providers storing or processing PHI on behalf of covered entities.
  • Legal and Billing Firms – Third-party administrators, accountants, and counsel with access to patient information.

Complete and sign the BAA before giving a vendor access to PHI; update it when scope or vendors change.

Signing Authorities for a BAA

HIPAA Officer

Privacy or security officer at the covered entity who ensures the BAA maps to organizational policies, confirms safeguards meet HIPAA, and signs on behalf of the entity when authorized by corporate governance.

Vendor Executive

An authorized representative (CEO, CIO, or delegated contracting officer) from the business associate who accepts responsibilities, confirms technical controls, and signs to bind the vendor to contractual obligations.

Essential Clauses Every Professional HIPAA Business Partner Contract Should Include

A compliant BAA is concise but comprehensive. It should define PHI scope, list permitted uses, require safeguards, govern subcontractors, mandate breach notifications, and establish termination and return/destruction obligations.

Definitions

Clear definitions of 'Protected Health Information', 'Covered Entity', 'Business Associate', and any role-specific terminology to avoid scope ambiguity and support enforceability.

Permitted Uses

Explicitly state permitted uses and disclosures of PHI (e.g., treatment, payment, operations) and prohibit any unauthorized secondary uses such as marketing or sale of PHI.

Safeguards

Require administrative, physical, and technical safeguards aligned with the HIPAA Security Rule, including access controls, encryption where appropriate, and incident response procedures.

Subcontractors

Obligate the business associate to flow down BAA terms to subcontractors who create, receive, or access PHI and to maintain written agreements with those subcontractors.

Breach Notification

Specify prompt notification obligations for breaches of unsecured PHI, timelines for notification to the covered entity, and cooperation with required HHS notifications.

Termination & Return

Set termination rights for material breaches, procedures for return or secure destruction of PHI on termination, and conditions where limited retention is permitted for legal reasons.

Required Data Elements and Contract Fields

Party Names: Full legal names
Effective Date: MM/DD/YYYY
Scope of PHI: PHI categories listed
Permitted Uses: Allowed purposes
Breach Terms: Notification process
Subcontractor Rules: Flow-down requirement

Main Risks if the BAA Is Incorrect or Missing

Regulatory Penalties: Civil fines and corrective action
Civil Liability: Contractual damages and indemnity
Breach Costs: Notification and remediation expenses
Operational Disruption: Service interruptions and audits
Reputational Harm: Loss of trust and business
Termination: Contract cancellation risk

Common Mistakes to Avoid When Preparing a BAA

  • Using a generic vendor contract that lacks HIPAA-specific breach notification and PHI handling terms.
  • Failing to define permitted uses clearly, which can result in unauthorized PHI disclosures or compliance gaps.
  • Not requiring subcontractor flow-down; vendors often rely on subcontractors who also need BAA protections.
  • Skipping technical safeguards such as encryption or multifactor authentication where PHI is stored or transmitted.

Step-by-Step: How to Complete a HIPAA Business Partner Contract

Follow a consistent sequence to draft, review, and execute the BAA so both legal and technical requirements are addressed before PHI exchange.

  • 01
    Identify Parties: Record full legal entity names and contacts.
  • 02
    Define PHI Scope: List PHI types and permitted processing activities.
  • 03
    Specify Safeguards: Add administrative, technical, and physical controls.
  • 04
    Sign and Archive: Obtain authorized signatures and retain executed copy.

Where to Send, File, and Store the Executed BAA

After execution, route signed copies to legal, compliance, and IT security teams and ensure the document is stored where it can be retrieved during audits or incident response.

  • Legal Repository: Central contract management storage.
  • Compliance Team: Store with HIPAA policies.
  • IT Security: Record technical controls and attestation.
  • Vendor Folder: Keep accessible vendor agreement copy.

Key Timelines and Notification Expectations

Observe statutory and contractual deadlines for breach notifications, regular reviews, and retention to remain compliant with HIPAA and related obligations.

Effective Date:

Date BAA starts (MM/DD/YYYY)

Annual Review:

Review security controls yearly

Breach Notification:

Notify promptly; HHS notifications within 60 days (45 CFR §164.408)

Subcontractor Updates:

Update flow-down terms when subcontractors change

Termination Actions:

Return or destroy PHI on termination

Supporting Documents and Export Options

Include supporting schedules and preserve signed BAAs in secure, auditable formats; choose formats that maintain an audit trail and are easy to retrieve for compliance.

Supporting Schedule

Include an exhibit listing PHI categories, systems in scope, and processing activities; attach technical safeguards and contact lists for incident response.

Signed PDF

Save the fully executed document as an audit-ready PDF with timestamped audit trail metadata to preserve signature attribution and integrity.

Export Formats

Retain copies in PDF and DOCX; keep the original signed PDF (ISO-compatible) for legal admissibility and rapid retrieval.

Access Logs

Keep system access logs and encryption key management records alongside the BAA for audit purposes and breach investigations.

Practical Tips for Accurate, Efficient BAA Completion

Use a consistent, organization-wide BAA template and involve legal, compliance, and IT early to reduce rework and close onboarding faster.

Use a Standard Template
Maintain a vetted BAA template to reduce negotiation cycles and ensure required HIPAA clauses are always present.
Involve IT Early
Confirm technical controls and encryption requirements before signing to prevent later noncompliance or remediation costs.
Require Subcontractor Flow-Down
Ensure the vendor commits to cascading BAA terms to subcontractors and provides attestations or copies of subcontracts.
Keep Execution Records
Store the executed BAA with a clear audit trail (signer, timestamp, IP, version) to support audits and investigations.

How Organizations Use a HIPAA Business Partner Contract in Practice

Real organizations use BAAs to enable cloud services, analytics, and outsourced billing while documenting PHI responsibilities and breach response commitments.

Fertility Centers of Illinois

Fertility Centers adopted an e-signed BAA to support remote patient intake and records sharing.

  • The vendor retained audit trails for every signer.
  • The signed BAA, combined with technical controls, helped streamline vendor onboarding and provided documented evidence of HIPAA obligations during operational reviews.

Xerox (NetSuite Integration)

Xerox integrated e-signatures into existing ERP workflows to collect vendor BAAs electronically.

  • The process included API-based storage and audit logs.
  • Centralizing executed BAAs improved retrieval for audits and reduced manual recordkeeping time across legal, compliance, and procurement teams.

eSignature Vendor Comparison for BAAs — pricing and core capabilities

Compare starting prices and key capabilities relevant to HIPAA BAAs. signNow is listed first per the vendor order requirement.

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 Yes Yes Yes Varies
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Frequently Asked Questions About the HIPAA Business Partner Contract

Answers to common legal and practical questions about when a BAA is required, what it must contain, and how to execute and store the agreement.


Need help? Contact support

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