Hospice care is, at its core, about accompanying people through the most profound human experience — the dying process. The information that hospice organisations collect and manage to provide that care is correspondingly profound: terminal diagnoses, end-of-life wishes, family dynamics, spiritual beliefs, final conversations, and the intimate details of a person's last days. The HIPAA Security Rule applies to this information with the same force it applies to any other covered entity's ePHI. But the moral weight of that application is different at a hospice — because a breach of hospice patient information violates not just privacy rights but the sacred trust that every hospice patient and family extends when they invite care into their most vulnerable moments.
This guide provides the complete 2026 HIPAA Security Rule compliance framework for hospice agencies, adapted for the specific operational characteristics that distinguish hospice from other home health care settings: the interdisciplinary team model, the volunteer workforce, the bereavement programme, and the end-of-life care context that shapes every clinical and administrative decision.
The 2026 HIPAA Mandatory Requirements for Hospice Agencies
The six new mandatory requirements introduced by the 2026 HIPAA Security Rule update apply to hospice agencies in full, without exception or accommodation for organisational size or care setting:
• Multi-factor authentication: enforced on all accounts with access to ePHI — which at a hospice includes the EHR accounts of nurses, aides, social workers, chaplains, and bereavement coordinators; the email accounts that receive clinical notifications; and any administrative accounts that handle patient financial or scheduling information. The MFA requirement applies to volunteer accounts if volunteers access electronic systems containing patient information.
• Encryption at rest and in transit: every device that stores hospice patient information must have full disk encryption enabled and verified. Every electronic transmission of patient information — clinical notes, medication orders, care plan updates, family communication through digital channels — must use encryption in transit.
• Biannual vulnerability scanning: the technology environment used to deliver and document hospice care must be scanned for security vulnerabilities at least twice per year, with findings documented and remediated within defined timelines.
• Annual penetration testing: by a qualified third party, with a written report and documented remediation of findings.
• Technology asset inventory: a documented inventory of all hardware and software that creates, receives, maintains, or transmits ePHI — which at a hospice includes the EHR, the scheduling system, the volunteer management platform if it stores patient information, and the telehealth platform if used for virtual visits.
• Documented incident response plan: with hospice-specific elements including clinical downtime procedures, family communication protocols, and RHIO notification requirements for New York hospices participating in SHIN-NY.

