Glossary · Coding

Anesthesia modifier

An anesthesia modifier is a two-character HCPCS or CPT modifier appended to an anesthesia procedure code (CPT 00100–01999) that identifies who performed the anesthesia service, under what supervisory arrangement, and the type of anesthesia care delivered — information payers require before processing the claim.

Verified May 8, 2026 · 8 sources ↓

Drawn from NovitasEmblemhealthAsahqCMSDol

Definition

Source · Editorial summary grounded in 8 cited references ↓

Anesthesia modifiers fall into two functional buckets: payment modifiers and informational modifiers. Payment modifiers (AA, QK, AD, QY, QX, QZ) directly determine reimbursement rates by telling the payer whether an anesthesiologist personally performed the case, medically directed one to four concurrent cases, supervised more than four concurrent cases, or whether a CRNA worked with or without physician direction. Because these modifiers are mutually exclusive on a single claim line, submitting more than one pricing modifier triggers an automatic denial. Informational modifiers (QS, G8, G9) describe monitored anesthesia care scenarios; physical status modifiers (P1–P6) convey patient acuity at the time of service but carry no separate RVU weight under Medicare.

Placement order matters as much as modifier selection. Medicare and most commercial payers require the pricing modifier to occupy the first modifier field. If QS applies, it goes in the second field. When medical direction is involved, the direction modifier leads, followed by any additional modifiers. Violating this sequencing can cause claim edits to fire even when every individual modifier is technically correct.

The National Correct Coding Initiative (NCCI) Chapter 2 governs which services are bundled into the anesthesia global and therefore cannot be billed alongside an anesthesia code — regardless of modifier use. Modifiers 59, XE, or XU can unbundle genuinely separate encounters (e.g., a peripheral nerve block placed solely for postoperative pain after the anesthesia care period ends), but those modifiers do not override bundling for services that are integral to the anesthetic itself.

Why it matters

Missing or incorrect anesthesia modifiers are among the top reasons anesthesia claims are denied outright. A claim submitted without any pricing modifier (AA, QK, QY, QX, QZ, or AD) will be rejected as a billing error, requiring a corrected claim and delaying payment. Beyond denials, using the wrong modifier can trigger post-payment audits: billing AA when the physician was actually directing two concurrent cases overstates the personal-performance reimbursement rate, which CMS and commercial payers treat as a compliance risk. For orthopedic practices that employ or supervise CRNAs in ambulatory surgery settings, the distinction between QY (directing one CRNA) and QK (directing two to four concurrent cases) changes the reimbursement multiplier — typically 50% of the allowed amount per provider — and must accurately reflect the real-time supervision arrangement documented in the medical record.

Common mistakes

Where people most often go wrong with this concept.

Source · Editorial brief grounded in cited references ↓

Appending two pricing modifiers (e.g., AA and QK) on the same claim line — these are mutually exclusive and the claim will deny.
Placing QS in the first modifier field instead of the second, which can cause claim edits to fire even when the underlying service is payable.
Using modifier AA when the anesthesiologist was medically directing a CRNA rather than personally performing the case — this overstates the level of involvement and creates audit exposure.
Omitting the pricing modifier entirely when billing under CPT codes 00100–01999, which results in automatic denial as a billing error.
Billing modifier QK (2–4 concurrent cases) when the physician was simultaneously performing a non-anesthesia medical or surgical service, which instead triggers modifier AD and a reduced flat payment of three base units per procedure.
Failing to append G8 or G9 when a MAC case qualifies — missing these informational modifiers can result in downcoding or additional documentation requests from payers using LCD L35049.
Applying modifier 59 or XU to unbundle a service (e.g., epidural injection) that was integral to intraoperative anesthesia management rather than a distinct postoperative pain service.

Related codes

Codes commonly involved when this concept appears in practice.

Modifiers

59 Distinct procedural service

Frequently asked questions

Source · Generated from the editorial pipeline, verified against 8 cited references ↓

01What happens if I submit an anesthesia claim without any pricing modifier?

The claim will be denied as a billing error. You must submit a corrected claim with the appropriate pricing modifier (AA, QY, QK, QX, QZ, or AD) before the payer will process it.

02Can an orthopedic surgeon bill an anesthesia modifier for anesthesia they personally administered during their own procedure?

Generally no. CMS Anesthesia Rules prohibit separate payment for anesthesia services when provided by the same physician performing the surgical procedure. The anesthesia payment is considered included in the surgical fee.

03What is the difference between QY and QK?

QY applies when an anesthesiologist medically directs exactly one CRNA in a single concurrent case. QK applies when the anesthesiologist is directing two, three, or four concurrent cases involving CRNAs or anesthesiologist assistants. Both typically reimburse each provider at 50% of the applicable fee schedule amount.

04Do physical status modifiers (P1–P6) affect Medicare reimbursement?

No. Under Medicare, physical status modifiers are informational only and do not add units or change the allowed amount. Some commercial payers may treat them differently, so verify payer-specific rules.

05When is modifier G9 appropriate for an orthopedic anesthesia case?

G9 is appended to an anesthesia code when MAC is provided and the patient has a documented history of a severe cardiopulmonary condition. It works alongside QS and must be supported by medical record documentation of that history.

06Can modifier 59 be used to separately bill an epidural placed during orthopedic surgery?

Only if the epidural was placed exclusively for postoperative pain management after the anesthesia care period ended, and only when the operating physician separately requested it. An epidural that also provided intraoperative pain control is bundled into the anesthesia code and cannot be unbundled with modifier 59 or XU.

Sources & references

Editorial content was developed using the following public sources. Last verified May 8, 2026.

Mira AI Scribe

Mira's documentation layer monitors operative and pre-anesthesia notes for signals that determine which anesthesia modifier is appropriate before a claim is generated. Specifically, Mira looks for: (1) attestation language confirming the anesthesiologist was physically present and personally performed the entire anesthetic — required to support modifier AA; (2) documentation of the seven CMS medical-direction criteria (pre-anesthesia evaluation, presence at induction and emergence, monitoring, approval of the anesthesia plan, immediate availability, and post-anesthesia evaluation) when the physician directed one to four CRNA or AA cases — required for QY or QK; (3) concurrent case count at the time of service to distinguish QK from AD; and (4) MAC-qualifying language (deep or markedly invasive procedure, or documented severe cardiopulmonary history) to flag G8 or G9 alongside QS. When documentation gaps are detected — for example, no attestation of presence at induction in a QK case — Mira surfaces an inline alert requesting the missing element before the note is finalized, reducing the likelihood of a corrected-claim cycle. Modifier placement order (pricing modifier first, QS second) is enforced automatically at claim generation. Mira does not select a physical status modifier autonomously; it surfaces the documented ASA-PS from the anesthesia pre-op assessment and prompts the coder to confirm the corresponding P-modifier.

See Mira's approach