Business associate agreements

Managed IT Business Associate Agreements in Teaneck

A business associate agreement is the contract that sets the ground rules when an outside company handles a practice’s patient information. For Teaneck offices bringing in a managed IT provider, the useful questions are what belongs in it, what it does not do, and who should review it.

Qventive Healthcare, Hackensack, NJ · Updated November 2026

Quick answer

A business associate agreement, or BAA, is a written contract that limits how an outside company may use patient information, requires safeguards and incident reporting, and extends those duties to subcontractors. It is one required piece of HIPAA compliance, not all of it. Whether your IT provider needs one is a question for your counsel.

A nurse working at a computer in a clinic office while a masked physician stands beside her
Managed IT for a medical office is shared work between clinical staff and the people who run the systems. Illustrative stock photo.

What a BAA is, in plain terms

HHS’s page on business associate contracts explains that the HIPAA Rules generally require covered entities and business associates to enter into written contracts with their business associates. Those contracts set out how protected health information may be used and disclosed, require appropriate safeguards (including compliance with the Security Rule for electronic information), require reporting of breaches and incidents, pass the same obligations down to subcontractors, and provide for the return or destruction of PHI at the end of the relationship where that is feasible.

If you want the short version without the regulatory vocabulary, our explainer on what a HIPAA BAA contains covers it. This page is about the managed IT version of the question: what is different when the other party is the company that administers your servers, laptops, email and backups.

Not sure where your IT and HIPAA duties meet?Talk through your Teaneck practice setup with our Hackensack team.

Book a free conversation

Does an IT provider need one? Frame the question for counsel

We want to be careful here. HHS’s cloud computing guidance says that a cloud service provider that creates, receives, maintains or transmits ePHI for a covered entity is a business associate, and that a BAA is required. HHS’s business associate FAQs add that a software vendor is not a business associate merely for selling software when it has no access to PHI. Neither source addresses managed IT providers by name.

So the practical test is about access and function. Can the provider see, retrieve, copy, store or move your patients’ electronic information while doing the job, even if it never intends to? If it can, ask your attorney whether the arrangement is a business associate relationship and what the agreement should say. Do not rely on a vendor’s own statement either way, and do not treat the absence of a request for a BAA as proof that none is needed.

Why contract chains matter around Holy Name and its partner practices

Holy Name Medical Center lists nine medical partner practices, covering areas that include cardiovascular, pulmonary, OB/GYN, surgical, primary care, urology and women’s health. A Teaneck practice that exchanges referrals and records with a hospital-affiliated network is part of a chain of parties who each handle the same patients’ information. When one link has a weak contract, the others notice.

Take an illustrative case. A Teaneck specialty office uses a managed IT provider, which in turn uses a remote support tool and an offsite backup service. Patient data may touch all three. The practice signs one agreement, but the obligations need to reach the other two. That is what subcontractor flow-down means, and it is why we suggest practices ask for the names of any subcontractors that would handle ePHI, not just the provider’s own staff. Our own office is in neighboring Hackensack, so we meet these questions in the same referral landscape you do.

Provisions worth looking for

HHS publishes sample business associate agreement provisions, and it states that the sample language is not required for compliance. Treat the sample as a reference for what a complete agreement tends to cover, not as a template to paste. Under 45 CFR 164.314, a contract with a business associate must require it to comply with the applicable Security Rule standards, to ensure subcontractors that handle ePHI agree to the same security requirements, and to report any security incident it becomes aware of, including breaches of unsecured PHI. Beyond those rule-based items, read for the following:

  • What the provider may do with the data, and a clear statement that it may not do anything else.
  • Security safeguards the provider will maintain for ePHI, written in terms you can verify.
  • How and how quickly it will tell you about incidents it discovers.
  • Which subcontractors may touch ePHI, and how you are told when they change.
  • What happens to your data when the relationship ends.
From proposal to a reviewed agreementFive steps: list what ePHI the provider could reach, ask counsel whether the arrangement is a business associate relationship, name subcontractors, review incident and exit terms, then sign and file with the risk analysis.1List what they could reachSystems, backups, remote access2Ask counsel to classifyIs it a business associate role?3Name subcontractorsBackup, filtering, remote tools4Review incident and exittermsNotice, return, destruction5Sign and fileKeep with the risk analysis
Counsel review happens before signature, not after an incident.

What a BAA does not do

A signed agreement does not make a practice HIPAA compliant. It is one required element, and the practice still owes its own risk analysis, risk management, written policies and documentation. HHS’s cloud guidance makes a parallel point: signing with a vendor does not remove the customer’s own responsibilities for the controls it owns.

It also does not ensure the provider will perform. A contract states obligations. Whether the provider meets them is something you learn through reviews, reports and questions over time. NIST’s small-business guidance on outsourcing says even when you outsource, you do not transfer your liability. And HHS warns that its sample language may not make a binding contract under state law, and does not replace a lawyer, which is why your counsel should review the final text.

What a BAA does and does not doTwo columns. A BAA sets permitted uses, safeguards, incident reporting, subcontractor duties and data return. It does not make the practice compliant, replace the practice’s risk analysis, or confirm the vendor is performing.A BAA doesLimits how data may beusedRequires safeguards andreportingExtends duties tosubcontractorsSets data return termsA BAA does notMake the practicecompliantReplace a risk analysisProve the vendorperformsRemove the practice’sduties
A BAA is a required piece of the puzzle. The rest is still the practice’s work.

Subcontractors and the vendors behind your vendor

The Security Rule text requires a business associate contract to make subcontractors that handle ePHI agree to the same security requirements. In practice, this is where agreements either hold together or fall apart, because a managed IT provider typically depends on other companies for backup storage, email filtering or remote access.

