The Modifier 25 Request
A four-physician orthopedic practice bills Medicare and two commercial payers. In March, 12 claims for 99214 with modifier 25 billed alongside 20610 (arthrocentesis, major joint) are denied as bundled. The office manager tells the coder, "Just put modifier 25 on everything that has an E/M with a procedure - the payers won't catch it, and we need the revenue this quarter." The coder reviews the 12 notes: in 5, the E/M documents a separate chronic problem with its own history, exam, and medical decision making; in 4, the note reads "patient here for knee injection, no other complaints" with an exam limited to the knee; in 3, the note is templated and word-for-word identical to the prior visit. The manager then asks the coder to change the diagnosis on two of the claims so the payer covers them.
1. How should the coder respond to the manager's instruction, claim by claim?
Read the worked answer
The principle first: modifier 25 represents a significant, separately identifiable E/M service by the same physician on the same day as the procedure - one that goes above and beyond the usual pre-, intra-, and post-procedural work. It is a factual assertion about the encounter, and it must be supported by the documentation in each individual note. It is not a revenue lever.
Group of 5 - likely supportable. Separate history, exam, and decision making for an unrelated chronic problem. If the documentation genuinely reflects a distinct service, the 25 is appropriate and these are the claims to appeal.
Group of 4 - not supportable. The note says the visit was for the injection and nothing else. The E/M is the pre-procedural evaluation of the same joint, which is bundled. No modifier.
Group of 3 - cannot be determined from the record. Cloned text is not evidence that the elements were performed at this encounter. Send a compliant query asking the physician to confirm what was actually done and documented for that date, or obtain a corrected note. Absent that, no modifier.
The manager's "put it on everything" instruction: decline, in writing, and route the request to the compliance officer under the practice's compliance program. Do not accept a blanket instruction to append a modifier that the documentation does not support. Nine of twelve claims would be at risk, and repetition turns a coding error into a pattern.
2. What is the coder's exposure if the manager's instruction is followed, and how should the denials be worked instead?
Read the worked answer
Exposure:
- False Claims Act. Submitting claims with a modifier known to be unsupported is a knowing false claim. Penalties are per claim and treble damages are available; the manager's own words ("the payers won't catch it") are the kind of evidence that makes intent easy to establish. Individual coders can be named, and qui tam relators are often insiders.
- OIG compliance program expectations. A seven-element program requires monitoring and auditing, a reporting mechanism, and enforcement/discipline. A coder who documents the request and escalates is using that program; one who complies quietly becomes part of the finding.
- Professional ethics. AHIMA's code of ethics obligates the coder to refuse to participate in or conceal improper billing practices, and to report them through the proper channel.
Working the denials properly:
- Pull each note and evaluate the 25 on its own merits - never batch-append.
- For the 5 supportable claims, appeal with the note, a brief cover explanation of the separate service, and the NCCI/payer policy reference.
- For the 4 unsupportable claims, accept the bundling; rebill the E/M at zero or adjust, and do not shift the balance to the patient unless the notice requirements and the practice's financial policy were properly met.
- For the 3 cloned notes, hold the claims pending query response.
- Trend the denials - 12 in one month suggests the physicians need education on what makes an E/M separately identifiable, which is a documentation fix, not a modifier fix.
3. The manager asks the coder to change two claim diagnoses so the payer will cover them. How should the coder handle this, and what is the compliant alternative?
Read the worked answer
Refuse. Diagnosis codes must reflect what the physician documented in the record. Changing a code to meet a payer's coverage list is fabrication, regardless of whether the substituted code is "close." It is the clearest form of a false claim because the intent is explicit on its face, and it corrupts the data the practice uses for everything else.
Compliant alternatives, in order:
- Re-read the note. Sometimes an additional documented diagnosis exists that would support coverage - the physician documented it but the coder missed it. That is legitimate.
- Query the physician for a diagnosis that is clinically supported but not yet documented. If the physician documents it and it is supported by the record, code it.
- For Medicare, use an ABN. If the service may not be covered for the documented diagnosis, give the beneficiary proper advance notice so they can choose. The claim is then billed with the correct diagnosis and the ABN modifier as appropriate - not with a substituted diagnosis.
- Check the LCD/NCD and payer policy. If the policy actually covers the documented diagnosis and the denial was a processing error, appeal with the policy citation.
- Bill the patient responsibility only where it is legitimately theirs and notices were properly executed.
Document the refusal and the escalation. A coder who declines verbally and moves on leaves no record; the next coder receives the same instruction.