Chart Talk ~ Anesthesia Coding Conversations

When the Record Doesn’t Agree with Itself

You are almost finished auditing the case, the anesthesia record looks good. The procedure is documented, the anesthesia time is present, the modifiers appear appropriate, everything seems to be falling into place. Then you open another part of the medical record, and suddenly… the story changes.

The anesthesia record says one thing, the operative report says another, the procedure scheduled isn’t the procedure actually performed, the laterality changes the timestamps don’t line up, the block note identifies one nerve, but the documented anatomy suggests something different, and one portion of the record supports medical direction, while another raises questions about the provider’s participation. Now what?

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

The Medical Record Is More Than One Document. One of the easiest mistakes we can make when auditing anesthesia is reviewing a single document in isolation. An anesthesia encounter may include pre-anesthesia evaluation, anesthesia plan, anesthesia record, procedure notes, regional block documentation, operative report, nursing documentation, OR records, PACU documentation, medication administration records, post-anesthesia evaluation, provider attestations, and addenda or amendments.  Each document contributes another piece of the story. Most of the time, those pieces fit together. But what happens when they don’t? That’s when the auditor needs to stop and look closer.

Imagine the scheduled procedure says: Right total knee arthroplasty 

The anesthesia record also references a right knee procedure, but the operative report documents something different or perhaps the procedure changed after the patient entered the operating room. Which procedure should drive anesthesia code selection? The procedure that was actually performed. Scheduling information can help provide context, but it doesn’t necessarily establish the final procedure. Procedures change, cases are converted, planned procedures are abandoned, and additional procedures may be performed. An auditor should verify the actual surgical service before determining whether the anesthesia code is supported. Don’t code the schedule. Audit what happened.

The anesthesia record says: Right, the block note says: Left, the operative report says: Right. Now we have a problem. Perhaps one entry is simply a documentation error, but which one? The auditor shouldn’t silently choose the side that makes the claim work.

Instead, recognize the discrepancy and determine whether the record contains enough information to appropriately resolve it—or whether clarification is needed under the organization’s established process. Laterality discrepancies can affect diagnosis coding, procedure coding, regional anesthesia services, medical necessity, claim accuracy, and patient safety and compliance concerns.  A single word can matter.

The pre-anesthesia plan documents general anesthesia, another area identifies MAC, the procedure record suggests regional anesthesia, and the post-anesthesia note references general anesthesia. What actually occurred? Remember that a planned anestheticand the anesthetic ultimately administered may legitimately differ. Plans change and clinical circumstances change. A MAC case may convert to general anesthesia. A regional technique may be supplemented or converted. The discrepancy isn’t automatically an error, but the auditor should be able to understand the final anesthetic course from the record. Don’t confuse the planned anesthetic with the anesthetic actually delivered.

🚩 Red Flag: The Times Don’t Line Up

We talked about this in Red Flag #1, but conflicting documentation deserves another look here. Suppose the anesthesia record says: Anesthesia Stop: 10:42, but PACU documentation indicates: PACU Arrival: 10:31 Is that necessarily wrong? Not automatically, but it deserves review. Or perhaps: Patient Out of OR: 10:50 while Anesthesia Stop: 10:37. Again, the timestamps alone don’t necessarily give you the answer. The auditor needs to determine what the documentation says was happening during those intervals and whether the reported anesthesia time is supported. The clock is part of the story—but the documentation has to explain it.

🚩 Red Flag: Medical Direction Documentation and the Timeline Conflict

This can be one of the more significant anesthesia audit findings. The record contains an anesthesiologist’s attestation supporting medical direction. Everything looks appropriate when the case is reviewed alone. Then you compare the physician’s other cases. Two critical portions appear to occur at the same time, or the provider appears to be participating in another activity during an interval relevant to medical direction. Now the documentation and the timeline may be telling different stories. This is why concurrency auditing can be so important. A single record may look perfect until you place it beside the other records. When medical direction is being evaluated, the auditor may need to review more than attestations and checkboxes. The provider’s timeline can matter too.

🚩 Red Flag: The Procedure Note Says One Thing, but the Anatomy Says Another

This is one of my favorite anesthesia coding reminders: Don’t code the word. Code the anatomy. Suppose the title of the procedure note identifies a particular block, but when you read the actual procedure description, the documented needle placement, anatomical landmarks, target nerve, or injection location doesn’t appear consistent with that title. Which should you rely on? Don’t automatically code from the heading. Look deeper. Clinical terminology, shorthand, institutional naming conventions, and CPT terminology don’t always align perfectly. The documentation should support the procedure represented by the code. The name of the block is a clue. The anatomy tells the story.

🚩 Red Flag: The Claim Says Something the Record Doesn’t

