0MBS3ZXExcision of Right Foot Bursa and Ligament, Percutaneous Approach, Diagnostic
- Billable / Specific Code
0MBS3ZX is a billable ICD-10-PCS procedure code for Excision of Right Foot Bursa and Ligament, Percutaneous 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 | M | Bursae and Ligaments |
| 3 | Operation | B | Excision |
| 4 | BodyPart | S | Foot Bursa and Ligament, Right |
| 5 | Approach | 3 | Percutaneous |
| 6 | Device | Z | No Device |
| 7 | Qualifier | X | Diagnostic |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 0MBS3ZX under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 0MBS3ZX
Is 0MBS3ZX a billable code?
Yes. 0MBS3ZX is a complete seven-character ICD-10-PCS code, specific enough to report Excision of Right Foot Bursa and Ligament, Percutaneous Approach, Diagnostic on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 0MBS3ZX mean?
0MBS3ZX breaks down character by character: the 1st character 0 is the Section (Medical and Surgical); the 2nd character M is the Body System (Bursae and Ligaments); the 3rd character B is the Operation (Excision); the 4th character S is the BodyPart (Foot Bursa and Ligament, Right); the 5th character 3 is the Approach (Percutaneous); 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 0MBS3ZX?
Under the General Equivalence Mappings, Excision of Right Foot Bursa and Ligament, Percutaneous Approach, Diagnostic crosswalks to ICD-9-PCS 80.38 and 83.29. The mapping is approximate, so confirm it fits the documentation.
