Cloud Computing for HIPAA Compliance is finally gaining adoption in US Healthcare. When I attended the Medical Informatics World Conference in Boston last year, I joined an interactive breakout discussion group on "Leveraging the Cloud." Of the dozen or so people in the group, only a few people were actually using the cloud in their organization. The internet moves fast however, especially in Cloud computing. So I put together this post to answer the most frequently asked questions around Cloud computing and HIPAA compliance. To make it easier to navigate, you can click on any question and jump to the answer.
SEE ALSO: Speaking on the Future of Cloud Security at TiE Silicon Valley Without further ado, here are the Top 10 frequently asked questions around HIPAA and Cloud computing:
Yes, as long as the Covered Entity or Business Associate enters into a Business Associate Agreement (BAA) with the Cloud vendor. As a recap, the BAA establishes the permitted and required uses and disclosures of Protected Health Information (PHI) by the Business Associate performing services for the Covered Entity or Business Associate. The BAA also contractually requires the Business Associate to appropriately safeguard ePHI. This includes implementing the requirements of the Security Rule. It should be noted both Covered Entities and Business Associates must conduct recurring risk analyses to identify and assess potential threats and vulnerabilities to ePHI.
Yes. Lacking an encryption key does not exempt a Cloud vendor from Business Associate status and its obligations under HIPAA guidelines. As a recap, an organization that maintains ePHI on behalf of a Covered Entity or Business Associate is itself a business associate, even if it cannot actually view the data.
Yes. Health care providers, other Covered Entities, and Business Associates can use mobile devices to access electronic Protected Health Information (ePHI) in the cloud. Of course the appropriate physical, administrative, and technical safeguards must be in place to protect ePHI. This includes both on the mobile device and in the cloud. Lastly, BAAs must also be in place with any third party service providers for the device and/or the cloud vendor.
SEE RELATED: How Can You Protect and Secure Health Information When Using a Mobile Device?
No. HIPAA guidelines do not require a Business Associate to maintain ePHI beyond the time it provides services to a Covered Entity or Business Associate. In fact, the Privacy Rule says that a BAA requires a Business Associate to return or destroy all PHI at the termination of the BAA.
Yes. As long as a BAA is in place with the Cloud vendor and customer, HIPAA regulations do not specifically prohibit storing ePHI outside the U.S. There is some vagueness to this guidance however. The U.S Department of Health and Human Services ( HHS) warns that outsourcing storage of ePHI overseas may increase the risks and vulnerabilities to its protection. They also note these risks should be taken into account when conducting recurring risk analyses, which are required by the Security Rule.
No. Instead, HIPAA Regulations require Business Associates and Covered Entities to obtain BAA's with their respective Cloud vendor(s). The Cloud vendor is directly responsible for safeguarding electronic PHI in accordance with the HIPAA Security Rule. HIPAA Rules do not require Cloud vendors provide documentation of their security practices nor allow customers to audit their security practices. Customers may however, require a Cloud vendor to sign paperwork for additional assurances of PHI protections.
No. A Cloud vendor is not a Business Associate if it receives and maintains only de-identified information. According to the HIPAA Privacy Rule and Security Rule, de-identified information is not considered protected health information.
You can also find HIPAA Compliant Hosting through specialized vendors.
Source: Guidance on HIPAA & Cloud Computing [HHS]