Sometimes the inconsistency isn’t between two documents. It’s between the medical record and the claim. Perhaps: the claim reports a physical status modifier not supported by the documented patient condition, a qualifying circumstance is reported without supporting documentation, medical direction modifiers appear on the claim without sufficient supporting documentation, or a separately reportable procedure appears on the claim but can’t be connected to the provider. The anesthesia CPT code doesn’t match the procedure actually performed. A postoperative pain block is separately reported, but the record doesn’t clearly establish its purpose. This is where auditing becomes especially important. The claim is making a statement. Every code and modifier tells the payer something about the service. The medical record should support that statement.

🚩 Red Flag: Copy-Forward Documentation Doesn’t Fit the Case

Electronic health records make documentation easier, but they can also create inconsistencies. Templates, macros, smart phrases, and copied documentation can result in entries that don’t match the current encounter. You may see: wrong laterality, wrong procedure, wrong patient-specific information, references to a technique that wasn’t used, identical attestations across multiple cases, conflicting anesthesia types, documentation carried forward from an earlier encounter, and statements that don’t align with timestamps or other portions of the record.  A templated statement isn’t automatically unreliable, but when it conflicts with patient-specific documentation, the auditor should investigate. Documentation should describe this patient, this procedure, and this encounter.Which Document Wins? This is a question an auditor sometimes wants answered with a simple hierarchy. “Which document should I believe?” Auditing isn’t always that simple. The answer may depend on what information is conflicting, who documented it, when it was documented, the purpose of the documentation, applicable coding guidelines, payer requirements, organizational policies, whether the discrepancy can be resolved from the existing record, or whether clarification or a query is appropriate. The goal isn’t to choose whichever document supports payment. The goal is to determine what the complete medical record supports and sometimes the appropriate conclusion is: I don’t have enough information yet. That is a legitimate audit finding.

🚩 Don’t Make the Record Agree

This deserves its own reminder. When two pieces of documentation conflict, there can be a temptation to mentally connect the dots. We know what probably happened. The surgery makes sense, the block makes sense, the anesthesia technique makes sense, the code makes sense. So, we fill in the missing pieces ourselves. Don’t!  An auditor should not manufacture consistency where the documentation doesn’t provide it. If the discrepancy can be resolved through appropriate review of the existing record, resolve it. If additional clarification is required, follow the appropriate process. If authoritative guidance is needed, research it. But don’t turn “This is probably what happened” into “This is what the record supports.” Those are not the same thing.

🔎 Auditor’s Mini-Challenge

Consider this simplified record:

Scheduled Procedure: Left total knee arthroplasty 

Anesthesia Record: General anesthesia

Block Note: Right adductor canal block for postoperative pain

Operative Report: Left total knee arthroplasty performed

Claim: Anesthesia service + separately reported peripheral nerve block

What catches your attention? The laterality of the block. Now what?

A. Change the block documentation to left because the surgery was on the left.

B. Assume “right” was a typo and bill the block.

C. Automatically remove the block from the claim.

D. Identify the discrepancy and review the complete record to determine whether it can be appropriately resolved or requires clarification before reaching a coding or audit conclusion.

The best auditing approach is D.

You may strongly suspect what happened, but suspicion isn’t documentation.

The auditor identifies the discrepancy. The documentation must support the conclusion.

The Three-Document Test

Here’s a simple exercise you can incorporate into anesthesia audits. Pick three key documents: 1. The anesthesia record, 2. The operative/procedure report, and 3. The claim; then ask Do all three tell the same story?

The level of detail will obviously differ, but the fundamental facts should make sense together. What procedure occurred? What anesthesia service was provided? Who provided it? When did it occur? What additional procedures were performed? Why were separately reported services performed? What codes and modifiers ultimately represented those services? If those three pieces don’t align, you may have found your next red flag.

🚩 Auditor’s Takeaway

When the medical record doesn’t agree with itself, don’t automatically choose the documentation that produces the cleanest claim. Stop, Compare, Investigate, Research, Clarify when appropriate, and document your reasoning. Because the goal of an anesthesia audit isn’t simply to determine whether every field on a claim contains a valid code. The goal is to determine whether the claim accurately represents the service supported by the medical record. The record should tell a story, and the claim should tell the same one. If they don’t? 

🚩 Follow the red flag.

That’s a Wrap on Anesthesia Audit Red Flags Week!

This week we looked at five areas that should make anesthesia coders and auditors stop and look a little closer:

🚩 Red Flag #1: The Anesthesia Time Doesn’t Tell the Whole Story

🚩 Red Flag #2: The Modifier Says Medical Direction — Does the Record?

🚩 Red Flag #3: The Procedure Is Listed — But Where Is the Documentation?

🚩 Red Flag #4: Postoperative Pain Block or Primary Anesthetic?

🚩 Red Flag #5: When the Record Doesn’t Agree with Itself

The lesson connecting all five is simple. A red flag isn’t a conclusion. It’s an invitation to investigate.

See the red flag. Follow the documentation. Verify the guidance. Defend the conclusion.

And perhaps the most important question an anesthesia auditor can ask: “Could I defend this claim using the documentation in front of me?” If the answer is yes, you should be able to explain why. If the answer is no—or I’m not sure—you may have just found your next red flag.

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.