Chart Talk: Anesthesia Coding Conversations

How the payment model developed, why the requirements matter, and what happens when documentation does not support the claim

In anesthesia billing, the words medical direction are sometimes treated as if they simply describe the working relationship between an anesthesiologist and a CRNA. They mean much more than that.

When a claim is submitted as medically directed, the billing is representing that the anesthesiologist satisfied the requirements necessary for payment under the medical direction methodology.

An anesthesiologist may have been in the facility, assigned to the case, or involved in portions of the patient’s care. Those facts alone do not automatically establish Medicare medical direction. The requirements must be met and supported by the medical record.

That is why medical direction should never be viewed as simply choosing between QK, QY, QX, and QZ. It begins with the care actually provided and ends with documentation capable of supporting what was reported on the claim.

How Did Medical Direction Come to Be?

Anesthesia has long been delivered through several practice models. An anesthesiologist may personally perform an anesthesia service, a CRNA may provide anesthesia without medical direction where permitted, or an anesthesiologist may work with qualified nonphysician anesthesia professionals as part of an anesthesia care team.

Medicare therefore needed a payment methodology that could distinguish among these arrangements. The medical direction rules established the conditions under which Medicare recognizes the anesthesiologist’s involvement when the physician directs qualified anesthesia personnel in concurrent anesthesia cases.

Under current Medicare policy, medical direction may apply when an anesthesiologist directs qualified individuals in two, three, or four concurrent anesthesia procedures, provided the medical direction requirements are satisfied. For a single medically directed CRNA case, Medicare uses the QY/QX reporting structure.

The distinction is not merely administrative. It determines how the anesthesia service is represented and how Medicare calculates payment.

What Is the Purpose of Medical Direction?

The medical direction requirements establish the level of physician participation that must occur for Medicare to recognize and pay the anesthesiologist’s medical direction service.

Medical direction is not created simply because the anesthesiologist supervises a department, is available somewhere in the hospital, signs the anesthesia record, or works with the CRNA. Medicare identifies specific responsibilities that must be performed.

The Seven Medical Direction Requirements

1. Perform a pre-anesthetic examination and evaluation.
2. Prescribe the anesthesia plan.
3. Personally participate in the most demanding procedures in the anesthesia plan, including, when applicable, induction and emergence.
4. Ensure that procedures in the anesthesia plan the physician does not personally perform are performed by a qualified individual.
5. Monitor the course of anesthesia administration at frequent intervals.
6. Remain physically present and available for immediate diagnosis and treatment of emergencies.
7. Provide indicated post-anesthesia care.

Does the medical record demonstrate that the requirements applicable to this claim were actually satisfied?

Documentation Is What Connects the Service to the Claim

There is a difference between saying, “Our anesthesiologists medically direct our CRNAs,” and being able to demonstrate, “The documentation for this individual encounter supports billing this service under Medicare’s medical direction rules.”

The second statement is what matters when the claim is reviewed. CMS requires documentation of physician participation in important components of medical direction. The record therefore needs to tell the story of physician participation.

A billing system cannot create that story. A modifier cannot create that story. And an organizational policy cannot substitute for patient-specific documentation.

The Dangerous Assumption: “The Claim Paid”

One of the biggest compliance traps in anesthesia billing is assuming that a paid claim is necessarily a supported claim. It isn’t.

Claims are commonly processed electronically based on the information transmitted to the payer. The fact that a payer accepted a modifier and issued payment does not necessarily mean the payer reviewed the complete anesthesia record before paying the claim.

During an audit, the question changes from “Did Medicare accept the QK or QY modifier?” to “Can we prove that QK or QY was appropriate?” Those are two very different questions.

What Happens When Documentation Does Not Support Medical Direction?

Consider an anesthesiologist directing three CRNAs. The billing system assigns QK to the anesthesiologist and QX to the CRNAs. The claims process and payment is received. Months or years later, the cases are selected for review.

Now the medical records are examined. Perhaps required physician participation cannot be established. Perhaps post-anesthesia care is not supported. Perhaps concurrency cannot be reconstructed. Perhaps frequent monitoring is not demonstrated, or the physician was performing another service that interfered with the ability to satisfy medical direction requirements.

The issue is no longer whether the claim successfully passed through the billing system. The issue is whether the medical record supports the payment methodology represented on that claim.

Potential Consequences

• Claim denials or adjustments
• Recoupment of previously paid claims
• Overpayment identification and repayment obligations
• Expanded auditing or additional documentation requests
• Prepayment review
• Increased scrutiny of other anesthesia claims
• Compliance investigations when a pattern of unsupported billing is identified

Medical Direction Is Not Determined by the Modifier

Coders and billers should remember the correct sequence:

Documentation → Medical Direction Status → Modifier → Claim

QK and QY communicate information about the anesthesiologist’s role. QX communicates that the CRNA service was furnished with medical direction by a physician. These modifiers should be the result of determining the supported anesthesia arrangement, not the mechanism used to create one.

If the record does not support medical direction, attaching a medical direction modifier does not cure the documentation deficiency.

Concurrency Matters Too

Documentation of the seven requirements is only part of the analysis. Concurrency must also be evaluated.

