Chapter 11: Coding Complex Cases: Circulatory, Respiratory, Digestive, Musculoskeletal, Genitourinary, and Pregnancy

"Two conditions on a problem list. One of them the classification assumes is related to the other, and one of them it does not. Nothing in the note tells you which is which." — constructed

Overview

Chapter 10's conventions were mostly about what to code. This chapter's are mostly about what the classification assumes, and that is a harder problem.

Six body systems, and the ones with the sharpest conventions in ICD-10-CM. Hypertension carries assumed relationships — but not the same assumption in every direction, and the asymmetry is examined constantly and misapplied constantly. Myocardial infarction has a time rule that genuinely exists, unlike the pain duration rule that does not. Heart failure has four axes and clinicians document two of them. Chronic kidney disease has a staging convention that interacts with the hypertension convention and with the diabetes convention from Chapter 10. Respiratory failure has a sequencing rule that turns on why the patient was admitted. And obstetric coding takes priority over the body system a condition would otherwise belong to — a rule with no equivalent anywhere else in the classification.

A warning specific to this chapter. Several conventions here have been revised since ICD-10-CM took effect, and the hypertension guidance in particular has been clarified more than once. Every rule in this chapter must be verified against the current Section I.C before you rely on it. The chapter says so at the point of use, repeatedly, and that is not caution for its own sake — it is the single most-revised body of guidance in the document.

In this chapter, you will learn to:

• Apply the hypertension conventions and their asymmetry
• Code myocardial infarction across and after the acute period
• Code heart failure along its axes
• Distinguish an acute cerebrovascular event, its sequelae, and a history code
• Apply respiratory failure sequencing and the COPD and asthma conventions
• Stage chronic kidney disease and handle transplant status
• Apply obstetric priority, trimesters, and the fetus character

Learning Paths

🎓 Certification — §11.1 (hypertension), §11.2 (MI), §11.5 (respiratory failure sequencing), and §11.9 (obstetrics) are the four most examined sections. The hypertension asymmetry in §11.1 is the single most reliable question in circulatory coding.

💼 New Coder — All of it. §11.1 and §11.8 together are where most primary care and nephrology coding lives.

💵 Biller / AR — §11.5's sequencing and §11.9's priority rule explain two categories of facility denial. Skim the rest.

🏥 Practice Manager — §11.8 (CKD staging) and §11.1, because between them they determine a large share of a primary care panel's risk-adjustment picture.

11.1 Circulatory: hypertension and the assumed relationships

The most important asymmetry in ICD-10-CM.

Hypertension is coded I10 when it is essential hypertension with no associated heart or kidney involvement. Where involvement exists, the classification has combination categories — and whether you may use them depends on which organ, in a way that surprises everyone.

Kidney: the relationship is presumed

Where hypertension and a condition classifiable to chronic kidney disease are both present, the classification presumes a cause-and-effect relationship and classifies them together as hypertensive chronic kidney disease.

No stated linkage is required. This is the "with" convention (Chapter 9 §9.7) operating at its strongest, and the guidance states the presumption explicitly.

Heart: the relationship must be stated or implied

Where hypertension and a heart condition of the relevant kinds are both present, a combination code is assigned only when a causal relationship is stated or implied — documented as "due to hypertension," or as "hypertensive."

Without that, the two conditions are coded separately.

   THE ASYMMETRY — and it is the most tested thing in circulatory coding

   HYPERTENSION + CHRONIC KIDNEY DISEASE
     ► Relationship PRESUMED by the classification
     ► Combination code, no stated linkage needed
     ► Plus a code for the CKD STAGE

   HYPERTENSION + HEART CONDITION
     ► Relationship must be STATED or IMPLIED
       ("due to hypertension" / "hypertensive")
     ► Without it: TWO SEPARATE CODES

   HYPERTENSION + BOTH
     ► A further combination category exists

   ──────────────────────────────────────────────────────────
   SAME PATIENT. SAME NOTE. DIFFERENT RULE PER ORGAN.
   ──────────────────────────────────────────────────────────

