Body
Purpose
The HIPAA Contingency and Resiliency Pattern defines the approved implementation model for maintaining service availability and restoring HIPAA workloads following operational failures, service disruptions, infrastructure failures, or disaster events.
This pattern provides a consistent resiliency architecture supporting recoverability, operational continuity, restoration activities, and workload sustainability for systems that create, store, process, transmit, or provide access to Protected Health Information (PHI).
Use Cases
This pattern applies when:
- Hosting applications containing PHI
- Hosting databases containing PHI
- Hosting data products containing PHI
- Deploying HIPAA landing zones
- Deploying HIPAA subscriptions
- Implementing recovery and continuity capabilities for regulated workloads
This pattern does not apply to:
- Non-regulated workloads
- Sandbox environments without PHI
- Development environments without PHI
- Workloads outside approved HIPAA hosting environments
Design Principles
Resiliency by Design
Resiliency requirements should be incorporated into workload design rather than added after deployment.
Failure Assumption
Architectures should assume component failures will occur and should support recovery without unacceptable operational impact.
Recovery Validation
Recovery processes should be periodically validated through approved operational procedures.
Operational Continuity
Workloads should implement capabilities supporting continued operations during service interruptions whenever practical.
Logical Architecture
HIPAA Workload
Application Layer
Data Layer
Identity Layer
Network Layer
↓
Resiliency Services
Backup
Replication
Monitoring
Restoration
↓
Recovery Operations
Resiliency Components
Workload Availability
Supports:
- Service continuity
- Component redundancy
- Operational support
Backup Services
Supports:
- Restoration
- Data recovery
- Recovery operations
Monitoring Services
Supports:
- Failure detection
- Operational visibility
- Incident investigation
Recovery Services
Supports:
- Service restoration
- Data restoration
- Operational resumption
Recovery Scenarios
Architectures should support recovery from:
- Data loss
- Component failure
- Application failure
- Infrastructure failure
- Service interruption
- Accidental deletion
Workload Resiliency Model
Application Resiliency
Applications should support recovery and restoration using approved resiliency architectures appropriate for the workload.
Data Resiliency
Data platforms should support backup, recovery, restoration, and continuity through approved data protection capabilities.
Identity Resiliency
Identity services supporting HIPAA workloads should support continued authentication and authorization capabilities during operational disruptions.
Monitoring Resiliency
Monitoring capabilities should continue to provide operational visibility sufficient to support recovery operations and incident response.
Recovery Operations
Recovery procedures should support:
- Workload restoration
- Data restoration
- Application recovery
- Service validation
- Operational resumption
Recovery Validation
Recovery capabilities should be periodically evaluated and validated through approved operational processes.
Validation activities may include:
- Backup validation
- Restoration testing
- Recovery procedure reviews
- Operational readiness reviews
Monitoring Integration
Resiliency architectures should integrate with approved monitoring services.
Monitoring should support:
- Service health visibility
- Failure detection
- Recovery operations
- Operational investigation
Operational Responsibilities
Platform Team
- Platform resiliency architecture
- Recovery service administration
- Backup platform administration
- Platform recovery capabilities
Security Team
- Recovery requirements
- Resiliency reviews
- Security investigation support
- Compliance oversight
Workload Owner
- Application recovery procedures
- Business continuity participation
- Recovery validation participation
- Operational ownership
Automation Pattern
Resiliency capabilities should be deployed through approved platform automation whenever practical.
Automation areas may include:
- Backup onboarding
- Recovery configuration
- Monitoring enrollment
- Resiliency configuration
- Platform deployment
Reference Architecture Outcomes
A workload implementing this pattern should provide:
- Recoverability
- Operational continuity
- Restoration capability
- Failure detection
- Operational resiliency
- Consistent recovery implementation
- Supportable recovery operations