Key Takeaways
- HIPAA does not provide an official certification for AI tools.
- A BAA is generally required when a vendor acts as a business associate and handles PHI on your behalf.
- A BAA does not replace security controls, staff training, or your clinic's risk analysis.
- Every service that handles PHI within an AI workflow must be assessed for appropriate contractual coverage.
- Clinics should verify the exact product, plan, data retention rules, and security measures before implementation.
What Does HIPAA-Compliant AI Mean?
HIPAA-compliant AI refers to an AI tool used in a setup that follows applicable HIPAA requirements for protecting protected health information (PHI). Compliance depends on the product, how it is configured, the agreements in place, and how your team uses it.
Three key areas to review include
- Contracts: Verify that the vendor will sign a Business Associate Agreement (BAA) when required and that the agreement covers the specific product your clinic intends to use.
- Security: Evaluate access controls, encryption, audit logs, and data retention settings.
- Staff practices: Set clear guidelines for entering patient information and reviewing AI-generated content.
A vendor's marketing claims alone do not guarantee that your clinic's use of an AI tool complies with HIPAA.
What Is a BAA, and When Does Your Clinic Need One?
A Business Associate Agreement (BAA) is a written contract that defines how a business associate can use and protect PHI. A clinic generally needs a BAA in place before a vendor creates, receives, maintains, or transmits PHI on its behalf, unless an applicable exception applies.
AI tools that may process PHI include:
- AI medical scribes that handle appointment recordings.
- Chatbots that review messages from patients.
- Billing tools that process insurance claims.
- Voice agents that manage appointment requests.
Review the entire data flow, rather than focusing only on the primary vendor. If a service shares PHI with a cloud hosting provider or speech-processing service, those subcontractors may also require appropriate contractual coverage.
Review the HHS sample BAA provisions to understand common contractual requirements.
What Does a BAA Cover?
A BAA defines the permitted uses of PHI, the vendor's responsibilities, and the procedures for handling certain incidents and ending the business relationship.
Review whether the agreement addresses:
- Permitted uses and disclosures of PHI.
- Required safeguards and security responsibilities.
- Breach and security incident reporting.
- Subcontractor obligations.
- Return or destruction of PHI when the agreement ends, where applicable.
- Access to relevant records by the Department of Health and Human Services when required.
Do not assume every agreement covers every product or feature. Read the actual terms and confirm the scope with the vendor.
What Does a BAA Not Cover?
A BAA does not automatically secure an AI tool, configure its settings, or remove your clinic's own HIPAA responsibilities. You must still assess risks and ensure the tool is used appropriately.
Common gaps include:
- Incorrect configuration: Security features may be available but not enabled.
- Limited product coverage: The agreement may cover a business or API plan but exclude consumer accounts, add-ons, or beta features.
- Staff mistakes: A BAA with one vendor does not protect PHI entered into an unrelated personal chatbot account.
- AI accuracy: A BAA does not guarantee correct clinical notes, billing codes, or patient messages. Appropriate human review remains important.
- Other legal requirements: State privacy laws and certain rules governing substance use disorder records may impose additional obligations.
- Contractual liability: Liability limits and other contract terms can affect your options if an incident occurs.
If you need help identifying where AI could fit into your practice, start with our free AI readiness assessment.
Is a HIPAA-Compliant LLM or Generative AI Tool Compliant by Default?
No. A large language model (LLM) is not automatically HIPAA compliant simply because its provider offers enterprise security features. The specific service, contractual coverage, and safeguards determine whether it can be used appropriately with PHI.
When evaluating a HIPAA-compliant LLM or HIPAA-compliant generative AI tool, check:
- Whether a BAA covers the exact product and plan.
- Whether your data may be used to train or improve models.
- How long prompts, outputs, and uploaded files are retained.
- Whether encryption and role-based access controls are available.
- Whether audit logs are provided.
- How the vendor handles PHI in prompts, outputs, and connected services.
Ask the vendor to confirm these details in writing. If the answers are unclear, do not share patient information until the gaps have been resolved.
What Should Clinics Know About AI Agent Platforms With HIPAA BAA Compliance?
AI agent platforms can connect several services, including language models, phone systems, speech-to-text tools, and databases. Each service that handles PHI must be covered by appropriate agreements and safeguards.
Before choosing an AI agent platform, ask:
- Which companies process patient audio, text, and records?
- Does the contractual coverage extend to every relevant service?
- How long are call recordings and transcripts stored?
- Can unnecessary data storage be disabled?
- What permissions apply when an agent accesses an EHR?
A vendor describing its product as a BAA-compliant AI platform is not enough. Verify the agreement and controls for the complete workflow.
Our guide to connecting AI to your EHR explains considerations for integrating AI with healthcare systems.
What Are the Risks of Using AI With PHI?
The main risks include unauthorized disclosure, inadequate access controls, excessive data retention, and unreviewed AI-generated information. These problems can expose patient information or affect the accuracy of clinical records.
Watch for these issues:
- Sharing data without appropriate coverage: Entering PHI into a tool without the required contractual protections may result in an impermissible disclosure.
- Unclear data use: The vendor may retain prompts or use submitted information in ways your clinic has not approved.
- Weak access controls: Shared accounts and excessive permissions make it harder to track who accessed patient data.
- Unapproved tools: Staff may turn to consumer AI applications if your clinic has no clear approved alternative.
- Incorrect output: AI can generate inaccurate information that becomes harmful if no one checks it.
If a potential incident occurs, stop the affected use, document what happened, and involve your privacy officer or legal counsel to assess the appropriate response. Review the HHS breach notification guidance.
How Should You Evaluate an AI Vendor for HIPAA Compliance?
Ask for the BAA and verify how the vendor handles data, security, subcontractors, and incidents. Do not rely on a general statement that the product is secure or healthcare-ready.
| Area to check | What to look for |
|---|---|
| BAA coverage | The exact product and plan are identified |
| Subcontractors | Relevant providers and contractual protections are documented |
| Model training | Data-use and training policies are clear |
| Data retention | Retention periods and deletion procedures are documented |
| Access and logging | Role-based permissions and audit trails are available |
| Incident response | Reporting responsibilities and timelines are defined |
| Security evidence | Relevant independent audit reports or other supporting evidence are available |
Reports such as SOC 2 can provide useful security evidence, but they are not HIPAA certifications.
You can review our Trust Center for information about our security practices. For help evaluating vendors and planning an appropriate implementation, explore our healthcare AI consulting services.
What Should Your Clinic Do Before Using an AI Tool?
Use this checklist before introducing AI into a workflow that involves PHI.
1. Map the data flow. Identify the information the tool receives, where it goes, and who can access it.
2. Review the BAA. Confirm that the agreement covers the exact product, plan, and relevant services.
3. Update your risk analysis. Assess how the new tool changes risks to electronic PHI under the HIPAA Security Rule. See the HHS Security Rule guidance.
4. Set an AI use policy. Define approved tools, prohibited data sharing, access permissions, and human review requirements. Our guide to an AI governance policy for healthcare can help.
5. Train your staff. Explain which tools are approved and what to do if patient information is shared incorrectly.
6. Start with one workflow. Monitor the results, review access logs, and address problems before expanding.
These steps help your clinic make informed decisions instead of relying solely on a vendor's claims.
How Justin Healthcare AI Can Help
At Justin Healthcare AI, we help clinics evaluate AI opportunities, plan integrations, and consider patient data protection as part of implementation. The right approach starts with understanding your workflows, the information involved, and the safeguards your practice needs.
Ready to explore AI for your clinic?
- Start with our free AI readiness assessment.
- Review our Trust Center.
- Learn more about our healthcare AI consulting services.
Frequently Asked Questions
Is ChatGPT HIPAA compliant?
It depends on the specific product, plan, and contractual arrangement. Do not enter PHI into a consumer AI account unless the service and its terms have been verified for that use. Confirm the applicable BAA and safeguards before sharing patient data.
Does a BAA make an AI tool HIPAA compliant?
No. A BAA establishes contractual responsibilities but does not replace security controls, appropriate configuration, staff training, or your clinic's risk analysis.
Do I need a BAA for an AI scribe or chatbot?
A BAA is generally required when the service acts as a business associate and handles PHI on your clinic's behalf. Our pages on AI scribes for doctors and healthcare AI chatbots explain these use cases.
What makes an AI tool HIPAA compliant?
The full setup must meet applicable HIPAA requirements. This includes appropriate agreements, security safeguards, access controls, data-handling practices, and staff procedures. No single feature or contract guarantees compliance.
Can I use AI with de-identified data without a BAA?
Information properly de-identified under HIPAA's Safe Harbor or Expert Determination methods is no longer PHI under HIPAA. However, removing names alone may not be sufficient. Seek qualified guidance before relying on de-identification for sensitive data.
What happens if staff enter PHI into a tool without a BAA?
The disclosure may violate HIPAA, depending on the circumstances. Stop the affected activity, document the incident, and consult your privacy officer or legal counsel to determine the required assessment and response.


