Chart Talk ~ Anesthesia Coding Conversations

Postoperative Pain Block or Primary Anesthetic?

You open the anesthesia record and there it is. A beautifully documented nerve block. The nerve is identified, laterality is documented, ultrasound guidance is documented, the local anesthetic, concentration, and volume are recorded, the procedure note looks great, so, what’s the CPT code? Not so fast. 

Before asking “What code describes this block?”, an anesthesia coder or auditor needs to answer another question: Why was the block performed? Identifying the block is only part of the coding analysis.

Whether that block represents a separately reportable postoperative pain management service or was used as part of the primary anesthetic technique can completely change the coding outcome.

Welcome to Anesthesia Audit Red Flag #4.

A Block Note Doesn’t Automatically Mean a Separately Billable Block. This is one of the easiest traps to fall into when reviewing anesthesia records. You see a block note, identify the nerve, find the corresponding CPT code, confirm ultrasound guidance, and everything seems ready to go, but there is still an important question: Was the block separately reportable?

A regional block may be used for different purposes. It may serve as the primary anesthetic technique, be part of the anesthetic technique, be performed separately for postoperative pain management, and the procedure itself may look the same, but the purpose can make the difference.

When auditing a nerve block performed around the time of surgery, look beyond the block procedure note. Review the entire anesthesia record. What was the planned anesthetic, what was actually administered, was the patient receiving general anesthesia, was regional anesthesia listed as the primary anesthetic, was the block documented as postoperative analgesia, was there documentation of a request for postoperative pain management when required, does the operative or anesthesia documentation indicate why the block was performed, and does the timeline support the documented purpose? The answers may be found in several different parts of the record. Don’t audit the block in isolation.

Sometimes the documentation clearly states: “Block performed for postoperative pain management.” Other times, the record isn’t nearly that straightforward. You may see: “Regional block,” “For pain,” “Surgeon request,” “Patient comfort,” or simply the name of the block with no indication of its purpose. Those entries may require additional review. Why? Because pain management is part of anesthesia care. The fact that a block provides analgesia doesn’t automatically establish that it represents a separately reportable postoperative pain management service. A block relieving pain and a block being separately reportable for postoperative pain management are not necessarily the same thing.

Suppose a patient undergoes a lower-extremity surgical procedure. The anesthesia record identifies the anesthetic technique as regional anesthesia. A peripheral nerve block is performed and provides the surgical anesthesia. The block documentation itself may be excellent, but if the block is being used as the anesthetic technique for the surgical procedure, you cannot simply assume that it should also be separately reported as postoperative pain management. This is where auditors must separate two questions: Was the block performed and why was the block performed? The answer to the first question doesn’t automatically answer the second.

Another common assumption is: The patient received general anesthesia, so the block must have been for postoperative pain. Not necessarily general anesthesia and a regional technique may both be part of the anesthetic plan. The presence of general anesthesia doesn’t, by itself, establish that a regional block qualifies as a separately reportable postoperative pain procedure. The documentation still needs to support the purpose of the block and the applicable requirements for separate reporting. Never let the anesthesia type substitute for documentation of medical necessity and purpose.

Per Surgeon’s request, this phrase may catch an auditor’s attention—and it should, but don’t stop reading simply because you find it. Determine exactly what the documentation says. Was the block requested for postoperative pain management? Was postoperative pain management beyond the surgeon’s usual care? Does the documentation satisfy applicable CPT®, NCCI, CMS, Medicare Administrative Contractor, or payer-specific requirements? Requirements can vary depending on the payer and circumstances. One phrase should not become a substitute for reviewing the complete record and applicable guidance.

A block is performed before surgery. Does that mean it cannot be for postoperative pain management? No. A block’s timing alone doesn’t necessarily determine its purpose. A block performed before surgery may still be intended for postoperative pain management. Likewise, simply performing a block at a particular point in the perioperative period doesn’t automatically establish separate reportability. Look at timing—but don’t code from timing alone. The documentation should establish the purpose.

Now we move from why the block was performed to what was actually performed. Suppose the procedure note calls something an: “Adductor Canal Block.” Does that automatically tell you which CPT code should be reported? Not necessarily. Procedure names, institutional terminology, and clinical shorthand don’t always map neatly to CPT terminology. The auditor may need to examine: Anatomical location, Nerve targeted, Approach, Laterality, Single injection versus continuous catheter, Technique described, Ultrasound findings, and Medication placement.  This is where anatomy becomes extremely important. Don’t code the label. Code what the documentation actually describes.

