You should implement encryption to protect PHI any time it is stored.
*This article was taken from our HIPAA Guide. For more information on this topic, download our free HIPAA Guide.
"Currently, the strongest, most common encryption algorithm is AES-256.”
Even though HIPAA regulations indicate that encryption is an addressable item (§164.312(a)(2)(iv), §164.312(e)(1), §164.312(e)(2)(ii)), HHS has made it very clear in its posted settlement details that ePHI should be encrypted or protected in other ways of equal or greater effectiveness.
There are three common data protection processes that are often confused: masking, hashing, and encrypting. Let me break them down for you:
You should use encryption to protect PHI any time it is stored. You should also use masking to display only the information each user requires to complete their responsibilities. This will help you meet the Minimum Necessary rule.
Whenever implementing encryption, always use the strongest algorithm your system can handle, such as AES-256. TDEA (or 3DES) is a weaker algorithm and will soon be disallowed. Therefore,TDEA is not recommended for new implementations.
Remember that many older algorithms are not acceptable (e.g., RC4, 3DES).
Finally, it is critical to protect the key used to decrypt PHI. The strongest lock is useless if the key is easy to obtain. Backups of keys should be stored securely. For example, backups of keys could be stored in a safe or a safe deposit box. Most computer systems can automatically handle encryption if they’re properly configured.Practice Management and Electronic Health Record software may also provide an encryption feature. In each case, care should betaken to follow instructions provided by the vendor to correctly implement the encryption and secure the encryption keys.