Medicare explains that concurrency considers the maximum number of procedures the physician is medically directing within the context of a case and whether other procedures overlap. Concurrency is not determined only by counting Medicare patients.

This is why accurate anesthesia start and stop times, provider assignments, overlapping cases, and physician activities are so important. Sometimes you have to look at the entire timeline.

The Anesthesia Record May Look Complete and Still Fail Medical Direction

An anesthesia record can contain start and stop times, vital signs, medications, CRNA documentation, procedure information, signatures, anesthesia technique, and patient status—and still fail to establish medical direction.

The question is not simply, “Is there an anesthesia record?” The question is, “Does this record demonstrate the physician participation required for the payment methodology being reported?”

A clinically complete record is not automatically a billing-complete medical direction record.

Medical Direction Is a Compliance Process, Not Just a Coding Process

Organizations should not place the entire responsibility for medical direction on the coder. Coders can only code what the documentation allows them to see.

A strong medical direction process requires coordination among anesthesiologists, CRNAs and other qualified anesthesia professionals, coders, auditors, billing teams, and compliance leadership. Medical direction should not be treated as a billing department checkbox; it is an organization-wide compliance process.

What Should an Anesthesia Practice Audit?

A meaningful medical direction audit should go beyond checking whether QK, QY, and QX were paired correctly.

• Was the pre-anesthetic evaluation performed and documented?
• Was the anesthesia plan established?
• Is participation in the most demanding portions supported when applicable?
• Can physician monitoring during the case be demonstrated?
• Was the anesthesiologist physically present and available as required?
• Is indicated post-anesthesia care documented?
• How many cases were concurrent?
• What other services was the anesthesiologist performing during overlapping periods?
• Does the modifier submitted accurately represent the documented anesthesia arrangement?
• If this claim were pulled for review tomorrow, could we defend it using the medical record we have today?

Don’t Bill the Staffing Model — Bill the Supported Record

A practice may operate under an anesthesia care team model. That does not mean every encounter automatically qualifies as medically directed. A scheduling system may identify a directing physician; a physician may sign the chart; a claim may even be paid. None of those facts alone proves medical direction.

The medical record must support the payment methodology being reported. That is the difference between billing based on how the organization believes the case was staffed and billing based on what can actually be demonstrated.

The Auditor’s Perspective

When auditing medical direction, stop asking only, “Which modifier belongs on this claim?” Ask instead, “What does this modifier represent?”

When QK, QY, or QX is placed on a claim, it communicates something about how the anesthesia service was furnished. The modifier is small. The representation behind it is not.

Medical direction is not established because the anesthesiologist was somewhere in the building, because the anesthesiologist’s name appears on the record, because the practice routinely uses an anesthesia care team model, or because previous claims using the same billing methodology were paid.

Medical direction is established when the requirements are satisfied and the medical record supports the services being represented.

Final Takeaway

Medical direction was designed as a specific Medicare payment methodology recognizing physician participation in anesthesia care delivered with qualified anesthesia professionals. With that payment methodology comes responsibility.

Before reporting medical direction, the organization should be able to answer three questions:

Was it performed?

Was it documented?

Can we defend it?

If one of those answers is no, the claim deserves another look. In anesthesia coding, the goal isn’t simply to get the claim paid. The goal is to make sure the documentation supports keeping the payment when someone comes back and asks why it was billed that way.

Educational Disclaimer

This material is provided for educational purposes only and is not intended as legal advice or as a substitute for payer-specific guidance. Medicare requirements, payer policies, state laws, contractual provisions, and organizational policies should be reviewed when determining appropriate anesthesia billing and documentation. Always consult current CMS guidance and applicable payer requirements.

Primary Reference

Centers for Medicare & Medicaid Services (CMS), Medicare Claims Processing Manual, Chapter 12 — Physicians/Nonphysician Practitioners. Review the current version for anesthesia medical direction requirements, concurrency, documentation, and payment guidance.

© 2026 Chart Talk — Anesthesia Coding Conversations. All rights reserved.

Sometimes the difference between the right anesthesia code and the wrong one is knowing exactly where the surgeon worked.

Introduction

You open the operative report and see: Stone removal.

Seems straightforward. Then you realize the stone is located at the ureteropelvic junction (UPJ). Now the questions begin. Is that kidney? Is that ureter? Is it considered the upper third of the ureter? Which anesthesia code category best describes the procedure that was actually performed?

Suddenly, what looked like a coding question has become an anatomy question.

Sometimes anesthesia coding is an anatomy test in disguise. Knowing the surgical procedure is important. Knowing where the procedure occurred can be just as important.

The Procedure Name Doesn’t Always Give You the Answer

Anesthesia coders frequently begin with a surgical CPT® code, scheduled procedure, or operative description. But anesthesia codes are organized differently from surgical codes.

The surgical code may describe the specific technique performed. The anesthesia code may be organized primarily around anatomic site, type of procedure, surgical approach, patient circumstance, or a combination of these factors.

That means a coder cannot always look at the name of the procedure and immediately know the appropriate anesthesia code. Sometimes you have to ask: Where exactly is the surgeon working?

Think Anatomically Before You Think Numerically

One of the most useful habits an anesthesia coder can develop is to temporarily forget about the code number. Before opening the anesthesia section, identify the anatomy.

