BP1NZZZFluoroscopy of Right Hand

  • Billable / Specific Code
ICD-10-PCS BP1NZZZ
CMS Source: FY 2026 ICD-10-PCS dataset. Effective Oct 1, 2025 – Sep 30, 2026.FacebookXLinkedInPrint

BP1NZZZ is a billable ICD-10-PCS procedure code for Fluoroscopy of Right Hand. 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

ICD-10-PCS Code
BP1NZZZ
Billable Status
Yes — Valid for Submission
Code Describes
Fluoroscopy of Right Hand
Parent Code
Short Description
Fluoroscopy of Right Hand

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.

PositionDesignationValueMeaning
1SectionBImaging
2Body SystemPNon-Axial Upper Bones
3Type1Fluoroscopy
4BodyPartNHand, Right
5ContrastZNone
6QualifierZNone
7QualifierZNone

Convert to ICD-9-PCS

Closest ICD-9-PCS equivalents for BP1NZZZ under the General Equivalence Mappings.

88.23
Approximate match.

Questions About BP1NZZZ

Is BP1NZZZ a billable code?

Yes. BP1NZZZ is a complete seven-character ICD-10-PCS code, specific enough to report Fluoroscopy of Right Hand on inpatient claims from October 1, 2025 through September 30, 2026.

What do the characters in BP1NZZZ mean?

BP1NZZZ breaks down character by character: the 1st character B is the Section (Imaging); the 2nd character P is the Body System (Non-Axial Upper Bones); the 3rd character 1 is the Type (Fluoroscopy); the 4th character N is the BodyPart (Hand, Right); the 5th character Z is the Contrast (None); the 6th character Z is the Qualifier (None); the 7th character Z is the Qualifier (None).

What is the ICD-9-PCS equivalent of BP1NZZZ?

Under the General Equivalence Mappings, Fluoroscopy of Right Hand crosswalks to ICD-9-PCS 88.23. The mapping is approximate, so confirm it fits the documentation.