0TJ90ZZInspection of Ureter, Open Approach
- Billable / Specific Code
0TJ90ZZ is a billable ICD-10-PCS procedure code for Inspection of Ureter, Open Approach. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026) and groups to 6 MS-DRGs. The root operation Inspection involves visually and/or manually exploring 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 | J | Inspection |
| 4 | BodyPart | 9 | Ureter |
| 5 | Approach | 0 | Open |
| 6 | Device | Z | No Device |
| 7 | Qualifier | Z | No Qualifier |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 0TJ90ZZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 0TJ90ZZ
Is 0TJ90ZZ a billable code?
Yes. 0TJ90ZZ is a complete seven-character ICD-10-PCS code, specific enough to report Inspection of Ureter, Open Approach on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 0TJ90ZZ mean?
0TJ90ZZ 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 J is the Operation (Inspection); the 4th character 9 is the BodyPart (Ureter); the 5th character 0 is the Approach (Open); the 6th character Z is the Device (No Device); the 7th character Z is the Qualifier (No Qualifier).
What MS-DRG does 0TJ90ZZ group to?
On an inpatient stay, Inspection of Ureter, Open Approach maps to MS-DRGs 656, 657, 658, 659, 660, 661, with relative weights from 1.0354 to 3.1838. The MS-DRG sets the fixed Medicare payment for the stay.
What is the ICD-9-PCS equivalent of 0TJ90ZZ?
Under the General Equivalence Mappings, Inspection of Ureter, Open Approach crosswalks to ICD-9-PCS 56.2. The mapping is approximate, so confirm it fits the documentation.
