If your SaaS product stores or processes patient data for US healthcare customers, HIPAA applies to you as a business associate. This guide covers what that means in practice: the shared responsibility model with your cloud provider, the technical safeguards that matter most, what hospital security questionnaires ask and the evidence to keep. For hands-on help, see our HIPAA compliance consulting page.
When does HIPAA apply to a SaaS company?
HIPAA applies to a SaaS company when it creates, receives, maintains or transmits protected health information (PHI) on behalf of a covered entity, such as a hospital, clinic or health plan, or on behalf of another business associate. That makes the SaaS company a business associate, which must sign a business associate agreement (BAA) and meet the Security Rule.
Common SaaS examples include practice management software, telehealth platforms, patient engagement tools, healthcare billing software and analytics products that ingest clinical data. If PHI touches your system, including logs, support tickets and backups, HIPAA applies to that part of your service. Our guide to business associate agreements explains the contract side.
How does shared responsibility work with AWS, Azure and GCP?
Your cloud provider secures its infrastructure, and you secure everything you build and configure on top of it. AWS, Microsoft Azure and Google Cloud will each sign a BAA with you, but it covers only their part and only the services listed under it. Signing the cloud provider's BAA is essential, and it is only the first step.
In practice:
| Layer | Who is responsible |
|---|---|
| Physical data centres and hardware | Cloud provider |
| Core infrastructure of covered services | Cloud provider |
| Which services you use for PHI | You: use only services covered by the provider's BAA |
| Configuration: networks, storage, encryption, keys | You |
| Identity and access for your team and customers | You |
| Your application code and data handling | You |
| Logging, monitoring and incident response | You, using the provider's tools |
| Backups and recovery | Shared: the provider offers the tools, you set them up and test them |
Three practical rules:
- Sign the cloud provider's BAA before any PHI goes into the account.
- Keep PHI only in covered services. Check the provider's list before adopting a new service.
- Separate PHI environments from development and test, and never use real PHI in testing.
What technical safeguards matter most for HIPAA SaaS?
The technical safeguards in §164.312 cover access control, audit controls, integrity, person or entity authentication and transmission security. For SaaS teams that means unique user accounts and least privilege, strong authentication such as multi-factor authentication, encryption at rest and in transit, detailed logging with regular review, and integrity checks on PHI.
A practical baseline:
- Access control. Unique accounts for every user, role-based access, quick removal of leavers, and access reviews on a schedule.
- Authentication. Multi-factor authentication for your team, especially for production and admin access, and an option for your customers.
- Encryption. Encrypt PHI at rest and in transit, and manage keys carefully.
- Audit logging. Log access to PHI and admin actions, protect the logs and review them.
- Integrity. Protect PHI from improper change or deletion, with backups you have tested.
- Secure development. Code review, dependency scanning and penetration testing before major releases.
The administrative (§164.308) and physical (§164.310) safeguards still apply. Most SaaS companies cover physical safeguards through the cloud provider and their own office and device controls. Everything starts with a risk analysis; see our HIPAA risk assessment guide.
What do hospital security questionnaires ask SaaS vendors?
Hospital security questionnaires usually ask whether you will sign a BAA, where PHI is stored, how it is encrypted, who can access it, whether you use multi-factor authentication, how you log and monitor access, how you handle incidents and breaches, how you manage subcontractors, and what independent evidence you can share, such as an assessment report.
Expect questions in these areas:
- Contracts: BAA, subcontractor BAAs, data location.
- Data protection: encryption, key management, backups, deletion at contract end.
- Access: MFA, access reviews, privileged access, offshore access.
- Operations: logging, vulnerability management, penetration testing, change management.
- Incidents: response plan, breach notification timelines.
- People: background checks where applicable, security and HIPAA training.
- Evidence: risk analysis summary, policies, independent assessment report, SOC 2 report or HITRUST certification.
Answer with what you actually do and keep a library of approved answers. Inconsistent answers across questionnaires are a red flag for reviewers.
What evidence should a HIPAA SaaS company keep?
Keep the evidence an assessor or customer will ask for: your risk analysis and risk management plan, policies and procedures, signed BAAs, access reviews, training records, logs and log reviews, vulnerability and penetration test results, incident records and backup tests. HIPAA requires documentation to be kept for six years under §164.316.
Organise evidence by safeguard so it is easy to find and reuse. Our free HIPAA Security Rule evidence checklist lists what assessors typically ask for, and the HIPAA compliance checklist maps each requirement to evidence.
There is no official HIPAA certification. SaaS vendors show compliance through a risk analysis, documented safeguards and an independent third-party assessment report.
What HIPAA mistakes do SaaS teams make most often?
The most common mistakes are assuming the cloud provider's BAA makes the product compliant, letting PHI spread into logs, analytics and support tools, using real patient data in testing, skipping access reviews, and promising breach notification timelines the team cannot meet. Each one is easy to prevent if you plan for it early.
- PHI in third-party tools. Error trackers, chat widgets and analytics tools often receive PHI by accident. Either sign a BAA with the vendor or stop the data reaching it.
- Shared admin accounts. Every person needs their own account so access can be traced.
- Old access. Former staff and contractors keep access long after they leave.
- Untested backups. A backup you have never restored is a guess.
How should a SaaS company plan HIPAA compliance?
Plan it in stages: confirm you are a business associate, sign your cloud provider's BAA, map where PHI flows, run a risk analysis, close the gaps it finds, train your team and then get an independent assessment report. CyberWave GRC runs this as a gap assessment, guidance and templates, then an independent assessment by a separate assessor.
A sensible order:
- Confirm scope. Which products, customers and data are involved.
- Cloud BAA and architecture. Covered services only, separated PHI environment.
- Risk analysis and a risk management plan.
- Remediate: technical safeguards, policies, vendor BAAs.
- Train your workforce and record it.
- Independent assessment by an assessor who did no readiness work for you.
- Maintain: reviews, evidence collection and updates as the product changes.
Many SaaS vendors also need a SOC 2 report for non-healthcare customers. Building one control set for both saves time; see HIPAA vs SOC 2.
What about the proposed Security Rule update?
HHS proposed a major update to the HIPAA Security Rule in January 2025. As of November 2026 it is not final, and the current rule still applies. The proposal points to more specific technical requirements, such as encryption and multi-factor authentication, asset inventories and more frequent testing, which SaaS teams can start on now.
Building these in now is good practice whatever the final rule says. See the proposed HIPAA Security Rule update for the status and how to prepare.


