Most software companies meet HIPAA through a customer. A clinic, health system or health plan wants to use your product with patient data, their legal team sends a business associate agreement, and suddenly a startup that thought of itself as a scheduling tool or analytics platform is regulated under federal health privacy law.
This guide explains how that happens, what it obligates you to do, and how HIPAA's requirements map onto the way software teams actually build and run products.
Key points
- You become a business associate when you create, receive, maintain or transmit PHI on behalf of a covered entity or another business associate.
- Business associates are directly liable for Security Rule compliance — signing a BAA is not paperwork only.
- HIPAA does not require SOC 2 or HITRUST, though many customers expect one.
- Secure SDLC, audit logging and tenant isolation are where HIPAA meets engineering.
When a software company becomes a business associate
Under 45 CFR §160.103, a business associate is anyone who creates, receives, maintains or transmits PHI for a function or service on behalf of a covered entity. For software companies, the test is usually simple: if your customer is a covered entity (or a business associate) and your product stores or processes their patients' data, you are a business associate.
HHS's cloud computing guidance makes clear that a cloud service provider storing ePHI is a business associate even if the data is encrypted and the provider does not hold the key. The narrow "conduit" exception applies to entities that merely transmit data and do not store it beyond what transmission requires — it rarely fits a SaaS product.
Situations that often fall outside HIPAA
- A direct-to-consumer app where users enter their own data and no covered entity is involved — though FTC rules and state laws may apply.
- Software licensed for on-premises installation where the vendor never accesses PHI (support access changes this).
- Tools that only ever handle properly de-identified data under §164.514.
Business associate agreements with customers
A BAA must contain the elements in §164.504(e) and §164.314(a). Expect customer BAAs to go further — shorter breach notice windows, audit rights, data location restrictions, cyber insurance requirements and indemnities. Review every BAA with counsel; obligations you accept contractually become obligations you must operationally meet.
- Permitted uses and disclosures of PHI, and a prohibition on others.
- Appropriate safeguards and compliance with the Security Rule.
- Reporting of security incidents and breaches of unsecured PHI to the customer.
- Flow-down of the same restrictions to subcontractors — your cloud host, email provider, support tools and any other vendor touching PHI.
- Support for individuals' rights where applicable, and return or destruction of PHI at termination.
Translating the Security Rule into product security
| Security Rule standard | Common implementation in software products |
|---|---|
| Access control — §164.312(a) | SSO/SAML support, role-based access, tenant isolation, unique user IDs, session timeouts, emergency access procedures |
| Audit controls — §164.312(b) | Immutable application audit logs of PHI access and changes, centralized log retention, alerting |
| Integrity — §164.312(c) | Checksums, database constraints, change tracking, protection against unauthorized modification |
| Authentication — §164.312(d) | Strong authentication for users and administrators; MFA is recommended practice |
| Transmission security — §164.312(e) | TLS for all traffic, including internal service-to-service calls carrying PHI |
| Contingency plan — §164.308(a)(7) | Backups, tested restores, disaster recovery and documented RTO/RPO |
| Workforce security — §164.308(a)(3) | Least-privilege production access, joiner/mover/leaver process, access reviews |
Secure development lifecycle
HIPAA does not name a specific SDLC framework, but the risk analysis must cover how PHI could be exposed through your product. In practice, that brings engineering practices into scope:
- Keep PHI out of non-production environments, or protect those environments as if they were production.
- Threat model features that touch PHI — especially exports, integrations, sharing features and admin tools.
- Use code review, dependency scanning and secret scanning in CI.
- Control who can access production data and log that access.
- Scrub PHI from error tracking, crash reports and debug logs; these are frequent, overlooked leak paths.
- Assess third-party SDKs and analytics before they ship; anything that receives PHI needs a BAA.
Logging: what to capture and what to keep out
Audit logs serve two purposes that pull in opposite directions. You need enough detail to reconstruct who accessed which record and when — that is the point of §164.312(b) and of information system activity review under §164.308(a)(1)(ii)(D). But application and infrastructure logs that inadvertently contain PHI become another store of ePHI you must protect. Log identifiers and actions rather than clinical content, restrict log access, and set retention deliberately.
Incidents and breach notice to customers
As a business associate, you must report security incidents to your customer as the BAA specifies, and notify the covered entity of a breach of unsecured PHI without unreasonable delay and no later than 60 days after discovery under §164.410 — or sooner if the BAA sets a shorter window, which many health system BAAs do. Your notice must include, to the extent possible, the identity of each affected individual and the information the covered entity needs to notify them.
That has practical consequences for engineering. You need logs good enough to determine which tenants and which patients were affected, an on-call process that recognizes a potential PHI incident, and a pre-agreed internal path to legal counsel. Multi-tenant incidents are the hard case: one misconfiguration can trigger obligations to many customers with different contractual deadlines. Build a register of BAA notice terms before you need it.
Customer security questionnaires
Health system procurement teams typically send long questionnaires, sometimes based on standardized formats. Answer them from a maintained library tied to real evidence: your risk analysis summary, policy set, penetration test summary, incident response plan and BAA template. Never answer "yes" to a control you do not operate; the questionnaire often becomes part of the contract.
SOC 2, HITRUST and HIPAA
HIPAA does not require SOC 2, HITRUST, ISO 27001 or any other attestation. These are market expectations, and in enterprise healthcare sales they can be practically necessary. A SOC 2 report or HITRUST certification evidences that controls were examined against that framework — it is not a HIPAA certification, and it does not replace the HIPAA risk analysis. Mapping your HIPAA program to the framework your buyers request reduces duplicated effort.
If you are early-stage, see HIPAA compliance for startups and HIPAA consulting for SaaS companies for how to sequence this work.
Frequently asked questions
Do we need to be HIPAA compliant before signing a BAA?
Once you sign a BAA and receive PHI, you are obligated to comply. Ideally your risk analysis, core safeguards and policies are in place before you onboard PHI, not after.
Is our cloud host's BAA enough?
No. It covers the provider's responsibilities. You still need to configure services securely, control access, log activity and meet every other Security Rule requirement for your application.
Is SOC 2 required for HIPAA?
No. SOC 2 is a separate attestation that many healthcare customers request. It can support your HIPAA program but does not demonstrate HIPAA compliance by itself.
Can we use PHI to train models or improve the product?
Only as permitted by your BAA and the Privacy Rule. Many BAAs restrict such uses. De-identification under §164.514 may be an option. Review with counsel before using customer PHI for any secondary purpose.
Do our subcontractors need BAAs?
Yes. Any subcontractor that creates, receives, maintains or transmits PHI on your behalf is itself a business associate, and you must have a compliant subcontractor BAA with it.
Authoritative sources
- HHS — Guidance on HIPAA and Cloud Computing
- HHS — Sample Business Associate Agreement Provisions
- HHS — Summary of the HIPAA Security Rule
- NIST SP 800-66 Rev. 2
This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.