0DH50DZInsertion of Intraluminal Device into Esophagus, Open Approach
- Billable / Specific Code
0DH50DZ is a billable ICD-10-PCS procedure code for Insertion of Intraluminal Device into Esophagus, Open Approach. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Insertion involves putting in a nonbiological appliance that monitors, assists, performs, or prevents a physiological function but does not physically take the place of 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 | H | Insertion |
| 4 | BodyPart | 5 | Esophagus |
| 5 | Approach | 0 | Open |
| 6 | Device | D | Intraluminal Device |
| 7 | Qualifier | Z | No Qualifier |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 0DH50DZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 0DH50DZ
Is 0DH50DZ a billable code?
Yes. 0DH50DZ is a complete seven-character ICD-10-PCS code, specific enough to report Insertion of Intraluminal Device into Esophagus, Open Approach on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 0DH50DZ mean?
0DH50DZ 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 H is the Operation (Insertion); the 4th character 5 is the BodyPart (Esophagus); the 5th character 0 is the Approach (Open); 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 0DH50DZ?
Under the General Equivalence Mappings, Insertion of Intraluminal Device into Esophagus, Open Approach crosswalks to ICD-9-PCS 42.81. The mapping is approximate, so confirm it fits the documentation.
