Modifier 22 is often used to capture cases that required increased procedural services, but a key question remains: do your claims truly support it—and is it worth the effort?
What Payors Expect
To justify modifier 22, documentation must go beyond stating that a case was “complex.” Most payors expect:
- A clear, detailed explanation of how the procedure differed from the standard approach
- Specific factors contributing to the increased difficulty (e.g., anatomical challenges, complications, extra time/effort)
- Often, a separate paragraph or cover letter outlining the additional work
The more explicit and structured the documentation, the stronger the case for reimbursement above the contracted rate.
The Operational Reality
Even with strong documentation, modifier 22 claims frequently trigger:
- Manual review
- Payment delays
- Additional requests for information
- Potential denials
Recent findings published in JAMA Surgery suggest that modifier 22 may offer limited financial benefit in many cases, raising an important consideration for organizations.
Final Takeaway
Modifier 22 isn’t just a coding decision—it’s an operational one. Before routinely appending it, organizations should evaluate whether the incremental reimbursement outweighs the administrative burden.
📖 Sources: JAMA Surgery (2024); Noridian & Novitas Modifier 22 Guidance
Meet the Presenter: Deanna Upston, CPC, CCS, CPMA, COSC
Deanna is a Senior Coding Quality Auditor for The Haugen Consulting Group with over 20 years of health care industry experience. Her introduction was through medical assisting, which she enjoyed for several years. Once she was established at a surgeon’s office, she started coding their surgical cases and discovered that was her favorite part of the day. Deanna has experience working on the professional fee side of coding, audit, education and compliance serving coders and physicians. She has put together multiple education sessions for both provider and coder. She also has experience working as an analyst in which she validated the integrity of editing logic during the implementation of claim scrubbing software.

0 Comments