HIPAA vs GDPR for Health Apps: Side-by-Side Guide
HIPAA vs GDPR for health apps: scope, consent, patient rights, breach deadlines and data transfers side by side, plus what to build to satisfy both.
By the Clarigo Editorial Team · November 18, 2026 7 min read
Short answer: HIPAA protects health information held by US health plans, providers and their vendors, and lets them use it for treatment, payment and operations without asking. GDPR protects any personal data of people in the EU, treats health data as a special category that needs both a legal basis and a specific condition such as explicit consent, gives wider rights including erasure, and gives you 72 hours, not 60 days, to report a breach to the regulator. A health app serving both markets has to design to the stricter rule on each point.
HIPAA and GDPR are often described as "the US and EU versions of the same thing". They are not. HIPAA is a sector rule about who holds the data. GDPR is a general rule about whose data it is. That difference changes almost every answer below.
This comparison is general information, not legal advice. The EU rules are summarised from the European Commission's own guidance pages and the US rules from the regulation text on ecfr.gov. National laws in EU countries add to the GDPR for health data, so check the country you are launching in.
HIPAA vs GDPR at a glance
| Topic | HIPAA (US) | GDPR (EU) |
|---|---|---|
| Who it applies to | Covered entities (health plans, clearinghouses, providers using standard electronic transactions) and their business associates | Any organisation processing personal data in the context of an EU establishment, or offering goods or services to, or monitoring, people in the EU |
| Data covered | Protected health information held by those entities | All personal data; health data is a special category |
| Consumer health apps | Usually outside HIPAA | Inside GDPR if they serve people in the EU |
| Basis for using data | Treatment, payment and health care operations allowed without authorization; written authorization for many other uses | A lawful basis for all processing, plus a specific condition for health data, such as explicit consent |
| Individual rights | Access, amendment, accounting of disclosures, restrictions, confidential communications | Information, access, rectification, erasure, restriction, portability, objection, safeguards on automated decisions |
| Response time | Access within 30 days, one extension allowed | Without undue delay, in principle within one month |
| Breach: regulator | HHS: at the same time as individual notices for 500+ people; annually for smaller breaches | Supervisory authority without undue delay, at the latest within 72 hours, if the breach poses a risk |
| Breach: individuals | Without unreasonable delay, no later than 60 days | Without undue delay if the breach poses a high risk |
| Vendors | Business associate agreement | Data processing agreement with each processor |
| Transfers abroad | No HIPAA rule that keeps data in the US | Restricted: adequacy decision or appropriate safeguards required |
| Dedicated privacy officer | Privacy and security officials required | Data Protection Officer when core activities include large-scale processing of sensitive data |
Scope: sector rule vs people rule
HIPAA asks "who holds this data?" If it is a covered entity or its business associate, the rules apply. If it is a consumer app a person chose for themselves, they usually do not, and other US rules take over. We explain that split in our guide to healthcare app development.
GDPR asks "whose data is this?" The European Commission explains that the GDPR applies to a company processing personal data in the context of a branch established in the EU, wherever the processing happens, and to a company established outside the EU that offers goods or services (paid or free) to, or monitors the behaviour of, individuals in the EU. An Indian or US developer running an app for patients in Germany is inside GDPR, even with no office in Europe.
Consent and legal basis
Under HIPAA, a covered entity can use and disclose PHI for treatment, payment and health care operations without the patient's authorization. Marketing, sale of PHI and many other uses need a written authorization.
Under GDPR, every use of personal data needs a lawful basis, and health data needs more. The Commission's page on legal grounds for processing lists the conditions for special categories of data, starting with the individual's explicit consent, and notes that EU or national law may impose further conditions on health, genetic and biometric data. Its own example is a doctor logging symptoms and prescribed medication, which counts as health data.
For an app, the practical result is that the HIPAA "it's for treatment" reasoning does not carry over. Decide the legal basis and the special-category condition for each purpose (care, reminders, analytics, research) and record it.
Patient rights and response times
HIPAA gives patients a right to access their records. Under 45 CFR 164.524, the covered entity must act on an access request within 30 days, with one extension allowed if it explains the delay in writing. Patients can also request amendments and an accounting of disclosures. There is no general HIPAA right to have records deleted.
GDPR goes further: access, rectification, erasure (the "right to be forgotten"), restriction, portability and objection, plus limits on decisions based solely on automated processing. The Commission's guidance on dealing with requests from individuals says organisations must reply without undue delay and in principle within one month, should offer electronic means to make requests where data is processed electronically, and may only process health data in automated decisions with explicit consent or a substantial public interest under law, with safeguards.
Erasure is the right that most often surprises US teams. Medical record retention laws can override it, but your app still needs a working delete path for everything that is not a legally required record.
Breach notification timelines
This is the biggest operational difference.
Under the GDPR, the Commission's obligations page states that a breach likely to pose a risk to individuals must be notified to the supervisory authority without undue delay and at the latest within 72 hours of becoming aware of it. If the risk is high, the individuals must be told too. A processor must notify the controller of every breach.
Under HIPAA, individuals must be notified without unreasonable delay and no later than 60 days after discovery, and 45 CFR 164.408 sets the notice to HHS: at the same time as the individual notices for breaches affecting 500 or more people, and within 60 days after the end of the calendar year for smaller ones.
If you serve both markets, plan for 72 hours. That means logging good enough to tell quickly what was accessed, an on-call person, and a pre-agreed decision path.
Vendors and transfers
HIPAA uses business associate agreements; GDPR uses data processing agreements under which processors act only on the controller's instructions. A vendor serving both markets often signs both, and they are not interchangeable.
On transfers, HIPAA has no rule that keeps PHI inside the United States, though your BAAs and customer contracts may. GDPR restricts transfers outside the EU. The Commission's adequacy decisions page lists the countries it has recognised as adequate, including the United States for commercial organisations participating in the EU-US Data Privacy Framework. Transfers to other countries need safeguards such as standard contractual clauses. Choose hosting regions and support access with this in mind; our HIPAA-compliant cloud hosting service sets up separate regions where both rules apply.
When both rules apply at once
A US clinic group with patients who live in the EU, or a European telehealth service using a US vendor, can be inside both rules for the same record. Neither law switches the other off. In practice, teams map each requirement to the stricter of the two: the 72-hour regulator deadline from GDPR, the business associate chain from HIPAA, GDPR's erasure and portability rights where no retention law applies, and HIPAA's accounting of disclosures. Write that mapping down once, per feature, so product decisions do not reopen the legal question every sprint.
Building one app for both
- Separate data by region where you can, so each rule applies cleanly.
- Use a consent and purpose register per user, not one checkbox.
- Build export and delete from the start; retrofitting them is expensive.
- Log access in a way that answers "whose data, which fields, when" within hours.
- Keep a vendor list with a BAA and a DPA status for each.
- Run a data protection impact assessment for large-scale health processing, which the Commission's obligations page describes, alongside the HIPAA risk analysis.
A HIPAA compliance assessment is a good starting point for the US side, and our HIPAA-compliant software development work covers both. Video care adds its own requirements, covered in telehealth app development. For the US build in detail, see the HIPAA-compliant app development guide.
Our own products
Clarigo Clinic OS and Clarigo EHR are built on the same principles: role-based access, encryption, a full audit trail, and a person who approves anything medical or financial. Clinic OS signs a BAA before any patient data is touched, and the EHR's AI scribe only drafts notes for clinicians to sign.
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. Launching a health app in the US and Europe? Talk to our team.
Frequently asked questions
What is the main difference between HIPAA and GDPR?
+
HIPAA is a US sector rule that applies to health plans, providers, clearinghouses and their business associates. GDPR is an EU rule that applies to almost anyone processing personal data of people in the EU, and treats health data as a special category with stricter conditions.
Does GDPR apply to a health app built outside the EU?
+
Yes, if the app offers goods or services to people in the EU or monitors their behaviour, even when the company has no EU office. The European Commission's guidance states this directly.
How long do I have to report a breach under HIPAA and GDPR?
+
Under GDPR, a breach likely to pose a risk must be reported to the supervisory authority without undue delay and at the latest within 72 hours. Under HIPAA, individuals must be notified no later than 60 days after discovery, and HHS at the same time for breaches of 500 or more people, or within 60 days after year end for smaller ones.
Is consent required to process health data under GDPR?
+
Not always, but processing health data needs both a lawful basis and one of the specific conditions for special categories. Explicit consent is one condition; others include certain legal obligations and health care purposes under EU or national law.
Does HIPAA give patients a right to delete their data?
+
No. HIPAA gives rights to access, amend and receive an accounting of disclosures, among others, but no general right to erasure. GDPR does include a right to erasure, subject to exceptions such as legal retention duties.
Can EU patient data be stored in the United States?
+
Only under GDPR's transfer rules. The European Commission's adequacy decision covers US commercial organisations participating in the EU-US Data Privacy Framework; transfers to other recipients need safeguards such as standard contractual clauses.
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.
