Study guide
16.2 Integral Signs/Symptoms, the With Convention, and Uncertain Diagnoses
Certified Clinical Documentation Specialist CCDS
Track your progress as you read
Finished sections get a check mark.
1 Introduction & Exam Overview
1.1 Current Exam Facts 1.2 Eligibility Pathways and the 2,000-Hour Year 1.3 Allowed Resources and Test-Day Rules 1.4 Recertification, Fees, and How This Guide Maps the Eight Domains
2 IPPS Foundations
2.1 How IPPS Works and How CMS Updates It 2.2 MS-DRG Assignment, Relative Weights, and Grouping 2.3 Provider and Clinical Staff Documentation Duties under IPPS
3 Severity, CMI, Medical Necessity, and Oversight
3.1 CC versus MCC Recognition and CC Exclusion Lists 3.2 Case Mix Index and Why CDI Tracks It 3.3 Two-Midnight Rule, Medical Necessity of Setting, and Principal Diagnosis 3.4 MAC, RAC, CERT, OIG, and Denial-Vulnerable Practices
4 Nervous and Respiratory System CDI
4.1 Nervous System Conditions for CDI 4.2 Acute and Chronic Respiratory Failure, ABGs, and Ventilation Support 4.3 Pneumonia, COPD, PE, Pleural Effusion, and Respiratory Infections
5 Circulatory, Digestive, Hepatobiliary, Musculoskeletal, and Skin CDI
5.1 Circulatory Disorders 5.2 Digestive and Hepatobiliary Disorders 5.3 Musculoskeletal and Skin
6 Endocrine, Nutrition, Kidney, and Hematologic CDI
6.1 Diabetes, Dehydration, and Obesity 6.2 Malnutrition Criteria, Severity, and Audit Risk 6.3 AKI, CKD Staging, UTI, and Urinary Stones 6.4 Anemia, Coagulation, Sickle Cell, Lymphoma, and Leukemia
7 Infectious Disease, Other MDCs, and Clinical Indicator Tools
7.1 Sepsis, Severe Sepsis, Postoperative and Other Infections 7.2 Mental, Substance Use, Injuries/Toxicology, and HIV-Related Conditions 7.3 Medications, Diagnostic Tests, and Abbreviations as Clinical Indicators
8 Health Record Elements and Query Triggers
8.1 Which Record Elements Support Diagnosis and Procedure Codes 8.2 Attending versus Radiologist, Pathologist, and Other Providers 8.3 When a Physician Query Is Warranted 8.4 When Queries Are Not Appropriate
9 Query Timing, Verbal Queries, Formats, and Clinical Indicators
9.1 Concurrent, Retrospective, Pre-Bill, and Prospective Timing 9.2 Verbal Queries and Required Documentation 9.3 Open-Ended, Multiple-Choice, and Yes/No 9.4 Clinical Indicators and How to Source Them
10 Compliant Query Practice and Clinical Validation
10.1 Compliant versus Leading and Other Noncompliant Queries 10.2 ACDIS/AHIMA 2026 Guidelines for Achieving a Compliant Query Practice 10.3 Clinical Validation and Diagnoses without Clinical Support
11 CDI Program Metrics
11.1 Productivity, Query Volume, and Provider Response Rates 11.2 CMI, CC/MCC Capture, and High-Frequency DRGs 11.3 SOI/ROM as CDI Program Performance Metrics
12 Physician Metrics, PEPPER, Forecasting, and Public Data
12.1 Measuring Physician Documentation Performance 12.2 PEPPER, Forecasting, Hospital Financial Data, and Public Reporting
13 CDI Roles, Coder Collaboration, and Physician Education
13.1 Roles and Responsibilities of the CDI Specialist 13.2 Coder Roles Working with a CDI Department 13.3 Physician Education Tools, Forms, and Presentations
14 Provider Communication and DRG Reconciliation
14.1 Non-Confrontational Communication and When Verbal Beats Written 14.2 Working DRG versus Final DRG Reconciliation
15 Official Guidelines, Principal Diagnosis, and Secondary Diagnosis
15.1 Official Guidelines, Cooperating Parties, Updates, and AHA Coding Clinic 15.2 Principal Diagnosis Selection 15.3 Secondary Diagnosis Reporting Criteria
16 Sequencing, Coding Conventions, and POA Indicators
16.1 Sequencing When Two Diagnoses Equally Meet PD; Working DRG with Multiple Diagnoses 16.2 Integral Signs/Symptoms, the With Convention, and Uncertain Diagnoses 16.3 Present-on-Admission Indicator Assignment and Payment Impact
17 Hospital-Acquired Conditions, Disposition, and ICD-10-PCS Essentials
17.1 CMS Hospital-Acquired Condition Payment Provision 17.2 Discharge Disposition, Transfer Payment, Principal Procedure, and ICD-10-PCS Essentials
18 Ethics, Privacy, and Leading Queries as Compliance Failures
18.1 ACDIS Code of Ethics and CDI Goals beyond Reimbursement 18.2 HIPAA, Minimum Necessary, and Record Confidentiality 18.3 Leading Queries as a Compliance Failure
19 DRG Creep, OIG Oversight, PEPPER, and the False Claims Act
19.1 DRG Compliance, DRG Creep, and the OIG Work Plan 19.2 PEPPER Compliance Risks and the False Claims Act
20 Mortality Index, Observed-to-Expected Ratios, and Quality Data Sources
20.1 Documentation Impact on Mortality Index (SOI/ROM) 20.2 Mortality Reviews and Observed-to-Expected Ratios 20.3 Abstracted versus Claims-Based Quality Data
21 CMS Quality Programs, PSIs, and Infection versus Complication Codes
21.1 HVBP, HAC Reduction Program, HRRP, 30-Day Mortality, and Hospital IQR 21.2 PSI 90 Components and PSIs beyond the Composite 21.3 Healthcare-Associated Infections versus Complication Codes
16.2 Integral Signs/Symptoms, the With Convention, and Uncertain Diagnoses
Key Takeaways Explain This Topic AI
Signs and symptoms that are routinely integral to a diagnosed disease process are not assigned as additional codes unless the classification instructs otherwise
The words with and in in an ICD-10-CM Index entry or code title presume a causal relationship even without an explicit due-to statement, unless the record states the conditions are unrelated
A different Official Guideline can still require documented linkage (classic example: organ dysfunction with sepsis)
For inpatient discharges, diagnoses qualified as possible, probable, likely, suspected, or similar terms at the time of discharge are coded as if established, except for a named confirmed-only list (HIV, Zika virus disease, COVID-19, and influenza due to certain identified influenza viruses (categories J09 and J10)); that established-code rule also does not apply to outpatient encounters
The 2026 ACDIS/AHIMA query guidance directs specialists to use uncertain-diagnosis queries sparingly rather than querying every possible or probable statement to upgrade certainty
Last updated: September 2026
16.2 Integral Signs/Symptoms, the With Convention, and Uncertain Diagnoses
Quick Answer: Do not assign separate codes for integral signs and symptoms of a diagnosed disease. The words with and in in the ICD-10-CM Index or code title presume a causal relationship unless the record says the conditions are unrelated (or another guideline requires an explicit link). For inpatient discharges, possible / probable / likely (and similar) diagnoses documented at discharge are coded as if established . The 2026 ACDIS/AHIMA query guidance: use uncertain-diagnosis queries sparingly .
This independent ExamFinch teaching follows the ICD-10-CM Official Guidelines for Coding and Reporting and the August 2026 ACDIS/AHIMA Guidelines for Achieving a Compliant Query Practice . It is not an official ACDIS, AHIMA, or Cooperating Parties publication.
Integral signs and symptoms: when not to add a code
ICD-10-CM allows signs and symptoms when a related definitive diagnosis has not been established . Once a definitive diagnosis is established, signs and symptoms that are routinely associated with that disease process are not assigned as additional codes, unless the classification specifically says to add them.
Integral means the finding is part of how that disease presents, not a separately reportable problem. Typical inpatient examples:
Cough, fever, and leukocytosis with pneumonia (unless a guideline or note tells you to code a specific associated condition).
Chest pain that is the presenting symptom of acute coronary syndrome or unstable angina once that diagnosis is established.
Dyspnea that is the expected manifestation of the acute respiratory failure or pulmonary edema already being coded as the disease process.
Nausea with acute gastroenteritis when it is not evaluated or treated as a separate condition.
Not integral means the finding is not routinely part of the disease, or the classification/UHDDS treats it as its own reportable condition because it was evaluated, treated, monitored, or prolonged the stay. Examples CDI actually sees:
Hyponatremia that is repleted, worked up, and named as a problem in a patient who also has pneumonia. Hyponatremia is not “just pneumonia.” If it meets UHDDS secondary criteria, it is eligible as an additional diagnosis (clinical validation still applies).
Acute kidney injury in a patient admitted for decompensated heart failure, when the kidney injury is identified, monitored, and treated—not assumed to be “just heart failure.”
Ileus after surgery when it is more than the expected brief postoperative bowel quietness and is documented as a condition requiring treatment.
A symptom that points to a different process than the established diagnosis (for example, new focal neurologic findings in a patient whose PD is pneumonia).
The trap on CCDS items is coding every abnormal vital sign or lab as a secondary diagnosis “for severity.” Integral findings do not become CCs by being repeated in every note. Conversely, withholding a non-integral condition that was treated, just because a bigger diagnosis is present, under-reports the stay. Ask: is this finding routine to the disease , or is it a distinct problem the team managed?
If a code title or instructional note says to use an additional code for a manifestation or associated condition, follow the classification even if the finding feels clinically “part of” the disease. The Tabular List can override the general integral-symptom habit.
The with / in convention: presumed causal relationship
Section I.A.15 of the Official Guidelines (the “with” convention) is a high-yield CDI rule. The word with or in should be interpreted as associated with or due to when it appears in a code title , the Alphabetic Index , or an instructional note in the Tabular List. The classification presumes a causal relationship between the two conditions linked by those terms. Those conditions are coded as related even without provider documentation that explicitly says “due to” or “secondary to,” unless :
the documentation clearly states the conditions are unrelated , or
another guideline specifically requires a documented linkage between the two conditions.
In the Index, with is listed immediately after the main term (not in alphabetical order among subterms). CDI specialists who only skim progress notes for the phrase “due to” will undercode combination codes the classification already considers related.
Classic applications
Diabetes with stated manifestations in the Index. Type 2 diabetes with chronic kidney disease is a combination (or combination-plus-additional-code) situation because the Index links diabetes with CKD via with . You do not need “diabetic nephropathy” verbatim if both conditions are diagnosed and nothing says they are unrelated.
Hypertension with heart or kidney involvement. The classification links hypertension with heart disease and hypertension with chronic kidney disease through with in the Index. Hypertensive heart disease and hypertensive CKD concepts follow that presumption unless the provider documents that the heart or kidney disease is unrelated to hypertension.
Other Index-linked pairs. Many “X with Y” Index lines (for example, certain infection-with-organism constructions, or disease-with-complication constructions) work the same way: the presumed relationship lives in the classification , not in a required causal sentence.
When you must not presume
Unrelated is documented. Nephrology states chronic kidney disease is due to longstanding hypertension and is not diabetic kidney disease, despite coexisting type 2 diabetes. Do not assign the diabetes-with-CKD combination. Code the conditions as the record describes them.
Another guideline requires linkage. The sepsis guideline is the example CDI must not flatten into the with convention. Severe sepsis in ICD-10-CM requires organ dysfunction linked to sepsis (R65.2- category logic). If acute kidney injury or respiratory failure is attributed to another cause (for example, contrast nephropathy or flash pulmonary edema from systolic failure) and is not associated with the sepsis, you do not build severe sepsis from a silent “with.” That is a documented association rule, not a with-convention shortcut.
The Index never linked them. Two conditions appearing in the same note are not related just because both are serious. Atrial fibrillation and community-acquired pneumonia are not a with pair unless the classification or the provider creates that link. Do not invent etiology.
The documentation is unclear whether they are related. Then the correct move is often a nonleading query , not a silent presumption and not a silent refusal to use the combination. The with convention applies when the Index/title supplies the link and the record does not contradict it. If the record is ambiguous about relatedness , query rather than guessing.
Situation Code as related via with/in? Why
Both conditions diagnosed; Index links them with with ; record silent on cause Yes Classification presumes the relationship
Provider documents the conditions are unrelated No Explicit contradiction overrides the presumption
Sepsis plus organ failure not tied to the sepsis No (for severe sepsis) Chapter-specific guideline requires association
- Two conditions, no Index/title with or in link No No presumed causal relationship
- Relatedness unclear after reading the record Query Do not guess either direction
Compliant queries on relatedness must remain nonleading , cite clinical indicators , and avoid reimbursement language. Multiple-choice relatedness queries still need a clinically valid option plus an open-ended Other, please specify path under the 2026 query guidance. Yes/no format is appropriate for cause-and-effect between conditions already documented , not for introducing a new diagnosis.
Uncertain diagnoses at inpatient discharge
If the diagnosis documented at the time of discharge is qualified as probable , suspected , likely , questionable , possible , still to be ruled out , compatible with , consistent with , or similar terms , code the condition as if it existed or was established . This uncertain-diagnosis guideline applies to inpatient admissions to short-term acute, long-term care, and psychiatric hospitals. It does not apply to outpatient encounters (including ED visits that do not become inpatient, clinic, and same-day surgery without inpatient admission).
Code it: Discharge summary: “probable aspiration pneumonia; treat with a full antibiotic course.” For an inpatient claim, assign aspiration pneumonia as if established (with correct POA, covered in 16.3).
Do not code it as established: The same “possible pneumonia” statement on an ED encounter that ends in discharge home. Outpatient coding reports confirmed diagnoses, not possible ones.
Do not code it: “ Ruled out pulmonary embolism.” Ruled out is the opposite of uncertain-but-still-in-play. Do not assign the PE code.
Discharge timing matters. The guideline is anchored to documentation at discharge , not to every mid-stay hedge. A day-2 note that says “possible UTI” does not force a UTI code if the discharge summary and hospital course rule it out or never establish it. Conversely, a discharge diagnosis of probable CVA is coded as CVA even if some earlier notes were cautious. Read the discharge diagnostic statement in light of the whole record.
Conflict is different from uncertainty. One attending says possible colitis; the consultant says there is no colitis and imaging is normal. That is a conflict (and often a clinical-validation issue), not a clean probable diagnosis. Query rather than picking the code that helps the working DRG.
Confirmed-only exceptions to the uncertain-diagnosis rule
The discharge-uncertainty rule above is not universal. The ICD-10-CM Official Guidelines name a short, specific list of conditions where the opposite rule applies: code only a confirmed diagnosis , and a hedge word does not support the confirmed code. Section II.H itself contains no list; four chapter-specific guidelines each state that they are an exception to it, with the same wording in the FY 2026 guidelines and the FY 2027 guidelines effective October 1, 2026: HIV infection/illness , Zika virus disease (A92.5) , COVID-19 (U07.1) , and influenza due to certain identified influenza viruses —avian or other novel influenza A (category J09 ) and other identified, non-novel influenza virus (category J10 ).
Condition Confirmed code If the provider documents only “suspected/possible/probable”
Zika virus disease A92.5 Do not assign A92.5; code the presenting signs/symptoms or Z20.821 (contact with and suspected exposure to Zika virus)
COVID-19 U07.1 Do not assign U07.1 (the same applies to “inconclusive” COVID-19); code the signs and symptoms reported, adding Z20.822 (contact with and (suspected) exposure to COVID-19) when an actual or suspected exposure is documented
Avian or other novel influenza A J09 Do not assign J09; assign J11 (influenza due to unidentified influenza virus) instead
Other identified, non-novel influenza virus J10 Do not assign J10; assign J11 instead
HIV follows the same confirmed-only principle without a single substitute code: a provider statement of “suspected” or “possible” HIV does not support B20 . Code the presenting illness, reserve R75 for documentation that specifically describes inconclusive HIV serology, and use Z21 only when asymptomatic HIV-positive status is itself confirmed—not merely suspected.
For all four exceptions, “confirmation” is a documentation , not a laboratory , threshold: the provider’s own diagnostic statement that the condition is confirmed is enough, and a positive test result is not required on the chart. The reverse also holds: a positive COVID-19 test in an asymptomatic patient with no provider diagnosis is not coded as U07.1 on its own; the guidelines direct a query to the provider. The trap runs opposite to most of this exam’s uncertain-diagnosis teaching: everywhere else, a hedge word at discharge still earns the established code; for this named list, the same hedge word blocks it. Do not extend the exception by analogy—probable sepsis, probable Clostridioides difficile infection, and other conditions outside this list still follow the general Section II.H rule taught above.
2026 brief: uncertain-diagnosis queries used sparingly
The 2026 ACDIS/AHIMA Guidelines for Achieving a Compliant Query Practice (August 2026; supersedes 2022) still require nonleading queries with sourced clinical indicators and no reimbursement or quality-outcome language. On uncertain diagnoses , the practical brief for CCDS candidates is: use uncertain-diagnosis queries sparingly .
That means:
If the provider already documented possible/probable/likely pneumonia at discharge , the inpatient guideline already tells coding to report pneumonia. A query whose only goal is to upgrade “probable” to “confirmed” so the record “looks better” is usually unnecessary and can become leading if it pressures certainty the clinician does not have.
Query when uncertainty is not the real problem : conflicting statements (possible versus ruled out), a diagnosis that lacks clinical support (clinical validation), missing POA, or an Index-relatedness question the with convention cannot settle.
Do not use a yes/no query to introduce a new diagnosis that was never documented. Yes/no may not introduce a new diagnosis under the 2026 guidance.
If you do query an uncertain diagnostic statement, keep the provider’s independent judgment . Multiple-choice should include Other, please specify . Clinical-validation queries should allow ruled-out / no longer valid / confirmed with support / alternative diagnosis pathways.
Integral symptoms, the with convention, and uncertain diagnoses travel together on the exam because all three are classification rules that CDI cannot override with a preference for extra codes, extra certainty, or extra payment. Apply the rule in front of you: omit the integral symptom, honor the Index with unless unrelated is stated, code the inpatient probable diagnosis, and rarely query solely to erase a compliant uncertainty qualifier.