Blog

Building AI into your healthcare SaaS?

A shield with a medical cross in front of a cloud, next to a chat bubble and a crossed-out image

Most teams assume they need to negotiate a separate HIPAA Business Associate Agreement with OpenAI before touching any PHI.

That assumption is wrong. And it's slowing you down.

When you sign up for Microsoft Azure, you automatically enter into the Microsoft Products and Services Data Protection Addendum.

That addendum applies the Microsoft HIPAA BAA to all HIPAA-compliant services. Azure OpenAI is one of them.

I've seen healthcare startups burn weeks chasing a direct OpenAI BAA when they could have been building on Azure from day one.

One caveat: the HIPAA BAA only covers text-based interactions.
Do not send images containing PHI. No X-rays. No MRIs. Text only.

If you don't want automatic HIPAA BAA coverage for some reason, you can opt out by contacting Microsoft.

But for most healthcare teams, this is exactly what you need.

What compliance assumptions are slowing down your AI roadmap?

Originally posted on LinkedIn.

← Back to the blog