How to Code a Condition That Is Both Acute and Chronic

When a patient presents with a condition that is simultaneously in an acute and chronic phase, ICD-10-CM requires you to assign a separate code for each phase rather than choosing one over the other. The acute code is sequenced first. This dual-coding rule applies across organ systems, from kidney disease to respiratory failure to heart failure, and getting it wrong has real consequences for reimbursement accuracy, severity reporting, and audit risk. The mechanics seem straightforward, but in practice they trip up coders and clinicians regularly because the documentation, the code structure, and the electronic health record do not always cooperate.

The Basic Rule and Why the Acute Code Comes First

The ICD-10-CM Official Guidelines for Coding and Reporting spell this out directly: if the same condition is described as both acute (or subacute) and chronic, and the classification provides distinct codes for each, you code both. The acute form gets sequenced before the chronic form. This is not a judgment call. It is a rule built into the classification’s structure.

The sequencing matters because the principal or first-listed diagnosis drives downstream decisions. In inpatient settings, the principal diagnosis is the primary factor in Medicare Severity Diagnosis Related Group (MS-DRG) assignment, which determines what the hospital gets paid. An acute condition typically signals higher severity and greater resource use than a chronic one. If you list only the chronic code when the patient is actually in an acute flare, the encounter looks less complex than it was, the DRG may understate severity, and the hospital absorbs costs it should have been reimbursed for. Conversely, listing only the acute code and dropping the chronic code means the patient’s ongoing burden of disease disappears from the record, which distorts risk adjustment and continuity of care.

The rule has a built-in exception: when ICD-10-CM provides a single combination code that captures both phases, you use that code alone rather than splitting the condition into two codes. Some conditions in the Tabular List have entries like “acute on chronic” already baked in. Acute-on-chronic respiratory failure (J96.20 through J96.22) is a good example. When a combination code exists, using it is mandatory, and adding the separate acute and chronic codes on top of it would be incorrect because you’d be double-counting the same clinical reality.

Heart Failure and the Complexity of Phase Coding

Heart failure is one of the conditions where acute-and-chronic coding matters most, both clinically and financially. A patient with longstanding chronic systolic heart failure who presents in an acute decompensation episode has two things going on that need separate representation. ICD-10-CM provides distinct codes for acute systolic heart failure, chronic systolic heart failure, and acute-on-chronic systolic heart failure, with parallel sets for diastolic and combined forms. The acute-on-chronic combination codes (like I50.21 for acute on chronic systolic heart failure) are the correct choice when the documentation supports both phases simultaneously.

Getting the code right has measurable consequences for data quality. A study validating ICD-10 heart failure codes in a national Medicare sample found that the positive predictive value for identifying an acute heart failure hospitalization was 98% when the heart failure diagnosis appeared in the first position, but dropped to 66% when it appeared in the first or second position combined.¹ That gap highlights how much the sequencing position of the code shapes what researchers and payers can infer from claims data. When the acute phase is documented clearly and coded in the principal position, the data reliably reflects what happened. When it is buried in a secondary position or coded ambiguously, a third of the time the encounter does not actually represent what the code suggests.

The same study found that systolic heart failure codes had a positive predictive value of 90% for identifying patients with ejection fractions of 50% or below, but that dropped to 72% for the stricter threshold of 40% or below.¹ The lesson for coders is that precise documentation of both the acuity (acute, chronic, or acute on chronic) and the type (systolic, diastolic, combined) directly influences whether the code accurately identifies the patient’s actual condition. When clinicians write “heart failure exacerbation” without specifying the type and chronicity, coders are left guessing, and the accuracy drops.

COPD Exacerbations and Misclassification

Chronic obstructive pulmonary disease is another condition where the acute-on-chronic distinction creates persistent coding headaches. A patient with stable chronic COPD who develops an acute exacerbation needs the exacerbation coded, and ICD-10-CM provides specific codes for COPD with acute exacerbation (J44.1) versus COPD without exacerbation (J44.1 versus J44.0). The acute exacerbation represents a worsening of symptoms beyond normal day-to-day variation, and it fundamentally changes the severity profile of the encounter.

Research into how accurately these codes capture reality paints a sobering picture. A study examining over 1,100 patients assigned COPD exacerbation codes found that only about 64% of them had a confirmed exacerbation on chart review.² Among the roughly 36% who were miscoded, common reasons included the patient not actually having obstructive spirometry to support a COPD diagnosis in the first place, or the admission being driven by something else entirely, such as progressive cancer, asthma, or cardiovascular disease. On the flip side, a broader search uncovered nearly 300 additional patients who genuinely had a COPD exacerbation but were missed by the exacerbation codes altogether.²

