← Back to blog

Modifier 22 Documentation: What Payers Need to See

October 25, 2026
Modifier 22 Documentation: What Payers Need to See

Modifier 22 documentation has one job: prove that your surgeon's work was substantially greater than what the CPT code normally describes. The proof belongs in the operative report, in specific and measurable terms. A claim that says only "difficult case" will not get paid.

This guide shows you when to use the modifier, what to write, what to leave out, and how to check each claim before it goes out. It is written for practice administrators, coders and HIM staff in independent physician groups.

Himshield
Catch Documentation Risks Before Submission
HIMShield helps independent physician practices identify coding, documentation, and charge-capture risks with automated detection and physician-friendly guidance.
Visit Himshield

TL;DR

  • Modifier 22 is for surgical codes with a 0-, 10- or 90-day global period. It does not belong on E/M, anesthesia, radiology or pathology codes.
  • The operative report must explain why the case was extraordinary, and quantify the extra time and effort against the typical procedure.
  • Generalized statements such as "difficult surgery" or "obese patient" are the classic reasons for denial.
  • The modifier never guarantees extra payment. Payers can review the record every time, and some pay only a fixed percentage of the allowance.
  • Check each modifier 22 claim before submission, because it is far cheaper to fix a note than to appeal a denial.

Table of Contents

When modifier 22 applies

CPT describes modifier 22 as increased procedural services. The Medicare Claims Processing Manual explains the logic: fees represent the average work effort for a procedure, and an adjustment is only warranted in unusual circumstances, after review of the medical records. Medicare treats this as an infrequent event.

Three tests decide whether you have a legitimate case.

The code must be a surgical code with a global period

Noridian's modifier 22 guidance says to report it with surgical procedure codes that have a 0-, 10- or 90-day global period, and not to append it to an evaluation and management service. Look up the global indicator before you add the modifier. If the code has no global period, stop.

The work must be substantially greater, not just harder

The AAPC knowledge center makes the point plainly: difficulty alone does not justify the modifier, and only rare outlying cases qualify. The question is whether the work falls well outside the range the code already assumes. A surgeon who operates on a hard case every week has not found an exception. The code's value already reflects a spread of difficulty.

The cause must be clinical, not logistical

Blue Cross and Blue Shield of Illinois reimbursement policy RP013 (effective April 10, 2026) is a useful example of how commercial payers read this. Extra time caused by the surgeon's choice of approach, equipment failure or scheduling is not a basis for the modifier. What counts is something about the patient or the anatomy that changed the work.

Typical legitimate reasons include:

  • Dense adhesions or extensive scar tissue from prior surgery
  • Anatomic distortion, anomalies or trauma
  • Severe, documented obesity that changed the technique
  • Unexpected bleeding or tissue conditions that required significant extra dissection

Noridian lists the types of reasons it expects to see: increased intensity, time, technical difficulty, severity of the patient's condition, and physical and mental effort required.

What the operative report must contain

The modifier is only as strong as the note behind it. Four elements make a note defensible.

1. A clear reason for the extra work

Name the condition that created the difficulty. "Dense adhesions between the sigmoid colon and the anterior abdominal wall from two prior laparotomies" is a reason. "Adhesions were present" is a description. Documenting the specific pathological or anatomical interference, not just the difficulty, is what separates a paid claim from a rejected one, according to AAPC's modifier guidance.

2. A quantified comparison to the typical procedure

Payers want numbers: how long the step took, how much longer than usual, how many additional instruments or assistants were needed. The AAPC guidance says the documentation should compare the effort to what is typical for the procedure. Time alone is not enough, but time tied to a cause is persuasive.

3. The explanation inside the operative report

Put the explanation in the operative report itself. A separate letter can accompany it, but it cannot replace it. Noridian asks for a separate paragraph titled "Unusual Procedure" within the documentation. That heading makes the reviewer's job easy and signals that the physician planned the explanation, rather than adding it later.

4. Consistency across the record

The anesthesia record, nursing notes, operative times and the surgeon's report should tell the same story. A reviewer who sees a note claiming two extra hours next to an anesthesia record showing a routine duration will deny the claim. Check that the times line up before you bill.

Weak versus strong documentation

Noridian explicitly lists three generalized statements as incorrect use: the surgery took an extra two hours, it was a difficult surgery, and the patient was obese. The table shows how to turn each into something a reviewer can verify.

Weak statementWhy it failsStronger version
"Surgery was difficult."Conclusion without a cause or measure"Dense pelvic adhesions required 55 minutes of sharp dissection before the target structure was visible. This step typically takes about 10 minutes."
"Patient was obese."A diagnosis, not a description of added work"BMI 52. Abdominal wall thickness required extended retractors and a second assistant. Closure took roughly twice the usual time."
"Took an extra two hours."No reason for the time"Procedure time was 3 hours 40 minutes against a typical 1 hour 45 minutes. Causes: prior radiation fibrosis, distorted planes, and a 400 mL bleed controlled before proceeding."
"Complex case."Subjective"Anatomy distorted by prior mesh repair. Mesh excision was required before the planned procedure could begin."

The numbers in the stronger versions are illustrative examples of the level of detail to aim for. Your surgeon must record the facts of the actual case, never copy a template figure.

There is a second reason to write descriptively. According to an AMA Council on Medical Service report, payers and their systems increasingly screen modifier use. Conclusory entries are more likely to be flagged and denied. Descriptive EHR templates help the surgeon get the detail in at the time of surgery, when memory is fresh.

Weak versus strong documentation — overview diagram

A pre-bill checklist for every modifier 22 claim

