HIPAA email encryption requirements can be confusing because of the lack of clear instruction that leaves the rules open to interpretation. As a result, some question whether email encryption is truly a HIPAA requirement.
For example, the encryption requirements around Protected Health Information (PHI) are called “addressable” in the security rule. HIPAA encryption requirements for transmission state that covered entities should encrypt PHI “whenever deemed appropriate.”
What are HIPAA email encryption requirements?
HIPAA encryption requirements are specified by two main terms, “required” and “addressable.” Those labeled “required” must be put in place or it’s considered a failure to comply with HIPAA. Those that are called “addressable” only have to be implemented after a risk assessment has determined that encryption is needed for managing risks to PHI. You must document your reasoning behind that decision.
In addition, implement an equivalent solution to safeguard PHI if your organization determines that encryption is not appropriate. Since there is not an appropriate alternative for protecting PHI other than encryption, it’s effectively required.
Not using encryption is risky for your patient’s information and your organization.
Understanding HIPAA email encryption
The Department of Health and Human Services (HHS) wants to allow organizations to select the best solution for their individual needs. HHS realizes they can't demand covered entities use specific security technologies because of the constant need to stay current.
This doesn’t mean that encryption can be overlooked, only that an organization has to document a reason why action hasn’t been taken.
Plus, an alternative method must be used and its details made available to the Office for Civil Rights (OCR) in the case of an audit.
HIPAA email security and encryption requirements
HIPAA encryption requirements apply to every part of an organization’s IT system, including cloud servers and smartphones. The increased use of mobile devices in the work environment make it more complicated to comply with the encryption requirements. So, it is a challenge to include safeguarding PHI both at rest and in transit.
