E/M Plus a Minor Procedure: When the Modifier -25 Is Justified
A 44-year-old woman presents to the clinic with a 3-day history of dysuria and urinary frequency. The physician takes a problem-focused history, performs a problem-focused exam, and orders a urinalysis with dipstick in office; medical decision-making is straightforward. The same visit, the physician also performs an incision and drainage of a 2 cm abscess on the patient's right thigh, which was the reason she actually called for an appointment. The note documents both the urinary complaint and the abscess, with separate assessment and plan entries for each. The coder is considering appending modifier -25 to the E/M code.
1. Is modifier -25 supportable on the E/M service? Justify using the documentation.
Read the worked answer
Yes. The key test for -25 is whether a significant, separately identifiable E/M service was performed above and beyond the usual pre-, intra-, and post-procedure work of the minor procedure. Here the documentation shows a distinct problem (dysuria/frequency) with its own history, exam, and medical decision-making, separate from the abscess I&D. The urinary complaint has its own assessment and plan and is not part of the procedural work. The E/M is therefore separately reportable with -25 appended to the E/M code, and the I&D is reported on its own line.
2. What would make this same claim fail a -25 audit, and what is the compliance risk of appending it routinely?
Read the worked answer
It would fail if the note only documented the abscess and folded the urinary complaint into the procedure note without a separate assessment/plan - i.e., if the E/M content were indistinguishable from the procedure's inherent work. Appending -25 routinely to every E/M on a procedure day is a classic upcoding pattern: it inflates payment and is a frequent target of payer audits and RAC reviews. The defensible practice is to append -25 only when the note itself demonstrates a significant, separately identifiable service, and to be able to point to the specific documentation that supports it.