Why the asymmetry exists is worth a sentence, because it makes the rule memorable rather than arbitrary: the epidemiological relationship between hypertension and kidney disease is close enough that the classification is willing to assume it, and the relationship between hypertension and a given heart condition is not — many heart conditions have causes other than hypertension.

🎓 Exam Watch

This is the most reliable question in circulatory coding, and it is always built the same way: a scenario documents hypertension plus a heart condition with no stated relationship, and the distractor is the combination code.

Two separate codes. The relationship must be stated or implied for the heart.

Then the mirror: hypertension plus chronic kidney disease with no stated relationship, and the distractor is two separate codes. The combination code. The relationship is presumed.

If you learn one asymmetry in ICD-10-CM, learn this one. And verify the current guidance in Section I.C.9 — this is among the most-clarified passages in the document, and a description of it written at any point since 2015 may be describing a superseded version.

⚠️ Where Claims Die

Applying the kidney presumption to the heart.

A coder who learns "hypertension relationships are presumed" — a reasonable summary of the kidney rule — will apply it to heart conditions and assign a combination code the documentation does not support.

In a facility setting that changes the coded picture and can change the DRG (Chapter 33), which means an unsupported assumption becomes an overpayment. And it is exactly the kind of thing a risk-adjustment or DRG validation review is built to find, because the record either says "hypertensive" or it does not, and the reviewer can check in seconds.

The habit: when you see hypertension plus an organ condition, ask which organ before you ask anything else.

11.2 Myocardial infarction: initial, subsequent, and the four-week rule

A time rule that actually exists — unlike the chronic pain duration rule from Chapter 10 §10.9, which does not.

The rule

An acute myocardial infarction is coded as acute for a defined period from onset — the guidance uses four weeks (28 days). During that period the acute categories apply. After it, the infarction is no longer acute, and the classification has a code for an old myocardial infarction requiring no further care.

The three states

The subsequent-MI category is the one people miss. It exists specifically for a second infarction during the acute window of the first, and when it is used, both the subsequent MI code and the initial MI code are reported, with sequencing depending on the circumstances of the encounter.

And a documentation note: the acute MI categories distinguish infarctions by type and by site, and both come from the record. A record documenting only "MI" produces an unspecified code (Chapter 7 §7.9), and the specificity is frequently available in a cardiology note the coder has not opened.

The type distinction, and why it is not optional specificity

Contemporary cardiology distinguishes infarctions by mechanism, and the classification followed — adding categories that separate the infarction caused by an acute coronary event from infarctions arising from an imbalance between myocardial oxygen supply and demand, and from other mechanisms.

This matters to a coder for three reasons:

The classification asks the question, so the answer is codeable. Where the provider documents the type, there is a code for it, and using an unspecified code instead is §7.9's error.

The types are not clinically interchangeable, and the distinction affects how the record reads to every subsequent clinician.

And the documentation is frequently there. Cardiologists routinely document the type explicitly, because it drives management. The coder who codes from a hospitalist's summary rather than the cardiology consult will systematically miss it — which is Chapter 4 §4.3's point about reading the whole record, applied to a specific and common situation.

The four-week rule in practice

The rule sounds mechanical and generates one recurring question: what happens at an encounter after the acute period for a patient who is still being treated?

The answer is that the acute categories describe an acute infarction, and after four weeks the infarction is no longer acute — but the patient may still have ongoing ischemic heart disease, heart failure, or other conditions arising from it, and those are coded as what they are. The old infarction code identifies a healed infarction requiring no further care; it is a status-like statement, not a description of active disease.

The error to avoid: carrying an acute MI code forward on follow-up encounters because the patient "had an MI." The acute code describes an acute event within a window, and the window closes.

⚠️ Where Claims Die

The acute MI code that never expires.

A patient has an infarction in March. In September, a follow-up visit's claim still carries an acute myocardial infarction code, because it is on the problem list and nobody removed it.

Nothing rejects. The code is valid. The claim pays.

And the patient's record now describes six months of continuous acute myocardial infarction, their risk-adjustment picture is wrong in a direction that overstates burden (Chapter 10, Case Study 2's asymmetry), and the practice has a pattern in its data that is trivially visible to anyone looking.

