Legal and Regulatory Requirements for AI: Classifying an AI tool before deployment

NIST AI RMF GOVERN 1.1 is the legal and regulatory requirements for ai requirement. It is short to read and easy to underestimate, because satisfying it means producing an artifact rather than holding an intention.

What the rule says

NIST AI RMF GOVERN 1.1 sets the expectation for legal and regulatory requirements for ai. The framework describes the outcome rather than prescribing a technology, so the question is whether your implementation achieves it and whether you can show that it does.

What this looks like in practice

In an assessment, NIST AI RMF GOVERN 1.1 is not one question. It resolves into several, and each one is really asking for a different artifact:

• Document a regulatory classification determination for each AI clinical decision support tool
• An approved AI policy that sets its objectives, principles, and commitments for the responsible development and use of AI

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

NIST AI RMF is voluntary rather than binding, and that changes how it should be used. Adopting it does not create a legal obligation, and declining it is not a violation. It earns its place when a customer contract names it, when it gives structure to a program HIPAA describes only in outcomes, or when a recognized practice is worth having on record. Treat it as a way of organizing work you already owe, not as a second regime.

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. For each AI clinical decision support tool, document a determination of its regulatory classification against applicable criteria.
2. Record the basis for the determination and who approved it.
3. Reassess the classification when the tool's function changes.
4. Upload the clinical decision support regulatory classification determinations.
5. Draft an AI policy stating the organization's objectives, principles, and commitments for responsible AI.
6. Align the policy with organizational strategy and applicable obligations.

What else this satisfies

The same evidence answers more than one framework. The questions behind NIST AI RMF GOVERN 1.1 also map to HITRUST 06.a; ISO 42001 A.2.2, A.2.4, Clause 5.2. 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 policy 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 artifact and keep the superseded versions. No federal rule sets a retention period for a voluntary framework artifact, so this is our recommendation rather than a requirement: keep six years, because that is what HIPAA requires of the documentation this work usually overlaps with (45 CFR 164.316(b)(2)(i) for security documentation, 164.530(j)(2) for privacy), and holding two sets of dates is how the earlier one goes missing.

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 NIST AI RMF GOVERN 1.1 that means a signed, dated policy with a named owner and a review date 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.
• 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.
• Do not treat this as a legal obligation. It is a voluntary framework. Adopt it where a customer contract names it or where it gives structure to something HIPAA describes only as an outcome, and say in your own documentation which of those reasons applies.

Work backward from the evidence. Decide what artifact would prove legal and regulatory requirements for ai 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 artifact goes stale visibly.

References

• GOVERN 1.1, in NIST AI Risk Management Framework 1.0 (NIST AI 100-1). This is a voluntary framework, not a legal requirement.
• 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).