Skip to main content

Code Relationships & Conventions

FY2027 · CURRENT

Intermediate

Reviewed October 1, 2026

The “With” Convention: When ICD-10-CM Presumes Two Conditions Are Related

Part ofSequencing · step 3 of 4 · Read nextHow Do I Code Hypertension With Chronic Kidney Disease? I12, I13, and the N18 Stage, How Do I Code Heart Failure? Type, Acuity, and the Hypertension Combination Codes, How Do I Code Diabetes With Chronic Kidney Disease?, How Do I Code Postpancreatectomy Diabetes Mellitus?, Manifestation Codes: What Goes First, and Why It Can’t Be the Manifestation

Editorial explanation — not an official CMS/CDC rule. Official coding instructions and source material are identified below. How to read the labels

Current data releases:ICD-10-CM FY2027 · ICD-10-PCS FY2027 · HCPCS October 2026 · MS-DRG v44 · Medicare Code Editor v44.0 · NCCI PTP Q4 2026 · MUE Q4 2026 · NCD code lists 2026-01 · LCD export September 28, 2026 · All releases and sources

Quick answer · MedCoder editorial

When the Alphabetic Index or a code title links two conditions with “with” or “in,” ICD-10-CM presumes one causes the other — and they are coded as related without the provider saying so. The provider statement that changes the coding is the one saying they are unrelated.

Jump to the decision rule ↓

What decides the answer?

  • Whether the Index or a code title joins the two conditions with “with” or “in”
  • A provider statement that the conditions are unrelated — the one thing that breaks the presumption
  • Which companion codes the combination code’s notes call for (heart failure type, CKD stage)

Why it matters

The rule and where it comes from

1. The Official Guidelines, Section I.A.15 (“With”)

Official source

“The word ‘with’ or ‘in’ should be interpreted to mean ‘associated with’ or ‘due to’ when it appears in a code title, the Alphabetic Index (either under a main term or subterm), or an instructional note in the Tabular List. The classification presumes a causal relationship between the two conditions linked by these terms in the Alphabetic Index or Tabular List. These conditions should be coded as related even in the absence of provider documentation explicitly linking them, unless the documentation clearly states the conditions are unrelated…”

And the mirror rule for everything else: “For conditions not specifically linked by these relational terms in the classification or when a guideline requires that a linkage between two conditions be explicitly documented, provider documentation must link the conditions in order to code them as related.”

2. The hypertension application, Section I.C.9.a

Official source

“The classification presumes a causal relationship between hypertension and heart involvement and between hypertension and kidney involvement, as the two conditions are linked by the term ‘with’ in the Alphabetic Index. These conditions should be coded as related even in the absence of provider documentation explicitly linking them, unless the documentation clearly states the conditions are unrelated.”

3. The Tabular List’s own statements

The combination categories say the same thing as Includes notes: I11 includes “any condition in I50.- or I51.4-I51.7, I51.89, I51.9 due to hypertension”; I12 includes “any condition in N18 and N26- due to hypertension”; and I13 includes “any condition in I11.- with any condition in I12.-” — which is why the Guidelines say a patient with all three conditions takes an I13 code, never I11 plus I12.

The diabetes categories are the same convention at larger scale (Section I.C.4.a): “The diabetes mellitus codes are combination codes that include the type of diabetes mellitus, the body system affected, and the complications affecting that body system,” with as many codes from E08–E13 as needed to cover every documented complication.

Examples

The worked example: hypertension, heart failure, and CKD

A patient carries three documented diagnoses: hypertension, heart failure, and stage 3 chronic kidney disease. Nothing in the record says the heart failure or the CKD is due to the hypertension — and under the “with” convention, nothing needs to.

The combination category does the assembling. I13.0 (Hypertensive heart and chronic kidney disease with heart failure and stage 1 through stage 4 chronic kidney disease, or unspecified) carries two Use Additional Code notes, and both fire:

Official source

Use additional code (I13.0): to identify type of heart failure (I50.-); to identify stage of chronic kidney disease (N18.1-N18.4, N18.9)

  1. I13.0 — Hypertensive heart and chronic kidney disease with heart failure… (the combination)
  2. I50.- — the documented type of heart failure
  3. N18.30 — the documented CKD stage

Three code slots, one causal presumption, zero linking language required from the provider. And the risk capture follows the combination: I13.0 maps to V28 HCC 226 (Heart Failure, Except End-Stage and Acute); its stage-5 sibling I13.2 maps to both HCC 226 and HCC 326 (Chronic Kidney Disease, Stage 5) — the only code in the family carrying both categories at once.

