Chart Talk ~ Anesthesia Coding Conversations

Anesthesia Coding • Auditing • Compliance • Education

Tuesday — Case #2: Is This Block Separately Billable?

Chart Talk ~ Anesthesia Coding Conversations

Welcome to Day 2 of “Would You Code It?” Today we are looking at one of the most common questions in anesthesia coding: a peripheral nerve block is clearly documented—but does that automatically make it separately reportable?

THE CASE

A patient is scheduled for open reduction and internal fixation of an ankle fracture under general anesthesia.

Before induction, the anesthesiologist performs an ultrasound-guided popliteal sciatic nerve block. The block note documents the site, technique, local anesthetic, ultrasound guidance, and successful completion.

The anesthesia record shows general anesthesia for the surgical procedure. The block note states: “Popliteal block performed for postoperative pain management at surgeon request.”

BEFORE YOU KEEP READING

Would you:

A. Not report the block because it was performed by the anesthesia provider on the same day as the anesthetic.

B. Report the block separately because the documentation supports postoperative pain management distinct from the primary anesthetic.

C. Report the block only if it was performed after surgery.

D. Automatically report every documented nerve block in addition to the anesthesia service.

Make your choice: A, B, C, or D.

LET’S TALK THROUGH IT

A well-documented block procedure note answers an important question: what was performed. But separate reporting requires us to ask another question: why was it performed?

When a regional technique is used as the primary anesthetic or is integral to the anesthetic technique, separate reporting may not be appropriate. When a distinct block is performed for postoperative pain management and the documentation supports that purpose, separate reporting may be appropriate, subject to current coding guidance and payer requirements.

The key is not simply that a block was performed. The record must support the role the block played in the patient’s care.

WHAT I WOULD LOOK FOR

  • Was the block used as the primary anesthetic, part of the primary anesthetic technique, or for postoperative analgesia?
  • Is the purpose of the block clearly documented?
  • Is there documentation supporting the surgeon’s request or postoperative pain-management plan when required?
  • Does the anesthesia record show a separate primary anesthetic?
  • Does the block note support the specific nerve or plexus actually targeted?
  • Are current CPT®, NCCI, and payer-specific requirements satisfied?

MY ANSWER

B — Based on this hypothetical documentation, I would evaluate the block for separate reporting as postoperative pain management rather than automatically treating it as part of the general anesthetic.

The documentation identifies a separate primary anesthetic and states that the block was performed for postoperative pain management at the surgeon’s request. That gives us important support for evaluating the block as a distinct service.

However, the final coding decision still requires review of the complete record, current coding guidance, NCCI edits, and applicable payer policy.

CODER’S CHECKPOINT

Do not let the presence of a block note make the coding decision for you. First identify the role the block played in the anesthetic plan.

Ask: Was this the anesthetic, part of the anesthetic, or a distinct postoperative pain-management service?

TODAY’S TAKEAWAY

A block can be perfectly documented and still not be separately reportable.

Code the purpose—not merely the procedure note.

NOW IT’S YOUR TURN

What did you choose—A, B, C, or D?

What documentation do you look for before separately reporting a postoperative pain block? Would the phrase “for postoperative pain management at surgeon request” change your review?

Drop your answer in the comments. If you see the case differently, tell me why. That’s what Chart Talk is all about.

COMING TOMORROW

Wednesday — Case #3: The Anatomy Says Something Different

The provider gives the block a familiar name, but the documented target and needle location make you question whether that name tells the whole story.

Would you code the name—or follow the anatomy?

EDUCATIONAL DISCLAIMER

This hypothetical scenario is provided for educational and informational purposes only. It is not legal, billing, compliance, or payer-specific advice. Coding and billing decisions should be based on the complete medical record, current official coding guidance, applicable payer policies, contractual requirements, and organizational compliance policies.


Discover more from Chart Talk ~ Anesthesia Coding Conversations

Subscribe to get the latest posts sent to your email.

Posted in

“© Chart Talk ~ Anesthesia Coding Conversations – anesthesiacodingconversations.com”

Leave a comment