Last updated: November 2026. Written by the Webshark Web Services team.
Quick answer: A HIPAA-compliant healthcare app needs a documented risk analysis, Business Associate Agreements with every vendor that handles PHI, encryption in transit and at rest, unique user authentication with role-based access, audit logging, automatic logoff, secure hosting, backup and disaster recovery, a breach response plan and regular security testing. HIPAA does not certify apps, so compliance is about putting these safeguards in place, documenting them and keeping them up to date.
If your app creates, stores, receives or transmits protected health information (PHI) for a covered entity such as a hospital, clinic or health plan, HIPAA applies to you. Mistakes are expensive: breach investigations, fines and lost trust can sink a healthtech product. This checklist walks product owners, CTOs and developers through every requirement to plan before and during development.
Does HIPAA apply to your healthcare app?
HIPAA applies to covered entities (healthcare providers, health plans and clearinghouses) and their business associates, which includes app developers and vendors that handle PHI on their behalf. A consumer wellness app that users download on their own and that does not share data with a covered entity may fall outside HIPAA, though it can still be covered by FTC rules such as the Health Breach Notification Rule and state privacy laws.
PHI includes any health information linked to an identifier, such as name, email, phone number, device ID, address, dates or photos.
The HIPAA checklist for healthcare apps
1. Administrative safeguards
- ☐ Complete and document a security risk analysis covering every place PHI is stored, processed or transmitted.
- ☐ Create a risk management plan to address the risks you find.
- ☐ Appoint a security officer and privacy officer.
- ☐ Sign Business Associate Agreements (BAAs) with cloud hosting, video, messaging, analytics, email and any vendor that touches PHI.
- ☐ Write security policies and procedures, including access management and incident response.
- ☐ Train your team on HIPAA and security awareness, and keep training records.
- ☐ Define a contingency plan for backups, disaster recovery and emergency operations.
2. Technical safeguards
- ☐ Unique user IDs for every patient, provider and admin.
- ☐ Strong authentication, ideally multi-factor authentication for providers and admins.
- ☐ Role-based access control so users see only the minimum PHI they need.
- ☐ Encryption in transit using TLS 1.2 or higher for all APIs, web and video traffic.
- ☐ Encryption at rest using AES-256 for databases, file storage and backups.
- ☐ Audit logs recording who accessed, created, changed or deleted PHI and when.
- ☐ Automatic logoff after a period of inactivity.
- ☐ Integrity controls to detect improper changes to PHI.
- ☐ Emergency access procedure for authorised staff.
3. Physical safeguards
- ☐ Host on HIPAA-eligible infrastructure (for example AWS, Microsoft Azure or Google Cloud) under a signed BAA.
- ☐ Control and document access to any office devices or servers that handle PHI.
- ☐ Define how devices and media are securely wiped or disposed of.
4. Mobile app specific safeguards
- ☐ Do not store PHI on the device unless necessary; if you must, encrypt it with secure storage (iOS Keychain, Android Keystore).
- ☐ Keep PHI out of push notifications, lock screens and app previews.
- ☐ Never write PHI to logs, crash reports or analytics events.
- ☐ Support remote session revocation if a device is lost.
- ☐ Use certificate pinning and secure API tokens with short expiry.
- ☐ Check every third-party SDK for data collection and BAA availability.
5. Privacy Rule requirements
- ☐ Apply the minimum necessary standard to every feature and report.
- ☐ Provide a clear Notice of Privacy Practices where required by your covered entity client.
- ☐ Allow patients to access and request amendments to their records.
- ☐ Get proper authorization before using PHI for marketing or other non-treatment purposes.
6. Breach notification readiness
- ☐ Have a written incident response plan with named owners.
- ☐ Be able to assess breaches quickly using your audit logs.
- ☐ Notify affected individuals without unreasonable delay and no later than 60 days after discovery, and notify HHS (and media for breaches affecting more than 500 residents of a state or jurisdiction).
7. Testing and ongoing compliance
- ☐ Run vulnerability scans and an annual penetration test.
- ☐ Review access rights and audit logs regularly.
- ☐ Repeat the risk analysis when you add major features, vendors or integrations.
- ☐ Keep all HIPAA documentation for at least six years.
Common HIPAA mistakes in healthcare apps
- Using analytics, chat or email tools that will not sign a BAA
- Showing appointment details or diagnoses in push notifications
- Logging full API requests that include patient data
- Sharing admin accounts instead of unique logins
- Treating “HIPAA-compliant hosting” as full app compliance
What is changing in HIPAA security?
In January 2025, HHS published a proposed update to the HIPAA Security Rule that would make several safeguards, such as encryption, multi-factor authentication, asset inventories and regular testing, more explicit requirements. Until any final rule is published, follow the current rule, but designing your app to meet these stronger expectations now will save rework later.
How much does HIPAA compliance add to app cost?
Building compliance in from the start typically adds 10% to 20% to development cost, plus hosting, testing and audit costs each year. Retrofitting an existing app is usually far more expensive. See our breakdown of telemedicine app development cost in 2027 for real budget figures.
Build a HIPAA-ready healthcare app with Webshark
Webshark designs and develops secure healthcare software for US providers and healthtech companies, with BAAs, encryption, audit logging and documentation built into every project. Explore our healthcare app development services, telemedicine app development and EHR software development.
This checklist is for general guidance and is not legal advice. Work with qualified legal and compliance professionals for your specific situation.
Frequently asked questions
Is there an official HIPAA certification for apps?
No. HHS does not certify apps as HIPAA compliant. Compliance means implementing the required safeguards, signing BAAs and documenting your policies. Third-party audits can help demonstrate your controls.
Do I need a BAA with my cloud provider?
Yes. Any vendor that creates, receives, stores or transmits PHI on your behalf, including your cloud host, must sign a Business Associate Agreement.
Can push notifications include patient information?
They should not. Keep notifications generic, such as “You have a new message”, and show details only after the user logs in.
Does HIPAA require encryption?
Under the current rule encryption is an “addressable” safeguard, but in practice it is expected. Encrypting PHI in transit and at rest is the industry standard and can protect you under breach notification rules.
Do wellness apps need to follow HIPAA?
Only if they handle PHI for or on behalf of a covered entity. Consumer wellness apps may instead fall under FTC rules and state health privacy laws.
















