What is a Business Associate Agreement?

What is a BAA?

The HIPAA Privacy Rule amendment in 2003 introduced a new administrative safeguard declaring that all covered entities must have a signed Business Associate Agreement (BAA) in place with all Business Associates (BA) and Covered Entities that manage, process or archive Protected Health Information (PHI).

HIPAA Business Associate Agreement:

As one of the leading HIPAA compliant hosting companies in the United States, Atlantic.Net (and our healthcare partners utilizing our award-winning cloud platform) are directly impacted by this amendment. Atlantic.Net is a Business Associate of each healthcare organization with whom we process, store, manage or otherwise deal with PHI, and therefore, we are legally obliged to sign a contract of service with each organization to guarantee our HIPAA compliant status.

When is a HIPAA BAA required?

A BAA is not necessarily a single standalone agreement; BAAs often include a combination of service level agreements, response times for incidents, and RTO and RPO guarantees for a disaster recovery solution.

With HIPAA BAA, there are two types of business associate relationships:

• BAA between a Covered Entity and a Business Associate
• BAA between a Business Associate and a subcontractor

What is a subcontractor in a BAA?

Subcontractors are vendors and third parties that provide Atlantic.Net with services for our day-to-day business operations. Any vendor Atlantic.Net engages with as part of our HIPAA compliant business offerings will sign the BAA if offering in-scope services; this task is managed by Atlantic.Net.

What does a BAA achieve?

A HIPAA BAA creates a bond of liability, outlining the shared responsibilities of the Covered Entity and the Business Associate (in this case, Atlantic.Net). Atlantic.Net’s BAA offers assurances regarding our HIPAA and HITECH accreditations and details the guarantees we provide for each of the administrative, physical, and technical safeguards we implement to protect ePHI.

What guarantees does Atlantic.Net’s BAA offer?

As a trusted business associate, we will:

• Adhere and uphold the requirements of HIPAA legislation, including the Security and Privacy rule amendments
• Provide a HITECH compliant hosting environment
• Not disclose PHI, except as permitted by law
• Document the in-scope PHI to be transferred, processed and archived by Atlantic.Net on behalf of the CE
• Demonstrate that proven protections are in place to prevent unlawful PHI disclosures, including technical solutions such as a VPN, TLS encryption, DR capability, and managed firewall capabilities. Click here to find out more
• Provide guaranteed escalation processes to manage any ePHI breach notifications
• Upon request, Atlantic.Net must give the HHS access to the HIPAA policy documentation and detailed logging information of user activity
• When the contract ceases, if feasible, ePHI must be returned to the Covered Entity or evidence must be provided to confirm the destruction of ePHI

According to The Health Insurance Portability and Accountability Act (HIPAA), there are two different types of organizations that must ensure compliance: covered entities and business associates. Atlantic.Net™ falls into the latter category, a third-party entity contracted to handle ePHI (electronic protected health information).

In order to both comply with the law and assure our clients that we’re committed to keeping their information safe, we’ve drafted up a HIPAA Business Associate Agreement, or BAA. BAAs are a type of HIPAA-Compliant documentation that is critical to our relationship with healthcare firms and medical practitioners alike, as it firmly establishes the legal parameters for our use of ePHI. The following three components are central to this contract:

• Business associate’s role – the exact nature of the third party’s interaction with the healthcare data, including any forms of use and disclosure.
• Limitations – the prohibition of the third-party from any forms of use or disclosure not stated in the agreement.
• Security requirements – the necessity for extensive security technologies and protocols to guard against any unauthorized use or disclosure.

In conjunction with our SOC 2 TYPE II and SOC 3 TYPE II certified data center, our BAA documentation shows that we’re committed to keeping the private healthcare information of our clients both safe and secure. Moreover, BAAs show that we’re willing to go beyond the minimum standards of compliance established in HIPAA. Healthcare organizations that choose us as a host have the peace of mind that can only come from knowing that they’re partnered with a veteran - and one that’s completely committed to their best interests, at that.

For more information about our HIPAA Business Associate Agreement or to request a copy of our agreement, please contact us today!

Sample BAA:

Why choose Atlantic.Net as your next Business Associate

Atlantic.Net has built one of the most popular HIPAA compliant hosting environments available, bringing together our 25 years of experience in the information technology sector. We know what is important to our healthcare partners and are delighted they explicitly trust us to handle their patients’ ePHI.

Want to know more about the technical safeguards of our HIPAA hosting solution? Check out our HIPAA hosting page.

