Serving medical practices across 60+ specialties

When a Signed Note Still Needs Coding Clarification

A signature establishes completion of the note; it does not resolve every coding question. A review may still need the documented service, encounter setting, time when relevant, or the relationship between separately reported procedures.

Completion and Coding Support Answer Different Questions

A signed note indicates that a clinician has completed the record. A coding review asks a separate question: does the documented encounter support the codes, units, and modifiers proposed for that date of service? A record can be complete in the system while leaving a billing decision unresolved.

Start with the service actually described, the care setting, and the applicable coding framework. Where time affects selection, review the documented time under the relevant rules. Where two services are reported together, examine their relationship rather than assuming that two entries represent separately reportable work.

An Edit Is a Prompt to Review the Record

For Medicare, NCCI procedure to procedure edits identify code combinations subject to correct coding rules. CMS explains that a modifier indicator of 1 permits an associated modifier only under appropriate circumstances. It does not make the modifier automatic. An indicator of 0 does not allow such a modifier to bypass the edit.

NCCI coding edits also do not determine medical necessity. A claim can satisfy a code pairing requirement and still need review against coverage or documentation requirements. Keep these questions separate so the reviewer does not interpret an edit result as a complete payment decision.

Ask for the Missing Clinical Fact

A useful clarification identifies the unresolved fact without steering the clinician toward a financially favorable answer. If the record does not explain the distinct work behind a separately reported service, ask for clarification of that work. Do not ask the clinician to add a particular code or modifier merely to overcome an edit.

Consider an illustrative encounter with multiple recorded procedures. The reviewer should examine the narrative, relevant anatomy or encounter circumstances, and the applicable code relationships. If the record cannot support a decision, the inquiry belongs with the clinician who can clarify the actual care delivered.

A focused clarification record:

Record the encounter, the unresolved coding question, the documentation reviewed, the person receiving the inquiry, and the response. Keep the original question and the resulting decision visible together.

Bring the Answer Back Into the Workflow

Once a clarification arrives, reassess the claim using the supported facts. A response should not be copied into a claim without checking that it resolves the original question. Where an amendment is needed, follow the practice’s documentation process and preserve the appropriate audit trail.

Recurring clarification patterns can inform targeted education. For example, repeated uncertainty about time documentation should lead to a review of that documentation process, rather than a general reminder to “code accurately.”

The practical standard is explainability. A reviewer should be able to identify the record detail behind a code, the reason for a modifier, and any separate coverage question still awaiting review. This makes coding quality observable without claiming that a signed note guarantees reimbursement.

Sources & Scope

Primary references checked October 4, 2026. Apply the guidance to the relevant program, service date, and practice circumstances.

Bring the Question to Your Workflow.

Discuss the issue this publication raises and the operating context behind it in your practice.

Scroll to Top