The steps below take a coder or HIM reviewer a few minutes per claim. They fit in any workflow.

  1. Confirm the code. Check that it is a surgical code with a 0-, 10- or 90-day global period.
  2. Read the operative report first, not the charge. Look for the specific cause of the extra work. If you cannot find it in two minutes, a reviewer will not find it either.
  3. Look for quantification. Find the actual times, blood loss, extra instruments or extra staff. Compare them with the typical procedure.
  4. Rule out the excluded causes. Equipment failure, approach choice and scheduling delays do not qualify.
  5. Query the surgeon if the note is thin. A compliant addendum, dated and signed as an addendum, is acceptable. Rewriting the original note after the fact is not.
  6. Raise the charge. The BCBSIL policy says to increase the charge for the unusual procedure, not bill the standard amount with the modifier.
  7. Attach the record per payer instructions. Some payers want it with the claim, and others ask for it on request.
  8. Log the claim. Track outcomes by payer so you know where the modifier pays and where it does not.

Payers do not all treat modifier 22 the same way

This is where practices lose money without noticing. The modifier is a request, and each payer decides what to do with it.

  • Medicare Part B. Medicare contractors review the record against the criteria above. Noridian states that additional documentation is no longer requested after the claim, so the explanation must go in with the claim. If you appeal, include a separate, concise statement of the substantial additional work.
  • Commercial payers. BCBSIL's policy says the payer reserves the right to review the operative report whenever the modifier is used, and appending it does not guarantee additional reimbursement.
  • Fixed-percentage policies. Horizon NJ Health's policy, last reviewed May 28, 2026, says it reimburses eligible modifier 22 codes at 18% of the normal allowance when its criteria are met. Policies like this change what a successful claim is worth, so the extra work has to justify the effort of documenting and appealing.

Read each major payer's current reimbursement policy and keep a one-page summary at the coding desk. Policies are revised, and an old summary will cause denials.

The mistakes we see most often

  • Using it for E/M or non-surgical codes. This is outside the modifier's scope and tells an auditor that coding controls are weak. Horizon NJ Health's policy, for example, pays non-surgical codes with the modifier at the normal allowance.
  • Treating "long" as "complex." Duration without a cause is the first thing reviewers reject.
  • Billing the standard charge. If the charge does not change, there is nothing for the payer to adjust.
  • Adding the modifier at the billing stage. A biller who sees a long operative time and adds a 22 is guessing. The decision belongs with the coder and surgeon, from the note.
  • Skipping the follow-up. Denials for this modifier often need a short, focused appeal. Without one, the practice writes the revenue off.
  • Under-using it out of fear. Some physicians avoid the modifier entirely because they worry about audits. The AMA says that when a significant service is fully documented, it should be billed. Good documentation is the protection, and silence costs you earned revenue.

For a wider view of how modifiers are used and misused across a physician practice, see our guide to modifier usage in physician billing. If you also work with E/M plus procedure claims, our piece on modifier 25 documentation covers the other modifier auditors look at closely.

Our perspective: modifier 22 is a documentation problem, not a coding problem

We look at EHR data from independent practices, and the pattern is consistent. The surgeon did the extra work. The note did not record it. The coder had nothing to support the modifier, so the claim went out at the base level, and the practice never knew what it missed.

That is revenue leakage in its plainest form. It does not show up as a denial. It shows up as a claim that was paid correctly for what the record said.

There is also the opposite failure. A claim carries modifier 22 with a one-line justification, and an automated screen or reviewer denies it. The practice spends staff hours on an appeal it was always likely to lose.

Both failures have one fix: the right detail, captured at the time of the procedure, in the operative report. We think practices should do three things:

  1. Build an "Unusual Procedure" prompt into surgical note templates, so the surgeon is asked for cause, quantity and comparison.
  2. Review modifier 22 claims before submission, not after denial.
  3. Track modifier 22 results by provider and payer, so you can see which claims are paid and which are not.

This does not require new staff. It requires visibility into the records you already have. Our platform is built to scan EHR data before claims go out, flag where documentation does not support what was billed, and surface cases where it supports more than what was billed.

— Elena

How we help practices catch these gaps

If you want to know how many surgical claims in your practice are under-documented, over-coded or missing a supportable modifier, start with the free 30-day Revenue Leakage Audit. It looks at your EHR data, quantifies coding, documentation and charge-capture gaps, and reports them by provider and payer. You can see how HIMShield works before you decide.

Documentation quality matters well beyond modifier 22. Our guide to medical necessity documentation examples shows the same principle at work in everyday E/M notes.

FAQ

When should I use modifier 22?

Use it on a surgical code with a 0-, 10- or 90-day global period when the physician's work was substantially greater than typical because of a specific clinical factor. Examples are dense scar tissue, distorted anatomy or trauma. Document the cause and quantify the extra effort in the operative report. If the case was merely hard, do not use it.

Can I add modifier 22 to an E/M code?

No. Noridian's guidance says it should not be appended to an evaluation and management service. Other payers treat non-surgical codes the same way. If an E/M visit involved unusually high effort, look to the E/M documentation rules instead.

Does modifier 22 guarantee higher payment?

No. BCBSIL's policy says appending it does not guarantee additional reimbursement, and the payer may review the operative report each time. Some payers set a fixed percentage of the allowance. Check each payer's current policy.

Is a separate letter enough to support the modifier?

No. The explanation should be in the operative report itself. A concise cover statement can help the reviewer, and Noridian asks for one with appeals, but it supports the record and does not replace it.

Can the surgeon add detail after the claim is denied?

Only through a proper, dated and signed addendum that reflects what actually happened. The surgeon must never alter the original note to fit the claim. If you are unsure, ask your compliance officer or healthcare counsel before changing any record.

Sources