Ask yourself: What body system is involved? What specific organ or structure is involved? Where within that structure is the procedure being performed? What is the surgical approach? Does the procedure cross anatomical regions? Is the surgeon working superficially or deeply? Does the operative work extend beyond the structure suggested by the procedure title?

Once you understand the anatomy, the anesthesia code choices often become much clearer.

Example 1: Kidney, Ureter, or Both?

Consider a patient undergoing treatment for a urinary stone. At first glance, you might think: Urinary stone = urology = choose the usual anesthesia code. But that is not enough information.

Where is the stone? Is it located in the kidney, renal pelvis, ureteropelvic junction, upper ureter, middle ureter, lower ureter, or bladder? These are anatomically related structures, but they are not interchangeable.

The ureteropelvic junction, or UPJ, is the area where the renal pelvis transitions into the ureter. That anatomical detail may become important when determining which anesthesia code descriptor best corresponds to the operative work.

CODING LESSON: Don’t code the stone. Code the procedure performed at the anatomical location involved.

Example 2: Shoulder or Upper Arm?

Orthopedic procedures provide another excellent anatomy lesson. Suppose the operative report involves the proximal humerus. The word humerus may immediately make you think upper arm.

But anesthesia coding may require closer attention to whether the operative procedure is classified with the shoulder, shoulder girdle, upper arm, or another anatomical category.

Procedures involving the proximal humerus, humeral head, glenohumeral joint, acromioclavicular joint, scapula, and clavicle occur in the same neighborhood, but anesthesia coding does not necessarily treat every procedure identically.

Anatomical proximity does not guarantee coding equivalence.

Example 3: The Spine Is Not Just “The Back”

Few areas demonstrate the importance of anatomy better than spinal surgery. A procedure may be described simply as spinal fusion or decompression with instrumentation, but the anesthesia coder needs more information.

Is the surgery cervical, thoracic, lumbar, or sacral? Is instrumentation involved? How extensive is the procedure? Which vertebral levels are involved? Does the procedure meet the requirements of a more specific anesthesia descriptor?

The phrase “back surgery” is almost meaningless from an anesthesia coding perspective. A strong coder wants to know: Where? What levels? What approach? What work was actually performed?

Example 4: “Head and Neck” Is a Very Big Neighborhood

Consider how many structures are located within the head and neck: eye, ear, nose, oral cavity, pharynx, tonsils, adenoids, salivary glands, larynx, thyroid, trachea, skull, and brain.

They are all anatomically close, but they certainly do not all map to the same anesthesia code. The coder needs to know which structure is being treated and what procedure is being performed on it.

Example 5: “Intraoral” Can Mean More Than One Thing

The oral cavity is another area where terminology matters. Procedures may involve the lips, vestibule of the mouth, tongue, floor of mouth, dentoalveolar structures, palate, uvula, tonsils, or pharynx.

Some structures may be accessed through the mouth but are not necessarily classified identically for anesthesia coding purposes.

Surgical access does not always equal anatomical classification. Just because the surgeon reaches a structure through the mouth does not mean the coder should automatically stop at the word “intraoral.” Read further. What structure is actually being treated?

Surgical Approach Can Change the Picture

Anatomy is not limited to identifying the organ. Sometimes the surgical approach is equally important. A procedure may be open, percutaneous, endoscopic, laparoscopic, transoral, transurethral, or performed through another approach.

Two procedures involving the same organ may not necessarily lead to the same anesthesia code if the anesthesia descriptors distinguish the procedures or approaches.

The diagnosis tells you what the patient has. The operative report tells you what the surgeon did about it. Anesthesia coding needs the second piece.

Anatomy Can Help You Catch Coding Errors

Anatomical knowledge does more than help you choose a code. It can also help you recognize when something does not make sense.

If the surgical procedure involves the kidney but the anesthesia code selected describes a procedure involving the lower urinary tract, stop. If the operative report describes extensive cervical spinal instrumentation but the anesthesia code appears inconsistent with the documented procedure, investigate.

Anatomy gives the coder a built-in reasonableness check. When the code and the anatomy do not seem to agree, go back to the operative report.

Learn Medical Terminology—It Is a Coding Tool

Medical terminology is not something coders learn for an exam and then forget. It is one of our most valuable daily tools.

Common roots include: nephr/o — kidney; ren/o — kidney; ureter/o — ureter; cyst/o — bladder; laryng/o — larynx; pharyng/o — pharynx; tonsill/o — tonsil; aden/o — gland; arthr/o — joint; oste/o — bone; my/o — muscle; neur/o — nerve.

Common procedural suffixes include: -otomy — incision; -ectomy — excision/removal; -plasty — repair/reconstruction; -rrhaphy — suturing/repair; -scopy — visual examination; -desis — binding or fusion.

Medical terminology allows you to break the procedure into pieces: What structure? What was done to it?

Don’t Be Afraid to Look at an Anatomy Picture

Experienced coders sometimes feel that they should already know every anatomical relationship. That is unrealistic. Medicine is enormous.

If you are unsure whether a structure is considered part of one anatomical region or another, look it up. Use an anatomy reference. Review a medical illustration. Look at the relationship between surrounding structures. Read the operative report again.

A five-minute anatomy review can prevent a coding error that gets repeated hundreds of times.

