Platform feature

Business Associates

The business associate relationships §164.502(e) governs, tracked with every BAA, every subcontractor, and every signed-date on one register.

Administrative safeguards Physical safeguards Technical safeguards Privacy rule Breach notification

A list of vendors on a shared drive is not a Business Associate register — it is a backlog waiting to be found. Business Associates is the register §164.502(e) expects: every relationship, every PHI touch, every subcontractor, every signed date.

What it does

  • Catalogs every BA with the data categories they touch and the systems they touch them in.
  • Models the downstream chain: BAs’ subcontractors with flow-down obligations.
  • Flags BAs missing a current signed agreement with a visible owner for closing the gap.
  • Links each relationship to its vendor risk tier and to the signed BAA.

How it maps to HIPAA

The register implements the operational side of §164.502(e) (uses and disclosures to BAs), §164.504(e) (BAA contents and subcontractor flow-down), and §164.308(b)(1) (written contract requirements for the Security Rule).

Where it fits

Business Associates is a Privacy module capability; the contract artefact is held in BAA Management, and risk tiering is in Vendor Risk.

Questions

What's the difference between Business Associates and BAA Management?

This feature tracks the relationships — who is a BA, what PHI they touch, what subcontractors they use. BAA Management handles the agreement itself: template, redlines, countersignature, renewal dates. Most teams use both.

What about downstream subcontractors?

The register captures BA-to-subcontractor relationships explicitly, so flow-down obligations are visible. §164.504(e)(5) and HITECH's direct BA liability are modelled here, not inferred.

See your compliance program in one place

A 20-minute walkthrough with a practitioner. No slides, no pressure.

Book a demo