This is the same failure mode as Chapter 12's seventh-character problem and Chapter 10's history code problem: a code that was correct once, carried forward past the point where it describes anything true, with no signal that anything is wrong.

11.3 Heart failure and its four axes

Heart failure is classified along axes that clinicians document unevenly.

The unspecified heart failure code exists and is used a great deal, and §7.9's four costs all apply — particularly the risk-adjustment cost, because heart failure specificity matters materially to a risk score (Chapter 36).

The interaction with §11.1 is the part to hold. Heart failure is one of the heart conditions where the hypertensive relationship must be stated or implied rather than presumed. So a note documenting "hypertension" and "heart failure" with no linking language produces two codes, not a combination — and a note documenting "hypertensive heart disease with heart failure" produces the combination category plus a code identifying the type of heart failure, because the combination code does not carry the type.

That second point is a general pattern worth naming: a combination code carries the relationship; it frequently does not carry the specificity, and the Tabular instructs an additional code. Chapter 10 §10.6 showed the same structure with diabetes and CKD stage.

The instructed codes nobody adds

A convention that recurs across both the circulatory and respiratory chapters and is systematically omitted: several categories carry "use additional code" instructions for tobacco status — exposure to environmental tobacco smoke, history of use, dependence, current use.

They cost nothing on a professional claim. They are instructed by the Tabular, which Chapter 8 §8.6 established is not optional. And they carry information that matters clinically, epidemiologically, and — in risk-bearing arrangements — financially.

The reason they are omitted is structural rather than careless: the instruction sits at the category level in the Tabular, and a coder who found the code through the index and did not go to step two never saw it. This is Chapter 8 §8.1's argument with a concrete casualty.

A practical test for your own work: pick the five circulatory or respiratory codes you assign most often, look each one up in the Tabular, and count the "use additional code" instructions you are currently not following. For most coders the answer is not zero.

11.4 Cerebrovascular disease and the deficits that outlive it

Three distinct situations that a single clinical history can produce, and they are coded entirely differently.

1. The acute event. An acute cerebral infarction is coded from the acute categories, with specificity by mechanism and site where documented.

2. The sequelae. Deficits remaining after the acute phase are coded from the sequelae category, with codes identifying the specific deficit — hemiplegia, aphasia, dysphagia, cognitive deficits — and the affected side.

3. History with no residual deficit. A patient who had a stroke and has no remaining deficits is coded with a personal history status code, not with a sequelae code and not with an acute code.

   ONE STROKE, THREE CODING SITUATIONS

   During the acute event ..................... acute infarction codes

   Deficits remain afterward .................. SEQUELAE category
                                                + a code for EACH deficit
                                                + laterality (dominant/
                                                  non-dominant side)

   No deficits remain ......................... PERSONAL HISTORY code

   ── AND THE TWO ERRORS ─────────────────────────────────────────
   Coding the acute infarction at a follow-up visit years later.
   Coding history when deficits are documented and being treated.

The dominant/non-dominant distinction is a real and frequently-missed specificity axis. Several deficit codes distinguish whether the affected side is the patient's dominant side, and the classification provides default rules where handedness is not documented. Read them — they are in Section I.C.6 and I.C.9 and they are the kind of detail that is invisible until you know it exists.

11.5 Respiratory: COPD, asthma, pneumonia, and respiratory failure

COPD and asthma

Both are classified with attention to exacerbation and infection status, and both carry Tabular instructions to code associated conditions.

J44.1 — COPD with acute exacerbation — is the combination code Chapter 7 used as an example and Chapter 33 will use for its DRG demonstration. The categories carry instructions about coding associated infections and about tobacco use and exposure, and those instructions are the part coders skip.

Asthma is classified by severity (intermittent, mild persistent, moderate persistent, severe persistent) and by status (uncomplicated, with exacerbation, with status asthmaticus). Clinicians document severity inconsistently, and the unspecified option carries §7.9's costs.

Respiratory failure — the sequencing rule

The rule that generates the most argument in respiratory coding.