The coding errors run in both directions: overcoding exacerbations that did not happen, and undercoding exacerbations that did. For a condition that is both acute and chronic, this double failure matters because audit programs, quality metrics, and research datasets all rely on these codes to distinguish between a stable chronic patient and one in active crisis. If your documentation says “COPD flare” but the workup actually reveals decompensated heart failure as the driver, the exacerbation code is wrong regardless of how the patient’s lungs look on imaging.

Respiratory Failure and the Acute-on-Chronic Combination Codes

Respiratory failure is the clearest example of ICD-10-CM building the acute-on-chronic concept directly into its code structure. The system provides codes for acute respiratory failure (J96.0x), chronic respiratory failure (J96.1x), and acute-on-chronic respiratory failure (J96.2x), each with further specificity for hypoxia, hypercapnia, or both. When a patient with documented chronic respiratory failure develops an acute worsening, the acute-on-chronic combination code is the correct choice, and you do not code the acute and chronic forms separately.

Clinical documentation integrity programs have visibly influenced how these codes are used. An analysis spanning over a decade at multiple hospitals found that documentation of chronic respiratory failure increased significantly over time, as did documentation of acute respiratory failure, while documentation of ventilator dependence decreased.³ These shifts reflect deliberate efforts to capture what is actually happening to the patient. A patient on a ventilator because of acute-on-chronic respiratory failure is clinically different from a ventilator-dependent patient with chronic failure alone, and the documentation needs to reflect that distinction for the code to be correct.

The practical takeaway: when a combination code exists (as it does for respiratory failure), use it. Do not split the condition into separate acute and chronic codes. But when no combination code exists, as with many other conditions, the dual-coding approach applies.

Conditions Where Dual Coding Is Less Obvious

Heart failure, COPD, and respiratory failure get the most attention because they are common and financially significant. But the acute-plus-chronic rule applies across the classification. Kidney disease is a frequent example: a patient with chronic kidney disease who develops acute kidney injury has two distinct conditions that both need coding. ICD-10-CM does not provide a single “acute on chronic kidney disease” combination code the way it does for respiratory failure, so you assign the acute kidney injury code and the chronic kidney disease stage code separately, with the acute code sequenced first if it is the reason for the encounter.

Sinusitis, bronchitis, and certain types of pain conditions can also present in both acute and chronic forms simultaneously. The same logic applies: check whether a combination code exists in the Tabular List. If one does, use it. If not, assign both codes with the acute form sequenced ahead of the chronic form. The key is never to assume that one code covers both phases unless the code descriptor explicitly says so.

Pancreatitis is an instructive edge case. A patient with chronic pancreatitis who develops an acute episode gets both codes. But if the clinician documents “acute pancreatitis” alone, the coder cannot assume a chronic component exists just because the patient has a history of recurrent episodes. Coding is driven by what the provider documents for the current encounter, not by what the coder infers from the medical history. If the chronic component matters to care, the provider needs to say so.

Why Electronic Health Records Create Gaps

You might assume that a well-maintained electronic health record would make dual coding straightforward: the problem list carries the chronic condition, the encounter note captures the acute phase, and the coder puts them together. In reality, the two systems track conditions with surprisingly poor overlap. A study comparing chronic condition identification from encounter diagnoses versus problem lists found that the two sources agreed on only about 59% of chronic conditions identified.⁴ Roughly 12% of chronic conditions appeared only in encounter records, and about 28% appeared only on the problem list, never showing up in encounter diagnoses at all.

The agreement rate varied dramatically by condition. Diabetes had the highest overlap at about 84%, followed by HIV and hypertension in the mid-to-upper 70s. But sixteen conditions had less than 50% agreement between the two systems, including cancers and substance use disorders.⁴ For a coder trying to determine whether a patient in acute distress also has an underlying chronic form of the condition, these gaps are a real problem. If the chronic condition lives only on the problem list but was never addressed or documented in the current encounter, assigning the chronic code may not be supported. If it lives only in prior encounter records but fell off the problem list, the coder might not see it at all.

The practical implication is that coders cannot rely solely on the EHR’s automated suggestions or problem list entries. They need to check the provider’s clinical narrative for the current encounter. Does the note say “acute exacerbation of chronic condition X”? Does it describe the patient’s baseline chronic status? Without that explicit language, the coder has a documentation gap that needs a query rather than an assumption.

Common Coding Errors and How to Avoid Them

Several mistakes come up repeatedly in audits and quality reviews when conditions have both acute and chronic components:

