Is Your Software HIPAA Compliant? A Complete Checklist

A 15-point HIPAA compliance checklist for evaluating any software that handles protected health information (PHI).

Written by Bear Harper

•4 min read

The 15-Point HIPAA Software Compliance Checklist

Evaluating software for HIPAA compliance can feel overwhelming. There are hundreds of requirements spread across multiple HIPAA rules, and vendors often provide vague or misleading information about their compliance posture.

This checklist distills the essential requirements into 15 actionable items. If a software product passes all 15, it is likely suitable for handling PHI. If it fails even one, you need to investigate further before deploying it in a healthcare environment.

Print this out, share it with your team, and use it every time you evaluate a new tool.


Business Associate Agreement

1. The vendor will sign a Business Associate Agreement (BAA)

This is the non-negotiable starting point. No BAA means no PHI — period. Ask the vendor directly and get it in writing. Do not accept "we're working on it" or "our terms of service cover that." A BAA is a specific legal document with required elements. If the vendor will not sign one, stop here.

2. The BAA covers all relevant services and data types

A BAA that covers only one product line when you are using three is incomplete. Ensure the agreement explicitly covers every service you will use and every type of PHI that will be involved.


Encryption

3. Data is encrypted at rest using AES-256 or equivalent

All stored PHI must be encrypted. AES-256 is the gold standard. Some vendors use AES-128, which is acceptable but less robust. Ask for specifics — "we use encryption" is not a sufficient answer.

4. Data is encrypted in transit using TLS 1.2 or higher

All data moving between your systems and the vendor's servers must be encrypted. TLS 1.2 is the minimum; TLS 1.3 is preferred. Verify that older protocols (TLS 1.0, 1.1, SSL) are disabled.

5. Encryption keys are properly managed

Who controls the encryption keys? How are they rotated? Are they stored separately from the encrypted data? Key management is often the weak link in otherwise solid encryption implementations.


Access Controls

6. Role-based access control (RBAC) is supported

Not every user should see everything. The software must allow you to assign permissions based on roles — a front-desk coordinator should not have the same access as a physician.

7. Multi-factor authentication (MFA) is available

Passwords alone are not enough. The software should support MFA, ideally through authenticator apps or hardware keys rather than SMS (which is vulnerable to SIM-swapping attacks).

8. Automatic session timeouts are configurable

Unattended sessions are a common source of unauthorized access. The software should automatically lock or log out inactive sessions, and you should be able to configure the timeout duration.

9. Unique user identification is enforced

Every user must have their own credentials. The software should not allow shared accounts, and it should be technically possible to trace every action to a specific individual.


Audit & Monitoring

10. Comprehensive audit logs are maintained

The software must log all access to and modifications of PHI. Logs should capture who, what, when, and from where. These logs must be immutable — users should not be able to delete or modify their own audit trails.

11. Audit logs are retained for at least six years

HIPAA requires documentation retention for six years. Your software's audit logs should meet or exceed this retention period. Ask the vendor about their log retention policy explicitly.

12. Breach detection and alerting capabilities exist

The software should be able to detect anomalous access patterns and alert administrators. Examples include login attempts from unusual locations, bulk data exports, or access outside normal hours.


Data Management

13. Data backup and disaster recovery procedures are documented

PHI must be recoverable in the event of a system failure or disaster. The vendor should provide documentation of their backup frequency, recovery time objectives (RTO), and recovery point objectives (RPO).

14. Data can be exported and portably migrated

You should be able to extract your data in a standard format. Vendor lock-in that prevents data migration is both a business risk and a compliance concern — you need to be able to respond to patient data requests.

15. Data is properly destroyed upon contract termination

When your relationship with the vendor ends, all PHI must be returned to you or securely destroyed. The vendor should provide a certificate of destruction confirming that no copies of your data remain on their systems, backups included.


Scoring Your Evaluation

ScoreAssessment
15/15Strong compliance posture — proceed with implementation
12–14Minor gaps — address before deploying with PHI
8–11Significant concerns — requires vendor remediation
Below 8Not suitable for PHI — find an alternative

Beyond the Checklist

This checklist covers the technical and contractual essentials, but full HIPAA compliance also requires:

  • Staff training on how to use the software in a compliant manner
  • Policies and procedures documented for your organization's specific use case
  • Regular risk assessments to identify new vulnerabilities as the software evolves
  • Incident response planning so your team knows exactly what to do in the event of a breach

Tools to Help

Share: