HIPAA security for small practices
Which vendors need a business associate agreement
A vendor needs a business associate agreement when it creates, receives, maintains or transmits patient information on your practice's behalf, or when the service it provides you involves your patients' information. For a small practice that usually means the cloud EHR or practice management vendor, the billing company and clearinghouse, whoever supports your computers, cloud backup and storage, the email provider if email carries patient details, an answering service that takes patient messages, and an off-site shredding company. The postal service, your internet provider, the cleaning crew, the bank and a lab you send a patient to for treatment do not need one. The agreement has to be signed before the vendor gets the information, and HIPAA sets what it must say.
A business associate agreement, or BAA, is the written contract HIPAA requires between a practice and each of these vendors. The definition of a business associate is in 45 CFR 160.103, and the contract terms are in the Privacy Rule at 45 CFR 164.504(e) and the Security Rule at 45 CFR 164.314(a). The full guide to the HIPAA Security Rule for small practices covers where vendor agreements sit among the rule's other requirements.
What makes a vendor a business associate
Under 160.103, a business associate is a person or company, other than a member of your workforce, that does one of two things for your practice:
- It "creates, receives, maintains, or transmits protected health information" for a function HIPAA regulates. The rule's examples include claims processing, data analysis, quality assurance, billing and practice management.
- It provides "legal, actuarial, accounting, consulting, data aggregation, management, administrative, accreditation, or financial services" to your practice, where the service involves disclosing your patients' information to it.
Two words in that definition decide most cases. "Maintains" means a vendor that only stores your data counts, even if it never opens it. "On behalf of" means the vendor is doing your practice's work, not its own.
Your workforce is outside the definition. The rule defines workforce as employees, volunteers, trainees and others whose work is "under the direct control" of the practice, paid or not.
Who needs a business associate agreement in a small practice
HHS lists examples on its business associates guidance page, last reviewed July 30, 2026, and answers specific cases in its FAQs. Here is how the vendors a small practice usually has line up:
| Vendor | Needs a BAA? | Why |
|---|---|---|
| Cloud EHR or practice management software | Yes | HHS's software vendor FAQ says a company that hosts software containing patient information on its own server is a business associate |
| Software on your own computers, where the vendor never sees patient data | No, until it does | The same FAQ says selling software is not enough, but a vendor that accesses patient information when troubleshooting is a business associate |
| Billing company | Yes | Billing is named in the 160.103 definition |
| Clearinghouse | Yes | HHS lists a clearinghouse that translates claims for a provider |
| IT support or managed service provider | Yes, if it can reach systems holding patient data | HHS lists IT contractors and managed service providers that support those systems, in person or remotely |
| Cloud backup and file storage | Yes, even if the data is encrypted | HHS's cloud computing guidance |
| Email provider | Yes, if email holds patient information | A provider that stores your mailboxes is a cloud service that maintains the data |
| Internet provider, phone carrier, postal service, couriers | No | The conduit exception, below |
| Answering service that takes patient messages | Yes, in most cases | It creates and receives patient information for you |
| Off-site shredding or records storage | Yes | HHS's FAQ on incidental contact says a shredding service "likely would be a business associate" |
| Copier or device technician | Yes, when the service exposes stored patient data | HHS lists technicians who service devices that store patient information |
| Accountant or attorney | Yes, when the work involves patient information | HHS lists both |
| Cleaning crew, electrician | No | Any contact with patient information is incidental |
| Lab, specialist or hospital you refer a patient to | No | Disclosures to another provider for treatment are excluded |
| Bank or card processor | No | HHS says processing payments is the bank's own service, not work for the practice |
Two of these need a closer look.
Answering services. We found no HHS guidance that names answering services. The definition still fits: an operator who writes down a patient's name, callback number and symptoms is creating patient information for your practice. The phone company carrying the call is a conduit, and HHS says a provider can call a patient through a Telecommunications Relay Service without a BAA. The service taking the message is a different matter.
Shredding on your premises. HHS's FAQ says that when shredding or records work is done "under the direct control" of the practice, such as on your premises, you may treat the service as part of your workforce. A truck that takes the bins away is not under your direct control.
The conduit exception
A conduit carries information without accessing it, except "on a random or infrequent basis," and doesn't need a BAA. HHS's conduit FAQ names the US Postal Service and certain private couriers.
In the preamble to the 2013 Omnibus Rule, HHS called the exception "a narrow one," limited to "mere courier services" and their electronic equivalents, "such as internet service providers (ISPs) providing mere data transmission services." What separates the two is how long the vendor holds the data. A conduit's access is transient. A company that keeps the data has persistent access and is a business associate, and the preamble says document storage companies count whether or not they look at what they hold.
For a practice, that puts the internet provider on the conduit side and the company hosting your email, files or backups on the business associate side.
Cloud and email providers
HHS's cloud guidance says a cloud service provider that stores patient information for you is a business associate "even if the CSP processes or stores only encrypted ePHI and lacks an encryption key for the data." Using one without a BAA is a violation in itself, and the guidance cites a resolution agreement with a covered entity that stored the information of over 3,000 people on a cloud server with no BAA.
The two big office suites handle the agreement differently:
- Microsoft 365. Microsoft's HIPAA compliance page says its BAA is available "by default" to covered entity customers through the Microsoft Online Services Data Protection Addendum. Exchange Online, OneDrive for Business, SharePoint Online and Teams are on its in-scope list. Microsoft says it can't use a customer's own BAA.
- Google Workspace. Google's HIPAA help page says administrators must review and accept the BAA before using patient information in Google services. A super administrator does it in the Admin console under Account settings, Legal and compliance. It covers only the services on Google's HIPAA Included Functionality list.
Microsoft says its BAA alone doesn't make you compliant. Your practice still sets up the accounts, sign-ins and sharing.
Subcontractors
Your vendors' vendors count too. Under 160.103, a business associate includes "a subcontractor that creates, receives, maintains, or transmits protected health information on behalf of the business associate." If your billing company stores your claims with a cloud host, that host is a business associate.
You don't sign with the subcontractor yourself. 45 CFR 164.502(e)(1) says a practice "is not required to obtain such satisfactory assurances from a business associate that is a subcontractor." Your vendor gets its own BAA from the subcontractor, and your agreement with the vendor has to require that.
What the agreement must say
Under 164.504(e)(2), the contract must:
- Say what the vendor may and must do with your patients' information, and nothing the Privacy Rule wouldn't let your practice do.
- Bar any other use or disclosure, except as the law requires.
- Require appropriate safeguards and, for electronic information, compliance with the Security Rule.
- Require the vendor to report any use or disclosure the contract doesn't allow, including breaches of unsecured patient information.
- Pass the same restrictions on to any subcontractor.
- Require the vendor to help you give patients access to their records, amend them and account for disclosures.
- Require the vendor to follow the Privacy Rule for any of your duties it carries out.
- Open its records on your patients' information to HHS.
- Require the vendor to return or destroy the information when the contract ends, or keep protecting what it can't return.
- Let you end the contract if the vendor violates a material term.
The Security Rule's version, 164.314(a)(2)(i), adds that the vendor will comply with the Security Rule, make its subcontractors agree to the same, and report "any security incident of which it becomes aware," including breaches.
Signing isn't the end of it. Under 164.504(e)(1)(ii), if you know of a pattern of activity by the vendor that materially breaches the agreement, you must take reasonable steps to fix it, and end the contract if that fails and ending it is feasible.
What HHS's sample agreement leaves to you
HHS publishes sample business associate agreement provisions, dated January 25, 2013. HHS says using them isn't required, and that they alone may not make a binding contract under state law.
On October 16, 2026 we read the sample provisions in full and counted what they leave open. The sample lists nine obligations of the vendor and marks ten provisions optional. It has five blanks: both parties' names, the start date, the end date or event, and one cross-reference. It offers three either-or choices, covering how to limit the vendor's uses, how to apply the minimum necessary standard and what happens to the data at the end. In four places it suggests the parties add detail, starting with when the vendor must report a breach.
No number of days appears anywhere in the sample. The deadline for a vendor to tell you about a breach comes from the Breach Notification Rule instead: "without unreasonable delay and in no case later than 60 calendar days after discovery," under 45 CFR 164.410(b). Your own notices to patients can't go out until you hear from the vendor. The sample's note suggests "a stricter timeframe," and you can ask for one.
Large vendors use their own agreement, as Microsoft does. Read it against the list above, and look for the breach reporting deadline and the subcontractor clause.
What happens without one
HHS's FAQ on certification says a vendor can't self-certify or be certified as HIPAA compliant in place of the contract. A "HIPAA compliant" badge on a vendor's website is not a BAA.
The enforcement record includes a small practice. In 2017 the Center for Children's Digestive Health, which HHS described as "a small, for-profit health care provider," paid HHS $31,000 and agreed to a corrective action plan. It had sent patient records to a records storage company since 2003, and neither side could produce a signed BAA from before October 12, 2015.
Keeping the vendor list current
- List every company that touches patient information, including the ones that only store it.
- Mark each one yes or no, with the reason.
- For each yes, get the signed agreement and note the date and where the copy is kept.
- Check that each agreement has a subcontractor clause and a breach reporting deadline you can live with.
- Get the agreement signed before a new vendor gets any patient data.
- When a vendor relationship ends, confirm in writing that the data was returned or destroyed.
- Keep the agreements with your other Security Rule records, which 164.316(b)(2) says to keep for six years.
- Review the list with your HIPAA risk analysis each year.
The same list answers the vendor questions on insurance forms, which common cyber insurance application questions walks through.
Crashcart, which runs IT for small offices, keeps this list for a practice under HIPAA: each vendor that handles patient data and whether it has signed an agreement. Crashcart signs one with your practice too. An admin at the practice reads and signs it in the dashboard under Settings, Agreements, Crashcart countersigns, and it appears on the vendor list with its agreement in place. Your practice still decides which vendors get patient data, and reads and signs every other vendor's agreement.
This is general information, not legal advice. For your situation, ask your attorney.
More in this topic
Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.