0TB37ZXExcision of Right Kidney Pelvis, Via Natural or Artificial Opening, Diagnostic
- Billable / Specific Code
0TB37ZX is a billable ICD-10-PCS procedure code for Excision of Right Kidney Pelvis, Via Natural or Artificial Opening, Diagnostic. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Excision involves cutting out or off, without replacement, a portion 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 | T | Urinary System |
| 3 | Operation | B | Excision |
| 4 | BodyPart | 3 | Kidney Pelvis, Right |
| 5 | Approach | 7 | Via Natural or Artificial Opening |
| 6 | Device | Z | No Device |
| 7 | Qualifier | X | Diagnostic |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 0TB37ZX under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 0TB37ZX
Is 0TB37ZX a billable code?
Yes. 0TB37ZX is a complete seven-character ICD-10-PCS code, specific enough to report Excision of Right Kidney Pelvis, Via Natural or Artificial Opening, Diagnostic on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 0TB37ZX mean?
0TB37ZX breaks down character by character: the 1st character 0 is the Section (Medical and Surgical); the 2nd character T is the Body System (Urinary System); the 3rd character B is the Operation (Excision); the 4th character 3 is the BodyPart (Kidney Pelvis, 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 X is the Qualifier (Diagnostic).
What is the ICD-9-PCS equivalent of 0TB37ZX?
Under the General Equivalence Mappings, Excision of Right Kidney Pelvis, Via Natural or Artificial Opening, Diagnostic crosswalks to ICD-9-PCS 55.23 and 59.21. The mapping is approximate, so confirm it fits the documentation.