The Operative Report Is Your Anatomy Lesson

One of the best ways to improve anesthesia coding skills is to stop reading operative reports solely for procedure names. Read them anatomically.

Identify the operative site, structures exposed, structures treated, surgical approach, extent of the procedure, additional anatomical areas involved, and the final procedure actually performed.

The operative report often gives you the anatomical detail that the scheduled procedure does not.

Don’t Let the Surgical CPT Crosswalk Do All the Thinking

Crosswalks are valuable tools. They can point the coder toward potential anesthesia code choices. But a crosswalk should not replace analysis.

When multiple anesthesia codes are possible, return to the documentation. Ask: Which anesthesia descriptor best represents the procedure that was actually performed?

The operative report, anatomy, current code descriptors, official guidance, and applicable payer requirements should guide the final decision. The crosswalk helps you navigate. It should not prevent you from looking at the map.

A Simple Anatomy-First Coding Method

Step 1 — Identify the surgical procedure. What did the surgeon actually perform?

Step 2 — Identify the exact anatomical structure. Not just abdomen, arm, or head and neck. Be specific.

Step 3 — Identify the anatomical region. Determine how that structure relates to the anesthesia code categories.

Step 4 — Identify the surgical approach. Open, laparoscopic, endoscopic, percutaneous, transoral, transurethral, or another approach?

Step 5 — Review the anesthesia descriptors. Which descriptor most accurately reflects the documented procedure?

Step 6 — Verify. Review current authoritative coding resources and applicable guidance before finalizing the code.

Chart Talk: What Would You Do?

SCENARIO: The scheduled procedure states: Cystoscopy with stone removal.

A coder sees the word cystoscopy and immediately begins looking at anesthesia codes commonly associated with cystoscopic procedures. Then the operative report is reviewed. The cystoscope was used as part of the approach, but the operative work involved treatment of a stone located at the ureteropelvic junction.

Should the anesthesia code be selected simply because the procedure title says “cystoscopy”? Not necessarily.

The coder should evaluate the complete operative procedure, identify where the operative work occurred, review the applicable anesthesia descriptors, and determine which code most accurately represents the procedure performed.

The instrument used to reach the surgical site does not automatically define the anatomical site of the operative work. That is why anatomy matters.

The Difference Between a Good Coder and a Great Investigator

Anyone can search a procedure name. Strong anesthesia coders go further.

They ask: Where is it? What structure is involved? How did the surgeon get there? What exactly did the surgeon do? Does the anesthesia code descriptor match that anatomy?

When something does not make sense, they investigate. That is one of the skills that transforms anesthesia coding from code lookup into professional analysis.

Chart Talk Takeaway

The next time you are stuck between two anesthesia codes, don’t immediately search harder for the code. Go back to the anatomy.

Find the organ. Find the structure. Find the surgical site. Understand the approach. Then read the anesthesia descriptors again.

You may discover that the answer was never hidden in the codebook. It was hidden in the anatomy.

Because anesthesia coding is often an anatomy test in disguise. And the coders who understand where the surgeon is working are in a much stronger position to understand why the anesthesia code fits.

Educational Disclaimer

This article is provided for educational and informational purposes only and is not intended to constitute legal, coding, billing, reimbursement, or compliance advice or to replace official coding guidance, payer policies, organizational policies, or professional judgment. Coding decisions should be based on the complete medical record and current applicable CPT®, ASA Relative Value Guide®, ICD-10-CM, CMS, payer, and other authoritative guidance. CPT® is a registered trademark of the American Medical Association. ASA Relative Value Guide® is a publication of the American Society of Anesthesiologists.

© 2026 Chart Talk — Anesthesia Coding Conversations. All rights reserved.

I’m seeing documentation that simply states “saphenous nerve block,” and coders are automatically jumping to CPT 64450. But the name of the nerve alone does not tell the entire coding story.

The saphenous nerve is a terminal sensory branch of the femoral nerve, and the location where the nerve is approached matters when determining the appropriate CPT code.

An adductor canal/mid-thigh approach may support 64447, while a more distal saphenous nerve block at the proximal tibia or ankle may support 64450. Review the block note for the documented injection site, anatomical landmarks, technique, and ultrasound findings rather than selecting a code based solely on the block’s name.

The Tip Sheet below provides a quick visual comparison of 64447 vs. 64450 and the documentation clues that can help you make the distinction.

Want to keep it handy? A downloadable PDF version of the Tip Sheet is attached for educational and reference use.

See the anatomy. Read the approach. Code with confidence.

© 2026 Chart Talk — Anesthesia Coding Conversations. All rights reserved.

What we believe happened and what the medical record supports are not always the same thing.

Anesthesia coders develop an impressive ability to read between the lines.

After reviewing hundreds or thousands of anesthesia records, operative reports, procedure notes, and medication records, experienced coders begin to recognize patterns. We often know what probably happened before we finish reviewing the record.

But there is an important line that every coder, auditor, and compliance professional must remember:

Clinical probability is not the same thing as documentation support.

A service may have almost certainly occurred. A clinical circumstance may appear obvious. A procedure may typically require a particular intervention. But coding cannot be based solely on what normally happens, what probably happened, or what we believe the provider intended.

The medical record must support what is ultimately reported.

