The Operative Note That Never States a Size

Neither is reliable for code selection.

• The prior clinic note is a pre-operative clinical estimate from a different encounter. It describes a lesion that had not yet been excised and was not the basis of the operative documentation. Using it substitutes a guess for a documented fact.
• The pathology specimen measurement includes the surrounding margin of normal tissue and the fixative-induced changes in dimension; it is not the excised diameter of the lesion itself. Excision codes in the 11400–11646 series are selected on the diameter of the lesion plus the margin actually removed, as documented by the surgeon.
• The op note as written contains no size, so the code family cannot be closed correctly and the repair length cannot be determined.

Correct action: issue a non-leading query tied to the procedure date asking the surgeon to document the excised lesion diameter (and separately, the length of the layered closure). Do not let the vacation schedule push you into picking a size; the filing deadline is a workflow problem, not a coding rationale.

Both elements are wrong.

1. 11601 is a malignant lesion code (excision, malignant lesion, trunk, arms, or legs; excised diameter 0.6–1.0 cm). Pathology returned a benign compound nevus and the pre-op note used the word 'questionable,' which is not a malignancy diagnosis. Benign lesions are reported from 11400–11446 by site and size. Charge entry does not get to upgrade to a malignant code on suspicion.
2. No benign excision code can be assigned until the diameter is documented, which loops back to the query.
3. The repair is separately reportable only if documented. A layered closure is an intermediate repair (12031–12037 for scalp/trunk/extremities, with 12031 for a wound of 2.5 cm or less on an extremity), but the note gives no wound length. Simple closure is included in the excision code; intermediate and complex repairs are not. Because the repair length is undocumented, that portion also requires clarification.

Process fix: the MA should not be assigning procedure codes at all; charge capture should be built from the operative report by a qualified coder or from a structured template that forces size and closure length.

Escalate per the compliance plan rather than guess. A defensible sequence:

1. Second query through a different channel (secure message to the surgeon, notification to the department chief) with the deadline stated.
2. Document the query, the response attempts, and the dates - the audit trail is the defense if the record is later reviewed.
3. Do not default to a code. Selecting the largest plausible size, or the malignant code the MA entered, converts a documentation gap into a misrepresentation.
4. Options if the query is never answered: hold the claim, or report the lowest size in the range only if the record affirmatively supports it (it does not here), or, as a last resort under written policy, hold the charge and route the account to the compliance officer for a decision on whether an unlisted or unclassified approach is appropriate. Under-coding to clear the account is equally unacceptable - the goal is accuracy, not speed.
5. Root cause: add a size and closure-length field to the procedure template and require it before the note can be signed.