00BN4ZXExcision of Acoustic Nerve, Percutaneous Endoscopic Approach, Diagnostic
- Billable / Specific Code
00BN4ZX is a billable ICD-10-PCS procedure code for Excision of Acoustic Nerve, Percutaneous Endoscopic Approach, 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 | 0 | Central Nervous System and Cranial Nerves |
| 3 | Operation | B | Excision |
| 4 | BodyPart | N | Acoustic Nerve |
| 5 | Approach | 4 | Percutaneous Endoscopic |
| 6 | Device | Z | No Device |
| 7 | Qualifier | X | Diagnostic |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 00BN4ZX under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 00BN4ZX
Is 00BN4ZX a billable code?
Yes. 00BN4ZX is a complete seven-character ICD-10-PCS code, specific enough to report Excision of Acoustic Nerve, Percutaneous Endoscopic Approach, Diagnostic on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 00BN4ZX mean?
00BN4ZX 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 B is the Operation (Excision); the 4th character N is the BodyPart (Acoustic Nerve); the 5th character 4 is the Approach (Percutaneous Endoscopic); 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 00BN4ZX?
Under the General Equivalence Mappings, Excision of Acoustic Nerve, Percutaneous Endoscopic Approach, Diagnostic crosswalks to ICD-9-PCS 41.1. The mapping is approximate, so confirm it fits the documentation.
