Skip to content
HIPAA ComplianceConsulting

HIPAA Consulting Service

HIPAA Business Associate Compliance Consulting

Help for vendors that handle PHI and for covered entities that rely on them: BAA review, subcontractor flow-down, vendor inventories and the Security Rule obligations business associates carry directly.

Reviewed Request a HIPAA Consultation

Since the HITECH Act and the 2013 Omnibus Rule, business associates are directly accountable for parts of HIPAA, not just contractually bound by a covered entity’s paperwork. A billing company, a hosting provider, a practice management SaaS vendor or an outsourced IT firm can face its own enforcement exposure for failing to safeguard electronic protected health information (ePHI) or for impermissible uses and disclosures.

Our HIPAA business associate compliance service works on both sides of the relationship. For business associates, we map what HIPAA actually requires of you and build the program to meet it. For covered entities and upstream business associates, we help you find every vendor that touches PHI, get the right agreements in place and decide how much assurance to ask for.

Key points

  • Business associates must comply with the Security Rule directly and can be liable for certain Privacy Rule violations.
  • BAA content requirements are set out in §164.504(e) and §164.314(a).
  • Subcontractors that handle PHI on a BA’s behalf are business associates too and need their own BAAs.
  • A signed BAA is a contract, not evidence that the vendor actually protects PHI.

What this service covers

Business associate work sits at the junction of contract terms and operational reality. A BAA can say all the right things while the vendor has no risk analysis, no breach procedure and no idea which of its own subcontractors store PHI. Equally, a covered entity can have dozens of vendors receiving PHI with no agreement on file at all.

The engagement typically combines three workstreams: a review of existing BAAs against regulatory content requirements; a vendor (or subcontractor) inventory showing where PHI flows; and, for business associates, a review of the internal program needed to honor the obligations those agreements create. Where contract language needs legal drafting or negotiation, we work alongside your legal counsel rather than replacing them.

Who needs business associate compliance support

  • Healthcare SaaS, cloud and managed service providers that create, receive, maintain or transmit ePHI for covered entities — see HIPAA consulting for business associates.
  • Medical billing, coding and revenue cycle companies, which typically hold large volumes of claims and patient data.
  • Hospitals, clinics and health plans that need a defensible vendor inventory and a consistent BAA process.
  • Business associates that themselves rely on subcontractors (hosting, support, analytics, offshore processing) and must flow obligations downstream.
  • Startups signing their first enterprise healthcare contract, where the customer’s BAA and security questionnaire arrive before the company has a formal program.

Regulatory considerations for business associates

The definition of a business associate is in 45 CFR §160.103. Broadly, it is a person or entity that performs functions or activities on behalf of a covered entity (or another business associate) involving the use or disclosure of PHI. Conduits that merely transport data without persistent access are a narrow exception; a cloud provider that stores ePHI is generally a business associate even if it cannot view the data, according to HHS cloud computing guidance.

Who signs what
RelationshipAgreement neededKey regulatory basis
Covered entity → business associateBusiness associate agreement§164.502(e), §164.504(e), §164.308(b)
Business associate → subcontractor handling PHISubcontractor BAA with the same restrictions§164.502(e)(1)(ii), §164.314(a)
Covered entity → vendor with no PHI access (e.g. janitorial with incidental exposure)Generally no BAA; confidentiality terms may still be prudentIncidental disclosure provisions, §164.502(a)(1)(iii)
Covered entity → another provider for treatmentNo BAA required for treatment disclosures§164.502(e)(1)(ii)(A)

Required BAA content

Under §164.504(e), a BAA must, among other things, establish permitted uses and disclosures, prohibit other uses, require appropriate safeguards, require reporting of non-permitted uses and disclosures (including breaches of unsecured PHI), require subcontractor agreements with the same restrictions, address individual rights (access, amendment, accounting) where applicable, make books and records available to HHS, and require return or destruction of PHI at termination where feasible. Section 164.314(a) adds Security Rule-specific terms, including compliance with the Security Rule and reporting of security incidents.

Direct liability

HHS has published a fact sheet listing the provisions for which business associates are directly liable, including failing to comply with the Security Rule, failing to provide breach notification to the covered entity, impermissible uses and disclosures, failing to enter BAAs with subcontractors and failing to provide records to HHS during an investigation. Civil money penalties follow four inflation-adjusted culpability tiers, from lack of knowledge through uncorrected willful neglect.

