Skip to main content

Medical Practice Cloud Provider Checklist Before You Sign

November 20, 2026 5 min read
Closed folder beside a glass sculpture representing cloud storage in a medical office.

A medical practice cloud provider checklist should do more than ask whether a vendor is “HIPAA compliant.” Before moving electronic protected health information (ePHI), confirm which cloud services will handle it, whether the provider is acting as a business associate, and how responsibilities are divided between the provider and your practice.

Review the business associate agreement (BAA), service-level agreement, and service description together. A promise in one document may be limited or qualified by another. Use the questions below to identify what needs clarification before signing or migrating data.

Confirm which service will handle patient information

Start with the specific product, feature, and service configuration you plan to use. A cloud company may offer multiple services, but that does not mean every service is covered by the same terms or BAA.

  • Will the service create, receive, maintain, or transmit ePHI for the practice?
  • Which applications, storage locations, support tools, and connected services will be in scope?
  • Will the provider or its subcontractors be able to access or handle the information?
  • Does the BAA name or otherwise clearly cover the exact service and arrangement being used?

Do not rely on a general statement about the vendor’s HIPAA readiness. Verify that the agreement applies to the service that will actually store or process patient information. For background on healthcare privacy and security resources, consult Health IT’s privacy and security resources for providers.

Interlocking transparent forms above a closed folder representing shared cloud security responsibilities.

Review the BAA alongside the other contract terms

When a cloud provider performs work involving ePHI on a practice’s behalf, the parties should determine whether a BAA is required and ensure the agreement covers the service. Read the BAA together with the service description and SLA, rather than treating it as a standalone form.

Check whether the documents clearly address:

  • Permitted uses and disclosures: What may the provider do with ePHI to deliver the service, and what uses are outside that scope?
  • Safeguards: What security commitments apply, and are they consistent across the agreement and service description?
  • Subcontractors: Which subcontractors may handle ePHI, and how are their responsibilities addressed?
  • Incident reporting: What events must be reported, who receives the report, what information it includes, and how quickly the provider must notify the practice under the contract?
  • Practice access: How can the practice retrieve information it needs to support patient care, operations, or its own obligations?
  • End of service: What assistance is available for exporting data, and what happens to remaining copies?

Clarify terms that are vague, inconsistent, or dependent on another document. For help thinking through service commitments and responsibilities, see this guide to what to review in an IT service-level agreement.

Document the shared security responsibilities

Using a cloud provider does not make the practice’s security responsibilities disappear. The provider may operate parts of the underlying service, while the practice remains responsible for decisions and safeguards within its own environment. The division depends on the service and configuration, so get it in writing rather than assuming who handles a task.

Ask the provider and practice team to document who is responsible for:

  • Configuring accounts, permissions, and access controls
  • Approving and removing staff access
  • Monitoring activity and reviewing alerts
  • Applying updates and maintaining the service
  • Securing devices and connections used to access cloud information
  • Responding to incidents, preserving relevant records, and coordinating communications
  • Managing backups, restoration, and recovery testing
  • Providing information that helps the practice assess and document safeguards

Be specific about operational ownership. For example, “the provider monitors the service” does not necessarily explain who reviews account activity, handles a compromised user account, or contacts the practice when something requires its attention.

Include the cloud arrangement in the practice’s risk analysis

A provider’s security materials can inform the practice’s evaluation, but they do not replace the practice’s own assessment of its cloud arrangement. Consider the information being stored, how it moves between systems, who can access it, and what could happen if the service or an account is unavailable or compromised.

Before migration, document the relevant systems, data flows, access needs, and safeguards. Identify dependencies such as connected applications, user devices, and third-party services. Then decide how the practice will address identified risks and keep its documentation current as the service or configuration changes. A cybersecurity risk assessment can help organize this review, but the cloud-specific arrangement still needs to be understood and recorded.

Check backups, recovery, and availability terms

Do not assume that cloud storage alone provides the backup and recovery arrangement the practice needs. Confirm what is backed up, how restoration works, and what the provider commits to in the relevant service terms.

  • Which information and configurations are included in backups?
  • How can the practice request restoration, and who coordinates the work?
  • What service availability and support commitments apply?
  • How will the practice access information or continue essential workflows during an outage?
  • Does the practice have a way to verify that recovery procedures work for its needs?

Make sure the answers fit the practice’s own continuity plans. “Backups are included” is not enough if the contract does not explain scope, access, restoration support, or the practice’s responsibilities.

Plan for incidents and the end of the relationship

Agree on an incident communication process before patient information is moved. The contract should explain how the provider reports a suspected or confirmed security incident involving ePHI, what details it will share, and how the parties will coordinate investigation and response. Confirm that the timing and process are clear to the practice team. Do not assume a general support ticket or routine service notification is the same as a security incident report.

Also plan for an orderly exit. Confirm the available data export format, the steps and support needed to retrieve information, and how the provider handles copies that remain after the service ends. If complete deletion is not feasible in a particular situation, clarify what is retained, why, how it remains protected, and when it can be removed. Make sure the agreement’s exit terms align with the practice’s operational needs and documentation.

Frequently asked questions

Does a cloud provider that stores patient information need to sign a BAA?

It depends on the provider’s role and the service. If the provider handles ePHI on the practice’s behalf in a way that makes it a business associate, the practice should ensure the appropriate BAA covers that service. Confirm the arrangement rather than relying on a general vendor statement.

Who is responsible for security when a practice uses cloud storage?

Responsibilities are shared and depend on the service. The provider and practice should document who handles configuration, access, monitoring, incident response, backups, recovery, and related operational tasks.

Does encryption mean a provider does not need a BAA?

Do not treat encryption by itself as proof that a BAA is unnecessary. Determine the provider’s role and how the service handles ePHI, then confirm the agreement requirements for that specific arrangement.

Can a provider store ePHI outside the United States?

Do not assume location alone answers whether an arrangement is appropriate. Confirm where information is stored and accessed, which subcontractors are involved, and how the contract and safeguards address the arrangement. Seek qualified privacy, security, and legal review for practice-specific questions.

What should happen to patient data when the cloud service ends?

Agree in advance on how the practice can export its information, what support the provider will provide, and how remaining copies will be handled. The contract should also address any situation where complete deletion is not feasible.

Make the decision with clear ownership

A careful review helps a practice understand what it is adopting, what the provider is committing to, and which responsibilities remain with the practice. Zevonix provides managed IT, cybersecurity, and technology planning, including compliance support and cloud services. If your practice is evaluating a cloud arrangement, contact Zevonix to discuss the technical responsibilities, security considerations, and continuity planning involved.

Ready to Strengthen Your IT?

Let Zevonix handle your technology so you can focus on what matters most — your business.

Schedule a Free IT Assessment