Acute respiratory failure may be sequenced as the principal diagnosis when it is the condition chiefly responsible for the admission, and the guidance addresses what to do when respiratory failure and another acute condition are both present on admission.

The general shape:

• Respiratory failure occurring after admission is a secondary diagnosis.
• Respiratory failure present on admission and chiefly responsible for it may be principal.
• Where respiratory failure and another acute condition are equally responsible, the guidance addresses the selection, and chapter-specific sequencing rules elsewhere may direct otherwise — obstetrics, poisoning, HIV, and others all have their own priority rules.

This is a Chapter 33 problem as much as a Chapter 11 problem, because the answer changes the DRG. What matters here is knowing that the rule turns on why the patient was admitted, not on which condition is more severe — which is Chapter 9 §9.4's "after study" definition applied to a specific and common situation.

⚠️ Where Claims Die

Sequencing respiratory failure first because it sounds like the most serious thing.

It frequently is the most serious thing. That is not the test. The test is what, after study, was chiefly responsible for occasioning the admission — and a patient admitted for a COPD exacerbation who developed respiratory failure on day two has a different principal diagnosis from a patient brought in in respiratory failure.

The record distinguishes them and the coder has to read for it. "Present on admission" is not just an indicator to assign (Chapter 33 §33.7); it is a fact that changes the sequencing.

11.6 Digestive

Fewer trap conventions, and two patterns worth knowing.

Combination codes are common and specific. Many digestive conditions have codes carrying the condition plus a complication — with or without obstruction, with or without perforation, with or without bleeding. Where the record documents the complication, the combination code carries it, and a coder who assigns the plain code has lost specificity that was available.

Ulcers, diverticular disease, and hernias are the three families where this matters most, and in each the fourth or fifth character carries the complication. Read the category before assigning.

And the post-procedural distinction: the classification distinguishes conditions that are ordinary consequences of a procedure from those that are complications, and the difference requires provider documentation. A coder may not characterize an outcome as a complication because it seems like one — that is a clinical judgment (Chapter 4 §4.7), and it has consequences well beyond the code.

Why the complication distinction matters more than it looks

Three reasons, and the third is the one people do not anticipate.

It changes the code. The classification has distinct categories for postprocedural conditions, and several of them sit in the body-system chapters with their own instructional notes. A postprocedural hemorrhage and an ordinary expected drainage are different codes.

It changes the payment picture in a facility setting. Chapter 33 §33.7 covers present-on-admission indicators and hospital-acquired conditions; a condition documented as a complication of care that was not present on admission is treated differently from one that was.

And it is read by people who are not payers. A coded complication of a procedure appears in quality reporting, in a surgeon's outcome data, and — in some circumstances — in publicly reported measures. Coding a complication that the provider did not document as one attributes an outcome to a clinician on the strength of a coder's inference.

The rule, stated as a habit: if the record does not use the language of complication — "due to," "resulting from," "complication of," or an explicit statement — you do not have one. Where the clinical picture strongly suggests one and the documentation does not say, that is a query (Chapter 4 §4.9), and it is one of the more delicate queries a coder writes, because the answer implicates the clinician's own care.

📞 On the Phone

The complication query is the hardest conversation in diagnosis coding, and it is worth rehearsing.

What makes it hard: you are asking a surgeon whether an outcome was a complication of their own procedure. The question is legitimate, the answer matters, and the framing determines whether you get a real answer or a defensive one.

What not to write: "Was the bleeding a complication of the surgery?" It reads as an accusation, it invites a no, and it is also leading in the other direction — it proposes the conclusion rather than asking for one.

What works: present the documented facts and ask for the clinical relationship, exactly as any other query would:

The record documents a hemoglobin drop from 12.1 to 8.4 on postoperative day 1 and two units transfused. The assessment documents "blood loss." Based on your clinical judgment, please characterize the relationship between the blood loss and the procedure: ( ) expected intraoperative and postoperative blood loss ( ) postprocedural hemorrhage ( ) other — please specify ( ) clinically undetermined

Note the first option. A query that offers only "complication" and "other" is leading, and it is leading in the direction that is worse for the clinician — which makes it both improper and unlikely to be answered honestly. Offering the benign option first is not softening the query. It is what makes it a real question.