• How to Become HIPAA-Compliant: Our 10-Step Guide
• What Are HIPAA Compliance Rules and Guidelines?
• HIPAA Compliant Hosting Requirements Checklist
• What Is a HIPAA Compliant Cloud?
• HIPAA Security Services
• HIPAA IT Compliance Guide
• How to Make Your WordPress Site HIPAA-Compliant
• How to Find the Best Hosting Platform for HIPAA Compliant Forms
• Why Is Encryption So Key to HIPAA Compliance?
• What Is HIPAA Healthcare Hosting?
• How HIPAA Compliance Affects Employees
• Do I Need to Be HIPAA Compliant?
• HIPAA Compliant Developers Guide
• What Is a BAA?
• Best Practices for Creating a HIPAA Compliant cPanel Host
• What Is a HIPAA API?
• Top 13 Difficult Questions Your HIPAA Consultant Should Be Asking You
• Top HIPAA Software Developers
• Top HIPAA Training Companies
• HIPAA Compliant Hosting for a Web Application: 8 Questions to Ask
• How to Make a Website HIPAA-Compliant
• COVID-19: Will the OCR Exercise Enforcement Discretion and Waive Penalties for HIPAA Violations?
• How to Run an Online Business While Ensuring HIPAA Compliance
• Achieving HIPAA Compliance with Mobile Devices
• What Is the HIPAA Security Rule?
• Most Common HIPAA Violations and Tips to Stay Compliant
• Penalties for Non-Compliance of HIPAA – What Is the Fine?
• How to Prevent a HIPAA Data Breach
• HIPAA White Papers
• HIPAA Case Studies
• HIPAA Brochures

More About BAAs

How the BAA fits in – basic HIPAA elements & definitions

A brief review of HIPAA and its primary component parts allows us to place the business associate’s agreement in context.

The vast majority of healthcare companies must abide by the parameters of the Health Insurance Portability and Accountability Act (HIPAA), an Act passed by the United States Congress in 1996 that safeguards American citizens’ health data. The data that falls under the auspices of the law – as governed by the Department of Health & Human Services (HHS) – is designated, collectively, as protected health information (PHI).

PHI is typically handled by covered entities. Organizations in that category include healthcare providers, healthcare plans, and healthcare clearinghouses. Examples of each type of HIPAA-compliant organization are as follows:

• providers – doctors, dentists, nursing homes, pharmacies, etc.
• plans – health insurance companies, HMOs, Medicare, Medicaid, etc.
• clearinghouses – transcription services, etc.

Any of the above organizations necessarily handle PHI as a central responsibility of their business. The Privacy Rule and Security Rule of HIPAA require covered entities to protect patient data from loss, theft, or any other misuse.

A covered entity can choose to work with a business associate, outsourcing certain aspects of operations to a trusted third party. In order to appropriately place responsibility into the hands of the external organization, both companies must agree to the terms of a BAA. By signing the agreement, the business associate agrees to safeguard PHI and to perform its obligations to the covered entity within the guidelines of HIPAA.

Characteristics of a HIPAA BAA

According to the HIPAA guidelines, a BAA must do the following (as discussed by healthcare video-conferencing company SecureVideo in a 2013 article):

• describe the specific ways in which PHI is being used (transferred, processed, and/or stored) by the business associate, along with any ways in which they are being contracted by the covered entity to disclose PHI;
• establish that the business associate cannot use or disclose any health data beyond the purposes established in the agreement, except in special cases when cooperating with law enforcement;
• dictate that the business associate must have strong, proven protections established that disallow any malicious or otherwise unlawful PHI disclosure, use, or access – one part of which is the electronic means stipulated by the HIPAA Security Rule (including VPN capability and SSL encryption within a firewall-secured private network);
• stipulate that the business associate must immediately notify the covered entity if PHI is used or disclosed in a manner that goes beyond the parameters established in the agreement, such as in the event of a data breach;
• direct the business associate that it must protect data but also make it readily available, so that individuals can get access to their medical records as established by the law and have the ability to revise their PHI according to the amending/accounting guidelines set forth in HIPAA;
• outline the business associate to follow the Privacy Rule of HIPAA (to whatever degree the covered entity is entrusting the business associate to handle privacy-related activities);
• state that the business associate must allow the Department of Health & Human Services access to its policy documents and all accounting files that pertain to PHI use and disclosure – whether the applicable data is obtained directly from the covered entity or representing its interests – so that the US government can properly determine compliance;
• delineate the need for the business associate to return any PHI to the covered entity or to completely delete all PHI data – whether that data was obtained via the covered entity or in the business associate’s capacity as its representative – if and when the agreement between the two parties ends, if such return or deletion is possible and reasonably accomplished;
• hold the business associate responsible for its relationship with subcontractors who may additionally be exposed to PHI, so that they are held accountable with the same requirements that pertain to the business associate; and
• allow the covered entity to cancel the agreement at any time if the business associate is in noncompliance with any of its stipulations.

This page was updated on February 8, 2021.