0FB53ZXExcision of Right Hepatic Duct, Percutaneous Approach, Diagnostic
- Billable / Specific Code
0FB53ZX is a billable ICD-10-PCS procedure code for Excision of Right Hepatic Duct, 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 | F | Hepatobiliary System and Pancreas |
| 3 | Operation | B | Excision |
| 4 | BodyPart | 5 | Hepatic Duct, 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 0FB53ZX under the General Equivalence Mappings.
Code History
Similar Procedure Codes
Questions About 0FB53ZX
Is 0FB53ZX a billable code?
Yes. 0FB53ZX is a complete seven-character ICD-10-PCS code, specific enough to report Excision of Right Hepatic Duct, Percutaneous Approach, Diagnostic on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 0FB53ZX mean?
0FB53ZX breaks down character by character: the 1st character 0 is the Section (Medical and Surgical); the 2nd character F is the Body System (Hepatobiliary System and Pancreas); the 3rd character B is the Operation (Excision); the 4th character 5 is the BodyPart (Hepatic Duct, 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 0FB53ZX?
Under the General Equivalence Mappings, Excision of Right Hepatic Duct, Percutaneous Approach, Diagnostic crosswalks to ICD-9-PCS 51.12. The mapping is approximate, so confirm it fits the documentation.
