Industry track, The AI Decision Course
AI in healthcare
For leaders in hospitals, health systems and health companies: easing the documentation burden on clinicians, deciding what AI may see in the patient record, prior authorization, and who carries the risk when AI touches care.
10 short lessons. Each one is a short read with a card your team fills in and three AI prompts to test it. Part of The AI Decision Course: membership is $299 a year and includes all 12 courses, with a full refund within 14 days.
About this course
This course covers bringing AI into hospitals, health systems and health companies: taking the documentation burden off clinicians first, naming the use before AI touches the patient record, and fitting clinical AI into the clinician's day. It also covers prior authorization a rung at a time, how far AI may go with patients, paying for health AI, and who carries the risk when AI touches care.
You leave able to pick the first clinical users by documentation load and to name the use before AI touches the patient record, from care to operations. You can also put AI on prior authorization a rung at a time, keep a person on anything that reaches a payer, and allocate every risk control in the contract before deployment.
Lessons in this course
- Take the documentation burden off your clinicians first
- Before AI touches the patient record, name the use
- Clinical AI that helps the clinician decide, and fits the day
- Watch the patient all the time, or test now and then?
- Put AI on prior authorization, one rung at a time
- Will anyone pay for the health AI you build?
- How far to let AI go with your patients
- Your first regulated medical AI claim: one question, one study
- Who carries the risk when AI touches care
- Access to the specialist, not a better specialist
Questions
How do we reduce the documentation burden on clinicians?
Start with the clinicians who write the most notes, and gate the rollout on a note bar a clinician panel signs while every note still gets read. Ask consent aloud and log it, and measure time in the record and after-hours work from day one. The lesson 'Take the documentation burden off your clinicians first' covers the start.
How far should AI go with patient messages?
Tier patient channels by consequence: rescheduling for an established patient can run fully automated, while symptom triage needs a tested bar and a human checkpoint. Keep clinical judgment with a person, and tell patients when a machine is involved, since patients who dislike AI mostly accept it once the disclosure is routine. The lesson 'How far to let AI go with your patients' covers the tiers.
Who carries the risk when AI touches patient care?
Name who answers before rollout, because with no one answerable the clinician holds the risk. Allocate every risk control in the contract, stamp which system and which version touched the record, and own only the decisions you helped make. The lesson 'Who carries the risk when AI touches care' covers the allocation.
The other courses in the membership
- Proving AI's value: use cases and ROIFree lesson Before you fund an AI project, make someone name the problem
- Data foundations for AIFree lesson A better model won't fix data it can't see
- Building AI skills and the workforceFree lesson Next year's hiring plan: fewer hires, more output, new roles
- Getting AI adoptedFree lesson Before you buy more AI, close the understanding gap
- Governance, risk and responsible AIFree lesson Count the AI you already have
- Agents in productionFree lesson Ask what a so-called agent actually does
- Build, buy and choosing modelsFree lesson Test an AI vendor on your own work before you sign
- Securing AIFree lesson Where company data leaks into outside AI tools
- AI in customer service and experienceFree lesson Launch the chatbot on one question, because you answer for every reply
- AI for software and technical teamsFree lesson Pick the delivery numbers to watch before coding tools land
- Where AI is heading