AI Roles and Responsibilities: Who owns an AI decision in a clinical setting

If you have been asked for evidence of AI roles and responsibilities, the framework outcome behind the question is NIST AI RMF GOVERN 2.1. What follows is what it says, what satisfies it, and where organizations usually come up short.

What the framework says

Roles and responsibilities and lines of communication related to mapping, measuring, and managing AI risks are documented and are clear to individuals and teams throughout the organization.

That is the text of NIST AI RMF GOVERN 2.1. Read it closely: it describes an outcome to achieve, not a product to buy, which is why two practices of the same size can satisfy it in different ways and both be right.

What this looks like in practice

In an assessment, NIST AI RMF GOVERN 2.1 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:

• Are roles, responsibilities and lines of communication for mapping, measuring and managing AI risk documented and understood across the organization?
• Does the organization have roles and procedures for communicating generative AI incidents outside the organization, to affected parties and downstream stakeholders, including, where appropriate, through public resources such as the AI Incident Database?
• Has the organization assigned named people the responsibility and authority for running the AI management program and for reporting program performance to senior leadership?

Ownership usually sits with the AI governance lead, 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 AI governance work you already owe under a law or a contract, or when a recognized practice is worth having on record. Treat it as a way of organizing that work, 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. Define accountable, responsible, consulted and informed roles for each AI risk management activity.
2. Name the escalation path for AI risk issues from teams to leadership.
3. Communicate the roles to affected staff and confirm understanding.
4. Define which generative AI incidents are communicated outside the organization, to whom and how quickly, including any notice a law or contract requires, confirmed with legal staff.
5. Assign the roles that decide on, review and make each communication.
6. Identify the public or sector resources the organization will report to where appropriate, such as the AI Incident Database, AVID or CVE.

Where else this maps

The questions behind NIST AI RMF GOVERN 2.1 also map to NIST AI 600-1 2.12, 2.7 and ISO/IEC 42001 5.3, A.3.2, which are voluntary guidance and standards rather than law; following them 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 outcome the evidence types that satisfy it are procedure 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. The framework sets no retention period, so this is our recommendation rather than a requirement: keep each version for as long as the system it describes is in use and for a period after it is retired, because a question about a past decision is answered from the version that was in force when it was made.

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 NIST AI RMF GOVERN 2.1 that means a step-by-step procedure someone unfamiliar with the task could follow 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 AI governance lead should be recorded as the owner. Where the work is done by someone else, say so in the document: the split between who owns it and who performs it is where the trail usually breaks. 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.
• Do not treat this as a legal obligation. It is a voluntary framework. Adopt it where a customer contract or a regulator's guidance names it, or where it gives structure to AI governance work you owe for other reasons, and say in your own documentation which of those reasons applies.

If NIST AI RMF GOVERN 2.1 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.

Related outcomes

• Ongoing AI Monitoring: Monitoring a model after it goes live
• Human Oversight of AI: Keeping a person accountable for the output
• Risk Management Processes for AI: Sizing AI risk management to the use case

References

• GOVERN 2.1, in NIST AI Risk Management Framework 1.0 (NIST AI 100-1). This is a voluntary framework, not a legal requirement. The quoted statement is NIST's own, from the Core tables of NIST AI 100-1.
• 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 framework outcome asks for and what evidence documents it. It is not legal advice, and your counsel owns the conclusion. State law may impose additional obligations of its own.