Copilot vs. ChatGPT vs. Claude
Copilot, ChatGPT, or Claude: which AI should your ABA practice use?
It’s the question every practice is asking. The honest answer: there’s no universal winner – the leading tools are all excellent. The real decision is which one fits how your practice already works, and how each handles client information.
The short answer
There’s no single right tool
For a growing ABA or behavioral-health practice, the smartest question isn’t “which model is smartest?” It’s “which tool fits our workflows, our data, and how our staff will actually use it?” Often the answer is a mix – and the tool matters less than choosing the right first workflow and setting it up right before adoption spreads.
Where each tool fits
Often the place to start
Microsoft 365 Copilot
If your practice already runs on Microsoft 365, Copilot is usually the natural first step – not because its model is “better,” but because it works inside the identity, permissions and tools your team already uses. No new app, no new login, and it draws on content your team can already reach. Because it follows your existing access, setup matters: reviewing who can reach what comes first.
A strong general assistant
ChatGPT (OpenAI)
Excellent for drafting, brainstorming, research and analysis, and flexible enough to support a wide range of everyday workflows. For anything that touches client information, the plan you’re on, workspace controls, data-retention settings and business terms all matter – so it’s worth setting up deliberately rather than letting staff sign up ad hoc.
Strong writing & long documents
Claude (Anthropic)
Strong on long documents, careful writing and reasoning – a useful complement to the others when the work is document-heavy. As with any tool, client-data use should be reviewed based on the workspace, integrations and terms in place before it becomes part of daily work.
| Tool | Best first fit | Strong at | Set up first |
|---|---|---|---|
| Microsoft 365 Copilot | Practices already on Microsoft 365 | Email, meetings and documents inside Office, using your existing access | Reviewing who can access what – it inherits your permissions |
| ChatGPT | A flexible general assistant | Drafting, brainstorming, research and analysis | The plan and data settings – and what staff put into it |
| Claude | Document-heavy work | Long documents, careful writing and reasoning | The workspace, integrations and terms before client-data use |
The question everyone asks
But is it HIPAA-compliant?
It’s usually the first question – and the honest answer is that no AI tool is simply “HIPAA-compliant” or “not” on its own. What matters is the plan you’re on, the business terms and data settings behind it, whether a Business Associate Agreement is in place where one is needed, and – just as much – how access is set up on your side before staff start using it.
A BAA is a starting point, not the finish line – two things still matter just as much. First, the version you use: the free, personal apps generally aren’t meant for client information; that’s what specific business or enterprise plans, with the right agreement and data settings, are for. Second, how it’s set up on your side: a connected assistant like Copilot works within the access your team already has, so an over-shared mailbox or folder can surface information a user shouldn’t reach, while a standalone tool depends on what staff choose to put into it. Setting AI up the HIPAA-minded way means choosing an approved tool and plan, deciding what information is off-limits, and reviewing who can reach what first – so the safeguards hold as adoption grows.
In practice, “set it up right” comes down to a short checklist:
- Confirm the exact plan or service is eligible for the way you’ll use it
- A signed Business Associate Agreement wherever client information is involved
- A quick look at what data would be used and where it goes
- Minimum-necessary access – who can reach what
- A one-page rule on what staff may and may not enter, plus brief training
- Basic logging and retention, and a plan if something goes wrong
One thing to avoid
Don’t let staff experiment with client information
The most common misstep isn’t choosing the “wrong” tool – it’s letting staff try tools informally with client information before there’s any policy or access review in place. A connected assistant works within the access your team already has, so an over-shared folder, mailbox or SharePoint site becomes easier to surface, not harder.
The fix isn’t to slow adoption down. It’s to decide which tools are approved, what information is off-limits, and who can access what – so it’s safe to say yes. That’s the same HIPAA-minded discipline we bring to IT for ABA practices every day.
The recommended first step: a small pilot
For most practices, the right start is small: a handful of leadership, finance, HR or admin users, a few everyday workflows using material that has no client information in it, clear rules on what can and can’t be entered, and a quick review of who can access what. Prove the value in weeks, then expand when it’s clearly working. Start small, move fast, and set it up right.
Where to start
Everyday admin work – with no client data in it
The first useful AI workflows usually aren’t futuristic – they’re the administrative work that quietly eats your team’s week. One caution: “administrative” doesn’t mean “free of client data” – a billing, scheduling or HR file often still contains it. So start with these using material that has no client information in it, with leadership or admin users, and leave anything touching client details until the setup and rules are clearly defined.
Common questions
Is ChatGPT, Copilot, or Claude HIPAA-compliant?+
No AI tool is simply “compliant” or “not” on its own. It depends on the plan you’re on, the business terms and data settings behind it, whether a Business Associate Agreement is in place where one is needed, and how access is set up on your side. We help you choose an approved tool and set it up the HIPAA-minded way.
Do we need a BAA to use AI in our practice?+
Where AI could touch information that identifies a client, a Business Associate Agreement with the provider is part of the picture – but it isn’t the whole story. The agreement covers the vendor’s obligations; it doesn’t decide what your own staff can access or do. Both need to be right.
Can we just use the free version of ChatGPT or Copilot?+
For anything involving client information, the free and personal plans generally aren’t meant for it. The business and enterprise plans – set up with the right agreement and data settings – are what make careful use possible. We help you get on the right plan and configure it.
How do we get a BAA for an AI tool?+
Usually a qualifying business or enterprise plan is required, and an administrator turns on the HIPAA-ready configuration and accepts the agreement in the provider’s admin settings (API use is enabled separately). The exact route differs by vendor and changes over time – we help you confirm the current path and get it in place.
Which tool should we use – Copilot, ChatGPT, or Claude?+
There’s no universal winner. If you already run on Microsoft 365, Copilot is often the natural first step because it works inside the tools and permissions you already have. ChatGPT and Claude can fit specific workflows too. We help you choose the right mix rather than sell one answer.
Can our team use AI while limiting client-data exposure?+
Yes – start with workflows that use no client information, and for anything that involves it, use an approved, BAA-covered setup with the right safeguards. A connected assistant like Copilot works within the access your team already has, so reviewing who can reach what comes first; standalone tools need clear rules on what staff put in. Good controls reduce risk – they don’t eliminate it.
What should we use AI for first?+
Low-risk, high-frequency admin and leadership work: drafting email, summarizing meetings, reviewing documents, explaining spreadsheets and answering policy questions. Leave clinical or client-specific workflows until approved tools, rules and access are clearly defined.
How quickly can we get started?+
Usually weeks, not quarters. We start with a small leadership or admin group and a few everyday workflows, prove the value, and expand from there when it’s clearly working.
Not sure which fits your practice?
Tell us a bit about your practice and what you’d like AI to help with, and we’ll set up a short, no-commitment call. You’ll leave knowing:
- which tool likely fits your practice first
- the first workflow worth trying
- what to line up before staff use it
Prefer to grab a time now? Book directly →
More on our approach: AI for ABA practices – started safely in weeks, Microsoft 365 Copilot for ABA practices, or join our free webinar, Wednesday, August 26, 2026 · 12:00 PM ET.