HIPAA Rules for Mobile Health Apps: When They Apply
Does HIPAA apply to your health app? A decision table for clinic, consumer and wellness apps, the FTC rule that covers the rest, and what to build in.
By the Clarigo Editorial Team · November 18, 2026 7 min read
Short answer: HIPAA applies to a mobile health app when the app is offered by, or works on behalf of, a covered entity such as a clinic, hospital or health plan. A consumer app that people download and use for themselves is usually outside HIPAA, but if it keeps health records drawn from more than one source it is likely covered by the FTC's Health Breach Notification Rule (16 CFR Part 318). Covered apps must meet the HIPAA Security Rule: access control, audit logs, integrity, authentication and transmission security, with BAAs for every vendor that touches the data.
The question "is my app HIPAA compliant?" usually comes before the more useful one: "does HIPAA apply to my app at all?" The answer depends less on the data than on who the app is working for. A blood pressure reading in a clinic's patient app is protected health information (PHI). The same reading in an app a person bought from an app store usually is not.
This guide gives you the test, a decision table, the alternative rule for consumer apps, and the build requirements for apps that are covered. It is general information, not legal advice; confirm your position with a healthcare lawyer.
The test: who is the app working for?
HIPAA regulates covered entities and their business associates. Under the definitions in 45 CFR 160.103, covered entities are health plans, health care clearinghouses, and health care providers that transmit health information electronically in connection with standard transactions such as claims. A business associate creates, receives, maintains or transmits PHI on a covered entity's behalf.
So ask three questions about your app:
- Who offers it? If a clinic, hospital or health plan gives the app to its patients or members, HIPAA applies, and you as the developer are its business associate.
- Whose data flows in? If the app receives records from a covered entity because that entity hired you, HIPAA applies to that data.
- Who chose it? If a person found the app themselves and enters or imports their own data, the app is usually not working for a covered entity, so HIPAA usually does not apply.
The definition also names one edge case explicitly: a company that offers a personal health record to individuals on behalf of a covered entity is a business associate.
Decision table
| App scenario | HIPAA applies? | What likely applies instead or as well |
|---|---|---|
| Patient app a clinic gives its patients for booking, messages and results | Yes. The clinic is a covered entity, the developer is a business associate | BAA between clinic and developer, and down to its vendors |
| Telehealth platform licensed to providers | Yes, for the providers' patient data | BAAs with video, messaging and hosting vendors |
| Health plan's member app | Yes | Same as above |
| Remote monitoring app prescribed by a provider, data sent to the provider | Yes, for the provider's data | BAAs with device data and cloud vendors |
| Fitness, sleep or diet tracker people download themselves | Usually no | FTC Health Breach Notification Rule if it is a personal health record; FTC Act; state law |
| Symptom checker or AI health chatbot for consumers | Usually no | FTC rule and FTC Act; state health privacy laws |
| Consumer app a patient connects to their provider to import records | Usually no for the app | FTC rule likely, because the app draws data from multiple sources |
| Employee wellness app | It depends on whether it is run through a group health plan | Get legal advice on the plan structure |
If two rows seem to fit, the stricter one usually wins in practice, because enterprise buyers will ask for a BAA anyway.
When HIPAA does not apply: the FTC Health Breach Notification Rule
Consumer health apps are not unregulated. The Health Breach Notification Rule, 16 CFR Part 318, applies to vendors of personal health records, PHR related entities and third party service providers. It expressly does not apply to HIPAA covered entities, or to any entity to the extent it acts as a business associate. In other words, it fills the gap HIPAA leaves.
Key points from the rule text:
- A personal health record is an electronic record of identifiable health information that can draw information from multiple sources and is managed, shared and controlled by or primarily for the individual. An app that pulls data from a wearable, a phone's health store and a user's own entries can meet that test.
- Apps are named. The definition of health care services or supplies includes any website, mobile application or internet-connected device that tracks diseases, conditions, medications, vital signs, symptoms, fitness, fertility, sexual health, sleep, mental health, diet and similar.
- A breach is not only a hack. A breach of security includes an unauthorized disclosure, so sharing data with an advertising or analytics partner without the person's authorization can count.
- Deadlines. Notices to individuals go out without unreasonable delay and no later than 60 calendar days after discovery. Breaches affecting 500 or more people must be reported to the FTC at the same time, and prominent media must be told when 500 or more residents of one state are affected.
The FTC also enforces against unfair or deceptive practices more broadly, and several US states have their own health data laws. Treat "not HIPAA" as "different rules", not "no rules".
What HHS says about apps patients choose
HHS has published guidance on health apps and HIPAA, including scenarios about patients using third-party apps. The general principle matches the table above: when a patient directs their provider to send their records to an app the patient picked, and the app does not work for the provider, the app is not the provider's business associate. Once the data is in the app, HIPAA no longer governs what that app does with it. Read the HHS pages for the exact scenarios before relying on this for your product.
Build requirements for apps that are covered
If HIPAA applies, the Security Rule technical safeguards in 45 CFR 164.312 set the baseline. Here is how each one translates to a mobile app.
| Safeguard (164.312) | Required or addressable | What it means in a mobile app |
|---|---|---|
| Unique user identification | Required | Every user has their own account; no shared clinic logins |
| Emergency access procedure | Required | A documented way for authorised staff to reach data in an emergency |
| Automatic logoff | Addressable | Session timeout and re-lock with PIN or biometrics after inactivity |
| Encryption and decryption | Addressable | Encrypt data on the device (iOS Keychain, Android Keystore, encrypted databases) and on the server |
| Audit controls | Required standard | Server-side logs of who viewed, changed or exported which record |
| Integrity | Required standard | Protect records from improper change; signed or checksummed data where it matters |
| Person or entity authentication | Required standard | Strong sign-in, with multi-factor for staff accounts |
| Transmission security | Required standard; encryption addressable | TLS for every API call; no PHI over plain SMS or email |
"Addressable" does not mean optional. It means you must implement it if it is reasonable and appropriate, or document why not and what you do instead. For a phone that can be lost, encryption is hard to argue against.
Mobile-specific traps
- Push notifications. Lock screens show them. Send "You have a new message", not a diagnosis or a result.
- Third-party SDKs. Analytics, crash reporting and advertising SDKs can collect identifiers and screen content. Remove them from PHI screens, or use vendors that sign a BAA.
- Logs and caches. Keep PHI out of device logs, screenshots in the app switcher and web view caches.
- Offline data. Store only what the user needs offline, encrypted, and wipe it on sign-out.
- Backend vendors. Hosting, email, SMS, video and AI model providers that see PHI each need a BAA.
Underneath all of this sits the risk analysis that the administrative safeguards require. Our HIPAA compliance assessment starts there, and our HIPAA-compliant app development guide covers the full build.
Choosing a stack
HIPAA does not prefer a framework. Native, React Native and Flutter apps can all meet the safeguards above; what matters is secure storage on the device, a well-designed backend and disciplined vendor choices. If your app includes video visits, see our telehealth app development service; if it includes an assistant that answers patients, see HIPAA-compliant chatbot development.
Our approach
We build healthcare apps as a healthcare app development company with our own products in production. Clarigo Clinic OS runs front-office automation for specialty clinics, with a person approving anything medical or financial, a full audit trail and a BAA signed before patient data is touched. Clarigo EHR adds an AI scribe that drafts notes for clinicians to sign, with HL7 and FHIR interfaces, encryption and role-based access.
About Clarigo Infotech
Clarigo Infotech is an AI-first software and app development company in Indore, India. Since 2016, our in-house senior team has delivered 600+ projects for clients in 20+ countries. Our HIPAA-trained team has HL7 and FHIR integration experience, and we offer 24/7 support. Senior engineers typically cost US$25 to US$49 per hour, a first version (MVP) is usually live in roughly 25 to 30 days, and you own the source code. Not sure which rules apply to your app? Tell us what you are building.
Frequently asked questions
Does HIPAA apply to all health apps?
+
No. HIPAA applies when the app is offered by, or works on behalf of, a covered entity such as a clinic, hospital or health plan. A consumer app that people download and use for themselves is usually outside HIPAA, though other rules such as the FTC Health Breach Notification Rule and state laws can apply.
What is the FTC Health Breach Notification Rule?
+
It is 16 CFR Part 318. It covers vendors of personal health records, PHR related entities and their service providers that are not HIPAA covered entities or acting as business associates. It requires notifying individuals, the FTC and in some cases the media after a breach, which includes unauthorized disclosures as well as hacks.
Is a fitness tracker app covered by HIPAA?
+
Usually not, if people buy and use it for themselves. It becomes covered when a provider or health plan offers it or it works on their behalf. A consumer fitness app that draws data from several sources is likely within the FTC Health Breach Notification Rule instead.
Is encryption required for a HIPAA mobile app?
+
In the Security Rule, encryption is an addressable specification, which means you must implement it if reasonable and appropriate or document an equivalent alternative. For data on phones and in transit over the internet, encryption is the practical standard.
Can I use analytics SDKs in a HIPAA app?
+
Only with care. Analytics and advertising SDKs can collect identifiers and screen content. Keep them off screens that show PHI, or use a vendor that will sign a business associate agreement and configure it so PHI is not collected.
From our own work
Projects our team has delivered that relate to this article.
Healthcare
Clarigo Clinic OS
Our own product: an automation tool that handles a clinic's front-office work (calls, intake, insurance checks, prior authorizations, denied claims and reminders) while the EHR and staff stay exactly as they are.
Read the case study →
Healthcare
Clarigo EHR
Our own cloud EHR: clinical records, scheduling, billing and patient engagement in one system, with AI built into every step and HL7/FHIR interoperability, built to HIPAA compliance.
Read the case study →
About the author
Clarigo Editorial Team
Written by the team at Clarigo Infotech, an AI-first software and app development company in Indore, India. Since 2016 our in-house team has delivered 600+ projects for clients in 20+ countries, and our articles draw on that work. Read about the company, or see our case studies and portfolio.
Planning something like this?
Get a free consultation. A senior engineer replies within one working day with a scoped plan.
