HIPAA security rule enforcement is on the rise. HIPAA is the Health Insurance Portability and Accountability Act. This law regulates the privacy and security of individually identifiable patient information.
HIPAA affects any company that regularly transmits or stores employee health insurance information (e.g. healthcare providers, health plans, healthcare clearing houses). Even organizations outside the heathcare industry must consider regulatory compliance requirements associated with HIPAA and implement "appropriate administrative, technical and physical safeguards to protect the privacy of patient information".
Protected Health Information (PHI) is "any information which identifies or could be used to identify an individual and has anything to do with past, present or future physical or mental health conditions, care or payment for care".
HIPAA privacy provisions pose a compliance challenge. Organizations that fail to protect this information face stiff fines and possible jail time.
The privacy of PHI extends to email and computer files. HIPAA requires organizations to reduce or eliminate the risk of interception of emails and receipt of emails by unauthorized persons.
A new security rule focusing solely on PHI that is stored and transmitted electronically is part of HIPAA. The requirements of this rule, which are simply information security best practices, focus on the three cornerstones of a solid information security infrastructure – confidentiality, integrity, and availability of information.
HIPAA enforces well-known best practices that include:
* Ensuring that e-mail messages containing PHI are kept secure when transmitted over an unprotected link
* Ensuring that e-mail systems and users are properly authenticated so that PHI does not get into the wrong hands
* Protecting e-mail servers and message stores where PHI may exist
So HIPAA has requirements for transmission, storage and discoverability of private information (PHI). The technical standards of HIPAA's security rule require the use of encryption, such as PGP, for electronic communication of protected health information over open networks.
So what does your organization need to do about HIPAA?
Most likely you will be doing these two steps:
1) use a secure server for your website. Rather than emailing PHI data send links to the secure server.
2) set up encrypted email via PGP.
Still not sure what you need to do for HIPAA? Look here for answers:
H&HS Office for Civil Rights - HIPAA
H&HS HIPAA FAQ
California Office of HIPAA Implementation
Many healthcare professionals add postscripts to their email signature lines. They are for the security of protected health information
Here is a HIPAA compliant example:
First Name Last Name
This message may contain private information for persons named above. Please don't share that information with anyone without a need to know. If you received confidential information without a PGP wrapper, assume it was compromised, delete it, tell the sender, and try to tell the victim. Please don't send someone else's private information if you're not reasonably certain the recipient has a need to know and that the message will be kept private. Plain email is not private. In some cases, such as health information protected under the US HIPAA law or information protected under the US Privacy Act, plain email may be illegal. If you must relate a person's identity to their private information in email, use Hushmail or insist your recipients provide you their PGP public key. You can get my public key from the keyservers or my webpage.