0DL44ZZOcclusion of Esophagogastric Junction, Percutaneous Endoscopic Approach
- Billable / Specific Code
0DL44ZZ is a billable ICD-10-PCS procedure code for Occlusion of Esophagogastric Junction, Percutaneous Endoscopic Approach. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Occlusion involves completely closing an orifice or the lumen of a tubular 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 | L | Occlusion |
| 4 | BodyPart | 4 | Esophagogastric Junction |
| 5 | Approach | 4 | Percutaneous Endoscopic |
| 6 | Device | Z | No Device |
| 7 | Qualifier | Z | No Qualifier |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 0DL44ZZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 0DL44ZZ
Is 0DL44ZZ a billable code?
Yes. 0DL44ZZ is a complete seven-character ICD-10-PCS code, specific enough to report Occlusion of Esophagogastric Junction, Percutaneous Endoscopic Approach on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 0DL44ZZ mean?
0DL44ZZ 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 L is the Operation (Occlusion); the 4th character 4 is the BodyPart (Esophagogastric Junction); the 5th character 4 is the Approach (Percutaneous Endoscopic); 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 0DL44ZZ?
Under the General Equivalence Mappings, Occlusion of Esophagogastric Junction, Percutaneous Endoscopic Approach crosswalks to ICD-9-PCS 42.99. The mapping is approximate, so confirm it fits the documentation.