A block note may identify more than one nerve. That doesn’t automatically mean multiple CPT codes should be reported. Sometimes multiple nerves are branches of the same larger nerve distribution. Sometimes the approach encompasses more than one nerve. Sometimes multiple injections represent one block technique. Other times, separately identifiable blocks may actually have been performed. The auditor needs to understand the anatomy, procedure, CPT code descriptions, bundling edits, and payer guidance before concluding that multiple block codes are appropriate. More nerves documented does not automatically mean more codes.

A complete ultrasound-guided block note may include documentation such as: Real-time visualization, Needle advancement, Identification of relevant anatomy, Visualization of local anesthetic spread, and Permanent image documentation when required.  That’s excellent documentation, but before separately reporting ultrasound guidance, there is still another question: Is ultrasound guidance separately reportable with the block code being billed? Documentation is only one part of the analysis. The coder or auditor must also determine whether separate reporting is permitted under current CPT®, NCCI, and payer rules.

When reviewing a regional anesthesia service, work through the analysis in this order:

1. Why was the block performed?

Primary anesthetic, Part of the anesthetic technique, Postoperative pain management, or something else?

2. What block was actually performed? 

Don’t rely only on the title of the procedure note. Review the anatomy, nerve, approach, technique, and documentation.

3. Is the service separately reportable?

Only after answering the first two questions should, you determine the appropriate coding and whether separate reporting is supported.

🔎 Auditor’s Mini-Challenge

Consider this simplified case: A patient undergoes a total knee replacement. The anesthesia record documents:

Anesthesia Type: General

A separate procedure note documents Ultrasound-guided adductor canal block, right lower extremity.  The note contains detailed procedural documentation, including the local anesthetic administered and ultrasound visualization. The block note does not clearly state the purpose of the block. 

What should the auditor do?

A. Report the block because a complete procedure note exists.

B. Report the block because general anesthesia was used for the surgery.

C. Assume the block was performed for postoperative pain because adductor canal blocks are commonly used for analgesia after knee surgery.

D. Review the complete record and applicable guidance to determine the purpose of the block and whether separate reporting is supported.

The best auditing approach is D.

A clinically reasonable assumption is still an assumption. The procedure may ultimately be separately reportable, but the auditor should reach that conclusion from the documentation and applicable guidance—not simply because that is how the block is commonly used.

Don’t Let a Perfect Procedure Note Distract You. This may be the biggest takeaway from Red Flag #4. A block procedure note can contain everything you need to identify the procedure and still leave unanswered whether the service should be separately reported. That’s why auditing regional anesthesia requires looking at more than the block note.

The block note tells you what happened. The anesthesia record helps tell you how it fit into the anesthetic plan. The documentation helps establish why it was performed. The coding and payer guidance tells you whether it can be separately reported. You need the complete story.

🚩 Auditor’s Takeaway

When you see a nerve block on an anesthesia record, resist the urge to immediately open the CPT book and find the block code. First ask: Why was the block performed then what does the anatomy support, was it the primary anesthetic or part of the anesthetic technique, or was it performed for postoperative pain management? Does the documentation support its purpose? 

Are applicable requirements for separate reporting satisfied? Does the block documentation support the specific code selected? Do bundling or payer rules affect reporting?

And finally, Could I defend both the code and the reason it was separately billed, because sometimes the biggest red flag isn’t that the block was coded incorrectly, it’s that nobody stopped to ask: “Why are we billing the block separately in the first place?”

Next: Anesthesia Audit Red Flag #5
When the Record Doesn’t Agree with Itself

The anesthesia record says one thing. The operative report says another. The timestamps tell another story. Which one supports the claim? We’ll finish the series by looking at what happens when the medical record starts contradicting itself.

Chart Talk ~ Anesthesia Coding Conversations
Anesthesia Coding • Auditing • Compliance • Education

Educational content is intended for informational purposes only and is not a substitute for current authoritative guidance. Always consult current CPT®, CMS, NCCI, Medicare Administrative Contractor, payer-specific, and other applicable guidance when making coding, billing, auditing, or compliance determinations.