Coding a Procedure When Documentation Is Thin
A general surgeon performs an excision of a 2.4 cm subcutaneous lesion on the patient's back and, in the same operative session, a separate 1.1 cm lesion on the forearm. The operative report describes the back lesion as 'excised down to fascia with layered closure' and the forearm lesion as 'shaved, specimen to pathology.' Pathology returns: back lesion - benign lipoma; forearm - benign intradermal nevus. The charge sheet lists only 'lesion excision x2' with no sizes or closure detail, and the coder sees that the back lesion code family distinguishes benign vs. malignant and by size and closure. The surgeon's note does not state whether the back excision required complex closure or whether the forearm shave was a full-thickness or partial-thickness removal. The coder is asked by the billing manager to 'just pick the highest-value codes that fit' before the month-end close in two days.
1. How should the coder proceed on the back lesion and the forearm lesion?
Read the worked answer
The coder should code from the documentation, not from a revenue target, and should not upcode to fit a deadline.
- Back lesion: The documentation supports an excision (full-thickness) of a benign subcutaneous lesion, 2.4 cm, with layered (intermediate) closure. The size and benign nature are documented; the closure type is described as 'layered,' which supports intermediate rather than simple closure if the note supports it - but the coder should confirm the closure description rather than assume complex. The code family must match benign + size + closure actually documented.
- Forearm lesion: 'Shaved' supports a shave removal code, not a full-thickness excision. A shave removal of a benign lesion is coded by site and is generally not size-dependent in the same way as excisions. The coder should not convert a shave into an excision.
- Do not 'pick the highest-value codes.' That is the definition of upcoding and is a compliance problem, not a coding shortcut. If the documentation is ambiguous, the correct action is a physician query, not a guess.
2. What is the appropriate action given the two-day close deadline and the missing closure detail?
Read the worked answer
Deadline pressure does not change the documentation standard.
- Query the surgeon with a specific, non-leading question: e.g., 'For the back excision, please clarify the closure type (simple/intermediate/complex) and confirm the lesion was benign and 2.4 cm.' A leading query that suggests the answer is improper.
- Hold the account rather than submit a code the documentation does not support. A held claim can be corrected; a submitted upcoded claim creates a false claim exposure and a rework cycle.
- Document the query and the response in the record.
- If the surgeon does not respond before close, code only what is clearly supported and flag the remainder for review - do not default to the higher-value code.
- Escalate the pattern (charge sheet lacking sizes/closure) to the coding manager as a process fix, since the root cause is the charge-capture template, not this one chart.