BF18YZZFluoroscopy of Pancreatic Ducts using Other Contrast
- Billable / Specific Code
BF18YZZ is a billable ICD-10-PCS procedure code for Fluoroscopy of Pancreatic Ducts using Other Contrast. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Fluoroscopy involves single plane or bi-plane real time display of an image developed from the capture of external ionizing radiation on a fluorescent screen. The image may also be stored by either digital or analog means.
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 | B | Imaging |
| 2 | Body System | F | Hepatobiliary System and Pancreas |
| 3 | Type | 1 | Fluoroscopy |
| 4 | BodyPart | 8 | Pancreatic Ducts |
| 5 | Contrast | Y | Other Contrast |
| 6 | Qualifier | Z | None |
| 7 | Qualifier | Z | None |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for BF18YZZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About BF18YZZ
Is BF18YZZ a billable code?
Yes. BF18YZZ is a complete seven-character ICD-10-PCS code, specific enough to report Fluoroscopy of Pancreatic Ducts using Other Contrast on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in BF18YZZ mean?
BF18YZZ breaks down character by character: the 1st character B is the Section (Imaging); the 2nd character F is the Body System (Hepatobiliary System and Pancreas); the 3rd character 1 is the Type (Fluoroscopy); the 4th character 8 is the BodyPart (Pancreatic Ducts); the 5th character Y is the Contrast (Other Contrast); the 6th character Z is the Qualifier (None); the 7th character Z is the Qualifier (None).
What is the ICD-9-PCS equivalent of BF18YZZ?
Under the General Equivalence Mappings, Fluoroscopy of Pancreatic Ducts using Other Contrast crosswalks to ICD-9-PCS 52.13 and 87.54. The mapping is approximate, so confirm it fits the documentation.