The Coder’s Dilemma: “I Know What They Did”

Consider this situation:

You are reviewing an anesthesia record and see evidence suggesting that an arterial line was used during the procedure.

The monitoring data are present. The arterial pressure values are documented throughout the case. Perhaps the operative circumstances make placement of an arterial catheter completely reasonable.

But you cannot locate adequate documentation of the arterial line insertion.

The temptation may be to conclude:

“Obviously, they placed an A-line.”

Clinically, that conclusion may be reasonable.

From a coding and auditing perspective, however, another question must be asked:

Where is the documentation supporting the separately reportable service?

Knowing that something probably occurred is different from having documentation sufficient to support reporting it.

That distinction is at the heart of compliant anesthesia coding.

Documentation Is the Bridge Between Clinical Care and Coding

Coders do not determine what happened clinically.

Providers document what happened clinically, and coders translate that documentation into reportable codes.

That means documentation serves as the bridge between the clinical service and the claim.

When that bridge is incomplete, the coder should be cautious about filling the gap with assumptions.

This becomes especially important in anesthesia because a single record may contain information from multiple sources:

• The anesthesia record
• Pre-anesthesia evaluation
• Post-anesthesia evaluation
• Operative report
• Procedure notes
• Medication administration record
• Nursing documentation
• Device information
• Monitoring data
• Electronic timestamps

These pieces may help us understand the clinical picture, but they do not automatically make every service separately reportable.

The question is not simply: “Is there evidence this happened?” The stronger coding question is: “Does the documentation meet the requirements necessary to support reporting this service?”

Five Common Places Where Assumption Can Become a Coding Risk

1. Invasive Lines

Arterial lines and central venous catheters are excellent examples.

A coder may see monitoring information throughout the anesthesia record that strongly suggests an invasive line was present.

But presence of the line does not necessarily establish who inserted it, when it was inserted, whether the anesthesia provider personally performed the service, or whether the documentation supports separate reporting.

Before assigning a separately reportable procedure, the coder should identify the documentation supporting the service.

Coding lesson: Evidence that a device was used is not automatically documentation that a particular provider performed a separately billable insertion.

2. Ultrasound Guidance

Another common assumption involves ultrasound guidance.

Perhaps the procedure is one for which ultrasound guidance is commonly used. Maybe the provider documents identifying anatomy or visualizing structures.

That does not mean the coder should automatically report ultrasound guidance.

When a separately reportable ultrasound-guidance service has specific documentation requirements, those requirements must be supported in the medical record.

The correct question is not: “Would ultrasound normally be used for this procedure?” It is: “Does the documentation support the requirements for reporting ultrasound guidance?”

3. Qualifying Circumstances

Anesthesia coders may encounter cases where the clinical situation appears to fit a qualifying circumstance.

For example, a case may appear extremely urgent.

Everyone reviewing the record may agree that the situation sounds emergent.

But coding should not automatically convert clinical urgency into a reportable qualifying circumstance without evaluating the applicable code requirements and documentation.

A coder should distinguish between clinically urgent and meeting the definition and documentation requirements of a reportable qualifying circumstance. Those concepts may overlap, but they are not automatically interchangeable.

4. Medical Direction

Medical direction may be one of the most important areas where assumption creates compliance risk.

A record may clearly show that an anesthesiologist and CRNA were involved in the case.

But participation alone does not establish that all requirements for medical direction were satisfied.

The coder must evaluate the documentation supporting the applicable medical-direction requirements rather than assuming: “The anesthesiologist was involved, so this must be medically directed.”

The documentation must tell the story.

If an organization reports a medical-direction modifier, the record should support the requirements associated with that reporting.

This is why medical-direction auditing cannot simply be a modifier review. It must be a documentation review.

5. Anesthesia Time

Perhaps nowhere is assumption more dangerous than anesthesia time.

Imagine that the anesthesia start time is clearly documented, but the end time is missing.

The PACU record begins at 10:42.

Can the coder simply use 10:42 as the anesthesia end time? Not necessarily.

The surrounding documentation may provide useful information when investigating the record, but coders should not create anesthesia time based solely on what seems logical.

The appropriate response may be to review the complete record and, when necessary and permitted by organizational policy, obtain clarification or corrected documentation from the provider.

A missing time should not quietly become an estimated time simply because the estimate appears reasonable.

“But It’s Obvious” Is Not a Coding Guideline

Experienced coders often recognize clinical patterns. That expertise is valuable.

It helps us identify documentation inconsistencies, recognize potential missed services, know when additional review is necessary, and formulate appropriate provider education.

But experience should make us better investigators—not more comfortable making unsupported assumptions.

When something appears obvious but is not adequately documented, that should trigger a question: “Is documentation missing?” Not an assumption: “I know what they meant.”

That small shift in thinking can significantly strengthen coding compliance.

Missing Documentation Does Not Always Mean the Service Did Not Occur

This distinction is equally important.

If the documentation does not support reporting a service, that does not necessarily mean the service was not performed. It may mean the documentation is incomplete.

That creates an opportunity for education.

For example, suppose anesthesia providers routinely perform arterial line insertions but frequently document only: “Left radial A-line placed.”

The solution should not simply be to decide whether the coder can “get away with” reporting the service.

