099P4ZZDrainage of Accessory Sinus, Percutaneous Endoscopic Approach
- Billable / Specific Code
099P4ZZ is a billable ICD-10-PCS procedure code for Drainage of Accessory Sinus, Percutaneous Endoscopic 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 | 9 | Ear, Nose, Sinus |
| 3 | Operation | 9 | Drainage |
| 4 | BodyPart | P | Accessory Sinus |
| 5 | Approach | 4 | Percutaneous Endoscopic |
| 6 | Device | Z | No Device |
| 7 | Qualifier | Z | No Qualifier |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 099P4ZZ under the General Equivalence Mappings.
Code History
- 099P8ZZ — Drainage of Accessory Sinus, Endo
Similar Procedure Codes
Questions About 099P4ZZ
Is 099P4ZZ a billable code?
Yes. 099P4ZZ is a complete seven-character ICD-10-PCS code, specific enough to report Drainage of Accessory Sinus, Percutaneous Endoscopic Approach on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 099P4ZZ mean?
099P4ZZ breaks down character by character: the 1st character 0 is the Section (Medical and Surgical); the 2nd character 9 is the Body System (Ear, Nose, Sinus); the 3rd character 9 is the Operation (Drainage); the 4th character P is the BodyPart (Accessory Sinus); the 5th character 4 is the Approach (Percutaneous 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 099P4ZZ?
Under the General Equivalence Mappings, Drainage of Accessory Sinus, Percutaneous Endoscopic Approach crosswalks to ICD-9-PCS 22.01. The mapping is approximate, so confirm it fits the documentation.
