What is this course about?
Clinical AI governance has to cover tools nobody approved, assess bias across populations where the consequence is clinical, and monitor for drift after deployment. This course builds the inventory, the committee, a bias audit protocol, and the decommissioning process for a model that stops performing.
Who is this course for?
- Chief medical informatics officers
- AI governance committees
- Quality, safety, and health equity officers
- Compliance and risk staff
What do I need before starting?
- Clinical or healthcare governance background
- Familiarity with your organization's governance structures
What will I be able to do afterwards?
- Build a clinical AI inventory including unapproved and embedded tools
- Stand up a governance committee with genuine authority
- Require local validation before clinical deployment
- Run bias audits across race, language, payer, and disability status
- Decommission a model that is no longer performing
What does each module cover?
What clinical AI is already running?
50 minThe inventory including tools embedded in systems nobody classified as AI.
Objectives
- Inventory clinical AI including embedded features
- Discover unapproved clinical use
- Capture the attributes governance needs
Topics
Activity. Run discovery in one service line and inventory everything found.
Who sits on the governance committee?
45 minComposition spanning clinical, legal, IT, quality, and equity, with real authority.
Objectives
- Define committee composition and authority
- Include health equity representation meaningfully
- Design a review process clinicians will use
Topics
Activity. Draft the committee charter and run a mock review of two real tools.
What must be validated before clinical deployment?
50 minPre-deployment requirements including local validation on your own population.
Objectives
- Define pre-deployment validation requirements
- Require local performance data
- Set criteria that can block a deployment
Topics
Activity. Write the pre-deployment requirements and test them against a tool leadership wants.
How do you audit for bias?
60 minBias auditing across race, ethnicity, language, payer, and disability status.
Objectives
- Design a bias audit protocol
- Select subgroups and comparison methodology
- Interpret findings clinically
Topics
Activity. Run a bias audit on one deployed model across four subgroups.
What do you do when the audit finds something?
50 minResponse when a model performs worse for a subgroup, including when to stop using it.
Objectives
- Determine whether a disparity is acceptable
- Design mitigation where possible
- Decide when to stop using the model
Topics
Activity. Work through the response to a real disparity finding.
How do you monitor after deployment?
45 minPost-deployment monitoring for drift, including drift the vendor caused.
Objectives
- Design post-deployment monitoring
- Detect performance drift
- Detect vendor-caused model changes
Topics
Activity. Design monitoring for one deployed model with drift alerting.
What do clinicians and patients get told?
40 minTransparency to clinicians using the tool and to patients affected by it.
Objectives
- Determine clinician transparency requirements
- Determine patient disclosure obligations
- Draft the disclosure language
Topics
Activity. Draft clinician and patient disclosure language for one deployed tool.
Building the bias audit protocol
50 minThe workshop module: a complete, repeatable audit protocol.
Objectives
- Produce a repeatable audit protocol
- Define audit cadence
- Plan the decommissioning path
Topics
Activity. Complete the protocol and schedule the first audit cycle.
What is the capstone project?
Clinical AI governance program with a bias audit protocol
Produce a governance program: inventory with discovery findings, committee charter with equity representation, pre-deployment validation requirements with blocking criteria, a completed bias audit across four subgroups, monitoring design, and disclosure language.
Deliverable: A governance program with one completed bias audit and a scheduled audit cycle.
How are learners assessed?
- Inventory must surface embedded or unapproved AI the committee did not know about
- Bias audit completed on real data across at least four subgroups
- Pre-deployment criteria tested against a tool leadership actively wants
What ships with the course?
Facilitator guide
Session-by-session running order, discussion prompts, and the questions that reliably derail a room.
Learner workbook
Exercises, checklists, and the templates each module's activity produces.
Hands-on lab environment
A sandboxed ibl.ai deployment so exercises run against real agents, not screenshots.
Assessment bank
Scenario questions and rubric criteria mapped to each stated learning outcome.
Source bibliography
Every primary regulation and standard cited on this page, linked and dated.
Which AI agents does this course use?
The hands-on modules run against agents already deployable on the ibl.ai platform for healthcare.
Where does the course material come from?
Every module is grounded in primary sources — the regulation, standard, or research itself, not a summary of it. Each was resolved at authoring time.
- AI Risk Management Framework
NIST
Governance structure and bias testing methodology.
- HealthIT.gov
ASTP/ONC
Algorithm transparency requirements for certified health IT.
- Agency for Healthcare Research and Quality
AHRQ
Health equity measurement methodology.
- Augmented Intelligence in Medicine
American Medical Association
Professional guidance on clinical AI oversight.
Delivery notes
Binding guidance for anyone preparing and delivering this course.
- Module 4's bias audit must run on real organizational data across real subgroups. A methodological overview without execution produces committees that believe they have audited when they have not.
- Module 5 must include stopping as a genuine option. Governance that can only recommend mitigation cannot address a model that should not be used.
- Module 1 will find embedded AI in the EHR and other systems that nobody classified. Build discovery to catch vendor features rather than only standalone tools.
- Health equity representation in Module 2 must be substantive. A committee with an equity seat that never blocks anything is worse than none, because it provides cover.
- Coordinate with MED-6 — local validation is covered there in clinical depth and this course should govern rather than re-teach it.
Why run AI training on a platform you own?
You own the course, not a licence to it
Course content, learner data, and the platform run inside your perimeter — you own all the code and the data.
Model-agnostic delivery
Run the course's AI components on any LLM — Claude, GPT, Llama, Gemini, Command — and switch anytime.
No per-seat training licences
Usage-based or self-hosted, so cost tracks actual use rather than headcount.
Deploy anywhere
Cloud, private VPC, on-premise, or fully air-gapped — including for cohorts that cannot use public AI tools.
Frequently asked questions
What does the Healthcare AI Governance and Bias Auditing course cover?
Clinical AI governance has to cover tools nobody approved, assess bias across populations where the consequence is clinical, and monitor for drift after deployment. This course builds the inventory, the committee, a bias audit protocol, and the decommissioning process for a model that stops performing. It runs 6 hours across 8 modules across 8 modules, at intermediate level, and closes with a capstone: Clinical AI governance program with a bias audit protocol.
Who should take Healthcare AI Governance and Bias Auditing?
It is written for Chief medical informatics officers, AI governance committees, Quality, safety, and health equity officers, Compliance and risk staff. Prerequisites: Clinical or healthcare governance background; Familiarity with your organization's governance structures.
Can we run this course on our own infrastructure?
Yes. ibl.ai is model-agnostic and deploy-anywhere — cloud, private VPC, on-premise, or fully air-gapped — and you own all the code and the data. Cohort data, submissions, and any material learners upload stay inside your perimeter, which matters for healthcare teams that cannot send work to a public AI tool.
How do we get access to Healthcare AI Governance and Bias Auditing?
Request access and we will set it up for your cohort — hosted by ibl.ai, or running against your own deployment. Tell us the group size and timing you need, and whether it should run inside your own perimeter.
How much does AI training for healthcare cost on ibl.ai?
There is no per-seat pricing — you pay for usage or self-host and pay only for the infrastructure, so a 5,000-person rollout does not cost 5,000 licences. 1.6M+ users across 400+ organizations run the platform this way, including NVIDIA, MIT, and Syracuse University.