Practice

Practice scenarios

Scenario 1

Three documented diagnoses: hypertension, heart failure, and stage 3 chronic kidney disease. The record does not say the heart failure or the CKD is due to the hypertension.

Coding question
Does the coder need a provider statement linking them?
Decision
No. The combination code I13.0 is assigned, followed by the I50 code for the documented heart-failure type and the N18 stage code.
Why
Section I.A.15: conditions the Index or a title joins with “with” are presumed related unless the provider states otherwise. I13.0 carries two Use Additional Code notes for the heart-failure type and the stage.
Documentation check
Whether the record states the conditions are unrelated, which is the only documentation that breaks the presumption, and the heart-failure type and CKD stage.

Scenario 2

Hypertension and heart failure documented; the cardiologist writes that the heart failure is due to a prior infarction and unrelated to the hypertension.

Coding question
Does the “with” presumption still apply?
Decision
No. The heart failure and the hypertension are coded separately (the I50 code and I10), sequenced by the circumstances of the encounter.
Why
The presumption is rebuttable by a provider statement that the conditions are unrelated; that statement removes the I11 combination code.
Documentation check
The explicit unrelated statement in the provider’s own documentation.

Each scenario restates one of the worked examples above in decision form; none adds a clinical fact or a code the example does not already assign.

Branches: when the presumption does not decide

If the provider states the conditions are unrelated → code them separately. The guideline is explicit: the same heart conditions with hypertension “are coded separately if the provider has documented they are unrelated to the hypertension,” with I10 (or I15.- for secondary hypertension) assigned alongside the heart condition and sequencing following the circumstances of the encounter. Unrelatedness is the thing that must be documented — not relatedness.

If the pairing is not linked by “with” in the classification → the provider must link it. The presumption covers only pairings the Index or Tabular actually joins. Hypertension with heart involvement and kidney involvement qualifies; a condition the classification does not join to hypertension needs explicit linking language (“due to,” “associated with”) before it can be coded as related.

If all three conditions are present → I13, never I11 + I12. The Guidelines read I13’s Includes note as settling this: “If a patient has hypertension, heart disease and chronic kidney disease, then a code from I13 should be used, not codes from I11 or I12.”

If acute renal failure is also present → code it too. Both the I12 and I13 guidelines add acute renal failure as its own code on top of the combination, sequenced by the circumstances of the encounter — the presumption never absorbs an acute condition into a chronic combination code.

In diabetes, the same presumption picks the combination code. “Diabetes with” complications — kidney disease, retinopathy, neuropathy, foot ulcer — take the E08–E13 combination codes on the same logic, stacking as many as the record supports, each with its own companion notes (N18.- stage, L97.- ulcer site, and so on).

When the folk rule is wrong

The folk rule: “don’t link hypertension to the heart failure unless the doctor links them.” It is cautious, it sounds like compliance, and for these pairings it is exactly backwards.

What is actually true: for conditions the classification joins with “with,” the linkage is the default and requires no provider statement — the coding only changes when the provider states the conditions are unrelated. The cautious-sounding habit produces real, systematic undercoding: I10 + I50.9 coded separately where I11.0 (and its Use Additional I50.-) belongs, which mis-states the classification and, in risk-adjusted contexts, still reaches HCC 226 through the I50 code but loses the hypertensive-disease combination the record supports.

The folk rule survives because it is the correct rule for every pairing the classification does not join — which is most pairings. The skill is knowing which side of the line a pair sits on, and the Index’s “with” subterms are the line.

Decision rule

Quick reference

DocumentedCodeCompanions
HTN + heart condition in I50.-/I51.4-I51.7/I51.89/I51.9I11.0 (with HF) or I11.9I50.- when heart failure is present
HTN + CKD stage 1-4 or unspecifiedI12.9N18.1-N18.4, N18.9
HTN + CKD stage 5 or ESRDI12.0N18.5, N18.6
HTN + heart + CKD 1-4, with HFI13.0I50.- and N18.1-N18.4, N18.9
HTN + heart + CKD 1-4, no HFI13.10N18.1-N18.4, N18.9
HTN + heart + CKD 5/ESRD, no HFI13.11N18.5, N18.6
HTN + heart + CKD 5/ESRD, with HFI13.2I50.- and N18.5, N18.6
Provider states conditions unrelatedI10 (or I15.-) + the condition, separatelySequence by the encounter
Acute renal failure alongside any of the aboveadd N17.-Sequence by the encounter

