Legal & Governing Documents

Business Associate Agreement

DadOfTheClan Consulting Group, LLC executes a Business Associate Agreement with all healthcare clients whose engagements involve access to or handling of Protected Health Information under HIPAA.


Template Reviewed

March 1, 2026

Governing Regulation

45 C.F.R. Parts 160 & 164

Execution

Upon Client Request

Ready to Execute a BAA?

If you are a covered entity or business associate requiring a signed BAA prior to or as part of your engagement, contact us directly. We will initiate the process and have an executed agreement in place before any PHI is accessed or handled.

Request a BAA →

What a BAA Means for Your Practice

Under the Health Insurance Portability and Accountability Act (HIPAA), covered entities — including healthcare providers, health plans, and healthcare clearinghouses — are required to execute a Business Associate Agreement with any vendor that creates, receives, maintains, or transmits Protected Health Information on their behalf.

As a technology consulting firm providing infrastructure management, monitoring, backup, and support services to healthcare clients, DadOfTheClan may qualify as a Business Associate under HIPAA. A signed BAA ensures both parties understand their obligations, your PHI is handled in compliance with the HIPAA Security and Privacy Rules, and your practice is protected in the event of an audit or incident.

🏥

Covered Entities

Hospitals, clinics, physician practices, dental offices, mental health providers, and any other entity that transmits health information electronically in connection with covered transactions.

🔗

Business Associates

Entities that perform functions or activities on behalf of a covered entity that involve the use or disclosure of PHI — including IT vendors, managed service providers, and cloud service providers.

📋

Subcontractors

Where DadOfTheClan engages subcontractors or infrastructure providers that may have access to PHI, those relationships are governed by equivalent BAA obligations passed down in accordance with the HIPAA Omnibus Rule.

Template Notice

The agreement below is DadOfTheClan's standard BAA template. Executed agreements are completed with the covered entity's legal name, effective date, and authorized signatures. Clients with specific requirements may request modifications prior to execution. Nothing below constitutes a legally binding agreement until signed by both parties.

BUSINESS ASSOCIATE AGREEMENT

Between [Covered Entity Legal Name] and DadOfTheClan Consulting Group, LLC

This Business Associate Agreement ("Agreement") is entered into as of [Effective Date] ("Effective Date") by and between:

[Covered Entity Legal Name], a [entity type] organized under the laws of [state], with its principal place of business at [address] (hereinafter "Covered Entity"); and

DadOfTheClan Consulting Group, LLC, a Michigan limited liability company with its principal place of business at Coldwater, Michigan (hereinafter "Business Associate").

Recitals

Covered Entity is a covered entity as defined under the Health Insurance Portability and Accountability Act of 1996 ("HIPAA") and the regulations promulgated thereunder, including the HIPAA Privacy Rule (45 C.F.R. Part 164, Subparts A and E), the HIPAA Security Rule (45 C.F.R. Part 164, Subparts A and C), and the HIPAA Breach Notification Rule (45 C.F.R. Part 164, Subpart D), as amended by the Health Information Technology for Economic and Clinical Health Act ("HITECH") and the HIPAA Omnibus Rule (collectively, "HIPAA Rules").

Business Associate provides technology consulting, infrastructure management, and related services to Covered Entity pursuant to a separately executed service agreement ("Service Agreement"), which may involve the creation, receipt, maintenance, or transmission of Protected Health Information ("PHI") on behalf of Covered Entity. The parties therefore enter into this Agreement to satisfy the requirements of 45 C.F.R. § 164.504(e).


1. Definitions

Capitalized terms used but not otherwise defined in this Agreement have the meanings assigned to them under the HIPAA Rules. The following definitions apply:

Breach: Has the meaning set forth in 45 C.F.R. § 164.402.
Business Associate: Has the meaning set forth in 45 C.F.R. § 160.103.
Covered Entity: Has the meaning set forth in 45 C.F.R. § 160.103.
Electronic Protected Health Information (ePHI): PHI that is created, received, maintained, or transmitted in electronic form.
Protected Health Information (PHI): Has the meaning set forth in 45 C.F.R. § 160.103, limited to the PHI created, received, maintained, or transmitted by Business Associate on behalf of Covered Entity.
Required By Law: Has the meaning set forth in 45 C.F.R. § 164.103.
Subcontractor: Has the meaning set forth in 45 C.F.R. § 160.103.
Unsecured PHI: Has the meaning set forth in 45 C.F.R. § 164.402.

