Chart Talk ~ Anesthesia Coding Conversations

Are You Reading All of It?

Every anesthesia record tells a story. It tells us about the patient, what was planned, what actually happened, who provided the care, when anesthesia care began and ended, what procedures and additional services were performed, and how the patient moved through the perioperative experience.

But here’s the question, are we reading the whole story—or are we simply looking for the information we need to code the claim?

Think about what you do when a new anesthesia record appears in front of you. Where do your eyes go first? Procedure, Anesthesia start and stop time, ASA physical status, Provider, Modifier, or maybe you’re already thinking “what anesthesia code am I going to use?” 

There is nothing wrong with knowing what information you need, but when we begin by searching only for individual coding elements, we can miss the connections between them and sometimes those connections are where the most important information is found.

An anesthesia record isn’t simply Procedure + Time + ASA + Modifier = Claim.  Each piece of documentation provides part of the clinical picture. The pre-anesthesia evaluation tells us what was anticipated. The anesthesia record tells us how anesthesia care progressed. The operative documentation tells us what procedure was actually performed. Separate procedure notes may tell us about blocks, invasive lines, TEE, ultrasound, or other services. Provider documentation tells us who participated in the care. Post-anesthesia documentation helps complete the timeline. Individually, those pieces provide information, but, together, they tell the story.

What was scheduled isn’t always what was performed. What was planned isn’t always what occurred. A procedure may be expanded, the surgical approach may change, the anesthesia technique may change, another service may become necessary, a different provider may assume care, and a procedure may even be aborted. That’s why we cannot assume the opening chapter tells us how the story ends, we have to keep reading.

This is where careful anesthesia coding becomes especially important.

Maybe:

• The anesthesia stop time doesn’t seem to align with another documented event.
• The operative report describes a different procedure than the surgical schedule.
• The anesthesia record contains an abbreviation for a service, but you can’t find the supporting note.
• A block is documented, but its purpose isn’t clear.
• Provider participation doesn’t appear to match the modifier.
• Two sections of the record seem to contradict one another.

Does that automatically mean something is wrong? No, but it does mean something deserves another look. Sometimes the most valuable thing a coder identifies isn’t a code, it’s a question.

For this week’s Chart Talk series, we’re going to slow down. Instead of opening the anesthesia record and immediately asking “what code should I use,” we’re going to begin with “what happened to this patient?” Then we’ll follow the story from beginning to end.

This Week We’ll Explore

Day 1 | Start Before the Start Time

We’ll begin with the pre-anesthesia evaluation and look at why understanding the patient, procedure, and anesthesia plan gives us important context before the anesthesia clock ever starts.

Day 2 | Follow the Anesthesia Timeline

We’ll look beyond start and stop times and follow the events, providers, and patient through the anesthesia record.

Day 3 | Read Beyond the Procedure Name

We’ll examine why the scheduled procedure isn’t always enough and reinforce one of our most important Chart Talk principles: Don’t code the word—code the anatomy.

Day 4 | The Details Hiding in the Record

We’ll look beyond the primary anesthesia record for blocks, lines, TEE, ultrasound, post-operative pain services, and other documentation that may add another chapter to the case.

Day 5 | Put the Whole Story Together

We’ll bring everything together and ask the final question, Does the claim tell the same story as the record?

💡 Coder’s Corner

Before you ask, “what code is this,” ask, “what happened?”

Before you ask, “can I bill this,” ask, “why was it performed?”

Before you assume something is wrong, ask, “is there another part of the record I haven’t read yet?”

Good anesthesia coding begins with understanding the care, the codes come after.

🔎 This Week’s Coder Challenge

Try something different with the anesthesia records you review this week. Before you start coding, read the record as a story ask:

WHO?
Who provided the care?

WHAT?
What actually happened?

WHERE?
What anatomy was involved?

WHEN?
Does the timeline make sense?

WHY?
Why were additional services performed?

HOW?
How does the documentation support the coding decision?

Then ask, does everything fit together?

🚩 Pay attention when two parts of the record don’t seem to agree. 

Don’t automatically choose one, don’t fill in the gap yourself, and don’t ignore the inconsistency simply because you already know which code you expected to use. Stop. Review. Investigate. Clarify when appropriate. Let the complete documentation tell you what happened.

This Week’s Takeaway

The anesthesia record is not a collection of boxes we check until we have enough information to submit a claim. It is documentation of a patient’s anesthesia care, and every section can contribute something to our understanding of that care.

So, this week, we’re going to practice looking beyond, the code, time, modifier, procedure name and start connecting the pieces. Because before we can accurately code the anesthesia story… we have to read it.

Coming Tomorrow

Day 1 | Start Before the Start Time

Before we look at anesthesia time, we’ll look at the opening chapter of the story, the patient, procedure and the anesthesia plan, because the anesthesia story begins before the clock starts.

Chart Talk ~ Anesthesia Coding Conversations ~
Lead. Educate. Comply. Excel.For educational purposes only. Always verify coding decisions using current CPT®, ASA, CMS, NCCI, payer-specific guidance, and other