Business Associate Contracts: The privacy-side contract requirements

45 CFR 164.504(e) is the requirement on business associate contracts. It is short to read and easy to underestimate, because satisfying it means producing evidence rather than holding an intention.

What the rule says

45 CFR 164.504(e) governs business associate contracts. The operative text is not reproduced here: read it at the source linked below, because the conditions in it are the requirement and a summary of a conditional rule is not a safe substitute for the rule.

The contract terms are in 45 CFR 164.504(e)(2). The contract establishes the business associate's permitted and required uses and disclosures ((e)(2)(i)), and provides that the business associate will: not use or further disclose the information other than as the contract permits or the law requires; use appropriate safeguards and comply, where applicable, with the Security Rule for ePHI; report any use or disclosure the contract does not provide for, including breaches of unsecured PHI as 164.410 requires; ensure, under 164.502(e)(1)(ii), that its subcontractors agree to the same restrictions and conditions; make PHI available for access (164.524), for amendment (164.526) and for an accounting of disclosures (164.528); comply with the Privacy Rule when it carries out a covered entity's obligation under it; make its books and records available to the Secretary; and, at termination, return or destroy the PHI if feasible ((e)(2)(ii)). It must also authorize the covered entity to terminate the contract if the business associate violates a material term ((e)(2)(iii)).

What this looks like in practice

In an assessment, 45 CFR 164.504(e) is not one question. It resolves into several, and each one is really asking for different evidence. These are among the questions asked about it:

• Does the organization have a written contract or other arrangement with every business associate that creates, receives, maintains, or transmits ePHI on its behalf, providing that the business associate will comply with the applicable requirements of the Security Rule, ensure that its subcontractors that handle ePHI agree to the same by contract, and report to the organization any security incident of which it becomes aware, including breaches of unsecured PHI?
• Does the organization follow a documented offboarding procedure that revokes access and recovers or confirms destruction of sensitive data when a third-party relationship ends?

Ownership usually sits with the security official, though the evidence is often produced by someone else, which is where the trail breaks. A control that works but has no owner tends to stop working the month the person who quietly maintained it changes roles.

Who this applies to

Covered entities. A business associate is bound directly by the provisions that name it (for example 45 CFR 164.502(a)(3), the minimum necessary standard at 164.502(b), and 164.410) and otherwise through its business associate agreement, so read the provision for whom it names. The Privacy Rule has no counterpart to the Security Rule's flexibility-of-approach clause (164.306(b)). Instead, 45 CFR 164.530(i)(1) requires policies and procedures reasonably designed for the size and type of your activities, and any deadline a provision sets applies at every size. A business associate is bound directly by this provision; it is not only a contract term.

Building it, in order

The sequence below is the order that produces evidence as a by-product rather than as a separate documentation exercise:

1. Maintain a current master agreement template, reviewed by counsel, that includes the required protection obligations.
2. Include in each contract the terms 45 CFR 164.314(a)(2)(i) requires: that the business associate will comply with the applicable requirements of the Security Rule, will ensure under § 164.308(b)(2) that any subcontractor that creates, receives, maintains, or transmits ePHI on its behalf agrees to the same by a contract or other arrangement that complies with § 164.314, and will report to the organization any security incident of which it becomes aware, including breaches of unsecured PHI as § 164.410 requires.
3. If the organization is itself a business associate, put the same terms in each subcontractor contract (45 CFR 164.314(a)(2)(iii)), and keep a list of every business associate or subcontractor that handles ePHI so none is without a contract.
4. Confirm every active agreement uses the current template.
5. Trigger offboarding on any termination of a third-party relationship, planned or unplanned.
6. Immediately revoke all system access and credentials.

Where else this maps

The questions behind 45 CFR 164.504(e) also map to NIST SP 800-66 Rev. 2 5.2.4, 5.4.1, which is voluntary guidance rather than law; following it does not by itself establish compliance with any law. That matters for scoping: the same evidence can be written once and referenced from each, rather than rewritten per framework.

Evidence an assessor asks for

For this requirement the evidence types that satisfy it are agreement and record. The distinction matters more than it looks: a policy states what you intend to do, a procedure states how, and a record proves it happened on a date. Auditors ask for all three, and a practice that has written the first two often has nothing for the third.

Date every document and keep the superseded versions. Under 45 CFR 164.530(j)(2) the documentation 164.530(j)(1) requires is kept six years from the date of its creation or the date when it last was in effect, whichever is later. It is the same period the Security Rule sets at 164.316(b)(2)(i), under a different provision, so cite the one that governs the document you are holding.

Where this usually goes wrong

In our question bank this is weighted Critical: a gap here is raised as a critical finding (a partial answer as high). The usual cause of a gap is drift: the control was implemented once, the environment changed, and nothing re-checked it. A dated review on a fixed cadence is cheaper than the remediation.

What to do about it

• Produce the evidence, not the intention. For 45 CFR 164.504(e) that means the executed agreement, with the signature date on it and dated records of each occurrence, not a description of the process. If the only evidence is that someone knows how this works, you have a practice and not a record.
• Put a name on it. Your security official should be recorded as the owner. A control with no owner stops working the month the person who quietly maintained it changes roles, and nobody notices.
• Review it on a fixed date, not when you remember. In our question bank this is weighted Critical: a gap here is raised as a critical finding (a partial answer as high). Put the review on the calendar with an owner, and keep the dated output of each one.

Work backward from the evidence. Decide what evidence would prove business associate contracts to someone who does not already trust you, then build the control that produces it. Programs built in that order tend to stay current, because the evidence goes stale visibly.

Related requirements

• Personal Representatives: Who may act for a patient, and when
• Authorizations: When an authorization is required and what it must contain
• Minimum Necessary: Applying minimum necessary to real workflows

References

• 45 CFR 164.504(e), in 45 CFR 164.504 on eCFR.
• Crosswalk references in this post are the mappings in our question bank, and are not verified against the published text of those standards.
• This post describes what a requirement asks for and what evidence documents it. It is not legal advice, and your counsel owns the conclusion. State law may impose stricter obligations (45 CFR 160.203).