2. Obligations of Business Associate

2.1 Permitted Uses and Disclosures

Business Associate may use or disclose PHI only as necessary to perform the services described in the Service Agreement, as Required By Law, or 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, except as permitted under Section 2.2.

2.2 Additional Permitted Uses

Business Associate may use PHI for the proper management and administration of Business Associate's operations and to fulfill legal responsibilities of Business Associate, provided that disclosures are Required By Law, or that Business Associate obtains reasonable assurances from the recipient that the PHI will be held confidentially and used or disclosed only as Required By Law or for the purpose for which it was disclosed, and that the recipient will notify Business Associate of any instances of which it is aware in which the confidentiality has been breached.

2.3 Safeguards

Business Associate shall implement and maintain appropriate administrative, physical, and technical safeguards that reasonably and appropriately protect the confidentiality, integrity, and availability of ePHI created, received, maintained, or transmitted on behalf of Covered Entity, in accordance with 45 C.F.R. Part 164, Subpart C (the Security Rule). Business Associate shall document and keep current such safeguards as required by 45 C.F.R. § 164.316.

2.4 Prohibition on Unauthorized Use

Business Associate shall not use or disclose PHI other than as permitted or required by this Agreement or as Required By Law. Business Associate shall not use PHI for marketing purposes, sell PHI, or use or disclose PHI in a manner that constitutes a violation of 42 U.S.C. § 17935.

2.5 Minimum Necessary

Business Associate shall, to the extent practicable, use, disclose, and request only the minimum amount of PHI necessary to accomplish the intended purpose of the use, disclosure, or request, in accordance with 45 C.F.R. § 164.502(b) and 45 C.F.R. § 164.514(d).

2.6 Subcontractors

Business Associate shall ensure that any 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 under this Agreement, in accordance with 45 C.F.R. § 164.504(e)(1)(ii) and 45 C.F.R. § 164.308(b)(2).

2.7 Reporting

Business Associate shall report to Covered Entity, without unreasonable delay and in no event later than ten (10) business days of becoming aware:

Any use or disclosure of PHI not permitted by this Agreement, including Breaches of Unsecured PHI as required by 45 C.F.R. § 164.410;

Any Security Incident of which Business Associate becomes aware, including any successful unauthorized access, use, disclosure, modification, or destruction of ePHI or interference with system operations;

Any use or disclosure of PHI required for Business Associate's proper management and administration or to carry out its legal responsibilities, as applicable.

2.8 Individual Rights

To the extent Business Associate maintains PHI in a Designated Record Set, Business Associate shall make available such PHI to Covered Entity as necessary for Covered Entity to fulfill its obligations under 45 C.F.R. §§ 164.524 (access), 164.526 (amendment), and 164.528 (accounting of disclosures). Business Associate shall respond to such requests within fifteen (15) calendar days of receipt.

2.9 Accounting of Disclosures

Business Associate shall document and make available to Covered Entity information required for Covered Entity to provide an accounting of disclosures of PHI in accordance with 45 C.F.R. § 164.528, and shall maintain such documentation for a minimum of six (6) years from the date of the disclosure or the date it was last in effect, whichever is later.

2.10 Government Access

Business Associate shall make its internal practices, books, and records relating to the use and disclosure of PHI received from or created or received by Business Associate on behalf of Covered Entity available to the Secretary of Health and Human Services for purposes of determining Covered Entity's compliance with the HIPAA Rules, in accordance with 45 C.F.R. § 164.504(e)(2)(ii)(I).

3. Obligations of Covered Entity

3.1 Notice of Privacy Practices

Covered Entity shall notify Business Associate of any limitation(s) in Covered Entity's Notice of Privacy Practices in accordance with 45 C.F.R. § 164.520, to the extent that such limitation may affect Business Associate's use or disclosure of PHI.