Common business associate compliance challenges

  • No reliable vendor inventory — PHI recipients discovered only when an invoice or incident surfaces them.
  • Customer-imposed BAAs with notification windows far shorter than the regulatory 60-day outer limit, which the vendor’s incident process cannot actually meet.
  • Subcontractors (cloud hosting, email, ticketing, transcription) handling PHI with no downstream BAA.
  • Business associates that assume the covered entity’s risk analysis covers them. It does not; each BA needs its own under §164.308(a)(1)(ii)(A).
  • Conflicting BAA templates across customers, each with different reporting timelines, de-identification rights and indemnities.
  • Termination clauses that require return or destruction of PHI that the vendor has no technical way to locate and purge.

Our approach

We start by tracing PHI rather than reading contracts. Interviews with finance, IT and operations, plus a review of accounts payable and SSO application lists, usually reveal vendors that procurement never flagged. Each vendor is then classified by the type and volume of PHI involved and the nature of access.

Next, we compare agreements on file against the required content in §164.504(e) and §164.314(a), and against what the organization can operationally deliver. For business associates, we compare the commitments in customer BAAs against the internal program — risk analysis, incident response, workforce training, access controls — and identify where a promise has no process behind it. Findings feed into a HIPAA gap analysis where a broader view is needed.

Typical deliverables

  • PHI vendor (or subcontractor) inventory with risk tiering and BAA status.
  • BAA content review matrix against §164.504(e) and §164.314(a), flagging missing or problematic clauses for counsel.
  • Vendor due diligence questionnaire and tiered review procedure.
  • For business associates: an obligations register summarizing reporting timelines and commitments across customer BAAs.
  • Policy updates covering vendor onboarding, BAA execution, monitoring and offboarding — often delivered alongside HIPAA policies and procedures work.
  • A prioritized remediation list for missing agreements and program gaps.

Engagement process

  1. 1

    Scoping call

    Confirm whether you are a covered entity, a business associate or both, and agree on which vendor population and contract set is in scope.

  2. 2

    PHI flow discovery

    Interviews and document review to identify every party that creates, receives, maintains or transmits PHI on your behalf.

  3. 3

    Agreement review

    Compare each BAA and subcontractor agreement against required content and flag issues for legal counsel.

  4. 4

    Program alignment

    For business associates, test whether internal processes can meet the commitments made in customer agreements.

  5. 5

    Reporting and handoff

    Deliver the inventory, review matrix and prioritized actions, and walk your team through ownership of each item.

What drives the cost

Cost is driven mainly by the number of vendors or customer agreements in scope, how much discovery is needed to build the inventory, and whether the work includes a review of the business associate’s own security program. A covered entity with a clean contract repository and a few dozen vendors is a much smaller project than a business associate reconciling hundreds of customer BAAs with differing terms. See HIPAA consulting cost for how we scope engagements.

Frequently asked questions

Is a cloud provider that only stores encrypted PHI a business associate?

According to HHS guidance on cloud computing, a cloud service provider that creates, receives, maintains or transmits ePHI is a business associate even if the data is encrypted and the provider does not hold the key. The conduit exception is narrow and generally applies to transmission-only services.

Can a business associate be penalized directly by OCR?

Yes. Since the HITECH Act and the 2013 Omnibus Rule, business associates are directly liable for specific provisions, including Security Rule compliance, breach notification to the covered entity, impermissible uses and disclosures, and executing BAAs with subcontractors.

Do you draft business associate agreements?

We review BAAs against regulatory content requirements and operational feasibility, and we can propose clause language. We are not a law firm, so final drafting and negotiation should involve your legal counsel. HHS also publishes sample BAA provisions as a starting point.

How short can a breach reporting window in a BAA be?

HIPAA sets an outer limit of 60 calendar days after discovery for a business associate to notify the covered entity, but the parties can agree to a shorter period. The practical question is whether your incident process can meet what you sign.

Does using the same BAA template for every vendor work?

A standard template is a good baseline, but vendors differ in risk. Many organizations keep one template while varying the level of due diligence, reporting expectations and assurance requested according to vendor risk tier.

Authoritative sources

This page is general information, not legal advice. Regulations and guidance change; confirm current requirements with the official sources above and, where needed, qualified legal counsel.

Talk through your HIPAA obligations with a consultant

Tell us about your organization, how you handle patient information, and what’s prompting the review. We’ll suggest a practical scope — and tell you if you don’t need us.