005K3ZZDestruction of Trigeminal Nerve, Percutaneous Approach
- Billable / Specific Code
005K3ZZ is a billable ICD-10-PCS procedure code for Destruction of Trigeminal Nerve, Percutaneous Approach. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Destruction involves physical eradication of all or a portion of a body part by the direct use of energy, force, or a destructive agent.
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 | 0 | Central Nervous System and Cranial Nerves |
| 3 | Operation | 5 | Destruction |
| 4 | BodyPart | K | Trigeminal Nerve |
| 5 | Approach | 3 | Percutaneous |
| 6 | Device | Z | No Device |
| 7 | Qualifier | Z | No Qualifier |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 005K3ZZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 005K3ZZ
Is 005K3ZZ a billable code?
Yes. 005K3ZZ is a complete seven-character ICD-10-PCS code, specific enough to report Destruction of Trigeminal Nerve, Percutaneous Approach on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 005K3ZZ mean?
005K3ZZ breaks down character by character: the 1st character 0 is the Section (Medical and Surgical); the 2nd character 0 is the Body System (Central Nervous System and Cranial Nerves); the 3rd character 5 is the Operation (Destruction); the 4th character K is the BodyPart (Trigeminal Nerve); the 5th character 3 is the Approach (Percutaneous); 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 005K3ZZ?
Under the General Equivalence Mappings, Destruction of Trigeminal Nerve, Percutaneous Approach crosswalks to ICD-9-PCS 42. The mapping is approximate, so confirm it fits the documentation.
