The Foundational Steps of a HIPAA Program
This is educational guidance, not legal advice. Consult a qualified healthcare attorney or compliance professional for guidance specific to your organization.
Determine regulatory status and compliance scope
What should exist when completed
- CE / BA / clearinghouse determination
- Services involving PHI / ePHI
- Applicable BAAs
- Applicable state and federal requirements
- Organizational boundaries
Establish HIPAA governance and assign responsibility
What should exist when completed
- Security Official
- Privacy responsibility / lead
- Documented authority
- Management approval
- Escalation paths
Identify PHI/ePHI, assets, systems and data flows
What should exist when completed
- Asset inventory
- ePHI repositories
- Applications
- Servers / endpoints
- Network components
- Cloud services
- Remote access
- Data-flow diagrams
- Locations
Identify vendors, subcontractors and external dependencies
What should exist when completed
- Vendor inventory
- PHI / ePHI involvement
- BA / subcontractor determination
- Service dependency
- Vendor owner
Conduct the Security Risk Analysis
What should exist when completed
- Scope
- Threats
- Vulnerabilities
- Existing controls
- Likelihood
- Impact
- Risk levels
- Documented findings
Establish Risk Management
What should exist when completed
- Risk register
- Mitigation plan
- Risk owner
- Target date
- Treatment decision
- Residual risk
- Management acceptance
- Addressable-specification decisions
Establish workforce security and access management
What should exist when completed
- Joiner / mover / leaver process
- Access authorization
- Role-based access
- Unique IDs
- Privileged access
- Termination procedures
- Periodic access review
Implement administrative, physical and technical safeguards
What should exist when completed
- Actual controls resulting from the SRA
- MFA
- Encryption decisions
- Endpoint protection
- Logging
- Backups
- Workstation security
- Facility controls
- Transmission security
Establish HIPAA policies, procedures and document control
What should exist when completed
- Security policies
- Privacy-related BA policies as applicable
- Sanctions
- Acceptable use
- Access control
- Incident response
- Retention / version / approval process
Put BAAs and subcontractor controls in place
What should exist when completed
- Client BAAs
- Subcontractor BAAs
- BAA register
- Review process
- PHI handling obligations
- Incident / breach notification requirements
Train and manage the workforce
What should exist when completed
- HIPAA / security training
- Security awareness
- Role-specific training
- Acknowledgments
- Sanctions
- Training records
Establish security incident and breach response
What should exist when completed
- Incident Response Plan
- Incident register
- Investigation process
- Escalation
- Breach risk assessment
- BA → CE notification process
- Evidence preservation
Establish contingency and recovery capability
What should exist when completed
- Data Backup Plan
- Disaster Recovery Plan
- Emergency Mode Operations Plan
- Application / data criticality
- Recovery priorities
- Testing and revision
Establish ongoing security operations
What should exist when completed
- System activity review
- Audit-log review
- Vulnerability / patch management
- Malware protection
- Security alerts
- Backup monitoring
- Account / access reviews
Evaluate, review and maintain compliance
What should exist when completed
- § 164.308(a)(8) evaluations
- Periodic SRA updates
- Compliance calendar
- Policy reviews
- Control testing
- Remediation tracking
- Evidence repository
Note on scope
HIPAA is a regulatory floor, not a ceiling. Many states impose additional or stricter health-data privacy and breach notification requirements — verify state-specific obligations alongside this checklist.