Part VIII — Audit, Certification, and the Career

Chapters 37–40

Four chapters about the rest of your working life.

Chapter 37 is the audit. Everything you code will eventually be looked at by someone whose job is to find it wrong — an internal auditor, a payer's special investigations unit, a Recovery Audit Contractor, a Unified Program Integrity Contractor, or in the worst case a federal prosecutor's expert. The chapter teaches auditing from both chairs: how to run an internal audit that finds problems while they are still cheap, how to score a chart and what counts as an error, and then what each of the external programs actually does, how extrapolation turns forty-two reviewed claims into a six-figure demand, how to respond to a records request, how to write an audit response, and what self-disclosure and the sixty-day clock require.

The most useful thing in the chapter is the least dramatic: an audit is a reading of your documentation by someone who was not there, has no stake in your interpretation, and will not give you the benefit of the doubt. Everything you write should be built for that reader.

Chapter 38 is the technology, and it is written without either the enthusiasm or the dread the topic usually attracts. Clinical documentation integrity is a mature discipline with real methods and a real failure mode — the leading query, which is both ineffective and, at scale, an enforcement exposure. Computer-assisted coding has been in production for two decades and is genuinely good at some things and reliably bad at others. Autonomous coding works today in narrow, high-volume, low-variance domains and does not work outside them. Large language models are changing the shape of the problem faster than the regulatory apparatus can respond.

The chapter's argument is specific: the engine is good at suggesting and bad at deciding, the asymmetry between a missed code and a fabricated one is enormous, and the human in the loop is there for the second kind of error. It also says plainly which parts of the job are most exposed, because you deserve a straight answer about that before you spend a year training for it.

Chapter 39 is certification — the credential that governs this field more than any degree does. The two organizations, what each is for, the AAPC credentials and the AHIMA credentials, how to choose honestly between them, what the exams actually test, a week-by-week preparation plan, the rules about annotating the code books you carry into the exam room, exam-day time management, the apprentice designation and how to remove it, and continuing education.

Chapter 40 is the capstone, and it does two things.

First, it assembles Account 10-4471 completely — every code, every form field, every dollar, every day, from the moment the patient signed in on a Tuesday in March to the zero balance one hundred days later. Second, it answers a question the book has been circling since Chapter 1 and has deliberately refused to answer: given what it cost to work that denial, and given how often appeals succeed, which denials are worth fighting?

The inputs to that answer have all been published, in chapters you have already read. The assembly is here. So is the conclusion, and it is not the comfortable one.

Then the career: getting the first job without experience, the first ninety days, the productivity and quality standards you will be held to, the ladder from coder to auditor to educator to manager to director, remote work and contracting and outsourcing, when to specialize, how to stay current for thirty years in a field that resets a piece of itself every October — and a thirty-day plan you can start on the day you close the book.

The themes Part VIII carries — all six of them, which is the point of a capstone.

Chapter 37 is compliance is not optional and if it isn't documented, it didn't happen, together. Chapter 38 is the code set is a language — and what happens when a machine learns to speak it. Chapter 40 is a clean claim is a fast claim and every day a claim sits, it is worth less, finally quantified, and you code from the chart, but you get paid by the contract, one last time, with the whole file on the table.

Chapters in This Part