0NPB4MZRemoval of Bone Growth Stimulator from Nasal Bone, Percutaneous Endoscopic Approach
- Billable / Specific Code
0NPB4MZ is a billable ICD-10-PCS procedure code for Removal of Bone Growth Stimulator from Nasal Bone, Percutaneous Endoscopic Approach. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Removal involves taking out or off a device from 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 | N | Head and Facial Bones |
| 3 | Operation | P | Removal |
| 4 | BodyPart | B | Nasal Bone |
| 5 | Approach | 4 | Percutaneous Endoscopic |
| 6 | Device | M | Bone Growth Stimulator |
| 7 | Qualifier | Z | No Qualifier |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 0NPB4MZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 0NPB4MZ
Is 0NPB4MZ a billable code?
Yes. 0NPB4MZ is a complete seven-character ICD-10-PCS code, specific enough to report Removal of Bone Growth Stimulator from Nasal Bone, Percutaneous Endoscopic Approach on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 0NPB4MZ mean?
0NPB4MZ breaks down character by character: the 1st character 0 is the Section (Medical and Surgical); the 2nd character N is the Body System (Head and Facial Bones); the 3rd character P is the Operation (Removal); the 4th character B is the BodyPart (Nasal Bone); the 5th character 4 is the Approach (Percutaneous Endoscopic); the 6th character M is the Device (Bone Growth Stimulator); the 7th character Z is the Qualifier (No Qualifier).
What is the ICD-9-PCS equivalent of 0NPB4MZ?
Under the General Equivalence Mappings, Removal of Bone Growth Stimulator from Nasal Bone, Percutaneous Endoscopic Approach crosswalks to ICD-9-PCS 21.1. The mapping is approximate, so confirm it fits the documentation.
