Chapter 11 — Key Takeaways

The hypertension asymmetry — the most tested thing in circulatory coding

Why: the hypertension–kidney relationship is close enough that the classification assumes it; many heart conditions have other causes.

When you see hypertension plus an organ condition, ask WHICH ORGAN before anything else.

The general pattern worth carrying

A combination code carries the RELATIONSHIP. It frequently does not carry the SPECIFICITY, and the Tabular instructs an additional code.

Hypertensive CKD + stage · hypertensive heart disease with failure + failure type · diabetes with CKD + stage.

Myocardial infarction

• Acute for four weeks (28 days) from onset — a time rule that genuinely exists
• Subsequent MI — a new infarction within that window; both codes reported
• Old MI — after the acute period, healed, no further care
• Type and site come from the record; "MI" alone produces an unspecified code

Heart failure — four axes

type (systolic / diastolic / combined) · acuity (acute / chronic / acute on chronic) · cause or association · other specified forms

It is a heart condition, so the hypertensive relationship must be stated or implied.

One stroke, three situations

   acute event ............. acute infarction codes
   deficits remain ......... SEQUELAE + a code per deficit
                             + DOMINANT / NON-DOMINANT side
   no deficits ............. PERSONAL HISTORY status code

Respiratory

COPD and asthma carry Tabular instructions about associated infections and tobacco status — the part coders skip.

Respiratory failure sequencing turns on WHY THE PATIENT WAS ADMITTED, not on severity:

• developed after admission → secondary
• present on admission and chiefly responsible → may be principal
• other chapter-specific priority rules may override

Digestive and musculoskeletal

Digestive: combination codes carry complications — obstruction, perforation, bleeding. A coder may not characterize an outcome as a complication; that is a clinical judgment.

Musculoskeletal: the heaviest specificity burden in the book. Pressure ulcers — site and stage; another clinician's staging is usable provided the provider documented the ulcer.

CKD and the three-convention collision

   DIABETES + CKD ............ presumed (Ch. 10 §10.6)
   HYPERTENSION + CKD ........ presumed (§11.1)
   BOTH ...................... the classification provides for it

   AND IN EVERY CASE:
     combination code = the RELATIONSHIP
     additional code  = the STAGE
     Section IV       = WHETHER the CKD is reportable at all

Transplant: a functioning transplant with residual CKD is CKD + transplant status, not a complication.

Obstetrics — a rule no other chapter has

• Chapter 15 codes take sequencing priority over all other chapters — unless the provider documents the condition is not affecting the pregnancy
• Trimester from the provider's documented weeks of gestation at the encounter, plus a code identifying the weeks
• Seventh character identifies the FETUS — assigned even in a single gestation
• Outcome of delivery on the maternal record only, when a delivery occurs

Key terms

hypertension table conventions · MI initial and subsequent · old MI · heart failure axes · sequelae · respiratory failure sequencing · CKD staging · transplant status versus complication · pressure ulcer staging · obstetric priority · trimester rules · outcome of delivery

Monday morning

You should be able to:

• Ask "which organ?" before coding hypertension with anything.
• Recognize that a combination code usually needs a companion for specificity.
• Tell an acute infarction from a subsequent one from an old one, by date.
• Distinguish a stroke's acute phase, its sequelae, and a history code — and catch the dominant/non-dominant axis.
• Sequence respiratory failure by admission reason rather than by severity.
• Apply obstetric priority without being talked out of it by the body system involved.

The Encounter: diagnosis C is I10. No heart condition is documented — the cardiac exam is normal. Chronic kidney disease is on the problem list and the hypertension–CKD relationship would be presumed.

And it is still I10, because the assessment does not address the kidney disease.

The rule this file has now demonstrated three times: a linkage convention tells you HOW to code two conditions together. It is never permission to code the second one. Section IV decides that, and it decides first.