“Due to” and “associated with” are the same convention

The Guidelines do not define “due to” or “associated with” as separate conventions; they define them as what “with” means. Section I.A.15: “The word ‘with’ or ‘in’ should be interpreted to mean ‘associated with’ or ‘due to’ when it appears in a code title, the Alphabetic Index (either under a main term or subterm), or an instructional note in the Tabular List.” The hypertension chapter uses the same vocabulary: “For hypertension and conditions not specifically linked by relational terms such as ‘with,’ ‘associated with’ or ‘due to’ in the classification, provider documentation must link the conditions in order to code them as related.”

So a code title reading “X due to Y” or an Index subterm reading “associated with” carries the same presumption as “with”: the two conditions are coded as related without the provider saying so, unless the documentation states they are unrelated or another guideline demands an explicit link (the sepsis guideline’s organ-dysfunction rule is the Guidelines’ own example). Where the classification uses none of these terms, the presumption does not exist and the provider must document the link.

How to apply it

How to apply the rule

  1. Find the two conditions in the Index; if one sits under “with” (or “in”) beneath the other, or a code title or tabular note links them with “with,” “in,” “due to” or “associated with,” the relationship is presumed.
  2. Assign the combination code — no provider linkage statement is needed.
  3. Break the presumption only when the documentation clearly states the conditions are unrelated, or when a guideline specifically requires a documented linkage (the sepsis organ-dysfunction rule).
  4. For conditions the classification does not link with these terms, require provider documentation of the link before coding them as related.
  5. Sequence per the combination code’s own notes (I11.0 → I50.-; I13.- → I50.-, N18.-; E11.22 → N18.-).

Common mistakes

Common mistakes

  • Coding hypertension and heart failure separately because the provider did not write “due to.”
  • Reading a “with” subterm as requiring provider linkage — it is the reverse.
  • Presuming a link the classification does not make (no “with” term) without documentation.
  • Ignoring an explicit “unrelated” statement.

Documentation matters

Documentation that changes the coding

  • A statement that the conditions are unrelated — the one thing that breaks the presumption.
  • A provider link, required only when the classification does not supply the relational term.
  • Any guideline-specific linkage requirement (sepsis organ dysfunction).

FAQ

Does the provider have to document that hypertension caused the heart failure?

No — the presumption runs the other way. The classification links hypertension and heart involvement with “with” in the Alphabetic Index, so they are coded as related (I11.0 plus an I50.- code) by default. Only a provider statement that the conditions are unrelated changes that, in which case I10 and the heart condition are coded separately.

Can I code I11 and I12 together instead of I13?

No. I13’s own Includes note covers “any condition in I11.- with any condition in I12.-,” and the Guidelines state directly that when hypertension, heart disease and chronic kidney disease are all present, a code from I13 is used — not codes from I11 or I12.

Which hypertension combination codes affect risk adjustment?

The ones carrying heart failure or stage-5 kidney disease: I11.0 and I13.0 map to V28 HCC 226 (Heart Failure, Except End-Stage and Acute); I12.0 and I13.11 map to HCC 326 (Chronic Kidney Disease, Stage 5); and I13.2 is the family’s only dual mapping, reaching both. I10, I11.9, I12.9 and I13.10 map to no HCC — the companion I50.- and N18.- codes carry their own weight regardless.

Does the “with” presumption apply to diabetes too?

Yes — it is the same Section I.A.15 convention. “Diabetes with” its complications takes the E08–E13 combination codes without explicit linking language, and the Guidelines instruct coders to assign as many combination codes as needed to capture every documented complication.

What if the record shows hypertension and a condition the classification does not join to it?

Then the presumption does not apply and the ordinary rule takes over: provider documentation must link the conditions — “due to,” “associated with” — before they can be coded as related. The “with” subterms in the Alphabetic Index are the boundary of the presumption.

Code set release

This guide was verified against ICD-10-CM FY2027, effective October 1, 2026.

Code relationships

