Skip to content
HIPAA ComplianceConsulting

HIPAA Resource

HIPAA Compliance for Startups: A Practical, Staged Approach

How early-stage digital health companies can decide whether HIPAA applies, build a right-sized program and get ready for enterprise customer security reviews.

5 min read Reviewed

Early-stage health tech teams usually meet HIPAA in one of two ways: a hospital or clinic prospect sends a business associate agreement and a security questionnaire, or an investor asks whether the company is "HIPAA compliant." Neither moment is a good time to start from zero.

This guide breaks HIPAA work for startups into stages that match how companies actually grow — from deciding whether HIPAA applies, to a minimum viable compliance program, to the controls enterprise customers expect. It is written for founders and early engineering leads. Where legal interpretation is needed, such as whether your product makes you a business associate, confirm with qualified legal counsel.

Key points

  • HIPAA applies to covered entities and their business associates — not to all health data.
  • Most B2B digital health startups are business associates and must meet the Security Rule directly.
  • A minimum viable program starts with a real risk analysis, core policies, training and BAAs.
  • Consumer health apps outside HIPAA may still be subject to the FTC Health Breach Notification Rule and state laws.

Stage 0: Determine whether HIPAA applies

HIPAA regulates covered entities — health plans, health care clearinghouses and health care providers that conduct standard electronic transactions — and business associates that create, receive, maintain or transmit PHI on their behalf (definitions at 45 CFR §160.103). Health data alone does not trigger HIPAA; the relationship does.

Common startup models
Business modelTypical HIPAA statusNotes
SaaS sold to providers or health plans that handles patient dataBusiness associateBAA required with each covered entity customer
Vendor to another business associate (e.g., subprocessor to a billing company)Subcontractor business associateBAA with the upstream business associate (§164.502(e)(1)(ii))
Telehealth company employing or contracting clinicians who bill electronicallyPossibly a covered entityPrivacy Rule patient-facing obligations may apply; confirm with counsel
Direct-to-consumer app where users enter their own data, no provider or plan relationshipOften not subject to HIPAAFTC Act, FTC Health Breach Notification Rule and state laws may apply

Stage 1: Get BAAs right with customers and vendors

If you are a business associate, your customers will send you a BAA, and you will need BAAs with your own vendors that touch PHI — cloud hosting, email, support tooling, analytics and logging services. Required BAA terms are set out in §164.504(e) and §164.314(a). See our detailed guide to the HIPAA business associate agreement.

  • Map which vendors will receive PHI and confirm each will sign a BAA before sending data.
  • Watch customer BAAs for breach notification windows shorter than the regulatory maximum, indemnification and audit-rights clauses — these are business terms to review with counsel.
  • Keep PHI out of tools that will not sign a BAA (many analytics, error-tracking and AI services require specific plans or configurations).
  • Track signed BAAs in one place.

Stage 2: Minimum viable compliance program

Business associates are directly liable for Security Rule compliance and for certain Privacy Rule obligations. A right-sized starting program for a small team includes the following, all documented and retained for six years under §164.316.

  1. 1

    Designate a security official

    Required by §164.308(a)(2). At a startup this is often the CTO or a senior engineer; name them in writing.

  2. 2

    Perform a risk analysis

    Cover all ePHI across your product, cloud environment, corporate systems and endpoints (§164.308(a)(1)(ii)(A)). This is the foundation for every other decision.

  3. 3

    Write a risk management plan

    Prioritize and track fixes for what the analysis finds (§164.308(a)(1)(ii)(B)).

  4. 4

    Adopt core policies

    Access control, acceptable use, incident response, contingency planning, device security, vendor management and sanctions. Tailor them to how you actually work.

  5. 5

    Train the team

    Security awareness training for everyone at onboarding and periodically, with records (§164.308(a)(5)).

  6. 6

    Set up incident and breach procedures

    Know how you will investigate, and how you will notify customers under your BAAs and §164.410.

Stage 3: Security foundations engineers can build in

The Security Rule's technical safeguards (§164.312) require access control, audit controls, integrity, person or entity authentication and transmission security. Encryption is addressable — which means you must assess it and implement it or document an equivalent alternative and your reasoning, not skip it. For a cloud-native product, encryption in transit and at rest is generally expected by customers. See HIPAA technical safeguards for the full list.

  • Single sign-on and MFA for all workforce access to production and corporate systems (recommended practice; widely expected).
  • Least-privilege roles, with production data access limited and logged.
  • Centralized logging with retention and someone assigned to review alerts.
  • Separate production from development and test; keep real PHI out of non-production environments.
  • Managed, encrypted endpoints with automatic updates.
  • Tested backups and a documented restore procedure.

Stage 4: Preparing for enterprise security reviews

Hospital and health plan security teams typically send lengthy questionnaires and ask for evidence. A documented program from the earlier stages answers most of them. What tends to slow deals is the absence of evidence rather than the absence of controls.

  • Keep a current risk analysis summary and policy index ready to share under NDA.
  • Prepare a standard security overview describing architecture, encryption, access and incident response.
  • Maintain a list of subprocessors and confirm BAAs with each.
  • Expect requests for third-party attestations such as SOC 2 or HITRUST, or penetration test summaries. These are market expectations, not HIPAA requirements, and none of them is a "HIPAA certification."

Common startup mistakes

For engagement options designed around these stages, see HIPAA consulting for healthcare startups.

  • Claiming to be "HIPAA certified" on a website — there is no such certification.
  • Assuming a cloud provider's BAA makes the product compliant; the provider covers its part of a shared responsibility model.
  • Sending PHI to tools before a BAA is signed.
  • Copying production data into staging for debugging.
  • Treating compliance as a one-time sprint before a deal closes.

Watching regulatory change

HHS published a proposed update to the Security Rule in the Federal Register on January 6, 2025. It would make several practices more explicit, but it is a proposal, not current law; verify its status before treating any element as a requirement. Building on a solid risk analysis now positions you well regardless of how final rules evolve.

Frequently asked questions

Does my health app need to be HIPAA compliant?

It depends on who you serve. If you create, receive, maintain or transmit PHI on behalf of a covered entity, you are likely a business associate. If consumers use your app on their own without a provider or plan relationship, HIPAA often does not apply, but FTC rules and state laws may. Confirm your status with counsel.

Can a startup be HIPAA certified?

No. HHS does not certify organizations. Startups can complete a risk analysis, implement safeguards, sign BAAs and obtain third-party attestations like SOC 2, but none of these is a HIPAA certification.

Is using a HIPAA-eligible cloud service enough?

No. The cloud provider's BAA covers its responsibilities. You are still responsible for configuring services securely, controlling access, logging, and your own policies and risk analysis.

When should a startup start on HIPAA?

Before the first PHI arrives. Designing access, logging and environment separation early is far easier than retrofitting them before an enterprise deal.

Do we need a privacy officer as a business associate?

The Privacy Rule's privacy official requirement in §164.530(a) applies to covered entities. Business associates must designate a security official and comply with applicable Privacy Rule use and disclosure limits and their BAAs; many still assign someone to own privacy.

Authoritative sources

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.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.