Day 3 | Read Beyond the Procedure Name
Yesterday, we followed the anesthesia timeline and asked; Does the documented sequence of events make sense as a whole? Today, we’re turning our attention to another part of the record that can easily become a shortcut; the procedure name.
You open the case. You see the scheduled procedure. You recognize the terminology. You know which anesthesia code you normally use. Done…right? Not so fast. The procedure name may point us in the right direction, but it doesn’t always tell us the whole story.
Before selecting the anesthesia code, ask:
- What procedure was performed?
- What anatomical site was involved?
- Is laterality relevant?
- What surgical approach was used?
- Was the scheduled procedure completed as planned?
- Was it expanded or modified?
- Was it converted to another procedure?
- Was any portion aborted?
- Were multiple procedures performed during the same anesthetic?
- Does the operative documentation agree with the anesthesia record?
These details help us move from what was scheduled to what actually happened?
Don’t Code the Word—Code the Anatomy. This is one of the most important habits an anesthesia coder can develop. Know the anatomy. Why? Because procedure terminology can be misleading when we don’t understand where the surgeon is actually working. Two procedures may sound similar but involve different anatomical locations. Two different procedure names may involve the same anatomical region. A surgical approach may help determine which anesthesia code is appropriate and sometimes one small anatomical detail completely changes the direction of the coding review. When the terminology is unfamiliar, don’t guess. Ask, where is it, what structure is involved, what did the surgeon actually do? Then use your authoritative resources to determine the appropriate anesthesia code.
Remember our lesson from Day 1? The pre-anesthesia evaluation tells us what was planned, but the completed record tells us what happened. The same rule applies to the procedure. A patient may enter the operating room for one procedure and leave having undergone something different. The case may be; expanded, converted, modified, partially completed, and or aborted. When that happens, don’t force the final coding decision to match the original schedule. Follow the documentation.
At this point in the week, we have several parts of the story to compare:
Surgical schedule
What was expected?
Pre-anesthesia evaluation
What was planned?
Anesthesia record
What anesthesia care was provided?
Operative documentation
What procedure was actually performed?
Those pieces should generally tell a coherent story, when they don’t, stop and investigate.
🚩 Audit Red Flag
Watch for anesthesia codes selected directly from:
- The surgical schedule.
- A shortened procedure title.
- A familiar abbreviation.
- The preoperative procedure description.
- A prior case with a similar name.
Especially when no one has confirmed the procedure performed. A familiar procedure name can create a false sense of certainty. Familiar words do not replace documentation review.
💡 Coder’s Corner
When you don’t recognize a procedure, resist the urge to immediately search “What anesthesia code goes with ______?” Start with what is the anatomy then determine what procedure was performed on that anatomy then ask which anesthesia code describes the service for that procedure? That sequence helps prevent coding from terminology alone.
🔎 What Should You Verify?
When selecting the anesthesia code, use the documentation and authoritative resources appropriate to the case.
Your review may include:
- The final operative documentation
- The anesthesia record
- Anatomical references
- Current CPT® anesthesia codes and instructions
- ASA coding resources
- Applicable CMS guidance
- Payer-specific policies when relevant
Remember a search engine result is not an authoritative coding source. It may help you understand unfamiliar terminology or anatomy, but the final coding decision should be verified using appropriate authoritative guidance.
🧠 Check Yourself
The surgical schedule lists a broad procedure description. You recognize the term and immediately think you know the anesthesia code. When you review the operative documentation, however, you discover that the procedure performed involved a more specific anatomical location that could affect code selection.
Question: Should you use the anesthesia code you originally selected from the scheduled procedure description?
Answer: Not without further review.
Determine the procedure performed and the anatomy involved then verify the appropriate anesthesia code using current authoritative resources. The scheduled procedure may have started the story, but the completed documentation tells you how it ended.
Today’s Takeaway
Don’t stop at the procedure name. Ask:
What was performed?
Where was it performed?
What anatomy was involved?
Did the procedure change?
Does the operative documentation agree with the anesthesia record?
Then select the code, because when it comes to anesthesia coding Don’t code the word—code the anatomy.
Coming Tomorrow
Day 4 | The Details Hiding in the Record
Tomorrow, we’re going looking for the information that may not be sitting directly in front of us on the primary anesthesia record. A block note, A-line, central line, Swan-Ganz catheter, TEE, ultrasound, and/or post-operative pain documentation. Finding one of these can add another chapter to the anesthesia story, but it will also lead us to another important question, “I found it…but can I report it?”
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 applicable authoritative resources.
Leave a comment