Provider documentation often includes phrases that sound clinically meaningful but do not give coders enough support to assign a causal relationship. One common example is “in the setting of.”
You may see documentation such as:
“Shortness of breath in the setting of CHF.”
Or:
“Acute kidney injury in the setting of sepsis.”
The phrase may suggest clinical context. It may show that two conditions are present at the same time. It may even point to a possible relationship. For coding purposes, though, “in the setting of” does not automatically mean one condition caused the other.
That distinction matters. A coder should not assume causation unless the provider clearly documents the relationship or the ICD-10-CM classification gives specific direction. The official ICD-10-CM guidelines are intended to work with the Tabular List and Alphabetic Index, and the classification instructions take precedence when assigning codes.
What Does “In the Setting Of” Mean?
In medical coding, “in the setting of” usually means one condition exists within the clinical context of another condition.
It may point to:
- A coexisting condition
- A clinical circumstance surrounding another diagnosis
- A possible association
- A condition that influenced the patient’s care
It does not prove a cause-and-effect relationship.
That means coders should pause before linking the two diagnoses. The documentation must support the code assignment, especially when the relationship changes:
- Code selection
- Sequencing
- Severity reporting
- Risk adjustment
- Payment
- Compliance exposure
Why Coders Should Not Assume Causality
A phrase like “in the setting of” is less direct than terms such as:
- Due to
- Secondary to
- Caused by
- Related to
- Associated with (when supported by coding guidance)
- With (when the ICD-10-CM classification allows a presumed linkage)
For example, if the provider documents:
“Shortness of breath in the setting of CHF”
the coder should not automatically code the shortness of breath as caused by CHF. Unless the provider documents a causal relationship or the ICD-10-CM guidelines support a presumed link, the conditions should be coded based on the documentation available.
A clearer statement would be:
“Shortness of breath due to acute on chronic systolic heart failure.”
That wording supports a direct relationship. “In the setting of” alone does not.
When Combination Codes May Be Appropriate
Some ICD-10-CM categories allow coders to presume a relationship between conditions when the classification supports that link.
Common examples include certain conditions involving:
- Diabetes and documented complications
- Hypertension with heart disease
- Hypertension with chronic kidney disease
- Sepsis with documented acute organ dysfunction, when all required documentation is present
The key is not the phrase alone. The key is whether the:
- Official coding guidance
- Alphabetic Index
- Tabular List
- Provider documentation
support the relationship.
Example
“Acute kidney injury in the setting of sepsis”
This statement may not be enough by itself to assign sepsis-related organ dysfunction.
If the provider documents sepsis with AKI, coding may include:
- A41.9 — Sepsis, unspecified organism
- N17.9 — Acute kidney failure, unspecified
The coder must also follow:
- Sepsis sequencing rules
- Payer requirements
- Facility-specific coding policies
For current coding guidance, review the official CMS ICD-10-CM resources:
Sequencing Depends on the Reason for the Encounter
When one diagnosis appears “in the setting of” another, sequencing depends on:
- The reason for the encounter
- The condition chiefly responsible for the admission or visit
For inpatient coding, the principal diagnosis is selected according to the condition established after study as chiefly responsible for the admission.
Example
“Chest pain in the setting of GERD”
If the visit is for chest pain and the provider does not state that GERD caused the chest pain, the coder may assign:
- The chest pain code first
- GERD as an additional diagnosis when supported
However, if the provider documents:
“Chest pain due to GERD”
then the coding and sequencing may change because the causal relationship is clearer.
When a Provider Query Is Needed
A provider query may be appropriate when the phrase “in the setting of” leaves the record unclear and the answer would affect coding.
A Query May Be Needed When:
- The relationship changes code selection
- The relationship affects sequencing
- The documentation supports clinical concern but not coding clarity
- The diagnosis needs more specificity
- Present on admission (POA) status is unclear
- Severity, acuity, or cause needs clarification
Example
“Respiratory failure in the setting of pneumonia”
A coder or CDI specialist may need clarification on:
- Acute, chronic, or acute-on-chronic respiratory failure
- Whether respiratory failure was due to pneumonia
- Whether the condition was present on admission
- Whether another condition contributed
The FY 2026 ICD-10-CM guidelines note that when documentation is unclear for present-on-admission reporting, it is appropriate to query the provider for clarification.
Coding Takeaways for “In the Setting Of”
Treat the Phrase as Context, Not Causation
“In the setting of” tells the coder that one condition occurred within the clinical context of another. It does not prove causation.
Code Each Condition Separately Unless the Record Supports a Link
Do not assign a causal relationship unless:
- The provider documents it clearly, or
- ICD-10-CM guidance allows it
Use Direct Linking Language When Needed
Terms such as:
- Due to
- Caused by
- Secondary to
- Related to
provide stronger support when a code requires a cause-and-effect relationship.
Query When the Answer Matters
If the unclear relationship affects:
- Reimbursement
- Risk adjustment
- Sequencing
- Reporting
- Severity
- Compliance
a compliant provider query can protect both the record and the organization.
Final Thought
“In the setting of” is useful clinical language, but it can create coding risk when treated as a confirmed link. Coders should read the full record, apply ICD-10-CM guidance, and query the provider when the documentation does not clearly support the code assignment.
Clear documentation protects:
- The claim
- The patient record
- The organization
When wording leaves room for interpretation, the safest path is to clarify before coding the relationship.
References
- CMS, FY 2026 ICD-10-CM Coding Guidelines
- CMS, ICD-10-CM Files and Coding Resources
- CDC, ICD-10-CM Official Guidelines for Coding and Reporting
- ACDIS, “In the Setting Of… Does This Link the Conditions?” October 2017
By Andria Hedrick, CCS, CPC | Facility Quality Auditor, Health Information Partners