HIPAA compliant app development checklist for health apps
A HIPAA compliant app development checklist starts with a question many teams skip: does HIPAA apply to your app at all? HIPAA is a US federal law enforced by the Office for Civil Rights at the Department of Health and Human Services (HHS). It applies to covered entities, such as health plans and most healthcare providers, and to the business associates that handle protected health information for them.
If your app creates, receives, stores or sends that information on behalf of a covered entity, you need administrative, physical and technical safeguards, signed business associate agreements with your vendors, and a breach plan. This checklist walks through each step, drawing on HHS's own guidance.
This article is general information, not legal advice. Confirm your obligations with US healthcare counsel.
Step 1: Decide whether HIPAA applies to your app
HHS's guidance on health apps turns on one distinction. When a hospital, clinic or health plan hires you to build or run an app that handles patient information for them, you are generally a business associate and HIPAA applies. When a consumer independently chooses your app, enters their own data and controls where it goes, HHS's scenarios indicate that you are generally not a business associate, even if the app can exchange data with a provider at the user's request. Any healthcare app development company you hire should settle this question with your counsel before scoping, because it changes the architecture, vendors and budget.
- Is the app provided by, or built under contract for, a health plan or healthcare provider?
- Does it create, receive, maintain or transmit health information on that organisation's behalf?
- Does the organisation, rather than the patient, decide what data flows into or out of the app?
- Will one product serve both a provider's patients and direct consumers? If so, HHS's scenarios suggest keeping those data sets separate.
Apps outside HIPAA are not outside the law. The US Federal Trade Commission updated its Health Breach Notification Rule in 2024 to make clear that it covers health apps and similar products that HIPAA does not reach, including unauthorised disclosures such as sharing health data with advertisers. State privacy laws may also apply.
Step 2: Map protected health information and data flows
You cannot protect what you have not mapped. Before design is final, list every piece of health information the app touches, where it is stored, which services process it and who can see it. Include the places teams forget: push notification text, error logs, crash reports, analytics events, support tickets, backups and staging databases. Telemedicine products add video recordings, chat transcripts and e-prescriptions to the list, which our healthtech and telemedicine work maps in the first week.
| Data location | Common risk | What to decide |
|---|---|---|
| Mobile device storage | Records cached in plain files | Encrypted storage, what is cached, wipe on logout |
| API and database | Broad access for staff and services | Role-based access, encryption, audit logging |
| Push notifications and SMS | Diagnoses or results shown on lock screens | Generic wording; details only after login |
| Logs and crash reports | Request bodies with patient data | Scrub fields before logging; vendor BAA if needed |
| Analytics and ad tags | Health information sent to tracking vendors | Remove or restrict tags on authenticated screens |
| Test and staging | Copies of real patient records | Synthetic or de-identified data only |
Apply HIPAA's minimum necessary standard as you map: HHS describes it as making reasonable efforts to limit protected health information to what is needed for the purpose. Where you need data for analytics or model training, HHS guidance describes two de-identification methods, Safe Harbor, which removes a defined list of identifiers, and Expert Determination, where a qualified expert assesses re-identification risk.
Step 3: Risk analysis and administrative safeguards
HHS's summary of the Security Rule requires regulated entities to protect the confidentiality, integrity and availability of electronic protected health information and to guard against reasonably anticipated threats. The starting point is a documented risk analysis: what could go wrong, how likely it is, how bad it would be, and what you will do about it. Repeat it when the app, infrastructure or vendors change.
- Name a security official responsible for the programme.
- Write and keep policies for access, incident response, backups and device use.
- Train everyone who touches production systems, including contractors.
- Define how access is granted, reviewed and removed when people leave.
- Keep a contingency plan: backups, restore tests and how the service runs during an outage.
- Document decisions on addressable specifications; HHS treats addressable as assess and document, not optional.
Step 4: Technical safeguards, translated into app features
The Security Rule's technical safeguards are written in general terms so they fit any technology. The table maps each one to the features and practices it usually means in a modern mobile or web app. HHS's Security Series marks unique user identification as required, while encryption and automatic logoff are addressable, which still means you must assess them and document your decision.
| Safeguard (HHS) | What it covers | In your app |
|---|---|---|
| Access control | Limit access to authorised people | Role-based permissions, unique user IDs, emergency access procedure, session timeout |
| Audit controls | Record and examine activity in systems with ePHI | Tamper-resistant logs of who viewed or changed which record, and when |
| Integrity | Protect ePHI from improper change or destruction | Validation, checksums, versioned records, restricted delete |
| Person or entity authentication | Verify users are who they claim | Strong passwords, multi-factor authentication, biometric sign-in on the device |
| Transmission security | Protect ePHI sent over networks | TLS for all traffic, certificate pinning where justified, no PHI in URLs |
| Encryption at rest (addressable) | Protect stored data | Encrypted databases, backups and device storage, with managed keys |
Physical safeguards still matter in the cloud: they cover facility access, workstations and device and media controls. Your cloud provider handles its data centres under its agreement with you, but laptops, phones and removable media used by your own team are your responsibility. Our DevOps and cloud work sets these controls up as code so they are repeatable and auditable.
Step 5: Vendors, business associate agreements and tracking
Every vendor that creates, receives, maintains or transmits protected health information for you needs a business associate agreement. HHS's cloud computing guidance says a cloud provider that stores only encrypted data, even without the decryption key, is still a business associate and needs one. Check hosting, databases, email and SMS providers, video calling, file storage, support desks, crash reporting and any AI or transcription service.
Tracking technologies need particular care. HHS's bulletin on online tracking says regulated entities may not disclose protected health information to tracking vendors except as the Privacy Rule permits. In June 2024 a federal court in Texas vacated part of that bulletin covering certain unauthenticated public web pages, but the rest of the guidance stands. Keep advertising and analytics tags off logged-in screens unless the vendor signs a BAA, and review what server-side setups forward; our guide to server-side tracking explains how data moves.
Step 6: Breach readiness
HHS's Breach Notification Rule sets the outer limits. Covered entities must notify affected individuals without unreasonable delay and no later than 60 days after discovering a breach of unsecured protected health information. A breach affecting more than 500 residents of a state or jurisdiction also requires notice to prominent media serving that area, and breaches affecting 500 or more people must be reported to the HHS Secretary within the same 60-day limit. Smaller breaches can be logged and reported to HHS within 60 days of the end of the calendar year.
Business associates must notify the covered entity without unreasonable delay and within 60 days of discovery, and many BAAs set a shorter deadline. Build the capability before launch: alerting, an incident runbook, audit logs that show exactly which records were accessed, and contact lists. Encryption consistent with HHS guidance matters here too, because properly secured data may fall outside the definition of unsecured information.
What is changing, and a pre-launch checklist
HHS published a proposed update to the Security Rule in December 2024 that would, among other things, make most implementation specifications required and add explicit expectations such as encryption and multi-factor authentication. HHS states that the current rule remains in effect while rulemaking continues, and trade press reported in 2026 that final action had been pushed back. Check HHS's page for the current status, and design to the stricter proposed controls where practical.
- Confirm in writing whether you are a covered entity, a business associate or neither.
- Complete and date a risk analysis, with owners for each risk.
- Sign BAAs with every vendor that touches protected health information.
- Turn on encryption in transit and at rest, multi-factor authentication and audit logging.
- Remove health information from notifications, logs, analytics and staging.
- Run an independent penetration test and fix findings before launch.
- Rehearse your breach runbook with the people who will use it.
- Schedule reviews after major releases and at least annually.
Our healthcare app development team builds these controls into the first sprint and maps them with your legal counsel; we do not certify compliance ourselves. If you want to work through this checklist against your own product, book the Growth Audit, a two-week paid diagnostic whose fee is credited to the next engagement. We review your data flows, vendors and safeguards with you and return a prioritised gap list. Teams building telemedicine products face extra integration work, such as video, e-prescriptions and pharmacy links, which we scope in the same review.