Diabetic CKD, Neuropathy, and the 'With' Convention
A 68-year-old man with type 2 diabetes mellitus, diabetic peripheral neuropathy, and chronic kidney disease stage 3b is seen in the nephrology clinic for follow-up. The problem list reads: 'T2DM'; 'CKD 3b - stable, creatinine 2.1'; 'neuropathy, diabetic.' The assessment names the diabetes and the CKD but does not state a causal link between them, and no CKD stage appears in the body of the note. The only renal data in the encounter are flowsheet values (eGFR 32, creatinine 2.1). A1c today is 8.4%. BMI 37.2 is recorded alongside a documented diagnosis of obesity, and the social history states 'quit smoking 3 years ago, 30 pack-years.' The physician spent 35 minutes reviewing labs and adjusting insulin.
1. Assign the ICD-10-CM codes for this encounter and state the sequence and your reasoning.
Read the worked answer
First-listed: E11.22 (Type 2 diabetes mellitus with diabetic chronic kidney disease) - this is the reason for the nephrology visit, and it is a combination code that describes both conditions.
Additional:
- N18.32 - CKD stage 3b. The ICD-10-CM tabular note under E11.22 instructs 'Use additional code to identify stage of chronic kidney disease,' so the stage must always accompany the combination code.
- E11.42 - diabetic polyneuropathy (also a combination code; the problem list documents it as diabetic).
- E66.9 + Z68.37 - obesity and BMI 37.0–37.9. BMI is coded only because the provider documented a corresponding obesity diagnosis in this record.
- Z87.891 - only if the record actually supports a history of nicotine dependence; a bare 'former smoker' statement without a dependence diagnosis is generally not coded. Flag this rather than default to it.
Sequencing rule: the condition chiefly responsible for the encounter goes first, and the stage code follows its combination code rather than leading the claim.
2. The problem list pairs diabetes and CKD, but the assessment never says they are related. Must you query before assigning E11.22?
Read the worked answer
No query is required on these facts. ICD-10-CM's 'with' convention treats two conditions joined by 'with' in a code title as associated unless the provider documents otherwise, and the diabetes category carries explicit 'with' notes for kidney manifestations. When the provider documents both diabetes and CKD, the coder reports E11.22 + the stage code.
Query only if:
- the provider documents that the CKD is not diabetic (e.g., hypertensive or obstructive nephropathy that fully explains it), or
- the renal diagnosis is too vague to map (e.g., 'renal insufficiency,' 'azotemia,' 'kidney problem') and no stage or type is stated.
Practical judgment: a short, non-leading query is still defensible if internal audit policy requires explicit linkage, but requesting confirmation of something the classification already presumes adds query burden without adding accuracy - and a leading query ('Would you agree the CKD is due to diabetes?') is a compliance risk in itself.
3. Can the Coder take CKD stage 3b from the problem list entry, or derive it from the eGFR of 32 in the flowsheet?
Read the worked answer
Do not derive the stage from the eGFR. Laboratory values are data, not diagnoses; ICD-10-CM assigns CKD stage according to the provider's clinical documentation, and an eGFR of 32 does not by itself authorize N18.32. Coders are not clinicians and cannot convert a lab result into a stage.
The problem list is a weaker source than the note. A problem list is coded from only when it is part of the patient's record and is maintained and current for that encounter. Here it is the only place the stage appears, and the narrative contradicts it by omitting the stage entirely.
Best practice: send a non-leading query - 'The problem list records CKD stage 3b; the assessment documents chronic kidney disease without a stage. Please document the stage of chronic kidney disease.' If the provider confirms 3b, report N18.32. If the query goes unanswered, report the diabetes combination code with the least specific supported CKD code and route the record to the compliance officer per the query-escalation policy - do not silently adopt the problem list entry and do not default to the highest-weighted option.