Should respiratory distress syndrome (RDS) and respiratory failure be coded together? Since coding guidelines changed the relationship between these diagnoses from an Excludes 1 note to an Excludes 2 note, many coders have begun reporting both conditions together. However, whether both diagnoses should be coded depends on documentation and clinical circumstances.
The coding guidelines now allow both conditions to be reported together when documentation supports two distinct diagnoses. Understanding when dual coding is appropriate—and when it is not—is critical for coding accuracy, denial prevention, and audit readiness.
Understanding the Coding Guideline Change
The Excludes 1 note for RDS and respiratory failure was converted to an Excludes 2 note. This means it is acceptable to report both conditions together if the documentation supports two separate clinical conditions.
However, respiratory distress syndrome and respiratory failure are generally not coded together because respiratory failure is considered inherent (integral) to severe RDS.
You do not code a symptom or condition that is an integral part of a diagnosed disease. In neonatal coding, RDS already implies impaired gas exchange. Therefore, P22.0 (Neonatal RDS) typically includes respiratory failure, making the additional assignment of P28.5 (Respiratory failure of newborn) redundant in many cases.
When Not to Code Both Conditions
Do Not Code Respiratory Failure with RDS When:
- It represents the expected progression of RDS.
- There is no separate provider documentation identifying respiratory failure as a distinct condition.
- There is no additional clinical significance beyond typical RDS severity.
When You May Code Both Conditions
You may report both diagnoses when the provider explicitly documents respiratory failure as a separate diagnosis and it is clinically significant beyond typical RDS.
Examples include:
- Severe or prolonged ventilation beyond the expected course.
- Unexpected clinical deterioration.
- A separate contributing etiology, such as sepsis in addition to RDS.
How Improper Coding Leads to Denials
Coding RDS and respiratory failure together without sufficient clinical support can become a major denial trigger.
The following best practices can help reduce denial risk.
1. Ensure Strong Provider Documentation
Denials frequently occur when documentation does not adequately support the diagnosis.
Documentation Elements That Should Be Present
- Gestational age (prematurity)
- Onset shortly after birth
- Clinical signs such as:
- Tachypnea
- Retractions
- Grunting
- Chest X-ray findings:
- Ground-glass appearance
- Air bronchograms
- Treatment provided:
- CPAP
- Surfactant
- Oxygen therapy
If key elements are missing, consider querying the provider before coding.
2. Use the Most Specific ICD-10-CM Code
Appropriate Code
P22.0 – Respiratory Distress Syndrome of Newborn
Additional Supporting Codes When Applicable
- Prematurity codes (P07.2–P07.3)
- Birth weight and gestational age codes
These additional codes can strengthen medical necessity and support claim accuracy.
3. Avoid Double Coding
Common Denial Scenario
Coding:
- P22.0 (Respiratory Distress Syndrome)
- P28.5 (Respiratory Failure of Newborn)
without clear documentation supporting two distinct conditions.
Best Practice
Do not code respiratory failure unless:
- The provider clearly documents it as a separate diagnosis, or
- It is clinically distinct and significant.
Otherwise, payers may consider the diagnosis duplicative or inherent to RDS.
4. Differentiate RDS from Similar Conditions
Misclassification can lead to denials and coding inaccuracies.
Ensure documentation clearly supports RDS rather than another neonatal respiratory condition.
| Condition | Coding Consideration |
|---|---|
| TTN (P22.1) | Typically mild, resolves quickly, normal lung volumes |
| Meconium Aspiration (P24.0) | Usually term or post-term infants, patchy infiltrates |
| Neonatal Pneumonia (P23.x) | Supported by evidence of infection |
5. Link the Diagnosis to Treatment
Payers often review whether the documented severity aligns with the interventions provided.
Strong Documentation Examples
- RDS + CPAP
- RDS + Surfactant therapy
- RDS + Mechanical ventilation
These combinations generally demonstrate clinical severity and support medical necessity.
Weak Documentation
Documentation lacking treatment correlation may increase denial risk.
6. Pay Attention to Timing
RDS typically develops shortly after birth.
If documentation identifies RDS later in the clinical course without clear continuity, payers may question the diagnosis.
Clarify timing with the provider whenever documentation is unclear.
7. Query Ambiguous Documentation
Consider a provider query when documentation includes:
- “Respiratory distress” without confirmed RDS
- Mixed diagnoses such as TTN versus RDS
- References to respiratory failure without diagnostic clarity
8. Audit-Proof Your Coding
Before final code assignment, confirm:
- RDS is clearly diagnosed.
- Clinical indicators are documented.
- Chest X-ray findings support the diagnosis.
- Treatment aligns with disease severity.
- No redundant codes are reported.
Final Denial Prevention Checklist
Before claim submission, verify:
- Radiologic confirmation is documented.
- Prematurity or other risk factors are documented.
- Documentation supports RDS rather than generic respiratory distress.
- Alternative diagnoses such as TTN have been appropriately differentiated.
- Respiratory failure is coded only when separately supported.
Conclusion
While coding guidelines now permit reporting respiratory distress syndrome and respiratory failure together under certain circumstances, coders should not assume both diagnoses are automatically reportable. The key is determining whether respiratory failure represents a clinically distinct condition supported by provider documentation and clinical evidence.
Careful review of documentation, diagnostic findings, treatment, and clinical significance can help reduce denial risk while supporting accurate neonatal coding and compliance.
References
- 2026 ICD-10-CM Official Coding Guidelines
- Coding Clinic, Second Quarter 2019, Page 29
By Andria Hedrick, CCS, CPC | Facility Quality Auditor, Health Information Partners