0BF97ZZFragmentation in Lingula Bronchus, Via Natural or Artificial Opening
- Billable / Specific Code
0BF97ZZ is a billable ICD-10-PCS procedure code for Fragmentation in Lingula Bronchus, Via Natural or Artificial Opening. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Fragmentation involves breaking solid matter in a body part into pieces.
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 | B | Respiratory System |
| 3 | Operation | F | Fragmentation |
| 4 | BodyPart | 9 | Lingula Bronchus |
| 5 | Approach | 7 | Via Natural or Artificial Opening |
| 6 | Device | Z | No Device |
| 7 | Qualifier | Z | No Qualifier |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 0BF97ZZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 0BF97ZZ
Is 0BF97ZZ a billable code?
Yes. 0BF97ZZ is a complete seven-character ICD-10-PCS code, specific enough to report Fragmentation in Lingula Bronchus, Via Natural or Artificial Opening on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 0BF97ZZ mean?
0BF97ZZ breaks down character by character: the 1st character 0 is the Section (Medical and Surgical); the 2nd character B is the Body System (Respiratory System); the 3rd character F is the Operation (Fragmentation); the 4th character 9 is the BodyPart (Lingula Bronchus); the 5th character 7 is the Approach (Via Natural or Artificial Opening); 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 0BF97ZZ?
Under the General Equivalence Mappings, Fragmentation in Lingula Bronchus, Via Natural or Artificial Opening crosswalks to ICD-9-PCS 33.48. The mapping is approximate, so confirm it fits the documentation.