11.7 Musculoskeletal and the site/laterality burden

The chapter Account 10-4471's knee code lives in (Chapter 7 §7.2), and the one with the heaviest specificity demands in the book.

Nearly everything requires site and laterality, and many categories require more: which bone, which region, which joint, and — for some conditions — whether it is primary or secondary and post-traumatic or not.

Two conventions specific to this chapter:

The site convention. Where a condition affects multiple sites and the classification provides a multiple-site code, use it; where it does not, report each site. Which the classification provides varies by category, and this is Chapter 7 §7.7's laterality warning generalized: verify per category.

Pressure ulcers. Coded by site and stage, and this is one of the narrow places where a specific detail may be taken from documentation other than the provider's — a wound care nurse's staging is usable provided the provider has documented the pressure ulcer itself. Chapter 4 §4.3 gave the general form of that rule: another clinician may supply a detail; only the provider may supply the diagnosis.

The unstageable and the deep tissue injury categories exist for ulcers that cannot be staged, and they are not interchangeable with the unspecified-stage option. Read the distinctions.

They are three different statements:

This is Chapter 10 §10.4's neoplasm distinction in a different body system, and it is the same error: using the "cannot be determined" category when the coder cannot determine it. Unstageable is a clinical finding — the wound was looked at and its base was obscured. Unspecified means the record did not say.

Osteoarthritis, and where Account 10-4471 is eventually going

Chapter 7 §7.2 noted that osteoarthritis (M15–M19) and other joint disorders (M20–M25) are adjacent blocks, and that Account 10-4471's pain code sits in the second while the diagnosis Chapter 22 will eventually support sits in the first.

The osteoarthritis categories distinguish several axes at once, and it is worth knowing which because they are the specificity a definitive diagnosis makes available:

• Primary versus secondary versus post-traumatic — what caused it
• The joint — with laterality
• Generalized versus localized — how many joints
• Unilateral versus bilateral, where the category provides it

A diagnosis of "osteoarthritis of the knee" without more supports a less specific code than the categories can express, and this is the ordinary situation: the specificity exists in the classification and frequently not in the note.

Which is why the March 14 code is the right code for March 14. The provider explicitly declined to name a disease. When one is named, the classification is waiting with a block of codes asking four questions — and the answers will have to come from documentation that does not exist yet.

🔍 Check Your Understanding

1. A pressure ulcer's base is covered in eschar and cannot be visualized. Which category, and why is it not "unspecified stage"?
2. A postoperative hemoglobin drop and a transfusion are documented; the assessment says "blood loss." May you code a postprocedural hemorrhage?
3. Account 10-4471's knee code is in block M20–M25. Which block will Chapter 22's diagnosis sit in, and what has to happen first?

(Answers: 1. Unstageable — the stage cannot be determined because the base is obscured, which is a clinical finding. "Unspecified" means the record did not say. 2. No. The classification distinguishes an expected consequence from a complication and the difference requires provider documentation. This is a query, and the query must offer the benign option. 3. M15–M19, osteoarthritis — and what has to happen first is a definitive diagnosis, which the March 14 note explicitly declines to make.)

11.8 Genitourinary and CKD staging

The staging convention

Chronic kidney disease is classified by stage, with a distinct code for end stage renal disease.

The rule that matters: the stage comes from the provider's documentation, and where the record documents both a stage and end stage renal disease, the end stage code governs.

The three-convention collision

Chronic kidney disease is where three conventions from three chapters meet on one patient, and it is worth seeing them together because a real primary care note frequently triggers all three.

   ONE PATIENT WITH CKD — three conventions, three chapters

   1. DIABETES + CKD                     Chapter 10 §10.6
      ► "with" convention: relationship PRESUMED
      ► combination code + CKD stage code

   2. HYPERTENSION + CKD                 Chapter 11 §11.1
      ► relationship PRESUMED
      ► combination code + CKD stage code

   3. DIABETES + HYPERTENSION + CKD      both apply
      ► the classification provides for this
      ► read the Tabular instructions at BOTH categories

   AND IN EVERY CASE:
   ► the combination code carries the RELATIONSHIP
   ► an additional code carries the STAGE
   ► and Chapter 9 §9.3's ADDRESSED question still governs
     whether the CKD is reportable at this encounter at all

