HIPAA defines a business associate as anyone that performs on behalf of a covered entity a function or activity regulated under HIPAA privacy and security regulations. HIPAA regulates a covered entity’s passive storage of ePHI by imposing on the covered entity strict requirements to ensure the confidentiality, integrity and availability of ePHI maintained by the covered entity. Because HIPAA regulates a covered entity’s passive storage of ePHI, disclosure of ePHI by the covered entity to a cloud vendor for the purpose of storing the ePHI makes the vendor a business associate. Because the cloud vendor is a business associate, a BAA is required prior to the vendor assuming responsibility for the ePHI.
The Health and Human Services (HHS) Office of Civil Rights (OCR) enforces HIPAA’s Privacy and Security Rules. During a speech at the Health Care Compliance Association’s 16th Annual Compliance Institute, OCR’s David Holtzman, Information Privacy Division, said “[i]f you use a cloud service, it should be your business associate. If they refuse to sign a business associate agreement, don’t use the cloud service.”
Selecting a Cloud Vendor
From a compliance perspective, the most important consideration when establishing an ePHI storage arrangement with a cloud vendor is to negotiate and execute a HIPAA-compliant BAA with the vendor. HITECH imposes certain security and privacy requirements directly on business associates, but BAAs are still required for a covered entity to discharge its HIPAA obligations with respect to ePHI disclosed to a cloud vendor. As with any other business associate arrangement, the business associate will be directly and contractually obligated to comply with applicable provisions of HIPAA and HITECH regulations, including implementing and maintaining appropriate safeguards, protecting the confidentiality of ePHI and providing notification to the covered entity in the event of a breach.
Other considerations when selecting a cloud vendor include confirming the rigor of authentication protocols imposed by the cloud vendor, confirming that the vendor adequately ensures data is and remains segregated from other data in the shared cloud, and confirming that the form and format of ePHI delivered to and from the cloud vendor is compatible with the covered entity’s needs.
Another important consideration is the level of encryption offered by the cloud vendor for ePHI stored in the cloud as well as ePHI transferred between the provider and cloud vendor. HITECH breach notification requirements apply to a breach of unsecured ePHI transferring to and from, and stored in the cloud. Unsecured ePHI means that the ePHI is not encrypted to make the information unusable to unauthorized individuals. Ensuring adequate encryption for ePHI transferred to and from, and stored with a cloud vendor significantly reduces the potential for liability associated with a required breach notification.
In summary, “cloud computing” can offer significant advantages for health care providers and related health care entities, but covered entities and their cloud vendor business associates must be mindful that the same HIPAA and HITECH requirements apply “in the cloud.”
Clay B. Wortham
McBrayer, McGinnis, Leslie & Kirkland, PLLC
 45 C.F.R. § 160.103
 45 C.F.R. § 160.103.
 45 C.F.R. §§ 164.302, 164.306 and 164.502.
 45 C.F.R. § 164.103.
 45 C.F.R. § 164.502(e)(2).
 The Secretary of HHS delegated authority for administration and enforcement of the Security Rule from CMS to OCR on July 27, 2009.
 45 C.F.R. § 164.502(e)(2); HITECH Act, Pub. L. 111-5 §§ 13401, 13404.
 45 C.F.R. § 164.404.
 45 C.F.R. § 164.402.