The larger question is: Why is the documentation consistently incomplete, and how can the organization improve it?

That is where coding becomes more than code assignment. It becomes documentation improvement, compliance, auditing, and education.

Coders Should Not Fill Documentation Gaps—They Should Identify Them

A strong anesthesia coder does not merely ask: “What code can I assign?” The coder also asks: “What documentation supports my decision?”

When the answer is unclear, several possibilities exist. The record may require additional review. Another portion of the medical record may contain the necessary documentation. The service may not be separately reportable. A provider clarification may be appropriate under organizational policies. Or the documentation pattern may reveal a larger educational opportunity.

The coder’s role is not to manufacture documentation that should have been there. The coder’s role is to recognize when the documentation does not support the conclusion being considered.

A Simple Three-Question Test

1. What exactly am I reporting?
Identify the specific procedure, circumstance, modifier, time, or service.

2. What documentation supports it?
Be able to point to the portion of the medical record supporting the coding decision.

3. Am I coding what is documented—or what I believe happened?
If the answer is, “I’m pretty sure that’s what the provider did,” you may need to look again.

Turn Uncertainty Into Education

Repeated documentation problems should not remain individual coding problems. They should become educational opportunities.

If coders repeatedly encounter missing arterial-line documentation, educate providers about the documentation elements needed to support reporting the service.

If qualifying circumstances are frequently unclear, develop education explaining the applicable definitions and documentation expectations.

If anesthesia times are repeatedly incomplete, identify the workflow causing records to remain open or incomplete.

If medical-direction documentation is inconsistent, perform a focused audit before the issue becomes a larger compliance concern.

Patterns matter. One incomplete record may require clarification. Fifty incomplete records may indicate a process problem.

The Auditor’s Perspective

Could someone unfamiliar with this case reach the same coding conclusion by reviewing the documentation?

That is a useful standard.

Imagine that the claim is reviewed months or years later. The reviewer was not in the operating room. They do not know the anesthesia provider. They cannot rely on what “usually happens” at that facility. They have the documentation.

Would the record independently support the reported service?

If the answer depends heavily on assumptions, the claim deserves another look.

The Bottom Line

Anesthesia coding requires clinical knowledge.

We need to understand anatomy, procedures, anesthesia techniques, medical direction, invasive monitoring, anesthesia time, qualifying circumstances, and the relationship between the surgical procedure and the anesthesia service.

But clinical knowledge should help us interpret documentation—not replace it.

There is an important difference between: “This probably happened.” and “This record supports reporting that it happened.”

The first is clinical probability. The second is coding support. And when a claim is submitted, documentation support is what matters.

Educational Disclaimer

This article is provided for educational and informational purposes only and is not intended to replace official coding guidance, payer policies, organizational policies, or professional judgment. Coding and billing decisions should be based on the complete medical record and current applicable CPT®, ICD-10-CM, CMS, payer, and other authoritative guidance.

© 2026 Chart Talk — Anesthesia Coding Conversations. All rights reserved.

One of the things I’ve learned during my journey in anesthesia coding is that no matter how many years of experience we have, there is always something that makes us pause and ask ourselves…

“Am I making the right coding decision?”

Anesthesia coding is unlike many other specialties. We aren’t simply assigning CPT® or ICD-10-CM codes—we’re interpreting documentation, understanding anesthesia techniques, evaluating medical direction requirements, identifying separately reportable services, and applying guidelines that often require careful analysis.

Even experienced coders and auditors can encounter cases that leave us questioning ourselves.

So that got me thinking…

If You Could Have ONE Resource…

If there was one resource that would make you feel more confident in your coding decisions, what would it be?

Would it be:

• A comprehensive ASA code reference guide with real-world examples?
• Documentation checklists by specialty?
• Operative report examples with step-by-step code selection?
• Medical direction decision trees?
• Modifier reference guides?
• Case studies that explain why a particular code was selected?
• Specialty-specific quick reference sheets?
• Something else entirely?

I’d genuinely love to know.

For Those New to Anesthesia Coding…

If you’re just entering the world of anesthesia coding, your perspective is equally important.

What would have made—or would make—your transition easier?

Maybe it’s:

• A structured learning roadmap.
• A beginner-friendly anesthesia coding manual.
• Weekly case studies.
• Anatomy and surgical procedure overviews.
• Recorded walkthroughs of actual anesthesia records.
• Common mistakes to avoid.
• A mentor to answer those “Is this right?” questions.
• A place where no question feels too small.

Learning anesthesia coding can feel overwhelming at first because there are so many moving pieces. The right educational tools can make all the difference between simply memorizing codes and truly understanding why those codes are correct.

Why I’m Asking

As many of you know, Chart Talk – Anesthesia Coding Conversations has grown from an idea into something much bigger than I ever imagined.

My goal has always been simple:

To create practical, real-world education that helps anesthesia coders feel more confident every time they review a record.

I’m continually developing new educational materials, quick-reference guides, coding examples, webinars, and training resources, but I want those resources to solve the challenges that you face every day—not just the ones I think are important.

Your feedback will help shape future content and ensure it provides real value to our anesthesia coding community.

Join the Conversation

I’d love to hear from you.

What’s the one resource you wish you had as an anesthesia coder or auditor?

Or…

