HIPAA is the U.S. law that sets the rules for health data. It tells you who may see patient records, how to keep them safe, and what to do when something goes wrong.
This checklist breaks those rules into plain steps. If you are building a health product, a firm that knows mobile app development for healthcare can bake these steps into the app from day one.
What is the HIPAA compliance checklist?
8 min read
In this article
- 1. What is the HIPAA compliance checklist?
- 2. What is the HIPAA Privacy Rule?
- 3. What counts as identifiable patient data?
- 4. Who does the Privacy Rule apply to?
- 5. What rights do patients have?
- 6. What is the HIPAA Omnibus Rule?
- 7. What is the HIPAA Security Rule?
- 8. How does the Security Rule protect your data?
- 9. Is the HIPAA Security Rule changing?
- 10. What is the Breach Notification Rule?
- 11. HIPAA standard transactions
- 12. Your HIPAA compliance checklist in 10 steps
- 13. Building a HIPAA-compliant app? How we help
- 14. Final thoughts
A HIPAA compliance checklist is a list of the steps your team must take to protect Protected Health Information (PHI). It turns the Privacy, Security and Breach Notification Rules into tasks you can assign and track.
You don’t need a breach to get in trouble. Weak policies alone can lead to fines, so close gaps early.
Note: this is general information, not legal advice. Ask a HIPAA expert about your own setup.
Three HIPAA terms you need to know:
- Protected health information (PHI)
- A covered entity (CE)
- Business Associate (BA)
Protected health information
PHI is any health data that can be tied to a real person, such as a named lab result, bill or claim. Stored or sent online, it is called ePHI. A good healthcare app development team designs every screen and database around keeping it private.
Covered Entity
A covered entity is an organization that must follow HIPAA directly. There are three kinds: health plans, health care clearinghouses, and health care providers who send health data online for things like billing. Doctors, clinics, hospitals, dentists and pharmacies are common examples.
Business Associate
A business associate is an outside company that handles PHI for a covered entity. Cloud hosts, billing firms, IT vendors, lawyers and app developers often fall into this group.
Before it touches PHI, a business associate must sign a Business Associate Agreement (BAA). Since 2013, business associates can be fined directly for breaking HIPAA rules.
What is the HIPAA privacy rule?
The Privacy Rule limits who can use or share PHI, and why. PHI may be used for treatment, payment and health care operations. Most other uses need the patient’s written OK.
What information does the privacy rule protect?
The Privacy Rule covers PHI in any form: paper, spoken or electronic. It applies whether a covered entity or a business associate holds it.
It protects data about a person’s past, present or future health, the care they get, and how that care is paid for. A key idea is “minimum necessary”: share only the PHI a task truly needs.
What counts as identifiable patient data?
- Names
- Addresses, and dates such as birth or admission dates
- Phone numbers, fax numbers and email addresses
- Social Security numbers
- Medical record and health plan numbers
- Account, license and device numbers
- Biometrics, full-face photos, IP addresses and any other unique ID
Who does the Privacy Rule apply to?
- Providers: doctors, clinics, dentists, nursing homes and pharmacies
- Health plans: insurers, HMOs, company plans and Medicare
- Clearinghouses that turn health data into a standard format
- Business associates that handle PHI for any of the above
What rights do patients have?
Patients have the right to get a Notice of Privacy Practices (NPP). It explains how a provider or plan uses their data and how to complain. HIPAA also gives patients these rights:
- See and get a copy of their health records, usually within 30 days
- Ask for mistakes in their records to be fixed
- Get a list of certain disclosures of their data
- Ask for limits on how their data is shared, and how they are contacted
- File a complaint with the provider or with HHS
What is the HIPAA Omnibus Rule?
The Omnibus Rule took effect in 2013. It made business associates and their subcontractors directly liable under HIPAA. It also raised fines, tightened the breach rules, and banned health plans from using genetic data to set coverage.
What the Omnibus Rule means for your checklist:
- Update your BAAs – Cover the Omnibus duties, including subcontractors, and keep signed copies.
- Refresh your privacy policies – Match them to the current rules.
- Update your NPP – Include breach notice rights and the right to opt out of fundraising messages.
- Train your staff – Run training on a regular schedule.
What is the HIPAA Security Rule?
The Security Rule sets the minimum standards for protecting ePHI. Its goal is to keep data private, accurate and available when needed. To get there, it asks for three kinds of safeguards: administrative, physical and technical.
How does the Security Rule protect your data?
The rule starts with how you run your security program. Two steps come first.
Security management process: Set policies to prevent, find and fix security problems. Review your risks again whenever you add a new system or change a process.
Assigned security responsibility: Name one security officer who owns the Security Rule program.
The three safeguard types:
- Administrative safeguards
- Technical safeguards
- Physical safeguards
Administrative safeguards
Administrative safeguards are the policies and people side of security. They link the Privacy and Security Rules together. Most teams name both a privacy officer and a security officer.
- Risk analysis – Find where ePHI lives and what could put it at risk.
- Risk management – Put fixes in place that cut those risks to a fair level.
- Contingency plan – Plan for data backup, disaster recovery and emergency access.
Physical safeguard
Physical safeguards protect the places and devices that hold PHI. That means servers, laptops, hard drives and paper files.
Facility access – Keep people without a reason to be there out of areas that hold PHI. Have a plan for access during an emergency.
Workstation use – Only the right staff should use workstations that show PHI. Place screens and lock devices so others can’t see the data.
Device control – Wipe PHI from any device or drive before you reuse it or throw it away.
Technical safeguards
Technical safeguards are the tools that protect ePHI and control who can reach it. The rule does not name a brand or a product. You pick the tools, as long as they cover these areas:
Access and audit controls – Give each user a unique login, and log who views or changes ePHI.
Authentication – Check that each user is who they say they are, for example with multi-factor login.
Integrity – Make sure no one can change or delete PHI without permission. Our custom software development team builds these checks into the backend.
Transmission security – Encrypt ePHI when it moves across a network, and at rest wherever you can.
Is the HIPAA Security Rule changing?
Maybe. On January 6, 2025, HHS published a proposed update to the Security Rule. It would make some steps that are now “addressable” required, such as encryption and multi-factor login. It would also ask for an asset inventory and regular scans.
As of November 2026, it is still a proposal, not a final rule. The current Security Rule is the one you must follow today.
What is the Breach Notification Rule?
A breach is any use or sharing of unsecured PHI that the rules don’t allow. Properly encrypted data is not “unsecured”.
- Patients: tell them without delay, and no later than 60 days after you find the breach.
- HHS: for 500 or more people, report within 60 days. For fewer, log it and report within 60 days after the year ends.
- Media: if 500 or more people in one state or area are hit, tell local media too.
- Business associates: must tell the covered entity.
HIPAA standard transactions
HIPAA also sets standard formats for electronic health transactions. When a covered entity sends one of these online, it must use the standard format.
Standard transactions include:
- Claims and encounter information
- Payment and remittance advice
- Claims status
- Eligibility
- Enrollment and disenrollment
- Referrals and authorization
- Coordination of benefits
- Premium payment
Your HIPAA compliance checklist in 10 steps
- Name a privacy officer and a security officer.
- Map where PHI and ePHI live and how they move.
- Run a risk analysis, and repeat it when systems change.
- Write and adopt privacy and security policies.
- Sign a BAA with every vendor that touches PHI.
- Limit access by role, and use unique logins and multi-factor login.
- Encrypt data in transit and at rest, and keep audit logs.
- Back up data and test your disaster recovery plan.
- Train staff on a schedule, and keep records.
- Keep a breach response plan ready, with the 60-day deadline in mind.
Building a HIPAA-compliant app? How EchoInnovate IT helps
We build telehealth apps, patient portals and remote monitoring tools with role-based access, encryption, audit logs and BAA-ready hosting from the first sprint.
The first step is a short scoping call. We map your PHI flows, flag risks and send a fixed quote. See our healthcare app development services, or our wearable app development work for remote monitoring.
Final thoughts
HIPAA compliance is not a one-time task. Review your risks, BAAs and training each year, and watch for news on the Security Rule update.
Planning a health product? Contact us, or read our guide on how to build a healthcare app.
Frequently Asked Questions
What is HIPAA?
HIPAA is the Health Insurance Portability and Accountability Act, a U.S. law from 1996. It sets national rules for keeping patient health data private and secure. Its main parts are the Privacy Rule, the Security Rule and the Breach Notification Rule.
Who needs to be HIPAA compliant?
Covered entities must comply: health plans, health care clearinghouses, and providers who send health data online. Their business associates must comply too. That includes cloud hosts, IT vendors and app developers that handle PHI for them. Each business associate needs a signed BAA before it touches any PHI.
Does a health app need to be HIPAA compliant?
It depends on who the app serves. If it handles PHI for a provider, health plan or their vendor, HIPAA applies. A consumer app that people use on their own may not be covered. Even then, the FTC’s Health Breach Notification Rule can apply.
What are the main HIPAA rules?
The Privacy Rule controls who can use and share PHI. The Security Rule sets safeguards for electronic PHI. The Breach Notification Rule says who you must tell after a breach, and how fast. The Omnibus Rule of 2013 updated all three and made business associates directly liable.
Is the proposed HIPAA Security Rule update final?
No. HHS published the proposal on January 6, 2025, and as of November 2026 it has not been finalized. The current Security Rule still applies. It would make steps like encryption and multi-factor login required, so many teams adopt them early.
HIPAA-ready healthcare apps, with compliance built in from day one.
Telehealth, EHR/EMR integrations (FHIR, HL7), patient portals and remote monitoring. Our team builds access control, encryption and audit logs in from the first sprint, not at the end. Start with a short scoping call and a fixed quote.