AI use case registry
What it is
The AI use case registry is the artifact that satisfies RUAIH focus area 1 — Governance — at the control level.
Who signs it
The accountable executive for AI, usually the CMIO or chief digital officer.
A document without a signature is a draft. An assessor is checking that someone with authority put their name to it.
What an assessor asks for
The register, and the method by which it was compiled. The second question is harder and more revealing.
What goes in it
- Tool name, vendor, and whether it is embedded in another product
- The workflow it sits in and the decision it influences
- Data it touches, including whether it processes PHI
- Named operational owner and named clinical sponsor
- Risk tier, and the date that tier was assigned
- Go-live date and current status
- Validation status and date
- Monitoring plan reference
- Contract and renewal date
The most common failure
The register is incomplete in a predictable direction: it lists what was procured and misses what arrived inside something already procured. Build it from your EHR vendor’s own feature list and two years of contracts, then ask departments — in that order.
Where this sits
See the RUAIH crosswalk for how this control maps across CHAI’s playbooks and the NIST AI RMF.
Written and reviewed by Neel Chauhan, MD MBA, physician-executive and founder of the Healthcare AI Institute. Last reviewed 2026-07-30.
Specified from the published RUAIH focus areas and the September 2025 Joint Commission and CHAI guidance, plus the failure modes we see most often in practice.
The Institute accepts no vendor sponsorship, holds no vendor equity and takes no referral fees.