3.2 Changes in Authorization

Covered Entity shall notify Business Associate of any changes in, or revocation of, authorization by an Individual to use or disclose PHI, to the extent that such changes may affect Business Associate's use or disclosure of PHI.

3.3 Restrictions

Covered Entity shall notify Business Associate of any restriction on the use or disclosure of PHI that Covered Entity has agreed to in accordance with 45 C.F.R. § 164.522, to the extent that such restriction may affect Business Associate's use or disclosure of PHI.

3.4 Permissible Requests

Covered Entity shall not request Business Associate to use or disclose PHI in any manner that would not be permissible under the HIPAA Rules if done by Covered Entity, except as permitted under Section 2.2 of this Agreement.

4. Term and Termination

4.1 Term

This Agreement is effective as of the Effective Date and shall remain in effect until terminated in accordance with this Section or until the underlying Service Agreement expires or is terminated, whichever occurs first.

4.2 Termination for Cause

Either party may terminate this Agreement immediately upon written notice if the other party has materially breached a material provision of this Agreement and has failed to cure such breach within thirty (30) days of written notice specifying the breach in reasonable detail. Where cure is not possible, the non-breaching party may terminate this Agreement immediately.

4.3 Effect of Termination

Upon termination of this Agreement for any reason, Business Associate shall, at the election of Covered Entity, return or destroy all PHI received from or created or received by Business Associate on behalf of Covered Entity that Business Associate still maintains in any form, and shall retain no copies of such PHI. If return or destruction is not feasible, Business Associate shall extend the protections of this Agreement to such PHI and limit further uses and disclosures to those purposes that make return or destruction infeasible, for so long as Business Associate maintains such PHI.

4.4 Survival

The obligations of Business Associate under Section 4.3 and any obligations arising from a Breach discovered prior to termination shall survive termination of this Agreement.

5. Miscellaneous

5.1 Regulatory References

A reference in this Agreement to a section in the HIPAA Rules means the section as in effect or as amended at the time the obligation is performed or the reference is applied.

5.2 Amendment

The parties agree to take such action as is necessary to amend this Agreement from time to time to comply with the requirements of the HIPAA Rules and other applicable law. No amendment to this Agreement shall be valid unless made in writing and signed by authorized representatives of both parties.

5.3 Interpretation

This Agreement shall be interpreted as broadly as necessary to implement and comply with the HIPAA Rules. Any ambiguity in this Agreement shall be resolved in favor of a meaning that permits Covered Entity to comply with the HIPAA Rules.

5.4 No Third-Party Beneficiaries

Nothing in this Agreement shall confer any rights, remedies, obligations, or liabilities upon any person or entity other than Covered Entity and Business Associate and their respective successors and permitted assigns.

5.5 Governing Law

This Agreement shall be governed by and construed in accordance with federal law, including the HIPAA Rules, and to the extent not preempted by federal law, the laws of the State of Michigan, without regard to conflict of law principles.

5.6 Entire Agreement

This Agreement, together with the Service Agreement, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior agreements, understandings, negotiations, and discussions between the parties relating to such subject matter. In the event of a conflict between this Agreement and the Service Agreement with respect to PHI, this Agreement shall control.


Signatures

The parties have executed this Business Associate Agreement as of the Effective Date first written above.

Covered Entity

Authorized Signature

Printed Name: ___________________________

Title: ___________________________

Organization: ___________________________

Date: ___________________________

Business Associate

Authorized Signature

Printed Name: Caleb Lopez

Title: Founder & Managing Member

Organization: DadOfTheClan Consulting Group, LLC

Date: ___________________________

Disclaimer

This template is provided for informational purposes and represents DadOfTheClan's standard starting position for BAA negotiations. It does not constitute legal advice. The template has not been reviewed by legal counsel and should be reviewed by qualified healthcare counsel prior to execution. Covered entities with specific regulatory requirements, state law obligations, or non-standard PHI handling arrangements should request modifications before signing. Nothing on this page constitutes a legally binding agreement until executed in writing by authorized representatives of both parties.