The AI governance committee
The mapping
| Framework | Where this control sits |
|---|---|
| Joint Commission RUAIH | Focus area 1 — Governance |
| CHAI governance playbooks | Playbook 2 — Organizational structure |
| NIST AI RMF | GOVERN |
The artifact: AI governance committee charter
Who signs it: The chief executive or the board committee that delegates the authority
What an assessor actually asks for
The charter, the membership roster against it, and minutes for the last three meetings. An assessor is checking that the committee exists, that the named expertise is actually in the room, and that it met.
Why the mapping is not obvious
The mapping looks obvious and it is not. CHAI’s organizational structure playbook describes a committee; RUAIH’s governance area asks whether that committee has authority. Those are different tests. A committee that reviews tools after procurement has satisfied CHAI’s structure and failed RUAIH’s governance, and almost every organisation we have looked at is in exactly that position.
The most common failure
The committee exists, meets, and has no exclusive decision right. Tools reach production through procurement, through an IT project, or through a departmental pilot that was never called a deployment. Test it by asking how the last three tools actually got in.
Where this sits in the whole map
This is one control in the RUAIH ↔ CHAI ↔ NIST crosswalk. The artifact itself is specified at AI governance committee charter.
Written and reviewed by Neel Chauhan, MD MBA, physician-executive and founder of the Healthcare AI Institute. Last reviewed 2026-07-30.
Generated from data/crosswalk.yaml, where the mapping and the commentary for each control are authored individually. Reviewed on each framework revision.
The Institute accepts no vendor sponsorship, holds no vendor equity and takes no referral fees.