If you’re new to anesthesia coding, what would have made your learning experience easier?

Drop your thoughts in the comments. There are no wrong answers, and your idea may inspire a resource that helps hundreds of other coders.

After all, the best educational tools are often created by listening to the people who use them every day.

I’m excited to hear your ideas and continue building resources that make anesthesia coding a little less intimidating—and a lot more rewarding.

Let’s start the conversation!

Understanding Hypothermic Circulatory Arrest and Correct Cardiac Anesthesia Code Selection

Don’t Leave Base Units on the Table

Cardiac anesthesia coding is one of the most specialized areas of anesthesia coding, and one of the most common opportunities identified during audits is the undercoding of ASA 00563.

Many coders automatically assign ASA 00562 whenever cardiopulmonary bypass (pump oxygenator) is documented. However, not every cardiac procedure performed with cardiopulmonary bypass is coded the same. One of the most important distinctions is whether hypothermic circulatory arrest (HCA) was performed.

Just as importantly, the anesthesia record should also support this service. The anesthesia record frequently documents systemic cooling, the period of circulatory arrest, target temperature, cerebral perfusion techniques, and other details that confirm the use of hypothermic circulatory arrest. Reviewing both the operative report and the anesthesia record helps ensure accurate ASA code selection.

Understanding the Difference

ASA 00561 – Anesthesia for procedures on heart, pericardial sac, and great vessels of chest; with pump oxygenator, younger than 1 year of age.

ASA 00562 – Anesthesia for procedures on heart, pericardial sac, and great vessels of chest; with pump oxygenator, age 1 year or older, for all noncoronary bypass procedures (e.g., valve procedures) or for re-operation for coronary bypass more than 1 month after original operation.

ASA 00563 – Anesthesia for procedures on heart, pericardial sac, and great vessels of chest; with pump oxygenator with hypothermic circulatory arrest.

Why Is ASA 00563 Commonly Undercoded?

Many coders stop reading once they identify documentation of cardiopulmonary bypass (pump oxygenator) and immediately assign ASA 00562. Unfortunately, this can result in missed reimbursement when documentation later confirms that hypothermic circulatory arrest was performed.

Always continue reviewing both the operative report and the anesthesia record before assigning the anesthesia code.

Documentation Clues to Look For

Operative Report

• Hypothermic circulatory arrest (HCA)
• Deep hypothermic circulatory arrest (DHCA)
• Systemic cooling
• Total circulatory arrest
• Antegrade cerebral perfusion
• Retrograde cerebral perfusion
• Aortic arch reconstruction
• Hemiarch replacement
• Ascending aortic replacement
• Complex thoracic aortic repair

Anesthesia Record

• Initiation of cardiopulmonary bypass
• Cooling to target temperature
• Hypothermic/deep hypothermic circulatory arrest
• Duration of circulatory arrest
• Antegrade or retrograde cerebral perfusion
• Rewarming following circulatory arrest
• Perfusion events documented by the anesthesia team

Coding Tip: Always compare the anesthesia record with the surgeon’s operative report. The anesthesia record often provides additional evidence that hypothermic circulatory arrest occurred.

Coding Example

Procedure Performed:

• Ascending aortic aneurysm repair
• Hemiarch replacement
• Cardiopulmonary bypass
• Deep hypothermic circulatory arrest
• Antegrade cerebral perfusion

Incorrect Coding: ASA 00562

Correct Coding: ASA 00563

Why? The documentation clearly supports the use of deep hypothermic circulatory arrest, which is specifically described by ASA 00563.

Auditor’s Tip

Don’t stop reading after identifying cardiopulmonary bypass. Review both the operative report and the anesthesia record for hypothermic circulatory arrest, cerebral perfusion, systemic cooling and rewarming, duration of circulatory arrest, and complex aortic reconstruction before assigning the anesthesia code.

The surgeon tells you what was repaired. The anesthesia record tells you how the patient was managed. Reviewing both records is essential to distinguish ASA 00562 from ASA 00563 and ensure accurate cardiac anesthesia coding.

Have you encountered cases where 00563 was missed? Share your experiences or questions in the comments. I’d love to continue the conversation.

Hey everyone!

The August edition of AAPC The Magazine is officially out, and I’m excited to share that my article is featured on page 52!

If you’re interested in learning more about my journey into anesthesia coding and reading my perspective on some of the unique nuances that make anesthesia coding such a fascinating specialty, I’d love for you to check it out.

Writing this article gave me the opportunity to reflect on how far this journey has taken me—from learning the specialty to educating others, speaking at local AAPC chapters, and now having the privilege of sharing my experiences with the broader coding community. It’s been an incredibly rewarding experience, and I’m grateful for everyone who has supported me along the way.

Thank you to AAPC The Magazine for the opportunity to contribute, and thank you to all of you who continue to encourage and support Chart Talk ~ Anesthesia Coding Conversations ~. Your support means more than you know.

If you read the article, I’d love to hear what you think!

📖 August AAPC The Magazine
📄 My article: Page 52

Happy reading!

Don’t Leave Base Units on the Table

One of the most common opportunities I encounter during anesthesia coding audits is the undercoding of ASA 00670. Too often, coders default to ASA 00630 for spinal procedures without taking a closer look at the operative report. While 00630 is appropriate for many lumbar spine surgeries, it is not always the correct choice—especially when spinal instrumentation or extensive spinal reconstruction is involved.

