0N9630ZDrainage of Left Temporal Bone with Drainage Device, Percutaneous Approach
- Billable / Specific Code
0N9630Z is a billable ICD-10-PCS procedure code for Drainage of Left Temporal Bone with Drainage Device, Percutaneous Approach. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Drainage involves taking or letting out fluids and/or gases 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 | 9 | Drainage |
| 4 | BodyPart | 6 | Temporal Bone, Left |
| 5 | Approach | 3 | Percutaneous |
| 6 | Device | 0 | Drainage Device |
| 7 | Qualifier | Z | No Qualifier |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 0N9630Z under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 0N9630Z
Is 0N9630Z a billable code?
Yes. 0N9630Z is a complete seven-character ICD-10-PCS code, specific enough to report Drainage of Left Temporal Bone with Drainage Device, Percutaneous Approach on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 0N9630Z mean?
0N9630Z 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 9 is the Operation (Drainage); the 4th character 6 is the BodyPart (Temporal Bone, Left); the 5th character 3 is the Approach (Percutaneous); the 6th character 0 is the Device (Drainage Device); the 7th character Z is the Qualifier (No Qualifier).
What is the ICD-9-PCS equivalent of 0N9630Z?
Under the General Equivalence Mappings, Drainage of Left Temporal Bone with Drainage Device, Percutaneous Approach crosswalks to ICD-9-PCS 10.9. The mapping is approximate, so confirm it fits the documentation.
