Security

Encryption at Rest

Cryptographic protection of stored ePHI such that the data is unreadable without the decryption key.

1 min read · Last reviewed May 23, 2026

At a glance

Category
Security
Primary sources
3
Workspace handoff
compliance binder

Where this comes up

This sits inside the security risk analysis under 45 CFR 164.308(a)(1)(ii)(A) — workstation controls, EHR access roles, ePHI transmission encryption, audit logging, vendor risk, and incident response. Reviewers expect dated evidence of the control, not a policy PDF that says it exists.

Full definition

What it is in practice

45 CFR 164.312(a)(2)(iv) makes encryption "addressable" — required if reasonable and appropriate, with a documented alternative if not. The HHS Breach Notification safe harbor requires encryption that meets NIST standards (FIPS 140-validated).

How it shows up in your practice

Encrypt laptops, mobile devices, and backups by default. Encrypted devices that are lost or stolen do not trigger breach notification, which alone justifies the cost.

Sources

Take it into the workspace

Document encryption decisions in the Compliance Binder

Open compliance binder
Authored by D3rx

D3rx is a healthcare-billing and compliance research aid maintained by D3rx Inc. Articles are drafted by an LLM (Anthropic Claude) against primary HHS, OCR, CMS, eCFR, NIST, and state-regulator publications, and reviewed for restraint and source fidelity by the D3rx team.

Reviewer status: a named credentialed reviewer (CHC, CHPC, or healthcare attorney) is being engaged. Until that engagement is finalized, this page does not claim credentialed review.

This glossary entry is a research aid for billing and compliance staff. It does not provide legal, medical, or financial advice and does not replace counsel. References cited link to primary sources at HHS, OCR, CMS, eCFR, NIST, and the relevant payer or industry body.