0FV83CZRestriction of Cystic Duct with Extraluminal Device, Percutaneous Approach
- Billable / Specific Code
0FV83CZ is a billable ICD-10-PCS procedure code for Restriction of Cystic Duct with Extraluminal Device, Percutaneous Approach. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Restriction involves partially closing an orifice or the lumen of a tubular 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 | V | Restriction |
| 4 | BodyPart | 8 | Cystic Duct |
| 5 | Approach | 3 | Percutaneous |
| 6 | Device | C | Extraluminal Device |
| 7 | Qualifier | Z | No Qualifier |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for 0FV83CZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About 0FV83CZ
Is 0FV83CZ a billable code?
Yes. 0FV83CZ is a complete seven-character ICD-10-PCS code, specific enough to report Restriction of Cystic Duct with Extraluminal Device, Percutaneous Approach on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in 0FV83CZ mean?
0FV83CZ 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 V is the Operation (Restriction); the 4th character 8 is the BodyPart (Cystic Duct); the 5th character 3 is the Approach (Percutaneous); the 6th character C is the Device (Extraluminal Device); the 7th character Z is the Qualifier (No Qualifier).
What is the ICD-9-PCS equivalent of 0FV83CZ?
Under the General Equivalence Mappings, Restriction of Cystic Duct with Extraluminal Device, Percutaneous Approach crosswalks to ICD-9-PCS 51.98. The mapping is approximate, so confirm it fits the documentation.
