Become the human authority AI can't replace

If you've spent any time in medical coding, you already know the feeling — the chart doesn't quite match the note, the code the EHR suggested seems off, and you're the one who has to make the call. That gap between what the system spits out and what should actually go on the claim? That's always been where skilled coders earn their keep. What's changed is the scale of the problem.

Ambient AI listeners are now in exam rooms and telehealth calls across the country, drafting transcripts and code sets before the physician has closed the chart. Health systems are adopting them because they reduce documentation burden. Payers are watching them because they affect reimbursement. And coders and auditors are caught in the middle — expected to sign off on AI output they were never trained to audit. I built this school because that training didn't exist in the form it needed to.

Here's what I want you to understand about how this curriculum is designed: I am not asking you to memorize code tables. Rote memorization is exactly what AI tools are better at than humans. What I'm teaching you is judgment — the clinical reasoning to know when a diagnosis doesn't fit the encounter, the regulatory literacy to recognize an over-coded E&M before it triggers a payer audit, the workflow discipline to document your corrections so they're legally defensible. That's what makes a Clinical Coding Auditor indispensable, and that's what every module in this school is built to develop.

We start with the foundations — anatomy, documentation, HIPAA, ICD-10-CM, CPT, HCPCS — not because I assume you know nothing, but because I want to make sure the foundation is solid before we build on it. Then we move into the revenue cycle, denial management, and appeals strategy, because understanding what happens after the claim goes out changes how you code when it goes in. From there: AI transcript auditing, the ICD-11 transition, FHIR data exchange, Remote Patient Monitoring, cross-border telehealth, and the resilient coding methods that keep you functional when the system goes down — including ransomware downtime protocols that most coders have never thought about until they need them.

The capstone is where it all comes together. You'll take a multi-specialty ambient transcript, audit the AI's code draft, strike hallucinated conditions with written justification, recover missed procedures, build the final claim, and sign off. It's the kind of case that shows up in job interviews and compliance reviews, and you'll have done it in a controlled environment before the stakes are real.

I'll be direct with you: this is not a simple course, and I didn't design it to be. The revenue cycle is complex, the regulatory environment is demanding, and AI is raising the bar on what it means to be a competent coder. But if you work through this curriculum the way it's designed — engaging with the scenario exams, thinking through the judgment calls, not just reading for the answer — you will come out the other side as a professional who can walk into any medical practice, health system, or revenue cycle consulting role and demonstrate a level of expertise most coders your age don't have yet. That's the outcome I'm designing for. I hope you'll join me.