HIPAA security for health-tech startups: what the Security Rule actually asks for

InsightsHealthcare & HIPAA

HIPAA security for health-tech startups: what the Security Rule actually asks for

Illustration of a medical cross with a padlock and a heartbeat line

Key takeaways

  • First settle whether you are a covered entity, a business associate or neither.
  • "Addressable" safeguards are not optional, and the risk analysis cannot be skipped.
  • Build on MFA, encryption and a current risk analysis now; proposed rule changes point the same way.

Health-tech founders hear "HIPAA compliant" constantly, usually from vendors selling something. The rule itself is more practical than the marketing suggests. It asks you to understand your risks, put reasonable safeguards in place, and be able to show your work. This article covers what the HIPAA Security Rule actually requires and where startups most often go wrong.

First question: does HIPAA apply to you?

HIPAA applies to covered entities (health plans, most healthcare providers and clearinghouses) and to their business associates, the companies that create, receive, store or transmit protected health information on their behalf. If you sell software or services to hospitals, clinics or health plans and you handle patient data, you are almost certainly a business associate, and your customers will ask you to sign a business associate agreement (BAA).

If you sell a health app directly to consumers and no covered entity is involved, HIPAA may not apply at all. Other rules can, such as the FTC's Health Breach Notification Rule and state privacy laws. Get this question answered early, because it shapes everything else.

What the Security Rule covers

The Security Rule protects electronic protected health information (ePHI). It is organized into three groups of safeguards:

  • Administrative safeguards. A documented risk analysis and risk management plan, a named security official, workforce training, access management, incident response, contingency planning and oversight of your own vendors.
  • Physical safeguards. Control over facilities and devices that hold ePHI, including laptops, workstations and how you dispose of old equipment.
  • Technical safeguards. Unique user logins, access controls, audit logs, integrity protections, authentication and protection of data in transit.

Some specifications are labeled "required" and others "addressable." Addressable does not mean optional. It means you must either implement the safeguard or document why an equivalent alternative is reasonable for your situation. Encryption is the classic example: in practice, every startup should encrypt ePHI at rest and in transit.

The one thing you cannot skip: the risk analysis

The risk analysis is the foundation of the rule, and failing to do one is among the most common findings in federal HIPAA enforcement. It means identifying where ePHI lives and moves, what could go wrong, how likely and how harmful each threat is, and what you are doing about it. It should be written down, updated when your systems change, and reviewed at least once a year.

Where startups go wrong

  • Treating a vendor's BAA as their own compliance. Your cloud provider signing a BAA covers their part of the infrastructure. How you configure it, who has access, and how you log activity are still yours.
  • ePHI in the wrong places. Patient data in email, chat tools, spreadsheets, test environments or support tickets that were never meant to hold it.
  • Shared or lingering accounts. Shared admin logins and accounts that stay active after someone leaves undermine the access and audit requirements.
  • No breach plan. A breach of unsecured ePHI triggers notification deadlines, and a business associate has to notify its covered entity customers without unreasonable delay. Decide who does what before you need it.
  • Believing in a certificate. There is no official HIPAA certification. Third-party assessments are useful evidence, but your customers and regulators care about your actual safeguards and documentation.

The rule is changing

In January 2025, HHS proposed the biggest update to the Security Rule in more than a decade. Among other things, it would remove most of the "addressable" flexibility and make safeguards such as multi-factor authentication and encryption explicitly mandatory. The proposal is not final yet, and the current rule remains in force. The practical advice is the same either way: if you build your program on MFA, encryption, asset inventories and a current risk analysis now, you will not have to rebuild it when a final rule arrives.

A practical starting point

  1. Confirm whether you are a covered entity, a business associate or neither.
  2. Map where ePHI enters, lives and leaves your systems, including vendors.
  3. Do a written risk analysis and rank the gaps.
  4. Turn on MFA, encrypt devices and data, and remove shared accounts.
  5. Write short policies that match how you work, and train your team on them.
  6. Sign BAAs with every vendor that touches ePHI, and keep a list.

If you also plan to pursue SOC 2, the two overlap heavily. A single program built once can satisfy both.

How Sollucio can help

Sollucio has delivered HIPAA security programs for healthcare and health-tech companies, from the first risk analysis to the documentation hospital customers ask for during vendor reviews. We focus on safeguards that fit a startup's size and budget, and we can combine HIPAA and SOC 2 into one program so you do the work once.

Next step

Getting HIPAA questions from a customer?

We will help you figure out what applies to you and what to do first.

Book a free consultation
Tom Greer

About the author

Tom Greer

Tom Greer, CISSP, leads Sollucio’s cybersecurity practice and serves as a vCISO for growing and regulated companies. He has delivered SOC 2 and HIPAA programs for multiple organizations and built security programs from the ground up, from policy and gap assessments to roadmaps that teams can actually follow.