The Addendum Request: Diabetic Neuropathy on the Problem List

Deficiency inventory

1. Conflict between assessment and problem list (highest risk). The assessment says without complication; the problem list says with neuropathy. A coder cannot code from the problem list - it is a longitudinal tracking tool, not evidence the condition was evaluated at this encounter. Because the distinction changes the code (a diabetes-with-neurologic-complication combination code vs. a diabetes-without-complications code) and materially changes risk adjustment, this is query-worthy, not a coder fix.
2. 'Uncontrolled' inferred from a lab value (high risk). A1c 7.8 does not by itself establish 'uncontrolled' - that is a clinical determination, and 7.8 would not meet most poor-control thresholds anyway. Coders do not assign or alter diagnostic language based on their own interpretation of a lab.
3. Missing laterality on the referral (low risk for this claim, moderate downstream). The office visit itself is not laterality-dependent, but the ortho order and any future procedure are. The exam finding ('positive Tinel, right wrist') supports right, but the provider must confirm - coders do not amend clinical content.

Ranking rationale: #1 and #2 both carry coding-accuracy and audit exposure; #1 also carries risk-adjustment exposure. #3 is a clarity issue that becomes a compliance issue only if it propagates to a billed procedure.

Distinguish amendment from post-hoc addition.

• An addendum is appropriate to correct or clarify something the provider did document but stated inaccurately or incompletely - e.g., a typographical omission, a missing laterality the provider personally confirmed, a plan item left out.
• An addendum is not appropriate to introduce a diagnosis that was never assessed or addressed at the encounter, especially after the claim has been released. That is functionally an unattributed post-service diagnosis change and looks like retroactive upcoding to any auditor.

Compliant path:

1. Ask whether the note elsewhere supports the diagnosis - diabetes medication management, a foot exam, gabapentin, prior EMG. The current note shows metformin continuation only; nothing addresses neuropathy.
2. If support exists, a clarification addendum is acceptable only if it is dated, timed, signed, states the reason for the change, and is linked to the original note. Do not backdate it to 3/4.
3. If support does not exist, send a query using the problem list entry as supporting evidence: 'The problem list indicates DM with diabetic neuropathy; the assessment documents diabetes without complication. Please clarify which best describes the patient's status at this visit.' Include 'unable to determine' as an option.
4. Do not word the addendum 'uncontrolled.' If the provider wants that language, it must come from the provider's own clinical judgment, documented in the assessment, and it must be consistent with the A1c.

Framing for the provider: the issue is not speed, it's that an addendum adding a new diagnosis after the fact will not survive a payer records request, and the risk score will be reversed anyway.

Coder role boundary: the coder may not write 'right' into the record, even though the exam supports it. Only the author (or an authorized clinician per practice policy) may clarify clinical content.

Steps:

1. Send a brief clarification request to the provider: the referral and plan do not specify side; the exam documents a positive Tinel on the right. Ask the provider to confirm right vs. left vs. bilateral.
2. Document the clarification in the record per practice policy - a dated, attributed clarification note, not a silent EHR edit.
3. Confirm the corrected side is reflected in the referral order so the ortho practice bills the correct side. A wrong-side referral is a patient-safety event waiting to happen and a classic denial source for the downstream procedure.
4. No change to the office visit code results from this clarification - do not treat the correction as a reason to re-level the E/M.

Teaching point for the provider: laterality is a hard requirement on procedure codes and a frequent denial driver; it is cheaper to fix in the order than in appeals.