When a hospital or health plan places records in a cloud environment, the company storing or processing those records does more than provide disk space. Under federal guidance from the Office for Civil Rights, including HHS documents published in the Federal Register, a cloud service provider that stores or processes protected health information is a business associate under HIPAA.
This classification applies even when the provider has no role in treatment or payment. Maintaining or processing the information brings the cloud arrangement within the business associate framework. The parties must address how the information may be used, protected, and handled during the relationship.
Why cloud storage creates a business associate relationship
A cloud provider may operate behind a hospital portal, a health plan website, or another service that patients use directly. Patients may not know which company maintains the systems or stores their records. That lack of visibility does not change the provider’s role under the guidance.
The relevant question is whether the provider stores or processes protected health information. If it does, the provider is a business associate, even if its work consists only of maintaining records or operating systems. A hospital or health plan cannot treat the arrangement as an ordinary technology purchase without health privacy obligations.
The organization placing records in the cloud and the provider handling them need to address the relationship directly. The provider’s duties should be defined in the business associate agreement. They should not depend on assumptions about the technology or on the fact that another company operates the underlying infrastructure.
Encryption does not end the obligation
The guidance considers whether a cloud provider falls outside HIPAA when it never sees records in decrypted form. The answer is no. Holding encrypted information still counts as maintaining it. Security rule obligations therefore apply even when the provider does not possess the key.
The absence of the key may affect the risk analysis for a particular safeguard. A provider that cannot decrypt the information presents different risks from a provider that can read it. That difference does not remove the obligation to protect the information. It also does not change the need to treat the provider as a business associate.
Encryption remains one part of the security assessment. It does not eliminate the need to evaluate the cloud service. The organization using the service still needs to know where records are stored, how the provider processes them, and which safeguards apply. The risk analysis can account for the provider’s inability to decrypt the records while recognizing that the provider maintains them.
What the business associate agreement should address
The practical result is a business associate agreement. The agreement should state how the provider may use the information and describe its responsibilities after a breach, including the timing of breach notifications.
It should also cover the provider’s obligations to its own subcontractors. Cloud services may include companies beyond the provider named in the initial arrangement. Responsibilities related to protected health information therefore need to extend through that structure.
The contract should contain clear terms for the end of the relationship. It should explain what happens to the data after the hospital or health plan stops using the cloud service. Those terms give the organization a defined way to determine how records will be handled once the service ends.
Availability also belongs in the agreement and in service planning. Service level terms matter because records that cannot be reached during an outage create a separate compliance problem. Protection against unauthorized access does not solve the problem of authorized users being unable to reach records when they need them.
What to check before sharing records
Telehealth coverage information sits behind many online intake forms or consultations for telehealth weight-loss programs. Cloud arrangements therefore sit behind an online intake form or consultation. Before sharing a medical history with a subscription clinic, a patient should identify the company operating the service and learn how it handles records.
Encryption by itself does not answer those questions. The patient should also consider which companies handle the information and whether the arrangement explains permitted uses. The handling of breach notifications, coverage of subcontractors, and treatment of records after the service ends also need review. Availability matters because an outage can make records inaccessible even when the information remains protected from unauthorized access.
For a comparison of companies selling these programs directly to patients, see our clinic comparison and record-handling considerations.