0DNF7ZZRelease Right Large Intestine, Via Natural or Artificial Opening
- Billable / Specific Code
0DNF7ZZ is a billable ICD-10-PCS procedure code for Release Right Large Intestine, Via Natural or Artificial Opening. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Release involves freeing a body part from an abnormal physical constraint by cutting or by the use of force.
Code Identity
PCS Table Breakdown
Each ICD-10-PCS code is built from seven characters, each an axis of the procedure. Hover or tap the icons for the official CMS definitions.
| Position | Designation | Value | Meaning |
|---|---|---|---|
| 1 | Section | 0 | Medical and Surgical |
| 2 | Body System | D | Gastrointestinal System |
| 3 | Operation | N | Release |
| 4 | BodyPart | F | Large Intestine, Right |
| 5 | Approach | 7 | Via Natural or Artificial Opening |
| 6 | Device | Z | No Device |
| 7 | Qualifier | Z | No Qualifier |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 0DNF7ZZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 0DNF7ZZ
Is 0DNF7ZZ a billable code?
Yes. 0DNF7ZZ is a complete seven-character ICD-10-PCS code, specific enough to report Release Right Large Intestine, Via Natural or Artificial Opening on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 0DNF7ZZ mean?
0DNF7ZZ breaks down character by character: the 1st character 0 is the Section (Medical and Surgical); the 2nd character D is the Body System (Gastrointestinal System); the 3rd character N is the Operation (Release); the 4th character F is the BodyPart (Large Intestine, Right); the 5th character 7 is the Approach (Via Natural or Artificial Opening); the 6th character Z is the Device (No Device); the 7th character Z is the Qualifier (No Qualifier).
What is the ICD-9-PCS equivalent of 0DNF7ZZ?
Under the General Equivalence Mappings, Release Right Large Intestine, Via Natural or Artificial Opening crosswalks to ICD-9-PCS 96.24. The mapping is approximate, so confirm it fits the documentation.
