Business Associate Agreement.
Our standard HIPAA BAA under 45 CFR 164.504(e). It is signed with every practice before any patient data enters MDIntern.
How this agreement works. MDIntern signs this Business Associate Agreement (BAA) with every practice before any patient data is shared with the MDIntern platform. A practice accepts it through the practice onboarding agreements step or a signed copy, and MDIntern countersigns and sends a fully executed copy to the practice. The public MDIntern website does not collect protected health information. To request a signed copy or propose changes, email akim7904@gmail.com.
This Business Associate Agreement (“Agreement”) is entered into by the health care practice that accepts it (“Covered Entity”) and MDIntern AI (“MDIntern” or “Business Associate”). Each is a “Party.” The Agreement takes effect on the earlier of (a) its acceptance by Covered Entity’s authorized representative and (b) the date Business Associate first creates, receives, maintains, or transmits Protected Health Information on behalf of Covered Entity (the “Effective Date”).
Background. Business Associate provides practice management, electronic medical record, AI-assisted documentation, scheduling, front-desk, eligibility, prior authorization, credentialing, billing, and revenue cycle services to Covered Entity under a separate customer agreement (the “Underlying Agreement”). In performing those services, Business Associate may create, receive, maintain, or transmit Protected Health Information. The Parties enter into this Agreement to comply with the Health Insurance Portability and Accountability Act of 1996 (“HIPAA”), the Health Information Technology for Economic and Clinical Health Act (“HITECH Act”), and the regulations at 45 CFR Parts 160 and 164 (the “HIPAA Rules”), including 45 CFR 164.502(e), 164.504(e), 164.308(b), 164.314(a), and 164.410.
1. Definitions
Capitalized terms used but not defined in this Agreement have the meanings given in the HIPAA Rules, including Breach, Data Aggregation, Designated Record Set, Disclosure, Health Care Operations, Individual, Minimum Necessary, Notice of Privacy Practices, Required by Law, Secretary, Security Incident, Subcontractor, Unsecured Protected Health Information, and Use.
- “Protected Health Information” or “PHI” has the meaning in 45 CFR 160.103, limited to information that Business Associate creates, receives, maintains, or transmits on behalf of Covered Entity. “Electronic PHI” or “ePHI” means PHI that is transmitted or maintained in electronic media.
- “Breach” has the meaning in 45 CFR 164.402, including the presumption that an impermissible acquisition, access, Use, or Disclosure is a Breach unless a documented risk assessment shows a low probability that the PHI has been compromised.
- “Security Incident” has the meaning in 45 CFR 164.304.
- “Part 2 Records” means records protected by 42 CFR Part 2 (Confidentiality of Substance Use Disorder Patient Records), as amended by the final rule published February 16, 2024 (89 FR 12472).
- “AI Features” means the components of Business Associate’s services that use machine learning or generative artificial intelligence, such as ambient scribing, note drafting, coding suggestions, and drafting of prior authorization or appeal content.
2. Obligations of Business Associate
- Permitted Uses and Disclosures only. Business Associate will not Use or Disclose PHI other than as permitted or required by this Agreement or as Required by Law. Business Associate will not Use or Disclose PHI in a manner that would violate Subpart E of 45 CFR Part 164 if done by Covered Entity, except as allowed by Sections 3.2 through 3.4.
- Security Rule safeguards. Business Associate will comply with Subpart C of 45 CFR Part 164 (the Security Rule) with respect to ePHI. It will implement administrative, physical, and technical safeguards that reasonably and appropriately protect the confidentiality, integrity, and availability of ePHI, including at least the following:
- an accurate and thorough risk analysis, reviewed at least annually and whenever its environment or operations change materially, and a risk management plan that reduces identified risks to a reasonable and appropriate level (45 CFR 164.308(a)(1));
- encryption of ePHI in transit and at rest, consistent with HHS guidance on rendering PHI unusable, unreadable, or indecipherable to unauthorized persons;
- unique user identification, role-based access controls, multi-factor authentication for access to systems containing ePHI, automatic logoff, and prompt removal of access when it is no longer needed;
- audit controls that record and allow review of activity in systems that contain ePHI;
- a security awareness and training program for its workforce, including phishing awareness, and sanctions for workforce members who violate its policies;
- contingency planning, including data backup, disaster recovery, and emergency-mode operations, with backups that are tested periodically;
- timely patching, malware protection, and vulnerability management; and
- written security policies and procedures, kept for six (6) years as required by 45 CFR 164.316.
- Minimum Necessary. Business Associate will limit its Uses, Disclosures, and requests of PHI to the Minimum Necessary to accomplish the intended purpose, in accordance with 45 CFR 164.502(b) and 164.514(d).
- Reporting. Business Associate will report to Covered Entity, as described in Section 4, any Use or Disclosure of PHI not provided for by this Agreement, any Security Incident, and any Breach of Unsecured PHI of which it becomes aware.
- Mitigation. Business Associate will mitigate, to the extent practicable, any harmful effect known to Business Associate of a Use or Disclosure of PHI in violation of this Agreement.
- Subcontractors. In accordance with 45 CFR 164.502(e)(1)(ii) and 164.308(b)(2), Business Associate will ensure that any Subcontractor that creates, receives, maintains, or transmits PHI on its behalf first agrees in writing to the same restrictions, conditions, and requirements that apply to Business Associate under this Agreement, including implementing safeguards under the Security Rule. Business Associate remains responsible for its Subcontractors’ performance and, on request, will provide Covered Entity with a list of the Subcontractors that have access to PHI.
- Access. To the extent Business Associate maintains PHI in a Designated Record Set, it will, within ten (10) business days after Covered Entity’s request, make the PHI available to Covered Entity, or as Covered Entity directs to an Individual or the Individual’s designee, in the form and format requested if readily producible, including in electronic form, so that Covered Entity can meet its obligations under 45 CFR 164.524. If an Individual asks Business Associate directly for access, Business Associate will forward the request to Covered Entity within five (5) business days.
- Amendment. To the extent Business Associate maintains PHI in a Designated Record Set, it will make any amendments that Covered Entity directs or agrees to under 45 CFR 164.526 within ten (10) business days after the request.
- Accounting of Disclosures. Business Associate will document Disclosures of PHI, and within ten (10) business days after Covered Entity’s request will provide the information Covered Entity needs to respond to a request for an accounting under 45 CFR 164.528.
- Covered Entity’s obligations. To the extent Business Associate carries out any of Covered Entity’s obligations under Subpart E of 45 CFR Part 164, it will comply with the requirements of Subpart E that apply to Covered Entity in performing that obligation.
- Books and records. Business Associate will make its internal practices, books, and records relating to the Use and Disclosure of PHI available to the Secretary of HHS to determine compliance with the HIPAA Rules. Unless the Secretary prohibits it, Business Associate will promptly notify Covered Entity of any such request.
- No sale of PHI or marketing. Business Associate will not sell PHI or receive direct or indirect payment in exchange for PHI (45 CFR 164.502(a)(5)(ii)). It will not Use or Disclose PHI for marketing or fundraising, except as permitted for Covered Entity under the HIPAA Rules and directed by Covered Entity in writing.
- AI Features. Business Associate will Use PHI in AI Features only to provide the services to Covered Entity. Business Associate will not use PHI, or data derived from PHI, to train, fine-tune, or improve artificial intelligence models offered to anyone other than Covered Entity, and will not permit any third-party model provider to do so, unless (i) the data has first been de-identified in accordance with 45 CFR 164.514(a)–(c) and the Underlying Agreement permits it, or (ii) Covered Entity has given prior written authorization. Business Associate will ensure that any third-party AI or model provider that receives PHI is bound as a Subcontractor under Section 2.6, and that such provider does not retain PHI beyond what is necessary to provide the service. AI-generated content is a draft for review by Covered Entity’s clinicians and staff. It is not final until a clinician or authorized staff member approves it.
- Location of PHI. Business Associate will not store, process, or permit access to PHI from outside the United States without Covered Entity’s prior written consent.
- Part 2 Records. If Business Associate receives Part 2 Records, it acknowledges that it is bound by 42 CFR Part 2 to the extent applicable. It will not Use or Disclose such records, or testimony about their content, in any civil, criminal, administrative, or legislative proceeding against the patient, except as permitted by 42 CFR Part 2. It will also keep any notice that accompanies a Disclosure of such records as required by 42 CFR 2.32.
- More stringent law. Where federal or state law gives greater protection to certain information than the HIPAA Rules do, Business Associate will comply with the more stringent law to the extent it applies to Business Associate. Examples include state laws on mental health, HIV, genetic, or reproductive health information.
- Restrictions and confidential communications. Business Associate will comply with any restriction on the Use or Disclosure of PHI, and any request for confidential communications, that Covered Entity has agreed to under 45 CFR 164.522 and communicated to Business Associate in writing. This includes an Individual’s request not to disclose PHI to a health plan about items or services the Individual paid for in full out of pocket.
3. Permitted Uses and Disclosures by Business Associate
- Services. Business Associate may Use and Disclose PHI as necessary to perform the services described in the Underlying Agreement for or on behalf of Covered Entity, consistent with the Minimum Necessary standard.
- Management and administration. Business Associate may Use PHI for its proper management and administration or to carry out its legal responsibilities. It may Disclose PHI for those purposes only if (a) the Disclosure is Required by Law, or (b) Business Associate obtains reasonable written assurances from the recipient that the PHI will be held confidentially, Used or further 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 instance in which the confidentiality of the PHI has been breached (45 CFR 164.504(e)(4)).
- Data Aggregation. Business Associate may use PHI to provide Data Aggregation services relating to the Health Care Operations of Covered Entity (45 CFR 164.504(e)(2)(i)(B)).
- De-identification. Business Associate may de-identify PHI only in accordance with 45 CFR 164.514(a)–(c), and only as needed to provide the services or as permitted by Section 2.13 and the Underlying Agreement.
- Reporting violations of law. Business Associate may Use PHI to report violations of law to appropriate federal and state authorities, consistent with 45 CFR 164.502(j)(1).
4. Reporting of Security Incidents and Breaches
- Discovery. A Breach is treated as discovered on the first day it is known to Business Associate, or by exercising reasonable diligence would have been known, to any person other than the person committing it who is a workforce member or agent of Business Associate (45 CFR 164.410(a)(2)).
- Timing. Business Associate will notify Covered Entity of any Breach of Unsecured PHI, and of any Use or Disclosure not permitted by this Agreement, without unreasonable delay. Notice will be given no later than five (5) business days after discovery, which is well within the sixty (60) calendar-day outer limit of 45 CFR 164.410(b). Business Associate will notify Covered Entity of any successful Security Incident within five (5) business days after discovery, and sooner if the incident disrupts the services or the availability of ePHI.
- Content. The notice will include, to the extent known, and will be supplemented as more information becomes available: the identity of each Individual whose Unsecured PHI has been, or is reasonably believed to have been, accessed, acquired, Used, or Disclosed; a description of what happened, including the date of the Breach and the date of discovery; the types of PHI involved; the steps Individuals should take to protect themselves; what Business Associate is doing to investigate, mitigate harm, and protect against further Breaches; and contact information for questions (45 CFR 164.410(c) and 164.404(c)). Business Associate will provide any other information Covered Entity reasonably requests to perform its risk assessment and meet its notification obligations.
- Unsuccessful Security Incidents. The Parties agree that this Section serves as notice, and no further notice is required, of the ongoing existence of unsuccessful Security Incidents that do not result in unauthorized access, Use, Disclosure, modification, or destruction of ePHI or interference with system operations. Examples include pings, port scans, blocked log-in attempts, and denial-of-service attempts that do not succeed.
- Notifications to Individuals and regulators. Covered Entity will decide whether notification to Individuals, the Secretary, the media, or state regulators is required, and how it is given. If a Breach results from Business Associate’s failure to comply with this Agreement or the HIPAA Rules, Business Associate will, at Covered Entity’s option, either provide the notifications on Covered Entity’s behalf, in a form Covered Entity approves, or reimburse Covered Entity’s reasonable costs of notification and of credit or identity monitoring where appropriate. Business Associate will also cooperate with Covered Entity’s obligations under applicable state breach notification laws, including A.R.S. § 18-552.
- Law enforcement delay. If a law enforcement official tells Business Associate that a notification would impede a criminal investigation or damage national security, Business Associate may delay notification as permitted by 45 CFR 164.412 and will document the request.
- Cooperation. Business Associate will cooperate in good faith with Covered Entity’s investigation of any Security Incident or Breach, and will keep documentation of its own investigation and risk assessment for six (6) years.
5. Obligations of Covered Entity
- Covered Entity will notify Business Associate of any limitation in its Notice of Privacy Practices under 45 CFR 164.520, of any change in or revocation of an Individual’s permission to Use or Disclose PHI, and of any restriction it has agreed to under 45 CFR 164.522, to the extent the limitation, change, or restriction may affect Business Associate’s Use or Disclosure of PHI.
- Covered Entity will not ask Business Associate to Use or Disclose PHI in any manner that would not be permissible under Subpart E of 45 CFR Part 164 if done by Covered Entity, except as permitted by Sections 3.2 through 3.4.
- Covered Entity will provide only the Minimum Necessary PHI and will use the security features Business Associate makes available, such as multi-factor authentication and role-based access, for its own workforce users.
- Covered Entity is responsible for obtaining any patient consents or authorizations that its own policies or applicable state law require, including any notice or consent for ambient recording by the AI scribe that state law requires.
6. Term and Termination
- Term. This Agreement begins on the Effective Date and continues until all PHI has been returned or destroyed under Section 6.4, or until protections have been extended under that Section.
- Termination for cause. If either Party knows of a pattern of activity or practice of the other Party that is a material breach or violation of this Agreement, the non-breaching Party will give written notice and allow thirty (30) days to cure. If the breach is not cured, the non-breaching Party may terminate this Agreement and the affected parts of the Underlying Agreement. Covered Entity may terminate immediately if cure is not possible (45 CFR 164.504(e)(1)(ii) and (e)(2)(iii)).
- Termination of the Underlying Agreement. This Agreement ends automatically when the Underlying Agreement ends, subject to Section 6.4.
- Return or destruction of PHI. When this Agreement ends, Business Associate will, at Covered Entity’s direction and within thirty (30) days, return to Covered Entity (in a commonly used electronic format, together with a reasonable data export) or securely destroy all PHI that it or its Subcontractors maintain in any form, and will keep no copies. Destruction will follow NIST SP 800-88 media sanitization guidelines, and Business Associate will certify the destruction in writing on request. If returning or destroying PHI is not feasible, for example because of legal hold or retention requirements, Business Associate will notify Covered Entity of the reasons. It will then extend the protections of this Agreement to that PHI and limit further Uses and Disclosures to the purposes that make return or destruction infeasible, for as long as it keeps the PHI.
- Survival. Business Associate’s obligations under Sections 2, 4, and 6.4 survive termination for as long as Business Associate or its Subcontractors keep any PHI.
7. Miscellaneous
- Regulatory references. A reference to a section of the HIPAA Rules or 42 CFR Part 2 means that section as in effect or as amended, with any compliance date that applies.
- Amendment for changes in law. The Parties will amend this Agreement as needed to comply with changes to HIPAA, the HITECH Act, the HIPAA Rules, 42 CFR Part 2, or other applicable law. This includes any final rule that modifies the HIPAA Security Rule or Privacy Rule. Business Associate will comply with any such change by its compliance date, even before this Agreement is formally amended.
- Interpretation. Any ambiguity in this Agreement will be resolved to permit compliance with the HIPAA Rules. If this Agreement conflicts with the Underlying Agreement on the protection of PHI, this Agreement controls.
- Independent contractor. Business Associate is an independent contractor and is not an agent of Covered Entity for any purpose, including under the federal common law of agency.
- Direct liability. Business Associate acknowledges that it is directly liable under the HIPAA Rules for its own compliance with the Security Rule, the applicable provisions of the Privacy Rule, and the Breach Notification Rule, as provided by the HITECH Act (42 U.S.C. 17931 and 17934) and 45 CFR 160.402.
- No third-party beneficiaries. Nothing in this Agreement gives any person other than the Parties and their permitted successors any rights, remedies, or obligations.
- Injunctive relief. Each Party agrees that an improper Use or Disclosure of PHI may cause irreparable harm. The affected Party may therefore seek injunctive relief in addition to any other remedy.
- Governing law. This Agreement is governed by applicable federal law and, to the extent not preempted, the laws of the State of Arizona.
- Notices. Notices under this Agreement must be in writing. They are effective when sent by email with confirmation of delivery, or when delivered by a nationally recognized courier. Notices to Business Associate go to akim7904@gmail.com. Notices to Covered Entity go to the primary contact and authorized signer named in its onboarding submission, or to any other contact that a Party designates in writing.
- Entire agreement; counterparts; electronic signatures. This Agreement, together with the Underlying Agreement, is the Parties’ entire agreement on its subject. It may be signed in counterparts and accepted electronically, and electronic signatures are binding to the same extent as handwritten signatures.
Signatures
Covered Entity
Practice legal name: ______________________
By (signature): ______________________
Name and title: ______________________
Date: ______________________
Business Associate: MDIntern AI
By (signature): ______________________
Name and title: ______________________
Date: ______________________
This page is MDIntern’s standard Business Associate Agreement. A practice may accept it through the agreements step of practice onboarding. MDIntern then countersigns and delivers a fully executed copy before any patient data is shared.