Skip to content
AIM Digital Technologies

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 electronicallyCovered entity. HIPAA applies.
A software company handling patient data for a covered entityBusiness 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 involvedUsually 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:

SafeguardWhat it means in an app
Access controlUnique user IDs, role-based permissions, automatic logoff, emergency access procedure
AuthenticationStrong passwords plus multi-factor authentication for staff and admin accounts
EncryptionTLS 1.2+ in transit, AES-256 at rest, managed keys, encrypted backups
Audit controlsLogs of who viewed, created or changed patient records, kept and reviewed
IntegrityChecks that records are not altered or destroyed improperly; versioning for clinical data
Transmission securityNo 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 faultPenalty per violation
Tier 1: did not know and could not reasonably have known$145 to $73,011
Tier 2: reasonable causeBetween the Tier 1 and Tier 3 ranges
Tier 3: willful neglect, corrected within 30 daysBetween 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.

FAQ

Frequently asked questions

Can't find your answer? Ask our team.

What makes an app HIPAA compliant?

An app supports HIPAA compliance when it protects health information with the Security Rule's safeguards (access control, encryption, audit logs, integrity checks and secure transmission) and the organization behind it has done a risk assessment, signed Business Associate Agreements with its vendors, trained staff and documented its policies. Software alone cannot be compliant; the organization is.

Is there a HIPAA certification for apps?

No. The US Department of Health and Human Services does not certify or approve software. Third-party audits and frameworks such as SOC 2 or HITRUST can demonstrate good security, but none of them is an official HIPAA certification.

Does a health or fitness app need to comply with HIPAA?

Only if it handles protected health information on behalf of a covered entity such as a provider, health plan or clearinghouse, or is one itself. A consumer fitness or wellness app that users download on their own is usually outside HIPAA, though the FTC Health Breach Notification Rule and state privacy laws can still apply.

What are the HIPAA penalties in 2026?

Civil penalties range from $145 to $73,011 per violation at the lowest tier and from $73,011 to $2,190,294 per violation at the highest tier, with a calendar-year cap of $2,190,294 for identical violations. HHS did not apply an inflation increase for 2026, so the 2025 amounts remain in force.

How much does it cost to build a HIPAA compliant app?

With our team, a HIPAA-ready MVP typically costs $6,250–$10,500 and a full platform $14,000–$24,000. Building to HIPAA safeguards usually adds 15–25% compared with a similar non-healthcare app, mainly for security work, audit logging, testing and documentation.

Can I use AWS, Firebase or Twilio in a HIPAA app?

Yes, with conditions. AWS, Google Cloud (including parts of Firebase) and Azure offer HIPAA-eligible services and sign Business Associate Agreements, as do Twilio and several video providers on specific plans. You must use only the eligible services for patient data, sign the BAA before going live, and configure them securely.

Free consultation

Turn ideas from this article into a product

Tell us about your project and get a free 30-minute consultation with a senior engineer. You'll leave with clear next steps, whether you work with us or not.

  • Reply within one business day
  • NDA on request, 100% IP ownership
  • Clear scope, timeline and estimate
  • Talk directly to senior engineers

Mon–Fri, 10:00–19:00 Islamabad time

Prefer email or a call?

reachus@aimdigital.tech+92 315 2333303 Book a call

We reply within one business day. Your details are kept confidential and we're happy to sign an NDA. See our privacy policy.

Free consultationCall