BW1J1ZZFluoroscopy of Upper Extremity using Low Osmolar Contrast
- Billable / Specific Code
BW1J1ZZ is a billable ICD-10-PCS procedure code for Fluoroscopy of Upper Extremity using Low Osmolar 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 | W | Anatomical Regions |
| 3 | Type | 1 | Fluoroscopy |
| 4 | BodyPart | J | Upper Extremity |
| 5 | Contrast | 1 | Low Osmolar |
| 6 | Qualifier | Z | None |
| 7 | Qualifier | Z | None |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for BW1J1ZZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About BW1J1ZZ
Is BW1J1ZZ a billable code?
Yes. BW1J1ZZ is a complete seven-character ICD-10-PCS code, specific enough to report Fluoroscopy of Upper Extremity using Low Osmolar Contrast on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in BW1J1ZZ mean?
BW1J1ZZ breaks down character by character: the 1st character B is the Section (Imaging); the 2nd character W is the Body System (Anatomical Regions); the 3rd character 1 is the Type (Fluoroscopy); the 4th character J is the BodyPart (Upper Extremity); the 5th character 1 is the Contrast (Low Osmolar); the 6th character Z is the Qualifier (None); the 7th character Z is the Qualifier (None).
What is the ICD-9-PCS equivalent of BW1J1ZZ?
Under the General Equivalence Mappings, Fluoroscopy of Upper Extremity using Low Osmolar Contrast crosswalks to ICD-9-PCS 88.35. The mapping is approximate, so confirm it fits the documentation.