That last line is the one Account 10-4471 turns on, and it is why Chapter 9's two-question structure keeps recurring: the conventions tell you how to code conditions you are coding; Section IV tells you whether the second condition belongs on this claim.

Transplant status

A patient with a kidney transplant has a status code, and the classification distinguishes:

• Transplant status — the patient has a functioning transplant
• Transplant complication — something is wrong with the transplanted organ, which requires provider documentation that the condition affects the transplanted organ
• CKD after transplant — a patient may have chronic kidney disease and a transplant, and the guidance addresses that a transplant does not fully restore function; CKD is coded with the transplant status code, and this is not a complication.

That third bullet is the tested one. A patient with a functioning transplant and residual CKD does not have a transplant complication, and coding one is an error with real consequences in a facility setting.

11.9 Pregnancy, childbirth, and the puerperium

The chapter with a rule no other chapter has.

Priority

Chapter 15 codes have sequencing priority over codes from other chapters.

An obstetric patient's conditions are coded from chapter 15 where a chapter 15 code exists, regardless of the body system involved. A pregnant patient with a condition that would otherwise be coded from the circulatory chapter gets the obstetric code for that condition in pregnancy, sequenced first.

The exception that proves it: where the provider documents that a condition is not affecting the pregnancy, the guidance permits coding it from the other chapter — with a code indicating the pregnancy as an incidental state.

Trimesters

Most chapter 15 categories carry a trimester character, and the trimester is determined by the provider's documentation of the weeks of gestation at the time of the encounter, not by the coder's calculation from a due date.

The classification also provides a code identifying the weeks of gestation, reported as an additional code on most obstetric encounters.

The trimester is the trimester at the time of the encounter or admission, and for an admission spanning a trimester boundary, the guidance addresses which applies.

The fetus character

Chapter 7 §7.6 mentioned that the seventh character in this chapter means something entirely different. Here it is: it identifies which fetus a condition applies to in a multiple gestation — with a value for a single gestation or where the character does not apply, values for identified fetuses, and a value for other.

In a single gestation you still assign the character. It is not optional because there is only one fetus.

Outcome of delivery

A code identifying the outcome of delivery is reported on the maternal record when a delivery occurs. It is not reported on the newborn's record, and it is not reported on an antepartum encounter.

🎓 Exam Watch

Obstetric questions cluster around four things:

The priority rule. A pregnant patient with any condition — the obstetric code comes first unless the provider documents the pregnancy as incidental.

The trimester, determined from documented weeks of gestation at the encounter.

The seventh character, which identifies the fetus here and the episode of care in chapter 19. Candidates who learned A/D/S apply it here and are wrong.

The outcome of delivery code, on the maternal record only, when a delivery occurs.

11.10 Five harder charts, coded

[All constructed. Verify every code and every convention currently.]

Chart 1

"Essential hypertension. Chronic kidney disease, stage 4. Both stable on current therapy."

The reasoning. Hypertension plus CKD — the relationship is presumed (§11.1). Assign the hypertensive chronic kidney disease combination code plus the code for CKD stage 4. Two codes, no stated linkage required.

The trap: coding I10 and the CKD separately, on the reasoning that no linkage was documented. The classification does not need one here.

Chart 2

"Hypertension. Chronic systolic heart failure. No relationship stated between them."

The reasoning. Hypertension plus a heart condition with no stated or implied relationship — two separate codes (§11.1). Code the hypertension and code the heart failure with its type and acuity.

The trap: the combination code, applying the kidney presumption to the heart. This is Chart 1's mirror and the pair should be studied together.

Chart 3

"Patient admitted with COPD exacerbation. On hospital day 2 developed acute respiratory failure requiring intubation."