A few extra minutes reviewing the operative report can make the difference between selecting the correct anesthesia code and leaving appropriate reimbursement on the table.

Understanding the Difference

ASA 00630

Anesthesia for procedures in the lumbar region; not otherwise specified

Typically reported for:

• Lumbar laminectomy
• Lumbar discectomy
• Simple decompression procedures
• Procedures without extensive instrumentation

ASA 00670

Anesthesia for extensive spine and spinal cord procedures (e.g., instrumentation or vascular procedures)

Frequently appropriate for:

• Posterior spinal fusion
• Transforaminal Lumbar Interbody Fusion (TLIF)
• Posterior Lumbar Interbody Fusion (PLIF)
• Anterior Lumbar Interbody Fusion (ALIF)
• Multi-level spinal fusion
• Pedicle screw fixation
• Placement of rods, cages, or plates
• Extensive spinal reconstruction

The RVG Comment Many Coders Miss

One of the most important pieces of guidance for ASA 00670 is found in the ASA Relative Value Guide (RVG).

RVG Comment:
Code 00670 is appropriate only if the surgical procedure includes segmental or non-segmental instrumentation as defined in CPT® or if the procedure includes multiple vertebral segments (minimum three vertebral bodies with the two associated interspaces).

This comment is critical because not every spinal fusion qualifies for 00670. Simply performing a lumbar fusion does not automatically support reporting ASA 00670.

Instead, the operative report must document one of the following:

Option 1

Segmental or non-segmental spinal instrumentation as defined by CPT®, such as:

• Pedicle screw systems
• Rod fixation
• Plates
• Hooks
• Interbody cages when part of instrumented fusion
• Other internal fixation devices used to stabilize the spine

OR

Option 2

The procedure involves multiple vertebral segments, defined in the RVG as:

A minimum of three vertebral bodies with the two associated interspaces.

What Does “Three Vertebral Bodies with Two Associated Interspaces” Mean?

Why Is 00670 Commonly Undercoded?

Many anesthesia coders develop the habit of assigning 00630 whenever they see a lumbar spine procedure. Unfortunately, the operative report often contains additional details that support 00670, but those details may be overlooked.

Common reasons include:

• Reviewing only the procedure title
• Not reading the body of the operative report
• Missing documentation of spinal instrumentation
• Assuming every lumbar fusion uses the same anesthesia code
• Relying solely on the surgical CPT code without analyzing the operative details
• Not being familiar with the RVG comment for ASA 00670

Documentation Clues to Look For

When reviewing the operative report, watch for terms such as:

✔ Pedicle screw instrumentation

✔ Segmental instrumentation

✔ Non-segmental instrumentation

✔ Rod fixation

✔ Interbody cage placement

✔ Posterior spinal fusion

✔ Anterior spinal fusion

✔ Multi-level fusion

✔ Spinal reconstruction

✔ Three or more vertebral bodies involved

These findings should prompt you to evaluate whether ASA 00670 is appropriate.

Coding Example

Clinical Scenario

Procedure Performed

• L4-L5 Transforaminal Lumbar Interbody Fusion (TLIF)
• Posterior spinal fusion
• Pedicle screw instrumentation
• Interbody cage placement
• Fluoroscopic guidance

Incorrect Coding

ASA 00630

The coder selected 00630 simply because the procedure involved the lumbar spine.

Correct Coding

ASA 00670

The operative report documents spinal instrumentation, making 00670 the more appropriate anesthesia code based on the RVG guidance.

Auditor’s Tip

Never determine the anesthesia code from the procedure title alone.

Instead, ask yourself:

• Was instrumentation placed?
• Was the instrumentation segmental or non-segmental?
• Were pedicle screws, rods, cages, or plates implanted?
• Does the procedure involve at least three vertebral bodies with two associated interspaces?
• Does the operative report describe spinal reconstruction rather than simple decompression?

If the answer to any of these questions is yes, pause before assigning 00630 and evaluate whether 00670 is supported by the documentation and RVG guidance.

Documentation Matters

Accurate anesthesia coding depends on understanding what actually occurred during the procedure—not simply matching the surgical CPT code to the first anesthesia code that appears in a crosswalk.

Developing the habit of reviewing the entire operative report helps ensure:

• Accurate reimbursement
• Consistent coding
• Reduced audit risk
• Stronger compliance
• Appropriate application of RVG guidance

Final Thoughts

ASA 00670 is one of the most frequently undercoded anesthesia codes because the documentation supporting it is often found within the details of the operative report—not the procedure title.

Just as importantly, coders should remember that 00670 is not automatically assigned for every spinal fusion. The ASA Relative Value Guide clearly limits its use to procedures that include segmental or non-segmental instrumentation or multiple vertebral segments involving a minimum of three vertebral bodies with two associated interspaces.

Understanding and applying this RVG guidance can improve coding accuracy, reduce audit risk, and help ensure your organization reports the most appropriate anesthesia code.

Have you encountered cases where 00670 was missed—or perhaps reported when the RVG criteria were not met? Share your experiences or questions in the comments. I’d love to continue the conversation.