Many health startups assume they are “HIPAA companies” because they handle health data. Others assume they are exempt because they sell to consumers. Both assumptions are often wrong. HIPAA applies based on who you are and on whose behalf you handle data — not on how sensitive the data is.
Our HIPAA consulting for healthcare startups starts with that determination, because it drives everything else: whether you need business associate agreements, which rules apply directly to you, and whether a different regime such as the FTC Health Breach Notification Rule is the one you actually need to plan for. Once the role is clear, we help you build a program that fits your stage and does not stall the product roadmap.
Step one: does HIPAA apply to you?
This analysis turns on contracts and facts, so we document it with you and recommend confirming the conclusion with your legal counsel.
- 1
Are you a health care provider, health plan or clearinghouse?
If you furnish care and conduct standard electronic transactions (such as billing insurers), or you are a health plan or clearinghouse, you are likely a covered entity.
- 2
Do you handle PHI on behalf of a covered entity?
If a provider, plan or another business associate gives you PHI so you can perform a function or service for them, you are likely a business associate.
- 3
Do you collect health data directly from consumers for your own product?
If users give you their data and you are not acting for a covered entity, HIPAA often does not apply to that data — even if it is health information.
- 4
Do you have more than one business line?
A company can be a business associate for its enterprise customers and outside HIPAA for its consumer app. Data flows need to be separated and documented accordingly.
When HIPAA doesn’t apply, other rules may
Some states have also enacted consumer health data laws — Washington’s My Health My Data Act is a frequently cited example — and comprehensive state privacy laws often treat health data as sensitive. These laws differ significantly, so we flag them for review by your counsel rather than offering legal conclusions.
What to build at each stage
| Stage | Focus | Typical deliverables |
|---|---|---|
| Pre-launch / prototype | Avoid real PHI in development; choose infrastructure and vendors that will sign BAAs | Data flow diagram, vendor shortlist with BAA status, role determination memo |
| First healthcare customer | Meet the BAA you are about to sign; answer the security questionnaire honestly | Initial risk analysis, core policies, security and privacy officer named, workforce training |
| Scaling (multiple customers) | Repeatability and evidence | Risk management plan, access reviews, incident response testing, subcontractor BAAs |
| Enterprise / growth | Customer audits and investor diligence | Updated risk analysis, documented evaluation under §164.308(a)(8), optional third-party attestations such as SOC 2 or HITRUST |
Risks specific to early-stage teams
- Production PHI copied into development or analytics environments, or shared in chat tools without a BAA.
- Engineers with standing administrative access to production databases.
- Product analytics, session replay or advertising SDKs collecting health information from logged-in users.
- Signing a customer’s BAA with commitments — breach notice windows, audit rights, offshore restrictions — the team cannot meet.
- Treating a cloud provider’s BAA as the whole compliance story. Cloud security follows a shared-responsibility model.
Common misconceptions we correct
- “We have a HIPAA certification.” There is no official HIPAA certification for companies or products.
- “We use a HIPAA-eligible cloud, so we’re compliant.” The provider’s BAA covers its responsibilities, not your configuration, access control or logging.
- “SOC 2 means we meet HIPAA.” SOC 2 is a useful attestation and good practice, but it is not a HIPAA requirement and does not map one-to-one to the Security Rule.
- “Consumer data is never regulated.” It may not be regulated by HIPAA, but FTC and state rules can still apply.
How we tailor startup engagements
Startup engagements are designed to be short and practical. A role determination and scoped HIPAA gap analysis tells you what you need now versus later. For companies about to sign their first BAA, a focused HIPAA risk assessment and core HIPAA policies and procedures usually come next, written for a small team rather than a hospital.
Founders often ask what this will cost before they budget. We explain the cost drivers — scope, number of systems and vendors, existing documentation — in our HIPAA compliance cost resource, and our HIPAA compliance for startups guide goes deeper on sequencing.
What customers and investors will ask for
Two audiences tend to test a startup’s HIPAA position early. Health system customers send security questionnaires and BAA templates during procurement, and they expect specific answers: where data is hosted, who can access it, how access is logged, how fast you will report incidents. Investors conducting diligence ask whether the company understands its regulatory role and whether any past incidents or unreported data flows could become liabilities.
In both cases, documents written before the question was asked carry far more weight than answers assembled overnight. A short role determination memo, a current risk analysis, a data flow diagram, a list of subcontractors with BAA status and an incident log give you consistent answers and show that compliance is being managed, not improvised. None of these is a certification, and no one should describe them as one, but together they are the evidence experienced buyers look for.
A starting checklist for founders
- Write down, in one paragraph, whether you are a covered entity, business associate, neither or a mix — and why.
- Draw a data flow diagram showing where health data enters, where it is stored and which vendors see it.
- Confirm BAAs are available from your cloud, email, support desk, logging and analytics vendors before PHI touches them.
- Keep real PHI out of development and test environments.
- Name a security officer and privacy officer, even if they are founders.
- Read your first customer’s BAA line by line before signing.
Frequently asked questions
We store health data. Doesn’t that make us subject to HIPAA?
Not automatically. HIPAA applies to covered entities and to business associates handling PHI on their behalf. A consumer app collecting data directly from users may fall outside HIPAA but within the FTC Health Breach Notification Rule or state laws.
Do we need SOC 2 to sell to hospitals?
HIPAA does not require SOC 2. Many hospital buyers ask for it or a similar attestation as part of vendor risk management, so it can be commercially useful. It complements, rather than replaces, HIPAA risk analysis and documentation.
Can you certify that our startup is HIPAA compliant?
No one can. HIPAA has no official certification, and compliance is ongoing. We can assess your program, document gaps and help you build the evidence customers and regulators expect to see.
When should a startup first engage a HIPAA consultant?
Ideally before you choose infrastructure or sign your first BAA, because those decisions are harder to reverse later. A short role determination early can save significant rework.
Authoritative sources
- FTC — Health Privacy guidance
- HHS — HIPAA for Professionals
- HHS — Guidance on HIPAA and Cloud Computing
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.