0TFC8ZZFragmentation in Bladder Neck, Via Natural or Artificial Opening Endoscopic
- Billable / Specific Code
0TFC8ZZ is a billable ICD-10-PCS procedure code for Fragmentation in Bladder Neck, Via Natural or Artificial Opening Endoscopic. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Fragmentation involves breaking solid matter in a body part into pieces.
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 | F | Fragmentation |
| 4 | BodyPart | C | Bladder Neck |
| 5 | Approach | 8 | Via Natural or Artificial Opening Endoscopic |
| 6 | Device | Z | No Device |
| 7 | Qualifier | Z | No Qualifier |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 0TFC8ZZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 0TFC8ZZ
Is 0TFC8ZZ a billable code?
Yes. 0TFC8ZZ is a complete seven-character ICD-10-PCS code, specific enough to report Fragmentation in Bladder Neck, Via Natural or Artificial Opening Endoscopic on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 0TFC8ZZ mean?
0TFC8ZZ 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 F is the Operation (Fragmentation); the 4th character C is the BodyPart (Bladder Neck); the 5th character 8 is the Approach (Via Natural or Artificial Opening 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 0TFC8ZZ?
Under the General Equivalence Mappings, Fragmentation in Bladder Neck, Via Natural or Artificial Opening Endoscopic crosswalks to ICD-9-PCS 59.95. The mapping is approximate, so confirm it fits the documentation.
