A business associate agreement (BAA) is the contract or other written arrangement in which a vendor assures a practice it will safeguard patient information, which HIPAA expects before the vendor handles it1. Each of these five vendors offers one. They differ in how you enter it, which AI services they name as covered, and what they say happens to your data afterward. We rank none of them.
What we read, and what this page cannot tell you
We read each vendor's own pages on November 11, 2026. Every statement below comes from those pages or from our checked evidence, and vendors change these pages often, so confirm the current wording before you rely on it.
Microsoft Azure, Amazon Web Services (AWS) and Google Cloud are platforms you build on. OhMD and Zoho are applications, so the question for them is whether their AI features sit inside the agreement. HHS's cloud guidance says that a covered entity that uses a cloud provider to maintain electronic protected health information (ePHI) without a BAA is in violation of the HIPAA Rules2. We are not lawyers. Read the rule and the agreement yourself, or ask your counsel how they apply to you.
How each BAA is entered and what it costs
Table 1. How each vendor's BAA is entered, as the vendor publishes it
| Vendor | How it is entered | Fee | Text of the agreement |
|---|---|---|---|
| Microsoft | Inside its Data Protection Addendum; no separate contract to sign3,4 | NF | Word file our checker could not confirm; BAA text NF |
| AWS | Click-through in AWS Artifact, after an NDA5,6 | Free of charge7 | Behind the Artifact NDA; not read6 |
| Google Cloud | Opt in within one project of the account8 | None stated; same pricing as other customers9 | Public on Google's site10 |
| OhMD | Automatic for every user at first use11 | Included in every plan, OhMD says12 | Public template, covered entity and date blank13 |
| Zoho | Request the template by email14 | NF | No public text found; names specific services14 |
Each route carries a condition. Microsoft offers its BAA by default to customers that are covered entities or business associates3, as part of the Product Terms (formerly Online Services Terms) for in-scope Azure services3. AWS applies its BAA only to HIPAA Accounts, which are accounts that keep PHI only in HIPAA Eligible Services and carry the security configurations the BAA requires6. AWS lists designating an account for HIPAA as unavailable under its new sign-up and available under Sign up for AWS (advanced)15.
The Microsoft row has two gaps. The addendum is a Word file that our checker could not confirm. The agreement's own text, and the list of services it covers in Appendices A and B of another document16, sit on Microsoft's Service Trust Portal. We opened the agreement's address on November 11, 2026, it asked for a Microsoft customer sign-in, and we did not sign in.
Which AI services each names as covered and as outside
Coverage is by named service, and the lists differ in how public they are. AWS and Google publish theirs9,17. Microsoft's Azure page sends the reader to a separate audit-scope document and lists no services itself3. OhMD and Zoho publish no list of AI features.
Table 2. AI services each vendor names as covered or outside the agreement, and what we did not find
| Vendor | Named as covered | Named as outside or limited | Not found |
|---|---|---|---|
| Microsoft | Copilot Studio18; Microsoft Copilot and Copilot Chat4 | Copilot web search queries19; Grounding with Bing Search20; other providers' models21 | Azure OpenAI named with the BAA on a public page4 |
| AWS | Amazon Bedrock and AgentCore17; Q Business17 | Unlisted services that hold ePHI17; betas and previews22; SageMaker AI exclusions17 | Marketplace models inside or outside the BAA23 |
| Google Cloud | On its public list, dated November 11, 2026: Gemini Enterprise Agent Platform, Gemini Enterprise, Gemini Code Assist, Conversational Agents, Speech-to-Text, Document AI9 | Pre-GA offerings with PHI9; Separate Offerings and Third-Party AI Agents24 | The Vertex AI name, except one line for Vertex AI Workbench instances |
| OhMD | Every channel in its table, which has a Voice AI row11 | None named | An AI feature named in the BAA text13 |
| Zoho | NF; its HIPAA table lists services with HIPAA features, not the BAA scope14 | Models for marked, encrypted health fields25; third-party apps14 | Zia named in the BAA14 |
Names matter. Microsoft's Foundry Tools page (Foundry Tools was formerly Azure AI Services) lists HIPAA BAA among the awards for the product family and names Azure OpenAI as one of the tools, an umbrella statement and not a service list26. A list line for Amazon Q Developer or for the Amazon Nova models is NF; the nearest lines are Amazon Q Business and Amazon Nova Act17. Google's BAA does not apply to any product, service or feature that is not a Covered Service10. We read its list ourselves on November 11, 2026: it has lines for Gemini Enterprise Agent Platform, Generative AI on Agent Platform, Gemini Enterprise, Gemini Code Assist, Conversational Agents, Speech-to-Text, Text-to-Speech, Document AI and Cloud Healthcare API. A reader who knows the service as Vertex AI should look for the current names.
Three kinds of feature recur on the outside. Previews: Google bars pre-GA offerings with PHI unless their terms say otherwise, AWS says betas should not process sensitive data, and Microsoft says previews may follow different privacy practices, including abuse monitoring9,22,27. Web search and grounding: Microsoft says Grounding with Bing Search sends customer data outside the Azure compliance boundary20. Other providers' models: Microsoft calls them Non-Microsoft Products under the provider's terms, and AWS lists third-party models as Third-Party Content under the applicable terms21,22.
Retention, monitoring and training
Retention is where the five differ most.
Table 3. What each vendor says about training, retention and where processing happens
| Vendor | Training on your data | Retention and monitoring | Where processing goes |
|---|---|---|---|
| Microsoft | Not without your permission or instruction27 | Automated abuse monitoring by default, human review as necessary27; retention period in days NF27 | Your geography, unless a Global or DataZone deployment27 |
| AWS | Bedrock inputs and outputs not used to train, AWS says28 | Depends on the model; up to 30 days for some29,30 | Geographic profiles stay in a geography; global profiles range worldwide31,32 |
| Google Cloud | Not without prior permission or instruction33 | Cache within 24 hours; grounding logs 3 and 30 days; partner-model abuse logs up to 30 days33 | Abuse logs in the us multi-region33 |
| OhMD | NF | Every AI interaction kept for review; no period given34 | Hosted on AWS in the US11 |
| Zoho | Differs by product page35,36 | Models suggestions not stored once copied25 | Zia LLM on Zoho servers; an admin may enable outside models25,37 |
Microsoft Azure and Microsoft Copilot
Microsoft says the customer is responsible for its own compliance program and for aligning its use of Azure with HIPAA3. Its Learn pages name Copilot Studio, Microsoft Copilot and Copilot Chat, Microsoft Copilot for Security and Healthcare Bot Service as in scope4,18. Azure OpenAI named with the BAA is NF on any page we read; the nearest statement is that Foundry is an Azure service and that the addendum governs data processing by Models sold by Azure27. Turning off Microsoft's abuse monitoring is open only to customers managed by a Microsoft account team or under an eligible program, with additional requirements38. For Claude in Foundry, Microsoft says Anthropic is the seller and operator and an independent data processor, and that page does not mention HIPAA or a BAA39.
Two Microsoft pages differ in age. The Azure page that says no separate contract is needed carries a 2023 date, updated in October 20243, while the Office 365 page was updated September 11, 2026 and still uses the older name, Online Services Data Protection Addendum4.
Amazon Web Services and Amazon Bedrock
AWS calls its agreement the Business Associate Addendum, while its Eligible Services page says business associate agreement5,17. The HIPAA Eligible Services Reference, last updated October 15, 2026, lists Amazon Bedrock with no exclusion note17.
On Bedrock, retention depends on the model. AWS says that under its default setting actual retention depends on the model29 and that most models do not currently require human review29. For Anthropic's Claude Fable 5, 5.1 and 5.2 models AWS retains all traffic for up to 30 days for automated abuse detection, says flagged traffic may be reviewed by humans at AWS, and requires you to set the retention mode aws_review before you can invoke them29,30. A zero-retention mode exists for models that allow it29. Whether the 30-day retention fits inside the BAA is NF; the nearest statement is that retained inputs and outputs are stored and processed by AWS and not shared with third-party model providers30. Model invocation logging is off by default, and once on it can collect full request and response data40.
A default worth a warning sits in the Service Terms. AWS may use and store content processed by several AI services, among them Amazon Comprehend, Lex, Polly, Textract and Transcribe, to develop and improve them, unless you configure an AI services opt-out policy in AWS Organizations22. Comprehend Medical, Transcribe Medical and HealthScribe are excluded, and Amazon Bedrock is not in the list22. Comprehend, Lex, Polly, Textract and Transcribe are also lines on the HIPAA Eligible Services Reference17. How that use sits beside the BAA is a question for the agreement text, which we did not read.
Google Cloud and Gemini Enterprise Agent Platform
Google says it offers HIPAA-regulated customers the same services at the same pricing as everyone else9. Its supported-services page, last updated November 11, 2026, says the BAA includes Google Cloud's entire infrastructure9. The BAA itself says it does not apply to any product, service or feature that is not a Covered Service10, so check the list by product name.
Google says it will not use Customer Data to train or fine-tune AI or ML models without prior permission or instruction, and that this covers all managed models on Gemini Enterprise Agent Platform33. Its prompt cache is evicted within 24 hours, Grounding with Google Search logs are kept for up to three days, and Grounding with Google Maps stores prompts, context and output for 30 days33. A customer under a BAA is told not to opt in to Speech-to-Text data logging, and not to put PHI in Conversational Agents definitions or in resource metadata9.
OhMD
OhMD says it gives every user an automatic BAA that covers texting, voice, video, forms, file sharing and care coordination11. Its channel table has a Voice AI row, and the page says every channel listed is covered11. We infer that voice AI is covered; no sentence says so directly. The published BAA is a template that leaves the covered entity and date blank, and it never mentions AI13. OhMD's voice AI agent, Nia, is built on Twilio's ConversationRelay41. A statement on training, a retention period for AI audio or transcripts, the language model and a subprocessor list are NF; the nearest statement is that OhMD keeps every AI interaction for review34.
The BAA lets OhMD create de-identified information, which is then outside the agreement13, and OhMD's Terms of Use, dated April 23, 2024, allow it to sell de-identified information42. Two OhMD pages disagree: one says the BAA is included "even on the free plan", and the pricing page shows Core at $300 and AI & Automation at $500 a month, both starting prices, with no free plan11,43.
Zoho
Zoho offers its BAA on request. The template comes by email, we found no public text, and the BAA covers specific Zoho services14. Zoho says no PHI should flow through any Zoho application until a signed BAA is in place14. Whether the BAA covers or excludes Zia's generative features is NF; the nearest statement is that any third-party application processing PHI needs its own BAA14.
In Zoho CRM an administrator can switch on Models, an LLM feature for Professional, Enterprise and Ultimate editions25. Zoho's help page says Models is not available for fields containing health-related information and that no LLM model processes PHI-encrypted fields25. That wording reaches fields the customer has marked and encrypted. Zoho says field encryption in CRM is not mandatory and lists field-level encryption in its Enterprise edition card44,45, while the same help page describes Record Summary and Notes Summary features25. We think unencrypted health fields and free text are left open by that wording.
Zoho's pages disagree in two places. Its architecture page says customer data used as AI context is never sent to external AI cloud providers37, while the Models page lets an administrator enable OpenAI, Google, Anthropic or Cohere models25. Zoho's Zia page says its AI solutions train on your data36, while its WorkDrive page says Zoho does not use customer data to train its AI models35.
Where the model makers' own BAAs sit
The model makers sell their own agreements, separate from the clouds'. On our check of November 10, 2026, OpenAI's self-serve API BAA needed an established history of API usage and covered only endpoints on OpenAI's eligible list; OpenAI said it offers no BAA for ChatGPT Business. Anthropic offered a BAA for Claude Enterprise plans and its first-party API, and said that Free, Pro, Max, Ultra and Team plans cannot enable HIPAA. ChatGPT and Claude are two of the 15 of 28 tools we checked that sign a BAA only on certain plans46. An Anthropic article we did not re-read that day says its BAA does not apply to Claude bought through Amazon Bedrock or Google Cloud, so ask which agreement applies.
What stays with the practice in every case
No agreement moves these duties. Microsoft says using its services does not on its own achieve HIPAA compliance4. AWS says customers must configure listed services consistently with HIPAA and are responsible for their own compliance17. Google calls compliance a shared responsibility and says you must configure and secure what you build9. OhMD says the vendor provides technical safeguards and the practice is responsible for the rest, including documenting patient consent to text11. Zoho says compliance depends on proper implementation and usage by the customer14. HHS's proposed Security Rule would have a risk analysis consider the type and amount of ePHI an AI tool accesses, to whom the data is disclosed and to whom the output goes47. It is a proposal, published January 6, 202548; the Unified Agenda entry we read on November 10, 2026 lists its final action as July 202749.
What this means for a small practice
Put these questions to any vendor, in writing, and keep the dated answers.
- How is the BAA in force for my account? Microsoft folds it into a contract, AWS requires an acceptance on a qualifying sign-up, and Zoho requires an emailed request3,14,15.
- Can I read the agreement and the covered-services list before patient information goes in, is the list dated, and is my exact AI feature on it under its current name?9,17,26
- Is it a preview, a web search or grounding feature, or another provider's model, and whose terms govern it?20,24
- What is kept from prompts and outputs, for how long, and who can read flagged content? Does that change with the model?29
- Who can turn monitoring or retention off?29,38
- Does the vendor use my content to improve its services unless I opt out?22
- Does content leave the region or the vendor's own infrastructure?25,27,31
- For an application: does the BAA name the AI feature, who supplies the voice and language models, and do subcontractors sign BAAs? What happens to de-identified data?13
- Which settings must be on or off before patient information goes in?9,40,44
- If my vendor built on a cloud, who signs with whom? Microsoft and AWS each say the vendor's customers sign a BAA with the vendor3,5.
Where our service fits
Technical Marketing builds marketing systems and HIPAA-ready front-desk tools for practices. Our HIPAA-ready Essentials program costs $1,500 setup plus $699 a month, per location, after a compliance consultation50. It is a compliance layer added to a plan and does not include the AI voice agent, which is a separate add-on at $299 a month with 250 call minutes included50,51.
People also ask
What is a business associate agreement for AI?
It is the agreement HIPAA calls for when a vendor's AI tool handles a practice's patient information. HHS says a covered entity may disclose protected health information to a business associate once it obtains satisfactory assurances, in a contract or other written arrangement, that the information will be safeguarded1. The contract must set the permitted and required uses and disclosures52.
Is Azure OpenAI HIPAA compliant?
Microsoft says its BAA is available by default to covered entities and business associates, for in-scope Azure services3. Azure OpenAI is not named with the BAA on any Microsoft page we read, and the per-service list sits in a document we could not open. Ask Microsoft to confirm in writing that the exact service is in scope.
Does AWS offer a business associate agreement for Amazon Bedrock?
AWS calls it a Business Associate Addendum and offers it free of charge in AWS Artifact5,7. Amazon Bedrock is a line on its HIPAA Eligible Services Reference with no exclusion note17. The BAA applies to HIPAA Accounts only, and accounts made through the new sign-up cannot be designated6,15.
How do I get a Google Cloud business associate agreement?
Google asks you to opt in to its BAA within one Google Cloud project in your account8. The person accepting confirms full legal authority to bind the customer10. Google says HIPAA-regulated customers get the same services at the same pricing as others9. The BAA does not apply to features that are not Covered Services10.
Does OhMD's BAA cover its AI voice agent?
OhMD says every channel in its channel table is covered by its automatic BAA, and that table has a Voice AI row11. The published BAA text never mentions AI13. So coverage is an inference from the table, and a statement on AI training or retention is NF. Ask OhMD to confirm it in writing.
Does Zoho offer a BAA, and does it cover Zia?
Zoho offers a BAA on request: you email its legal department for the template14. We found neither the text nor the list of covered services published. Whether the BAA covers Zia's generative features is NF. Zoho's help says no LLM model processes PHI-encrypted fields, and field encryption is not mandatory25,44.
Does signing a BAA make an AI tool HIPAA compliant?
No. Microsoft says using its services does not on its own achieve HIPAA compliance4, AWS says customers are responsible for their own HIPAA compliance17, and Google says you remain responsible for evaluating your own9. Configuration, consent and risk analysis stay with the practice.
Can I use ChatGPT or Claude with patient information?
Only on some plans. On our check of November 10, 2026, OpenAI said it offers no BAA for ChatGPT Business, and Anthropic said its Free, Pro, Max, Ultra and Team plans cannot enable HIPAA. ChatGPT and Claude are among the 15 of 28 tools we checked that sign a BAA only on certain plans46. Without a signed BAA covering your account, keep patient information out.
How to read this page: NF not found, ( ) our arithmetic on cited figures, and a small number points to a source below.
Sources
- HHS Office for Civil Rights. Business Associates Frequently Asked Questions (FAQs). U.S. Department of Health and Human Services, 2026. hhs.gov/hipaa/for-professionals/privacy/guidance/business-associates/i
- Office for Civil Rights. Guidance on HIPAA & Cloud Computing. U.S. Department of Health and Human Services, 2022. hhs.gov/hipaa/for-professionals/special-topics/cloud-computing/index.h Held through its record or abstract; passage not matched.
- Microsoft. HIPAA - Azure Compliance | Microsoft Learn. Microsoft, ms.date 2023-04-05; updated_at 2024-10-10. learn.microsoft.com/en-us/azure/compliance/offerings/offering-hipaa-us
- Microsoft. Health Insurance Portability and Accountability Act (HIPAA) & Health Information Technology for Economic and Clinical Health (HITECH) Act - Microsoft Compliance | Microsoft Learn. Microsoft, ms.date 2025-07-29; updated_at 2026-09-11. learn.microsoft.com/en-us/compliance/regulatory/offering-hipaa-hitech
- Amazon Web Services. HIPAA Compliance - Amazon Web Services (AWS). Amazon Web Services, 2026-11. aws.amazon.com/compliance/hipaa-compliance/
- Amazon Web Services. AWS Artifact FAQ - Amazon Web Services (AWS). Amazon Web Services, 2026-11. aws.amazon.com/artifact/faq/
- Amazon Web Services. What is AWS Artifact? - AWS Artifact. Amazon Web Services, 2026-11. docs.aws.amazon.com/artifact/latest/ug/what-is-aws-artifact.html
- Privacy compliance and records for Google Cloud. Google Cloud Platform Console Help, 2026. support.google.com/cloud/answer/6329727
- HIPAA compliance on Google Cloud and Google Workspace. Google Cloud, 2026. docs.cloud.google.com/docs/security/compliance/hipaa
- GCP HIPAA BAA | Google Cloud. Google Cloud, 2026. cloud.google.com/terms/hipaa-baa
- OhMD. HIPAA Compliant Patient Communication for Healthcare. OhMD, 2026-11. ohmd.com/hipaa-compliant
- OhMD. Automated Medical Answering Service: Why AI Beats Phone Trees. OhMD, 2026-11. ohmd.com/blog/automated-medical-answering-service
- OhMD. Business Associate Agreement | OhMD. OhMD, 2026-11. ohmd.com/legal/business-associate-agreement
- Zoho. HIPAA Compliance at Zoho. Zoho, 2026-11. zoho.com/hipaa.html
- Amazon Web Services. Compare sign-up options - AWS Account Management. Amazon Web Services, 2026-11. docs.aws.amazon.com/accounts/latest/reference/sign-up-for-aws.html
- Microsoft. Azure and other Microsoft cloud services in compliance audit scope - Azure Compliance | Microsoft Learn. Microsoft, Last updated on 2023-04-05; updated_at 2024-10-10. learn.microsoft.com/en-us/azure/compliance/offerings/cloud-services-in
- Amazon Web Services. HIPAA Eligible Services Reference - Amazon Web Services (AWS). Amazon Web Services, 2026-10-15. aws.amazon.com/compliance/hipaa-eligible-services-reference/
- Microsoft. Review ISO, SOC, and HIPAA compliance - Microsoft Copilot Studio | Microsoft Learn. Microsoft, ms.date 2024-12-20; updated_at 2026-10-07. learn.microsoft.com/en-us/microsoft-copilot-studio/admin-certification
- Microsoft. Data, privacy, and security for web search in Microsoft Copilot and Microsoft Copilot Chat | Microsoft Learn. Microsoft, ms.date 2026-10-29; updated_at 2026-11-04. learn.microsoft.com/en-us/copilot/plan/manage-public-web-access
- Microsoft. How to use Grounding with Bing Search in Foundry Agent Service (classic) - Microsoft Foundry (classic) portal | Microsoft Learn. Microsoft, ms.date 2026-03-06; updated_at 2026-07-11. learn.microsoft.com/en-us/azure/foundry-classic/agents/how-to/tools-cl
- Microsoft. Microsoft Foundry Models overview (classic) - Microsoft Foundry (classic) portal | Microsoft Learn. Microsoft, ms.date 2026-07-28; updated_at 2026-07-28. learn.microsoft.com/en-us/azure/foundry-classic/concepts/foundry-model
- Amazon Web Services. AWS Service Terms. Amazon Web Services, 2026-11-05. aws.amazon.com/service-terms/
- Amazon Web Services. Amazon Bedrock Marketplace - Amazon Bedrock. Amazon Web Services, 2026-11. docs.aws.amazon.com/bedrock/latest/userguide/amazon-bedrock-marketplac
- Service Specific Terms. Google Cloud, 2026. cloud.google.com/terms/service-terms
- Zoho. Zia AI Models Configuration. Zoho, 2026-11. help.zoho.com/portal/en/kb/crm/zia-artificial-intelligence/generative-
- Microsoft. What are Foundry Tools? - Foundry Tools | Microsoft Learn. Microsoft, ms.date 2025-10-02; updated_at 2026-07-13. learn.microsoft.com/en-us/azure/ai-services/what-are-ai-services
- Microsoft. Data, privacy, and security for Foundry Models sold by Azure in Microsoft Foundry - Microsoft Foundry | Microsoft Learn. Microsoft, ms.date 2026-05-18; updated_at 2026-06-05. learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/data-pri
- Amazon Web Services. Build Generative AI Applications with Foundation Models - Amazon Bedrock FAQs - AWS. Amazon Web Services, 2026-11. aws.amazon.com/bedrock/faqs/
- Amazon Web Services. Data retention - Amazon Bedrock. Amazon Web Services, 2026-11. docs.aws.amazon.com/bedrock/latest/userguide/data-retention.html
- Amazon Web Services. Amazon Bedrock abuse detection - Amazon Bedrock. Amazon Web Services, 2026-11. docs.aws.amazon.com/bedrock/latest/userguide/abuse-detection.html
- Amazon Web Services. Geographic cross-Region inference - Amazon Bedrock. Amazon Web Services, 2026-11. docs.aws.amazon.com/bedrock/latest/userguide/geographic-cross-region-i
- Amazon Web Services. Global cross-Region inference - Amazon Bedrock. Amazon Web Services, 2026-11. docs.aws.amazon.com/bedrock/latest/userguide/global-cross-region-infer
- Gemini Enterprise Agent Platform and zero data retention. Google Cloud, 2026. docs.cloud.google.com/gemini-enterprise-agent-platform/resources/zero-
- OhMD. AI Agents for Healthcare: What They Are, Why They Matter, and Where Most Get It Wrong. OhMD, 2026-02-17. ohmd.com/what-are-ai-agents
- Zoho. Zia Privacy Principles. Zoho, 2026-11. help.zoho.com/portal/en/kb/workdrive/zia-ai/articles/zia-privacy-princ
- Zoho. Zia | Zoho's AI Assistant. Zoho, 2026-11. zoho.com/zia
- Zoho. Zoho CRM SaaS Architecture and Deployment Options. Zoho, 2026-11. help.zoho.com/portal/en/kb/crm/getting-started/articles/zoho-crm-saas-
- Microsoft. Limited access to Azure OpenAI in Microsoft Foundry Models - Microsoft Foundry | Microsoft Learn. Microsoft, Last updated on 2026-05-19; updated_at 2026-06-05. learn.microsoft.com/en-us/azure/foundry/responsible-ai/openai/limited-
- Microsoft. Data, privacy, and security for use of Anthropic Claude models in Microsoft Foundry - Microsoft Foundry | Microsoft Learn. Microsoft, Last updated on 2026-06-29; ms.date 2026-06-23. learn.microsoft.com/en-us/azure/foundry/responsible-ai/claude-models/d
- Amazon Web Services. Monitor model invocation using CloudWatch Logs and Amazon S3 - Amazon Bedrock. Amazon Web Services, 2026-11. docs.aws.amazon.com/bedrock/latest/userguide/model-invocation-logging.
- OhMD. OhMD Launches Nia: A Human-in-the-Loop AI Voice Assistant to Transform Healthcare Communication Powered by Twilio's ConversationRelay. PR Newswire (source: OhMD), 2026-11. prnewswire.com/news-releases/ohmd-launches-nia-a-human-in-the-loop-ai-
- OhMD. Terms of Service | OhMD. OhMD, 2024-04-23. ohmd.com/legal/terms-of-service
- OhMD. OhMD AI Voice + Texting for Medical Practices. OhMD, 2026-11. ohmd.com/pricing
- Zoho. HIPAA Compliance with Zoho CRM. Zoho, 2026-11. help.zoho.com/portal/en/kb/crm/security-control/compliance-setting/hip
- Zoho. Zoho CRM Pricing and Editions - Free for 3 users. Zoho, 2026-11. zoho.com/crm/pricing/
- Technical Marketing. Which software will sign a HIPAA BAA? 28 common tools, checked. Technical Marketing, 2026-11. technicalmarketing.ai/reports/hipaa-baa-availability/ Our own data.
- HHS Office for Civil Rights. HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information (notice of proposed rulemaking, 90 FR 898). Federal Register (govinfo.gov), 2025-01-06. govinfo.gov/content/pkg/FR-2025-01-06/pdf/2024-30983.pdf
- Office for Civil Rights. HIPAA Security Rule To Strengthen the Cybersecurity of Electronic Protected Health Information. Office of the Federal Register, National Archives and Records Administration, 2025. federalregister.gov/documents/full_text/html/2025/01/06/2024-30983.htm
- HHS Office for Civil Rights. HHS/OCR RIN 0945-AA22: HIPAA Security Rule to Strengthen the Cybersecurity of Electronic Protected Health Information (Unified Agenda entry). Reginfo.gov (OIRA / GSA), 2026-11-10. reginfo.gov/public/do/eAgendaViewRule?pubId=202510&RIN=0945-AA22
- Technical Marketing. HIPAA-ready programs. Technical Marketing, 2026-11. technicalmarketing.ai/hipaa/ Our own data.
- Technical Marketing. Pricing. Technical Marketing, 2026-11. technicalmarketing.ai/pricing/ Our own data.
- U.S. Department of Health and Human Services. 45 CFR 164.504 (Code of Federal Regulations, current text as reproduced by Cornell LII). Legal Information Institute, Cornell Law School (copy of the CFR), 2024. law.cornell.edu/cfr/text/45/164.504