Skip the reading? Sign up and get a readiness score today. Plans from $47 a month, prices published.
HIPAA compliance for business associates means running the full Security Rule, honoring every term of the business associate agreements you sign, reporting breaches to your customers, and holding your own subcontractors to the same standard. Since the 2013 Omnibus Rule, HHS can fine a business associate directly. For a 30-person software or billing company with a few healthcare customers, year one usually costs about $13,000 to $32,000 before any outside assessment, most of it staff time.
This article is for the founder, operations lead or first security hire at a company that touches protected health information on behalf of someone else: a SaaS vendor whose customers are clinics, a medical billing company, a transcription or coding service, a managed IT provider with hospital clients. It covers what the law puts on you directly, what your customers add through the BAA, a worked budget, and where software fits. If you are budgeting HIPAA work in general, the companion piece on HIPAA certification cost has the penalty tiers and a broader cost breakdown.
Are business associates required to comply with HIPAA?
Yes. A business associate must comply with the whole Security Rule and with the parts of the Privacy and Breach Notification Rules that apply to it. HHS can investigate and fine a business associate directly, without going through the covered entity. The BAA you signed adds contract duties on top, and your customer can enforce those separately.
Before 2013 the usual view was that a vendor's only HIPAA exposure was the contract. The HITECH Act and the Omnibus Rule changed that. HHS published a fact sheet on the direct liability of business associates that lists the ten things it can penalize you for on its own authority. Read it once, because it is shorter than most BAAs and it is the list an investigator starts from.
What business associates are directly liable for
The fact sheet groups direct liability into ten items. This table restates them in plain terms and adds what you should be able to show for each one. The third column is the useful part: it is what a hospital security reviewer asks for in a questionnaire, and what an investigator asks for after a complaint.
| Direct liability under HHS rules | What it means day to day | What you should be able to show |
|---|---|---|
| Comply with the Security Rule | Risk analysis, risk management, access control, audit logs, training, contingency plan, policies | A dated risk analysis, the policy set with approvals, training records, access review records |
| Notify the covered entity of a breach | Tell your customer without unreasonable delay and within 60 days of discovery (45 CFR 164.410) | An incident register with discovery dates and notification dates |
| Enter BAAs with subcontractors | Every vendor that stores or processes PHI for you signs a BAA with you | A vendor list showing which ones touch PHI, with the signed BAA attached |
| Act on a subcontractor's material breach | If a subcontractor breaks its BAA, fix it or end the relationship | Vendor reviews with dates and decisions |
| No impermissible uses or disclosures | Use PHI only as the BAA allows | Data flow notes and access logs |
| Minimum necessary | Limit PHI to what each job needs | Role definitions and access reviews |
| Provide ePHI copies for access requests | Help the covered entity answer patient access requests as the BAA specifies | A documented procedure and turnaround |
| Accounting of disclosures | Keep records needed for certain disclosure accountings | A disclosure log where it applies |
| Cooperate with HHS | Provide records and compliance reports, allow access during investigations | Records you can produce within days, not weeks |
| No retaliation | Do not punish anyone for filing a complaint or helping an investigation | An HR policy that says so |
Notice how much of the right-hand column is just dated records. Most business associates already do a fair share of this work. What they lack is the proof, organized so it can be handed over in a day.
What does a business associate agreement add?
A BAA adds contract terms that are often stricter than the regulation: shorter incident reporting windows, specific encryption or hosting requirements, audit rights, cyber insurance minimums and return or destruction of PHI at termination. Breaking those terms is a contract breach even when HHS would see no violation.
The regulation allows up to 60 days to notify the covered entity of a breach. Hospital BAAs routinely ask for notice of a security incident within five or ten business days, sometimes 24 to 72 hours, and they often define "security incident" more broadly than a reportable breach. If you have three customers, you may have three different clocks. The practical fix is to keep one summary per customer of the terms that create recurring work or deadlines, next to the signed agreement.
Many vendors now sign BAAs electronically, which helps here. An executed copy from a tool such as SignElectronically carries its signing date and the names of both signers, which is exactly what a reviewer wants to see when they ask whether a BAA is in place. Store that copy with the customer's record, not in someone's inbox.
Do business associates need a risk assessment?
Yes. The Security Rule requires an accurate and thorough risk analysis of the ePHI you create, receive, maintain or transmit, under 45 CFR 164.308(a)(1)(ii)(A), plus a plan to reduce the risks you find. It has no fixed frequency in the rule, but HHS expects it updated when systems change, and customers usually ask for one less than a year old.
For a software vendor, the analysis is mostly about your production environment, your support tooling and your people. Where does PHI land: the database, backups, logs, error trackers, the support desk, the analytics tool somebody added last quarter? Each place is a system to list, an owner to name and a risk to rate. A dedicated HIPAA risk assessment tool turns that into a register you can update in an afternoon when you add a vendor, instead of a document rewritten every spring.
A worked year-one budget for a 30-person business associate
Take a 30-person SaaS company selling scheduling software to outpatient clinics. It hosts on a major cloud provider, uses eight other vendors, and has signed BAAs with four customers, one of them a regional health system. It has no compliance team. The security lead is also the head of engineering. These figures are planning estimates for that company, not quotes.
| Item | Year-one estimate | Notes |
|---|---|---|
| Risk analysis and risk management plan | 60 to 80 hours internal, or $5,000 to $12,000 with a consultant | Largest one-time cost. Much cheaper in year two |
| Policies and procedures | 30 to 50 hours | Drafts from software or templates, then edited to match reality |
| Workforce training | $750 to $1,500 | About $25 to $50 per person for an online course |
| Subcontractor BAAs and vendor reviews | 20 to 30 hours | Eight vendors, of which perhaps four touch PHI |
| Technical fixes found by the analysis | $2,000 to $15,000 | Logging, MFA gaps, backup encryption, removing PHI from logs |
| Compliance software | $564 to $1,428 | Complies Starter or Growth billed yearly |
| Optional third-party assessment | $8,000 to $25,000 | Only if a customer contract demands it |
At an internal cost of about $90 an hour for the people doing the work, the internal hours alone come to roughly $10,000 to $14,500. Add training, fixes and software and the total without an outside assessment lands between about $13,000 and $32,000. The external assessment is what pushes some vendors past $40,000, and it is worth asking the customer whether a SOC 2 report with HIPAA criteria would satisfy them instead, since you may need SOC 2 for non-healthcare buyers anyway.
Year two is far cheaper. The analysis becomes an update, the policies need a review instead of a draft, and the work shifts to keeping recurring tasks on time: access reviews, training renewals, vendor reviews, backup restore tests. That is where most small business associates slip, because nobody owns the calendar.
What hospital customers ask business associates for
A health system's vendor security review typically asks for the same short list, whatever the questionnaire looks like. Have these ready before the next renewal:
- Date and scope of your last HIPAA risk analysis, and the open items from it.
- Your policy list with approval dates, including incident response and breach notification.
- Workforce training completion for the last twelve months.
- Your subcontractor list with which ones handle PHI and whether each has a BAA.
- Encryption at rest and in transit, MFA, and logging, described briefly with evidence.
- Your incident history, or a statement that there has been none, plus your notification procedure.
- A SOC 2 report or other third-party assessment if you have one.
Questionnaires vary in length from 40 questions to several hundred, but they keep coming back to these items. Teams that answer them often use security questionnaire software to reuse approved answers, and the answers are only as good as the evidence behind them.
What software should a business associate use?
A business associate needs software that keeps the Security Rule work on a schedule with owners and evidence, tracks subcontractors and their BAAs, and records incidents with notification dates. Security tools such as endpoint protection or logging are separate purchases. The compliance tool holds the proof that they are in place and reviewed.
Complies loads HIPAA as 13 recurring obligations, from the risk analysis and risk management plan to contingency planning, device and media controls, audit logs, encryption checks and six-year documentation retention, each with an owner, a cadence and a place for evidence. The 164.308(b) obligation is your subcontractor BAA review. Starter at $47 a month billed yearly covers one framework and three seats, which suits a small vendor whose first problem is HIPAA. Growth at $119 a month adds the risk register, vendor risk management with review dates and stored documents, evidence collection and up to five frameworks, so HIPAA and SOC 2 can share controls. The full list is on the HIPAA compliance software page.
Be clear about what it does not do. Complies does not sign BAAs for you, scan your infrastructure or act as an assessor. It keeps the program running and gives you a dated record when a customer or HHS asks.
Common mistakes business associates make
The first is assuming the covered entity's compliance covers you. It does not. Your customer's risk analysis covers their systems, not yours. The second is signing every BAA a customer sends without tracking its terms, then missing a five-day incident clock because the regulation said 60. The third is forgetting downstream vendors. If your support desk, error tracker or backup provider can see PHI, it is a subcontractor and needs a BAA with you. The fourth is treating the first year's work as finished. Most findings in vendor reviews are stale items: a risk analysis from two years ago, training that lapsed, an offboarded engineer still in the production console.
None of those are expensive to fix. They are expensive to discover in a renewal, a breach investigation or a lost deal with a health system. A calendar with owners and the evidence attached is the cheapest insurance against all four.
RUN IT, NOT JUST READ IT
Turn this into tracked rows with owners
Everything in this guide becomes obligations, controls, and evidence with owners and due dates inside Complies, with a live readiness score on top. Plans from $47 a month, prices published.