HIPAA-compliant app development: a practical guide

When health apps fall under HIPAA, the safeguards they need, how to choose vendors and what applies when HIPAA doesn't, including FTC and state health privacy laws.

By the UK Technology Hub teamPublished 4 minute read

The short answer

HIPAA applies when an app creates, receives, stores or transmits protected health information for a covered entity, such as a healthcare provider or health plan, or their business associates. Compliant apps need administrative, physical and technical safeguards, signed business associate agreements with vendors handling PHI, and careful logging and access control. Health apps outside HIPAA still face FTC and state health privacy rules.

Health apps can improve care and save time, but they handle some of the most sensitive data there is. In the US, getting privacy and security right isn't optional. This guide explains the basics. It's general information, not legal advice; health privacy law is complex, so involve a qualified attorney and compliance expert.

Does HIPAA apply to your app?

HIPAA applies to covered entities, meaning healthcare providers that conduct certain electronic transactions, health plans and healthcare clearinghouses, and to their business associates, meaning vendors that handle protected health information (PHI) on their behalf.

Your app is likely in scope if, for example:

  • A clinic uses it to share test results with patients.
  • A health plan uses it to manage member claims.
  • A telehealth provider uses it to run video visits and store notes.

Your app may not be covered by HIPAA if a consumer uses it independently, such as a fitness tracker or a period-tracking app not offered on behalf of a provider. But that doesn't mean there are no rules, as explained below.

What counts as PHI?

Protected health information is individually identifiable health information, such as names, addresses, dates, phone numbers, email addresses, medical record numbers and many other identifiers, linked to health conditions, care or payment. Even appointment details can be PHI.

The safeguards you need

HIPAA's Security Rule requires administrative, physical and technical safeguards. In app terms, that typically includes:

Technical

  • Encryption of data in transit and at rest.
  • Unique user accounts with strong authentication, including multi-factor authentication.
  • Role-based access, so people see only what they need.
  • Automatic logoff and session management.
  • Audit logs recording who accessed or changed PHI.
  • Secure APIs and protection against common vulnerabilities.
  • Regular backups and a tested disaster recovery plan.

Administrative

  • A documented risk analysis, reviewed regularly.
  • Security policies and staff training.
  • Incident response and breach notification procedures.
  • Vendor management.

Physical

  • Hosting in facilities with appropriate physical security, which reputable cloud providers offer.
  • Device policies for staff who access PHI.

Business associate agreements

Any vendor that handles PHI on your behalf, such as cloud hosting, email, SMS, analytics, support tools or AI services, must sign a business associate agreement (BAA). Major cloud providers offer BAAs for specific eligible services. Many popular tools, including some analytics and marketing platforms, either won't sign BAAs or restrict what data you can send.

Watch out for tracking technologies

Analytics pixels and tracking scripts on patient portals, apps and some web pages can send health information to third parties. HHS and the FTC have both warned about this, and it has led to enforcement actions and lawsuits. Audit every third-party script in your app and website.

AI features and PHI

AI can help with transcription, summarization and patient communication, but sending PHI to an AI service requires a BAA and careful configuration. Check data retention, training use and access controls before connecting any AI provider.

When HIPAA doesn't apply

Consumer health apps outside HIPAA still face rules:

  • The FTC Health Breach Notification Rule requires many health apps not covered by HIPAA to notify users and the FTC of breaches, which include unauthorized disclosures such as sharing data with advertisers without permission. The FTC updated the rule in 2024 to clarify that it covers health apps.
  • The FTC Act prohibits unfair or deceptive practices, including misleading privacy promises.
  • State laws such as Washington's My Health My Data Act and consumer privacy laws in many states treat health data as sensitive. Our guide to website and app privacy laws in the US covers the state picture.

Building it right

  1. Map your data: what health data you collect, where it goes and who can see it.
  2. Minimize it: collect only what you need.
  3. Choose HIPAA-eligible services and sign BAAs.
  4. Design security into the architecture from day one.
  5. Test with security reviews and penetration testing.
  6. Document everything: risk analysis, policies, training and vendor agreements.
  7. Monitor and update as threats and rules change.

Costs

Compliance adds cost through specialized hosting, security work, testing and documentation. Our guide to app development costs explains how security requirements affect budgets.

How we help

Our app development team builds health and wellness apps with security designed in, using HIPAA-eligible infrastructure and vendors that sign BAAs. We build web apps such as patient portals and mobile apps for patients and clinicians, and we work alongside your compliance and legal advisers.

Frequently asked questions

Is there a HIPAA certification for apps?

No official government certification exists. Compliance is shown through safeguards, documentation, risk analysis and agreements, sometimes backed by third-party audits.

Do I need a BAA with my hosting provider?

Yes, if the provider stores or processes PHI on your behalf. Major cloud providers offer BAAs for eligible services.

Does HIPAA apply to fitness apps?

Usually not, unless offered on behalf of a covered entity. FTC rules and state health privacy laws may still apply.

This guide is general information, not legal, tax or financial advice, and details such as prices, features and rules can change. Product and company names mentioned are trademarks of their respective owners and are used only to identify those products; UK Technology Hub is not affiliated with or endorsed by them.

Related guides

All web & mobile apps guides for US businesses