HIPAA Compliance by Vertical
HIPAA Compliance for Healthcare SaaS Companies
HIPAA compliance for healthcare SaaS — you are a business associate the moment you handle PHI for a customer; here is a practical path to being ready to sign a BAA.
Key takeaways
- PHI in scope: Anything your customers send through your API or upload to your platform, Logs and metrics that may contain PHI snippets, Support tickets and screenshots from customer staff, AI/ML training data derived from customer usage.
- Start with these controls: PHI inventory across storage, logs, and analytics; A BAA template that covers the required elements of 45 CFR 164.504(e), reviewed by counsel; Subcontractor list with a BAA for each subcontractor that handles PHI.
- The most common mistake: Production logs containing raw PHI, with no scrubbing
- A signed BAA is required with every vendor that creates, receives, maintains, or transmits PHI on your behalf, and no tool is HIPAA compliant on its own.
PHI handled in this environment
- Anything your customers send through your API or upload to your platform
- Logs and metrics that may contain PHI snippets
- Support tickets and screenshots from customer staff
- AI/ML training data derived from customer usage
- Backups, replicas, and analytics warehouses
Common compliance pain points
- PHI you did not know you had: Logs, support attachments, and AI training data often hold PHI that does not appear on the architecture diagram. Finding it is the first compliance task, because the risk analysis has to cover every place ePHI is stored or sent.
- BAA readiness, HIPAA compliance, and SOC 2: Customers ask "are you HIPAA compliant?", but what they usually need is a signed BAA, evidence of documented safeguards, and often a SOC 2 Type II report. These are three separate things, and no single signature covers them.
- AI training and inference flows: If your platform sends customer data to an AI model provider, that provider is your subcontractor and needs a BAA, or the customer must control the flow, for example with their own API key. Using customer PHI to train models must be permitted by the BAA.
- Subcontractor sprawl: SaaS products use many vendors: error tracking, logging, email, SMS, payments. Every one that creates, receives, maintains, or transmits PHI on your behalf is a subcontractor business associate and needs a BAA. Many customers will also ask for the list.
Priority controls
- PHI inventory across storage, logs, and analytics
- A BAA template that covers the required elements of 45 CFR 164.504(e), reviewed by counsel
- Subcontractor list with a BAA for each subcontractor that handles PHI
- Documented AI data flows, with customer-controlled keys where possible
- SOC 2 Type II if enterprise customers require it
- A customer-facing trust center describing your controls
Common mistakes
- Production logs containing raw PHI, with no scrubbing
- Error-tracking, logging, or email vendors handling PHI without a BAA
- Training AI models on customer PHI without that use being permitted by the BAA
- No SOC 2 Type II despite enterprise customer requirements
- BAAs signed by sales staff without legal review
Enforcement context
Since the 2013 Omnibus Rule, business associates, including SaaS vendors, are directly liable for Security Rule compliance and for uses and disclosures their BAAs do not permit. Breaches at business associates appear regularly on HHS's public breach portal, and covered entity customers increasingly ask vendors for evidence of safeguards before signing. HHS's January 2025 Security Rule proposal (90 FR 898) would, if finalized, require business associates to verify their technical safeguards to customers at least once every 12 months; it is a proposal, not current law.
Frequently asked questions
What PHI do healthcare SaaS organizations handle?
Anything your customers send through your API or upload to your platform; Logs and metrics that may contain PHI snippets; Support tickets and screenshots from customer staff; AI/ML training data derived from customer usage; Backups, replicas, and analytics warehouses. Any of these, combined with an identifier, is protected health information when a covered entity or business associate holds it, and in electronic form it brings the Security Rule into scope.
What are the priority HIPAA controls for healthcare SaaS?
PHI inventory across storage, logs, and analytics; A BAA template that covers the required elements of 45 CFR 164.504(e), reviewed by counsel; Subcontractor list with a BAA for each subcontractor that handles PHI; Documented AI data flows, with customer-controlled keys where possible; SOC 2 Type II if enterprise customers require it; A customer-facing trust center describing your controls.
What are the most common HIPAA mistakes in healthcare SaaS?
Production logs containing raw PHI, with no scrubbing; Error-tracking, logging, or email vendors handling PHI without a BAA; Training AI models on customer PHI without that use being permitted by the BAA; No SOC 2 Type II despite enterprise customer requirements; BAAs signed by sales staff without legal review.
What does HIPAA enforcement look like for healthcare SaaS?
Since the 2013 Omnibus Rule, business associates, including SaaS vendors, are directly liable for Security Rule compliance and for uses and disclosures their BAAs do not permit. Breaches at business associates appear regularly on HHS's public breach portal, and covered entity customers increasingly ask vendors for evidence of safeguards before signing. HHS's January 2025 Security Rule proposal (90 FR 898) would, if finalized, require business associates to verify their technical safeguards to customers at least once every 12 months; it is a proposal, not current law.