HHS’s cloud guidance and FAQs also say a cloud provider that maintains ePHI is a business associate even if it cannot view the data because it is encrypted, and that using a cloud provider without a BAA puts a covered entity or business associate in violation of the HIPAA Rules. If your IT provider hosts or backs up data in a cloud, ask who signs with whom. Our vendor management guidance describes how practices keep a simple register of who holds what.

Clinician reviewing a prescribing decision support alert in the record system
Written responsibilities show a Teaneck practice what an IT provider handles and what the practice keeps. Illustrative stock photo.

Want a plain-language look at your IT setup?Ask us what a managed IT conversation should cover.

Talk with Qventive

Breach reporting clauses, and where New Jersey law comes in

Breach reporting is the clause that gets tested hardest. Under HHS’s Breach Notification Rule summary, a business associate must notify the covered entity of a breach without unreasonable delay and no later than 60 days from discovery. Sixty days is the outer limit, not a target. A practice that wants a faster notice, for example to meet its own obligations, can negotiate it into the agreement, and your counsel can advise on the wording. Our overview of HIPAA breach notification explains the practice’s side of the clock.

New Jersey adds its own statute. N.J.S.A. 56:8-163 requires a business or public entity that maintains computerized records with personal information to notify affected New Jersey customers in the most expedient time possible and without unreasonable delay, and it requires a party maintaining records for another business to notify that business immediately after discovery of a breach. The text, available from the New Jersey Legislature, does not mention HIPAA, so how the two regimes interact is a question for counsel. See also our page on New Jersey healthcare privacy laws.

Questions to ask before you sign

A good BAA conversation sounds more like diligence than a negotiation. HHS’s HICP guidance for small organizations says that vendors handling PHI need a BAA, that outsourcing does not remove cyber risk, and that practices should ask for security documentation and consider periodic business reviews. Use those themes as a checklist:

  • Will your staff or any subcontractor have access to ePHI, and which ones?
  • What written security documentation can you share?
  • How will we be told about an incident, and by whom?
  • How does the agreement handle subcontractor changes?
  • What will you return or destroy at the end, and in what form?
  • How often will we review the arrangement together?

Ending the relationship: data return and the exit clause

HICP’s small-practice volume notes that contracts should define data return or destruction after termination, and HHS’s contract page lists return or destruction as an element where feasible. Ask early, because exit terms are easiest to agree before anyone is unhappy. What formats will your data come back in? Who confirms destruction? Who holds the administrator credentials until the handover is complete?

If you are already in a contract and unsure of its terms, our guide to switching managed IT providers walks through a handover, and the guide to choosing a HIPAA managed IT provider lists what to ask up front. Your EHR vendor’s support terms deserve the same scrutiny, and the EHR support comparison for Teaneck shows where those agreements differ. We are glad to discuss BAA terms with your counsel as part of scoping, and the wider HIPAA compliance framework shows where the agreement sits among the other required pieces.

Review IT provider terms with a Teaneck-area team

Send us the agreement you are considering, or tell us what your current provider can access. We will point out technical questions to raise with your attorney and with the provider.

Call (201) 488-2750 or send us a message. Qventive Healthcare is at 200 Passaic Street, Hackensack, NJ 07601, and has served Northern New Jersey healthcare since 1994.

Questions Teaneck practices ask about IT provider BAAs

Is our managed IT provider automatically a business associate?

Not automatically, and we cannot answer that for your practice. HHS’s cloud guidance says a cloud provider that creates, receives, maintains or transmits ePHI is a business associate, and its FAQs say a software vendor with no PHI access is not one merely for selling software. Managed IT providers are not addressed by name in the sources we rely on. The deciding factor is what access the provider has to ePHI and what it does with it. Ask your attorney to make that determination for your specific arrangement.

If we sign a BAA, are we HIPAA compliant?

No. A BAA is one required element of the Security Rule’s organizational and administrative requirements. The practice still needs its own risk analysis, risk management, written policies, workforce training and documentation. A BAA also does not prove the vendor is doing what it promised. Treat it as the contract foundation and keep checking performance.

Can we use HHS’s sample BAA language as-is?

You can use it as a reference, but HHS states that the sample language is not required for compliance. HHS also notes that it may not make a binding contract under state law by itself and that it does not replace a lawyer. Have your attorney adapt the agreement to your practice and the services provided. Use the sample list of topics as a check on whether anything is missing.

What should a BAA say about subcontractors?

Under the Security Rule text, a business associate contract must require subcontractors that handle ePHI to agree to the same security requirements. In an IT context, that often means backup, email security and remote support vendors. Ask for the names of subcontractors who would touch your data and how you will be told if they change. Make sure the flow-down is in writing.

How soon must a vendor tell us about a breach?

HHS says a business associate must notify the covered entity without unreasonable delay and no later than 60 days from discovery, and 60 days is an outer limit. New Jersey’s statute separately requires a party maintaining records for another business to notify that business immediately after discovering a breach. Because the HIPAA and state rules were written separately, ask your counsel how they apply together. A practice can ask for a shorter contractual window; your counsel can advise on the wording.

How do we get started with Qventive on this agreement question?

Contact us at (201) 488-2750 and tell us which systems an IT provider would touch. We will walk through what access is involved, what documentation we can offer, and which points your counsel should look at. Qventive is based at 200 Passaic Street in Hackensack and has served Northern New Jersey healthcare since 1994. We work alongside your attorney instead of replacing one.

Does a BAA change what managed IT costs?

Not directly. Cost follows scope: the number of users and devices, the systems covered and the level of security work involved. We do not publish prices here because they would not mean much without that context. If a provider offers a very different price when you ask for a BAA, ask them to explain what is being added or removed in plain language.

This page is general information for practice leaders. It is not legal or clinical advice. Clinical content decisions belong to your physicians, and compliance questions belong with your counsel.