0DP0XDZRemoval of Intraluminal Device from Upper Intestinal Tract, External Approach
- Billable / Specific Code
0DP0XDZ is a billable ICD-10-PCS procedure code for Removal of Intraluminal Device from Upper Intestinal Tract, External Approach. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Removal involves taking out or off a device from a body part.
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 | P | Removal |
| 4 | BodyPart | 0 | Upper Intestinal Tract |
| 5 | Approach | X | External |
| 6 | Device | D | Intraluminal Device |
| 7 | Qualifier | Z | No Qualifier |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 0DP0XDZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 0DP0XDZ
Is 0DP0XDZ a billable code?
Yes. 0DP0XDZ is a complete seven-character ICD-10-PCS code, specific enough to report Removal of Intraluminal Device from Upper Intestinal Tract, External Approach on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 0DP0XDZ mean?
0DP0XDZ 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 P is the Operation (Removal); the 4th character 0 is the BodyPart (Upper Intestinal Tract); the 5th character X is the Approach (External); the 6th character D is the Device (Intraluminal Device); the 7th character Z is the Qualifier (No Qualifier).
What is the ICD-9-PCS equivalent of 0DP0XDZ?
Under the General Equivalence Mappings, Removal of Intraluminal Device from Upper Intestinal Tract, External Approach crosswalks to ICD-9-PCS 97.59. The mapping is approximate, so confirm it fits the documentation.
