A CMS survey or an OCR investigation of a hospice agency typically begins the same way: with a document request. Before surveyors or investigators assess your clinical operations or technical controls, they ask for the foundational compliance documentation. The organizations that survive these reviews with minimal findings are those that can produce complete, current documentation immediately — not after a frantic search through filing systems.
This checklist organizes the documents and controls that hospice agencies need to have ready — for routine CMS surveys, triggered OCR investigations following a complaint or breach, and cyber insurance renewals.
Tier 1: Documents Requested Within the First 24 Hours
These are the documents that surveyors and investigators request at the start of every audit. They should be immediately accessible, current, and complete.
- [ ] Written HIPAA Security Rule risk analysis — comprehensive, covers all systems storing or transmitting ePHI, dated within the past 12 months or since last significant operational change. Identifies risks, likelihood, impact, and controls.
- [ ] Written information security program (WISP) or equivalent — documents your hospice's security policies and procedures. Reviewed and approved by the governing body within the past 12 months.
- [ ] Incident response plan — written, with named roles and contact information. Includes 72-hour internal notification procedure and breach notification timelines for OCR and affected individuals.
- [ ] List of all business associates with signed BAAs — complete list of vendors, contractors, and business associates who have access to ePHI. Confirmation that current BAAs are on file for each.
- [ ] Staff security awareness training records — documentation that all workforce members with ePHI access have completed security awareness training within the past 12 months. Includes training completion dates and content covered.
Tier 2: Technical Control Evidence Requested in Days 1–3
After reviewing documentation, surveyors and investigators request evidence that technical controls are actually implemented.
- [ ] MFA implementation evidence — documentation or system screenshots confirming MFA is enforced on all accounts with ePHI access. For Microsoft 365: Conditional Access policy configuration. For EHR: SSO/MFA integration settings.
- [ ] Encryption verification — documentation confirming encryption at rest on workstations (BitLocker/FileVault enabled), mobile devices (verified encryption status), and cloud storage. Confirmation of TLS 1.2+ for data in transit.
- [ ] Vulnerability scan results — most recent automated vulnerability scan, dated within the past six months. Remediation plan for any identified findings. Previous scan for comparison.
- [ ] Penetration test results — most recent penetration test report, dated within the past 12 months. Remediation actions taken for identified findings.
- [ ] Audit log configuration and review records — confirmation that audit logging is enabled on all ePHI-containing systems. Documentation of most recent quarterly log review, including findings.
- [ ] Backup and recovery documentation — backup configuration documentation, most recent backup restoration test results, recovery time and recovery point objectives.

