HIPAA for startups
HIPAA for startups: the first program a hospital will expect
Most health-tech startups meet HIPAA the same way: a hospital, clinic or payer wants to pilot the product and sends a BAA and a security questionnaire. You do not need a compliance department to answer them. You need a small, real program that is written down, owned by someone, and backed by evidence. This guide covers when HIPAA applies to you and what to build first.
Key takeaways
- HIPAA applies when you handle PHI for a covered entity (you are a business associate) or when you are a covered entity yourself.
- Consumer health apps outside HIPAA can still fall under the FTC Health Breach Notification Rule and state health-privacy laws.
- The first program is small: a security officer, a risk analysis, policies, BAAs, training, core technical controls and a breach process.
- Build it in the order a buyer will check it, and keep the evidence as you go.
- Nobody can make you “HIPAA certified”. HHS does not certify anyone, so buyers look for evidence instead.
Does HIPAA apply to your startup?
HIPAA applies to covered entities (most health care providers, health plans and clearinghouses) and to their business associates. If you sell to providers or payers and your product handles patient information for them, you are almost certainly a business associate.
If you sell directly to consumers and no covered entity is involved, HIPAA may not apply. You are not off the hook: the FTC Health Breach Notification Rule covers many health apps outside HIPAA, and state laws such as Washington’s My Health My Data Act regulate consumer health data. Get advice on which applies before you rely on it.
| Your situation | HIPAA role | What it means |
|---|---|---|
| B2B software used by hospitals or clinics with patient data | Business associate | Security Rule, BAAs, breach notice to customers |
| You subcontract to another vendor that serves providers | Subcontractor business associate | Same obligations, BAA with the vendor above you |
| You provide care and bill insurance electronically | Covered entity | Privacy, Security and Breach Notification Rules in full |
| Direct-to-consumer app, no covered entity involved | Usually not HIPAA | Check the FTC Health Breach Notification Rule and state laws |
The minimum program a hospital will expect
- A named security officer (45 CFR 164.308(a)(2)). At a startup this is often the CTO; write the appointment down.
- A documented risk analysis and risk management plan (45 CFR 164.308(a)(1)).
- Written policies and procedures that match how you actually work, kept for six years (45 CFR 164.316).
- Signed BAAs with customers, and with every vendor that touches PHI for you (45 CFR 164.502(e), 164.308(b)).
- Security awareness training for everyone with access, with completion records (45 CFR 164.308(a)(5)).
- Technical safeguards: unique accounts, MFA, least-privilege access, audit logging, encryption in transit and at rest (45 CFR 164.312).
- Incident response and breach notification procedures, including the 60-day outer limit for notifying customers (45 CFR 164.410).
- Backups and a tested recovery plan (45 CFR 164.308(a)(7)).
The order to build it in
1. Map where PHI goes
List every system, vendor and person that touches PHI, and draw the data flow. Remove PHI from anywhere it does not need to be, such as logs, analytics and support tickets. Less PHI means a smaller program.
2. Name a security officer and run the risk analysis
Assess threats and vulnerabilities for each system in the map, rate the risks and decide what you will do about each. Have the security officer sign it.
3. Close the high risks first
MFA everywhere, offboarding that actually removes access, encryption, audit logs, backups you have restored at least once.
4. Adopt policies and train the team
Start from templates, edit them to match reality, get acknowledgements and run the training.
5. Sort out BAAs
Sign BAAs with the vendors in your PHI data flow and confirm which of their services are covered. Prepare your own customer BAA template.
6. Package the evidence
Put the risk analysis summary, policies, subprocessor list and security overview in one place a buyer can review, such as a trust center.
Myths that cost startups deals
- “We can get HIPAA certified.” HHS does not certify anyone. A badge from a private company is not something HHS recognises.
- “Our cloud is HIPAA compliant, so we are.” The cloud BAA covers the provider’s side only. Your configuration and your company are your responsibility.
- “Encryption is addressable, so it is optional.” Addressable means implement it or document an equivalent alternative and why. In practice, buyers expect encryption.
- “We will do HIPAA after the pilot.” If the pilot involves real PHI, the obligations apply from the first record.
- “SOC 2 covers HIPAA.” The controls overlap, but SOC 2 does not include BAAs, HIPAA breach notification or the HIPAA risk analysis.
What about the proposed Security Rule changes?
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.
How Shieldra helps a startup get ready
Shieldra gives a small team the structure of a HIPAA program without hiring a consultant to build it.
- A HIPAA readiness score and roadmap that show what is missing and what to do next.
- HIPAA Security Risk Analysis with Security Officer sign-off and a shareable report.
- HIPAA policy templates to adopt, plus security awareness training with completion records.
- Vendor BAA tracking with expiring BAAs highlighted, and document and evidence storage.
- Integrations with GitHub, KnowBe4 and MDM tools (Jamf, Kandji, Intune, JumpCloud, Google) to pull in evidence you already have. Cloud and identity-provider integrations are on the roadmap; today that evidence is uploaded.
- A trust center link to hand to a buyer, with gated documents released on request.
- Shieldra is a no-PHI service: keep patient data out of it.
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
Does HIPAA apply to my health-tech startup?
It applies if you handle PHI on behalf of a covered entity (you are a business associate) or if you are a covered entity yourself. Direct-to-consumer apps with no covered entity involved are often outside HIPAA but may be covered by the FTC Health Breach Notification Rule and state health-privacy laws.
Is there an official HIPAA certificate for startups?
No. HHS does not certify or endorse anyone for HIPAA. What hospitals accept is evidence: a signed BAA, a current risk analysis, written policies, training records and, for larger buyers, often a SOC 2 Type II report.
What is the very first HIPAA document a startup should produce?
The risk analysis required by 45 CFR 164.308(a)(1)(ii)(A). It forces you to map where PHI lives, and almost every hospital security review asks for it or a summary of it.
Do we need a dedicated compliance hire?
Not at first. HIPAA requires a designated security officer, which can be a founder or the CTO. What matters is that the role is written down and the work actually happens.
Should a startup do SOC 2 or HIPAA first?
If you handle PHI, HIPAA obligations apply now, so start there. Many hospitals then ask for SOC 2, and most of the HIPAA technical work carries over. See our SOC 2 for health-tech guide for sequencing.