HIPAA for SaaS companies

HIPAA for SaaS companies: what a business associate has to do

If your software creates, receives, maintains or transmits protected health information (PHI) for a hospital, clinic, health plan or another vendor that does, you are a HIPAA business associate. That makes you directly responsible for the Security Rule, bound by the business associate agreements you sign, and on the hook for breach notice to your customers. Here is what that means in practice, and what hospital security teams will ask you to show.

Key takeaways

  • A SaaS vendor that handles PHI for a covered entity is a business associate (45 CFR 160.103) and is directly liable for the Security Rule.
  • You need a signed BAA with each covered-entity customer, and BAAs with your own subprocessors that touch PHI.
  • The core of the program is a documented risk analysis under 45 CFR 164.308(a)(1), plus written policies, workforce training and a breach process.
  • You must notify the covered entity of a breach without unreasonable delay and no later than 60 days after discovery (45 CFR 164.410); many BAAs set a shorter deadline.
  • There is no official HIPAA credential. Buyers accept evidence: the BAA, the risk analysis, policies, training records and, increasingly, a SOC 2 report.

Are you a business associate?

HIPAA applies to covered entities (health care providers that bill electronically, health plans and clearinghouses) and to their business associates. A business associate is a person or company that performs a function or service for a covered entity that involves PHI (45 CFR 160.103). A subcontractor that handles PHI for a business associate is also a business associate.

For SaaS that usually means: EHR-adjacent tools, telehealth platforms, patient-engagement and scheduling software, billing and revenue-cycle tools, analytics on clinical data, and AI scribes. Hosting PHI counts even if you never look at it. HHS guidance on cloud computing says a cloud service that stores encrypted ePHI is a business associate even without the decryption key.

The narrow “conduit” exception covers transmission-only services such as an internet service provider. It does not cover services that store PHI beyond the transient storage incidental to transmission.

The business associate agreement (BAA)

A covered entity may only share PHI with you under a written BAA (45 CFR 164.502(e) and 164.504(e)). Expect to sign one before a pilot starts, and expect hospitals to send their own paper.

Read hospital BAAs closely. They often add breach-notice windows shorter than 60 days, cyber-insurance minimums, audit rights, offshore-access limits and indemnities that go beyond what HIPAA itself requires.

  • Permitted uses and disclosures: what you may do with PHI, and that you will not use it otherwise.
  • Safeguards: you will comply with the Security Rule for electronic PHI.
  • Reporting: you will report uses or disclosures not permitted by the BAA, security incidents and breaches of unsecured PHI.
  • Subcontractors: you will get the same written assurances from any subcontractor that handles PHI for you.
  • Individual rights: you will help the covered entity with access, amendment and accounting requests where they apply.
  • Termination: you will return or destroy PHI when the contract ends, or protect what cannot feasibly be returned.

Security Rule safeguards

The Security Rule is organised into five sections. Some implementation specifications are “required” and some are “addressable”. Addressable does not mean optional: you must implement it, implement a reasonable alternative, or document why neither is reasonable and appropriate.

In January 2025 HHS proposed changes to the Security Rule (90 FR 898), including stricter encryption, MFA, asset-inventory and testing requirements. As of November 2026, that proposal has not been finalized; the rule in force is the current 45 CFR Part 164, Subpart C. Many hospitals already ask for those controls in security reviews, so treat them as buyer expectations rather than law.

SectionWhat it coversWhat a SaaS team typically shows
45 CFR 164.308 AdministrativeSecurity officer, risk analysis and risk management, workforce security, training, incident procedures, contingency plan, evaluation, BAAsNamed security officer, signed risk analysis, risk register, training records, incident runbook, backup and DR plan
45 CFR 164.310 PhysicalFacility access, workstation use and security, device and media controlsCloud provider responsibility plus your own laptop policy, disk encryption and device management
45 CFR 164.312 TechnicalAccess control, audit controls, integrity, person or entity authentication, transmission securityUnique logins, MFA, role-based access, audit logs, encryption in transit and at rest
45 CFR 164.314 OrganizationalBusiness associate contracts and other arrangementsSigned BAAs with customers and with subprocessors
45 CFR 164.316 DocumentationWritten policies and procedures, kept for six years and reviewed periodicallyVersioned policy set with approval dates and review history

Risk analysis: the document every reviewer asks for

The first required specification in the Security Rule is a risk analysis: an accurate and thorough assessment of the potential risks and vulnerabilities to the confidentiality, integrity and availability of the ePHI you hold (45 CFR 164.308(a)(1)(ii)(A)). Risk management, reducing those risks to a reasonable and appropriate level, follows from it.

A missing or stale risk analysis is one of the findings HHS’s Office for Civil Rights cites most often in enforcement. For a SaaS company it should cover your product infrastructure, the third-party services in your data flow, your workforce devices and your support processes, and it should be updated when the system changes materially.