• Defaulting to unspecified codes: When documentation clearly states “acute on chronic,” using an unspecified code (one that does not indicate acuity) wastes specificity that ICD-10-CM was designed to capture. Unspecified codes are for situations where the provider genuinely has not determined the nature of the condition, not for situations where the coder did not drill down to the right code.
• Using a combination code and separate codes together: If you assign the acute-on-chronic respiratory failure code, do not also assign separate acute and chronic respiratory failure codes. The combination code already captures both phases. Adding the others is redundant and can flag in audits as overcoding.
• Coding chronic conditions only when they are actively treated: Chronic conditions that affect the management of the patient during an acute visit should be coded even if they are not the primary focus of treatment. A diabetic patient admitted for acute heart failure still has diabetes affecting their care. If the chronic condition influences monitoring, medications, or treatment decisions, it belongs on the claim.
• Assuming acuity from context: A patient in the emergency department is not automatically “acute.” The acuity designation comes from the provider’s documentation, not from the care setting. An ED visit for medication management of a chronic condition is still a chronic condition encounter.
• Missing the chronic baseline after an acute event resolves: If a patient is admitted for acute kidney injury superimposed on chronic kidney disease, and the acute injury resolves during the stay, the chronic kidney disease code should still appear on the claim because it was present and managed throughout.

Clinical Documentation Queries

When the provider’s documentation is ambiguous about whether a condition is acute, chronic, or both, the coder’s tool is the clinical documentation query (CDQ), not a guess. A CDQ is a formal, compliant request to the provider asking them to clarify, add specificity, or confirm a clinical detail so the code assignment can be accurate. For dual-phase conditions, common query triggers include notes that say “heart failure” without specifying systolic or diastolic, acute or chronic; notes that mention “exacerbation” without naming the underlying chronic condition; and notes where the assessment lists a chronic condition but the clinical picture clearly suggests an acute worsening that the provider did not explicitly document.

Queries should be non-leading. Asking “Is this acute on chronic respiratory failure?” is acceptable. Asking “Please confirm this is acute on chronic respiratory failure so we can assign J96.21” is not, because it suggests the desired answer and the code. The goal is to get the provider to document what is clinically true, and the code follows from that documentation. Clinical documentation integrity programs have driven measurable changes in how thoroughly providers describe both the acute and chronic dimensions of conditions, as the respiratory failure documentation trends discussed earlier illustrate.³

What ICD-11 May Change

ICD-11, which the World Health Organization released in 2019 and which countries are adopting on varying timelines, introduces a structural feature that could simplify the acute-and-chronic coding problem. The new classification uses extension codes, which are add-on codes that provide additional detail about a diagnosis without requiring a separate standalone code. Among the capabilities extension codes offer is more precise specification of diagnosis timing, including whether a condition is acute, chronic, or in transition between the two.⁵

Under the ICD-10-CM system, the acute-or-chronic distinction has to be built into the code itself, meaning the classification needs to create separate code entries for every permutation. ICD-11’s extension code approach would let a single base code for a condition be modified with a timing extension, potentially eliminating the need to memorize which conditions have combination codes and which require dual coding. Whether this actually simplifies the coder’s workflow will depend on how EHR systems implement the extension code architecture and how thoroughly provider documentation supports the added specificity. For now, the ICD-10-CM rules remain in effect in the United States, and the dual-coding and combination-code framework is what coders need to master.

Risk Adjustment and Why Chronic Codes Cannot Be Dropped

In value-based payment models, a patient’s chronic conditions contribute to their risk score, which determines the expected cost of their care and, by extension, what the payer allocates for them. Hierarchical Condition Categories (HCCs) are the mechanism Medicare Advantage and other programs use for this calculation, and many chronic conditions map to HCCs that must be reported at least annually to maintain the patient’s risk profile.

When a coder focuses only on the acute reason for an encounter and drops the chronic conditions, those conditions may fall out of the risk adjustment model. This does not just affect the current claim; it can reduce the patient’s risk score for future periods, leading to underpayment for a patient who genuinely requires higher-than-average resources. The reverse problem also exists: coding chronic conditions that are not documented as actively managed or monitored during the encounter can be flagged as unsupported in a Risk Adjustment Data Validation (RADV) audit.

The balance point is straightforward in principle: code every condition, acute or chronic, that the provider documents as relevant to the encounter. If the provider addresses, manages, evaluates, monitors, or treats a chronic condition during a visit driven by an acute problem, that chronic condition belongs on the claim. If the provider does not mention it and it does not influence care, leave it off regardless of what the problem list says. The documentation is the foundation, and neither the coder’s clinical judgment nor the EHR’s automated suggestions can substitute for what the provider actually wrote.