HIPAA-Compliant App Development: Requirements, Checklist and Costs
A HIPAA-compliant app protects electronic protected health information (ePHI) according to the HIPAA Privacy, Security and Breach Notification Rules. That means signing business associate agreements (BAAs) with every vendor that handles PHI, performing a risk analysis, and implementing administrative, physical and technical safeguards such as access controls, encryption, audit logging and breach response. HIPAA applies when your app creates, receives, stores or transmits PHI for or as a covered entity (healthcare providers, health plans, clearinghouses) or their business associates.
Does Your App Need to Be HIPAA Compliant?
Ask these questions:
| Question | If yes |
|---|---|
| Is your company a healthcare provider, health plan or clearinghouse? | You're a covered entity; HIPAA applies |
| Do you build or operate the app for a covered entity, and handle PHI on its behalf? | You're a business associate; HIPAA applies, and a BAA is required |
| Does the app exchange data with a provider's EHR on the provider's behalf? | Likely a business associate |
| Is it a consumer app where users enter their own health data, with no covered-entity relationship? | HIPAA usually does not apply, but other laws may (see below) |
Other health data laws: the FTC Health Breach Notification Rule covers many health apps outside HIPAA, and state laws such as Washington's My Health My Data Act regulate consumer health data.
| App example | HIPAA usually applies? |
|---|---|
| Hospital patient portal app | Yes |
| Telehealth platform used by clinics | Yes |
| Remote patient monitoring for a provider | Yes |
| Health plan member app | Yes |
| Consumer fitness or calorie tracker | Usually no (FTC rules may apply) |
| Consumer app that lets users download their records via a patient-access API | Often no for the app itself; check carefully |
What Counts as PHI?
What Counts as PHI?
The Three HIPAA Rules for App Developers
| Rule | What it requires |
|---|---|
| Privacy Rule | Limits on how PHI is used and disclosed; patient rights to access and amend records; minimum necessary use |
| Security Rule | Administrative, physical and technical safeguards for ePHI |
| Breach Notification Rule | Notifying individuals, HHS and, in some cases, the media after a breach of unsecured PHI |
Security Rule Safeguards, Translated for Developers
| Requirement | What your team does |
|---|---|
| Risk analysis & risk management | Formal risk assessment before launch and after major changes |
| Security officer | Named person responsible for security |
| Workforce training | HIPAA and security training for everyone with PHI access |
| Access management | Formal process to grant, review and revoke access |
| Contingency planning | Backups, disaster recovery, emergency mode |
| Business associate agreements | A BAA with every vendor that touches PHI |
Physical safeguards
| Requirement | What your team does |
|---|---|
| Facility access | Use HIPAA-eligible data centres (cloud providers) |
| Workstation & device security | Encrypted, managed laptops; screen locks |
| Device & media controls | Secure disposal; no PHI on personal devices |
Technical safeguards
| Requirement | What the app does |
|---|---|
| Access control | Unique user IDs, role-based access, automatic logoff |
| Authentication | Strong passwords + MFA; biometrics on mobile |
| Encryption | TLS 1.2+ in transit; AES-256 at rest, including mobile local storage |
| Audit controls | Immutable logs of who accessed or changed PHI, and when |
| Integrity | Protection against improper alteration; checksums, versioning |
| Transmission security | Certificate pinning; secure APIs; no PHI in push notifications or URLs |
HIPAA App Development Checklist
HIPAA App Development Checklist
HIPAA-Eligible Infrastructure and the BAA Rule
Major cloud providers, including AWS, Microsoft Azure and Google Cloud, sign BAAs and publish lists of HIPAA-eligible services. Only use the services covered by the BAA for PHI.
| Component | What to check |
|---|---|
| Cloud hosting & databases | A BAA is signed, and the service is on the eligible list |
| Email / SMS / push notifications | The vendor signs a BAA, or you send no PHI through it |
| Video (telehealth) | A BAA-covered video provider |
| Analytics & crash reporting | Configure to exclude PHI, or use a BAA-covered tool |
| AI / LLM APIs | Use only enterprise offerings that sign BAAs; never send PHI to consumer AI tools |
| Customer support tools | A BAA, or strict PHI exclusion |
Breach Notification Timeline
| Who to notify | When |
|---|---|
| Affected individuals | Without unreasonable delay, and no later than 60 days after discovery |
| HHS (500+ individuals) | Within 60 days of discovery |
| HHS (fewer than 500) | Within 60 days after the end of the calendar year (annual log) |
| Media | When a breach affects more than 500 residents of a state or jurisdiction |
| Covered entity (if you're a business associate) | Without unreasonable delay, and within 60 days of discovery (or sooner per the BAA) |
How to Build a HIPAA-Compliant App in 6 Phases
Compliant architecture
Secure development
Testing & validation
Launch readiness
Operate & monitor
Typical HIPAA-Ready Tech Stack
| Layer | Examples |
|---|---|
| Mobile | Swift / Kotlin or Flutter / React Native with encrypted local storage (Keychain / Keystore) |
| Back end | Node.js, Java, Python or .NET in private subnets |
| Database | Encrypted PostgreSQL or another eligible managed database |
| Interoperability | HL7 FHIR APIs, SMART on FHIR authorization |
| Identity | OAuth 2.0 / OpenID Connect with MFA |
| Logging & monitoring | Centralized, access-controlled, PHI-scrubbed logs |
| Cloud | AWS, Azure or GCP, using BAA-covered services |
How Much Does a HIPAA-Compliant App Cost?
| App type | Typical cost | Timeline |
|---|---|---|
| HIPAA-compliant MVP (patient app + basic portal) | $50,000–$100,000 | 4–6 months |
| Telehealth platform | $80,000–$150,000+ | 5–8 months |
| Remote patient monitoring with device integration | $100,000–$200,000+ | 6–10 months |
| EHR-integrated enterprise platform | $150,000+ | 8–12+ months |
Common HIPAA App Mistakes
Common HIPAA App Mistakes
Build Your Healthcare App on a Compliant Foundation
Our team designs HIPAA-aligned architecture, PHI-safe workflows and audit-ready documentation from day one.