RelationshipAtNamesNote
use-additionalI11.0I50.- (type of heart failure)
use-additionalI13.0I50.-; N18.1-N18.4, N18.9
use-additionalI13.2I50.-; N18.5, N18.6
includesI13any condition in I11.- with any condition in I12.-
code-firstI50I11.0; I13.- (heart failure due to hypertension / with CKD)
use-additionalE11Z79.4, Z79.84, Z79.85 (control agents)
hccI10no CMS-HCC V28 categoryCMS-HCC V28, payment year 2026 mapping file
hccI11.0HCC 226 — Heart Failure, Except End-Stage and AcuteCMS-HCC V28, payment year 2026 mapping file
hccI11.9no CMS-HCC V28 categoryCMS-HCC V28, payment year 2026 mapping file
hccI12.0HCC 326 — Chronic Kidney Disease, Stage 5CMS-HCC V28, payment year 2026 mapping file
hccI12.9no CMS-HCC V28 categoryCMS-HCC V28, payment year 2026 mapping file
hccI13.0HCC 226 — Heart Failure, Except End-Stage and AcuteCMS-HCC V28, payment year 2026 mapping file
hccI13.11HCC 326 — Chronic Kidney Disease, Stage 5CMS-HCC V28, payment year 2026 mapping file
hccI13.2HCC 226 — Heart Failure, Except End-Stage and Acute; HCC 326 — Chronic Kidney Disease, Stage 5CMS-HCC V28, payment year 2026 mapping file
ms-drgI11.0MDC 05 — MS-DRG 291-293Definitions of MS-DRGs v44, Appendix B (diagnosis / MDC / MS-DRG index)
ms-drgI11.0non-CC as a secondary diagnosisDefinitions of MS-DRGs v44, Appendix C Part 1
ccsrI11.0CIR019 — Heart failureAHRQ CCSR v2026-1 default inpatient category
ms-drgI13.0MDC 05 — MS-DRG 291-293Definitions of MS-DRGs v44, Appendix B (diagnosis / MDC / MS-DRG index)
ms-drgI13.0CC as a secondary diagnosis (26 principal-diagnosis exclusions)Definitions of MS-DRGs v44, Appendix C Part 1
ccsrI13.0CIR019 — Heart failureAHRQ CCSR v2026-1 default inpatient category
ms-drgI13.2Pre-MDC — MS-DRG 008Definitions of MS-DRGs v44, Appendix B (diagnosis / MDC / MS-DRG index)
ms-drgI13.2CC as a secondary diagnosis (26 principal-diagnosis exclusions)Definitions of MS-DRGs v44, Appendix C Part 1
ccsrI13.2GEN003 — Chronic kidney diseaseAHRQ CCSR v2026-1 default inpatient category

Relationships are quoted from the FY tabular notes and Official Guidelines the guide cites; none are inferred.

Relationships are quoted from the tabular notes and Official Guidelines sections the guide cites; the wording of each row is MedCoder’s.

Compare these pairs

Each pair below is one the tabular notes link; its Compare page quotes the note and says whether the two can be reported together.

Check these codes on a claim →

Authoritative sources

Applies to FY2027 ICD-10-CM

Verified against the FY 2027 ICD-10-CM Official Guidelines (Sections I.A.15 — including its definition of “due to” and “associated with” — I.C.4.a, I.C.9.a), the FY 2027 tabular list, Definitions of Medicare Code Edits v44.0, and the CMS-HCC V28 mappings for payment year 2026.

  • ICD-10-CM Official Guidelines for Coding and Reporting, FY 2027 (Sections I.A.15, I.C.4.a, I.C.9.a)
  • FY 2027 ICD-10-CM Tabular List
  • Definitions of Medicare Code Edits v44.0
  • CMS-HCC V28 mappings, payment year 2026

Official guidance cited

The Official Guidelines sections this guide quotes or applies, by heading. Passages set as quotations above are the sections’ own words; the surrounding text is MedCoder’s reading of them.

  • Section I.A.15 — “With”
  • Section I.C.9.a — Hypertension
  • Section I.C.4.a — Diabetes mellitus

Source document (CMS PDF) · Release and checksum

Passages set as quotations are verbatim official text from the sources listed. Surrounding explanation, decision tables and examples are MedCoder’s editorial reading of those sources and are not official statements. Examples are illustrative; they assign no code to any real patient.

Coder Takeaway: “With,” “in,” “due to” and “associated with” in the Index or Tabular presume the causal link — code the combination without a provider statement, unless the record says the conditions are unrelated or a guideline demands an explicit link.

Real-world questions this guide answers

Coding questions

No community questions relate to this guide yet.

Ask a Coding Question about this guide.

Didn’t find your answer?

Ask a coding question and get help from the MedCoder community.

Applicable code set: FY2027. Published September 3, 2026; last updated October 1, 2026; last reviewed October 1, 2026.