Policies and workforce training

You need written policies that match what you actually do (45 CFR 164.316), and a security awareness and training program for the whole workforce, including contractors with system access (45 CFR 164.308(a)(5)). Keep the evidence: who acknowledged which policy version, who completed which training and when.

  • Information security policy and acceptable use
  • Access control and account management, including onboarding and offboarding
  • Incident response and breach notification
  • Contingency planning: backup, disaster recovery, emergency mode operation
  • Vendor and subprocessor management
  • Sanctions for workforce members who violate policy

Breach notification: your clock and your customer’s clock

The Breach Notification Rule is at 45 CFR 164.400–414. An impermissible use or disclosure of unsecured PHI is presumed to be a breach unless a documented risk assessment shows a low probability that the PHI was compromised (45 CFR 164.402). PHI encrypted in line with HHS guidance is not “unsecured”.

A breach is treated as discovered on the first day it is known, or by exercising reasonable diligence would have been known, to anyone in your workforce other than the person who caused it. If you act as your customer’s agent under the federal common law of agency, your discovery is treated as theirs and their own 60-day clock starts when you discover the breach (164.404(a)(2)), so tell them early.

WhoNotifiesDeadline
Business associate (you)The covered entityWithout unreasonable delay and no later than 60 calendar days after discovery (164.410), or sooner if your BAA says so
Covered entityAffected individualsWithout unreasonable delay and no later than 60 calendar days after discovery (164.404)
Covered entityProminent media outletsFor breaches affecting more than 500 residents of a state or jurisdiction (164.406)
Covered entityHHS500 or more individuals: at the same time as individual notice. Fewer than 500: within 60 days after the end of the calendar year (164.408)

Subprocessors and the PHI data flow

Every service that stores or processes PHI for you, such as your cloud host, database, logging, email, support desk, transcription or LLM provider, is a subcontractor business associate. You need a BAA with each one (45 CFR 164.502(e)(1)(ii) and 164.308(b)), and you need to know which of their services the BAA actually covers.

Hospital reviewers will ask for a subprocessor list and a data-flow diagram. Keep PHI out of tools that are not covered: error trackers, analytics, product email and chat support are the usual leaks.

How Shieldra helps a SaaS business associate

Shieldra organises the HIPAA work a buyer’s security team will ask about, so you can show evidence instead of promises.

  • HIPAA Security Risk Analysis aligned to 45 CFR 164.308(a)(1), with Security Officer sign-off and a report you can share.
  • HIPAA policy templates you adopt and edit, with version history.
  • Security awareness training for your workforce, with completion records.
  • Vendor and subprocessor tracking: BAA status, BAA upload, and expiring BAAs highlighted.
  • Incident and breach tracking, so the 60-day clock and your decisions are documented.
  • A public trust center with a shareable link, and gated documents released through access requests.
  • Shieldra is a no-PHI service: you store compliance documentation in it, not patient data.

Working toward your first hospital security review?

We are looking for a small number of health-tech design partners. We will work with you hands-on to get your first hospital or payer security review done, and your feedback shapes what we build next.

This guide is general information, not legal advice. Shieldra helps you prepare and organise evidence; it does not certify compliance, and HHS does not approve or endorse any private HIPAA credential.

Frequently asked questions

Is my SaaS company a HIPAA business associate?

If your product creates, receives, maintains or transmits PHI on behalf of a covered entity or another business associate, yes (45 CFR 160.103). Storing PHI counts even if it is encrypted and you hold no key. If you never touch PHI, for example a tool that only sees de-identified data or staff scheduling with no patient information, you may not be.

Do we need to sign the hospital’s BAA or can we use ours?

Either can work; HIPAA only requires that the BAA contain the elements in 45 CFR 164.504(e). Large health systems usually insist on their own. Have your own template ready for smaller customers, and review hospital paper for terms that go beyond HIPAA, such as short breach-notice windows, insurance minimums and audit rights.

How fast must a business associate report a breach?

Without unreasonable delay and no later than 60 calendar days after discovery (45 CFR 164.410). Sixty days is the outer limit, not a target, and many BAAs require notice within days. You must also report security incidents and impermissible uses or disclosures as the BAA specifies.

Does using a HIPAA-eligible cloud make our product compliant?

No. A cloud provider’s BAA covers its own services and its side of the shared-responsibility model. Your configuration, access controls, application, workforce and policies are still yours, and so is the risk analysis.

Is there an official HIPAA credential for SaaS vendors?

No. HHS does not certify vendors or endorse private HIPAA credentials. What buyers accept is evidence: a signed BAA, a current risk analysis, policies, training records, incident procedures and often an independent SOC 2 report.