Guides··4 min read
HIPAA Compliance Checklist for Apps: What Founders and Developers Need in 2027
A plain-English HIPAA checklist for web and mobile apps in 2027: who must comply, the technical safeguards to build, BAAs, breach rules, current penalties and what it costs.
Short answer: an app is ready for HIPAA when (1) you know whether the law applies to you, (2) every vendor that touches patient data has signed a Business Associate Agreement, (3) the app enforces access control, encryption and audit logging, and (4) your organization has a written risk assessment and policies. There is no government certification: compliance is an ongoing practice, not a badge.
This checklist is written for founders, product managers and developers building for the US market. It is practical guidance, not legal advice; confirm your obligations with healthcare counsel.
Why it matters: the numbers
- About 61 million people were known to be affected by healthcare data breaches reported in 2025, according to HIPAA Journal's December 2025 breach report. The 2024 total was far higher because a single incident at Change Healthcare affected about 192.7 million people.
- $6.64 million is the average cost of a healthcare data breach in IBM's Cost of a Data Breach Report 2026, the highest of any industry.
- Up to $2,190,294 per violation is the top civil penalty tier under 45 CFR 102.3. HHS left the 2025 amounts unchanged for 2026 (HIPAA Journal).
Step 1: does HIPAA apply to you?
| You are… | HIPAA status |
|---|---|
| A provider, health plan or clearinghouse that bills electronically | Covered entity. HIPAA applies. |
| A software company handling patient data for a covered entity | Business associate. HIPAA applies, and you need a BAA with your customer. |
| A subcontractor of a business associate (hosting, SMS, analytics) | Also a business associate. A BAA is required down the chain. |
| A consumer wellness app with no provider or plan involved | Usually outside HIPAA, but FTC rules and state privacy laws may apply. |
Step 2: the technical safeguards to build
The Security Rule groups requirements into administrative, physical and technical safeguards (see the HHS summary of the Security Rule). These are the technical ones your app must implement:
| Safeguard | What it means in an app |
|---|---|
| Access control | Unique user IDs, role-based permissions, automatic logoff, emergency access procedure |
| Authentication | Strong passwords plus multi-factor authentication for staff and admin accounts |
| Encryption | TLS 1.2+ in transit, AES-256 at rest, managed keys, encrypted backups |
| Audit controls | Logs of who viewed, created or changed patient records, kept and reviewed |
| Integrity | Checks that records are not altered or destroyed improperly; versioning for clinical data |
| Transmission security | No patient data in email subject lines, SMS, push notifications, URLs or analytics events |
Step 3: the full checklist
Before you write code
- Map every place protected health information is collected, stored, displayed and sent.
- Collect the minimum data you need. Data you never store cannot leak.
- List every vendor in the data path and confirm each offers a BAA: cloud, database, video, SMS, email, error tracking, AI models.
- Decide who your privacy and security officers are, even in a five-person startup.
While you build
- Use only HIPAA-eligible services on AWS, Google Cloud or Azure for patient data.
- Separate environments, and use synthetic patient data everywhere except production.
- Enforce role-based access on the server, not just in the interface.
- Log access to records in an append-only store. Keep patient data out of application logs.
- Add session timeouts, device lock checks on mobile, and remote sign-out.
- Encrypt local storage on the device and avoid caching records in screenshots or backups.
- Automate dependency and vulnerability scanning in your CI pipeline.
Before launch
- Sign BAAs with every vendor and with your customers.
- Complete a written risk assessment and fix the high-risk items.
- Run a penetration test and keep the report.
- Write the policies you will actually follow: access reviews, incident response, backups, device use.
- Test restoring from backup.
After launch
- Review access rights and audit logs on a schedule.
- Train every new team member before they get access.
- Repeat the risk assessment when you add features, vendors or integrations.
If something goes wrong: breach notification
Under the HHS Breach Notification Rule, affected individuals must be notified without unreasonable delay and no later than 60 days after a breach is discovered. Breaches affecting 500 or more people must also be reported to HHS and to prominent media in the affected state within the same window; smaller breaches are reported to HHS annually. Business associates must notify the covered entity. Have an incident response plan written before you need it.
Current HIPAA penalty tiers
| Level of fault | Penalty per violation |
|---|---|
| Tier 1: did not know and could not reasonably have known | $145 to $73,011 |
| Tier 2: reasonable cause | Between the Tier 1 and Tier 3 ranges |
| Tier 3: willful neglect, corrected within 30 days | Between the Tier 2 and Tier 4 ranges |
| Tier 4: willful neglect, not corrected | $73,011 to $2,190,294 |
Amounts are the 2025 inflation-adjusted figures in 45 CFR 102.3, which stayed in force for 2026. Check the regulation for the current year before quoting them.
What is changing
In January 2025 HHS proposed the first major update to the Security Rule in over a decade, with more specific requirements such as multi-factor authentication, encryption, asset inventories and regular testing. As of late 2026 the rule is not final, and the federal regulatory agenda now projects July 2027 (Fierce Healthcare). The existing rule remains fully enforceable. Building with MFA, encryption and documented testing now means little rework later.
What it costs
With our team, a HIPAA readiness review of an existing app typically costs $500–$1,250, a HIPAA-ready MVP $6,250–$10,500, and a full platform with web and mobile apps $14,000–$24,000. Expect ongoing costs for BAA-tier vendor plans, penetration testing and compliance tooling.
See our HIPAA compliant app development service, the wider healthcare software development page, or estimate your build with the cost calculator.


