Limited Data Set: When a limited data set is the right tool

If you have been asked for evidence of limited data set, the requirement behind the question is 45 CFR 164.514(e). What follows is what it says, what satisfies it, and where organizations usually come up short.

What the rule says

45 CFR 164.514(e) governs limited data set. 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.

What this looks like in practice

In an assessment, 45 CFR 164.514(e) is not one question. It resolves into several, and each one is really asking for a different artifact:

• When the organization discloses a limited data set, does it enter into a data use agreement that restricts the recipient's use

Ownership usually sits with the compliance owner, 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

Every covered entity. Business associates are directly liable for only a defined subset of these obligations, so read your business associate agreement alongside the rule rather than assuming the duty transfers. There is no scalability defense here of the kind the Security Rule offers at 45 CFR 164.306(b): a deadline is a deadline at any size. What does scale is how you meet it, and 45 CFR 164.530(i) expects your policies to be designed for the size and activities of your organization.

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. Define the data elements that may appear in a limited data set and remove the direct identifiers that must be excluded.
2. Use a data use agreement template that restricts the recipient's permitted uses, prohibits re-identification, and requires safeguards.
3. Execute the agreement before any limited data set is disclosed.
4. Upload the data use agreement template and a log of executed agreements.

What else this satisfies

The same evidence answers more than one framework. The questions behind 45 CFR 164.514(e) also map to NIST 800-53 PT-7; NIST Privacy CT.PO-P4. That matters for scoping: if you are working toward SOC 2 or an ISO certification alongside HIPAA, this control is one piece of work and several answers, provided the artifact is written once and referenced rather than rewritten per framework.

Evidence an assessor asks for

For this requirement the artifact types that satisfy it are agreement. 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 artifact and keep the superseded versions. The Privacy Rule carries its own retention rule at 45 CFR 164.530(j)(2): six years from the date of 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

The usual gap is a control that exists in practice and nowhere in writing. Someone does the work, reliably, and it has never been written down, so the organization cannot demonstrate it and cannot notice when it stops. The fix is not more control, it is a dated record and a named owner.

What to do about it

• Produce the artifact, not the intention. For 45 CFR 164.514(e) that means the executed agreement, with the signature date on it. 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 privacy 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.
• Re-read it when something changes. A new system, a new vendor or a departure is what makes a correct control stale. Tie the review to those events as well as to the calendar, and date the result.

If 45 CFR 164.514(e) is new to you, the useful first step is not a policy template. It is writing down what you already do, dating it, and naming an owner. That turns an undocumented practice into evidence, and it usually reveals the real gap.

References

• 45 CFR 164.514(e), in 45 CFR 164.514 on eCFR.
• The Required and Addressable designations are defined at 45 CFR 164.306(d).
• Crosswalk references in this post are our own mapping 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).