The reasoning. The respiratory failure occurred after admission, so it is a secondary diagnosis. The COPD exacerbation was chiefly responsible for the admission and is principal (§11.5, and Chapter 9 §9.4's "after study" definition).

The trap: sequencing the respiratory failure first because it is more severe. Severity is not the test.

Chart 4

"Follow-up, 14 months after cerebral infarction. Residual right-sided hemiplegia, right-handed patient. Also hypertension."

The reasoning. Not an acute infarction — that was 14 months ago. Code from the sequelae category, with a code identifying the hemiplegia and specifying the dominant side, since the patient is right-handed and the deficit is right-sided. Plus the hypertension.

The trap: coding the acute infarction. And the subtler one: missing the dominant/non-dominant specificity, which is documented right there in "right-handed."

Chart 5

"28 weeks gestation, single intrauterine pregnancy. Admitted with pyelonephritis."

The reasoning. Chapter 15 priority (§11.9). The infection is coded from the obstetric chapter as an infection of the genitourinary tract in pregnancy, with the trimester character reflecting 28 weeks, plus a code identifying the weeks of gestation, plus the seventh character for the fetus — assigned even though this is a single gestation. Plus a code for the pyelonephritis itself if the Tabular instructs it.

The trap: coding the pyelonephritis from the genitourinary chapter and adding a pregnancy code as an afterthought. Chapter 15 has priority, and the sequencing is the reverse of the intuition.

🗂️ The Encounter

🗂️ The Encounter

What this chapter contributes: the hypertension line, and why it is I10 and not something larger.

```text ACCOUNT 10-4471 — DIAGNOSIS C, under the circulatory conventions

THE NOTE SAYS Assessment 2: "Essential hypertension - at goal on current therapy. Continue lisinopril 20 mg daily. No change." Problem list: Chronic kidney disease, stage 3a Exam: BP 132/84. Cardiac exam documented: regular rate and rhythm, no murmur, NO PERIPHERAL EDEMA.

THE QUESTION §11.1 FORCES Hypertension is present. Is there organ involvement?

► HEART? No heart condition is documented anywhere in this note. The cardiac exam is documented and NORMAL. There is nothing to combine with. And even if there were, §11.1 requires a STATED or IMPLIED relationship for the heart.

► KIDNEY? THIS is the interesting one. Stage 3a chronic kidney disease IS on the problem list. And §11.1 says the hypertension-CKD relationship is PRESUMED -- no stated linkage needed.

So why is this coded I10?

► BECAUSE OF THE SAME PRIOR QUESTION AS THE DIABETES LINE.

Chapter 9 §9.3: report additional diagnoses that were
ADDRESSED, that affect treatment, or that require management
at this encounter. The assessment addresses hypertension,
diabetes, and hyperlipidemia. It does not address the kidney
disease.

The presumption in §11.1 tells you HOW to code hypertension
and CKD if you are coding both. It does not tell you WHETHER
the CKD belongs on this claim.

ASSIGN: I10. Essential (primary) hypertension. ```

This is the second time the same structure has decided a code on this file, and that repetition is deliberate. Chapter 9 resolved it for diabetes. Chapter 10 confirmed it in the endocrine chapter's own terms. Chapter 11 now finds it again in the circulatory chapter, with a different and stronger presumption available — and the answer is the same.

The pattern to carry: a linkage convention is an instruction about how to code two conditions together. It is never permission to code the second condition. Section IV decides that, and it decides it first.

What this settles. Diagnosis C. And a general rule, now demonstrated three times on one file.

What it does not settle. Whether the practice is leaving something on the table by never addressing the CKD. It is. Chapter 36 §36.7 owns that, and the fact that two separate conventions — the diabetes one and the hypertension one — would each have supported a more complete code makes the point sharper rather than softer.

Open questions: Q1, Q5, and Q6 remain open. Q2 remains partially resolved, and this chapter has now shown that the same analysis applies to diagnosis C for the same reason.

Conclusion

Six body systems, and the conventions that decide what the classification is willing to assume.

What was decided in this chapter. The hypertension asymmetry — presumed for kidney, stated or implied for heart — which is the most reliable question in circulatory coding and the most frequently misapplied convention in the book. The myocardial infarction time rule, which unlike the chronic pain rule genuinely exists, and the subsequent-MI category people miss. Heart failure's four axes and the general pattern that a combination code carries the relationship and frequently not the specificity. The three distinct situations one stroke produces — acute, sequelae, and history — and the dominant/non-dominant axis that is invisible until you know it exists. Respiratory failure sequencing, which turns on why the patient was admitted rather than on severity. The digestive combination codes and the rule that a coder may not characterize an outcome as a complication. Musculoskeletal's specificity burden, and the pressure ulcer rule where another clinician may supply a detail but only the provider may supply the diagnosis. CKD staging, and the three-convention collision where diabetes, hypertension, and Section IV's addressed question all meet on one patient. And obstetric priority — a rule no other chapter has — with trimesters from documented weeks, a seventh character that means something entirely different here, and an outcome-of-delivery code on the maternal record only.

What remains open. The chapters that follow different rules altogether.

The bridge to Chapter 12. Injuries, poisonings, external causes, symptoms, and the Z-codes. These are the chapters where the seventh character carries episode of care, where one table has four columns that are four different clinical events, where a code describes how something happened rather than what happened, and where a third of primary care lives in a chapter about people who are not sick. Chapter 12 closes Part II.

Key Terms

Hypertension table conventions — the asymmetry by which the classification presumes a causal relationship between hypertension and chronic kidney disease, and requires a stated or implied relationship between hypertension and a heart condition. (Ch.11)

MI initial and subsequent — an acute myocardial infarction is coded as acute for four weeks (28 days) from onset; a new infarction within that period is coded from the subsequent category, with both reported. (Ch.11)

Old myocardial infarction — a healed infarction after the acute period requiring no further care. (Ch.11)

Heart failure axes — type (systolic, diastolic, combined), acuity (acute, chronic, acute on chronic), cause or association, and other specified forms. (Ch.11)

Sequelae (cerebrovascular) — deficits remaining after the acute phase of a cerebrovascular event, coded from the sequelae category with a code for each deficit and, where applicable, the dominant/non-dominant side. (Ch.11)

Respiratory failure sequencing — acute respiratory failure may be principal when it is chiefly responsible for the admission; it is a secondary diagnosis when it develops after admission; and chapter-specific priority rules elsewhere may govern. (Ch.11)

CKD staging — chronic kidney disease classified by stage from the provider's documentation, with end stage renal disease governing where both are documented. (Ch.11)

Kidney transplant status versus complication — a functioning transplant with residual chronic kidney disease is coded with the CKD and the transplant status code and is not a transplant complication. (Ch.11)

Pressure ulcer staging — coded by site and stage; the stage may be taken from another clinician's documentation provided the provider documented the ulcer itself. (Ch.11)

Obstetric priority — chapter 15 codes take sequencing priority over codes from other chapters, unless the provider documents that the condition is not affecting the pregnancy. (Ch.11)

Obstetric trimester rules — most chapter 15 categories carry a trimester character determined by the provider's documented weeks of gestation at the encounter, with an additional code identifying the weeks. (Ch.11)

Outcome of delivery — a code reported on the maternal record when a delivery occurs. (Ch.11)

Underdosing — taking less of a medication than prescribed or instructed; a column of the Table of Drugs and Chemicals, developed in Chapter 12 §12.6. (Ch.11)

Spaced Review

1. A note documents hypertension and chronic systolic heart failure with no stated relationship. Then a second note documents hypertension and stage 4 chronic kidney disease with no stated relationship. Code both and explain why they differ.

2. (Chapter 9) Account 10-4471 documents hypertension, and the problem list carries stage 3a chronic kidney disease whose relationship to the hypertension would be presumed. Explain in two sentences why the code is I10.

3. A patient is admitted for pneumonia and develops acute respiratory failure on day three. Which is principal, and what rule decides it?

4. (Chapter 7) In ICD-10-CM chapter 15, what does the seventh character identify? How does that differ from chapter 19?

5. A patient with a functioning kidney transplant has documented stage 3 chronic kidney disease. Is this a transplant complication? Code it and explain.