2W3FX3ZImmobilization of Left Hand using Brace

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

2W3FX3Z is a billable ICD-10-PCS procedure code for Immobilization of Left Hand using Brace. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Immobilization involves limiting or preventing motion of a body region.

Code Identity

ICD-10-PCS Code
2W3FX3Z
Billable Status
Yes — Valid for Submission
Code Describes
Immobilization of Left Hand using Brace
Parent Code
Short Description
Immobilization of Left Hand using Brace

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
1Section2Placement
2Body SystemWAnatomical Regions
3Operation3Immobilization
4BodyRegionFHand, Left
5ApproachXExternal
6Device3Brace
7QualifierZNo Qualifier

Convert to ICD-9-PCS

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

93.59
Approximate match.

Similar Procedure Codes

Questions About 2W3FX3Z

Is 2W3FX3Z a billable code?

Yes. 2W3FX3Z is a complete seven-character ICD-10-PCS code, specific enough to report Immobilization of Left Hand using Brace on inpatient claims from October 1, 2025 through September 30, 2026.

What do the characters in 2W3FX3Z mean?

2W3FX3Z breaks down character by character: the 1st character 2 is the Section (Placement); the 2nd character W is the Body System (Anatomical Regions); the 3rd character 3 is the Operation (Immobilization); the 4th character F is the BodyRegion (Hand, Left); the 5th character X is the Approach (External); the 6th character 3 is the Device (Brace); the 7th character Z is the Qualifier (No Qualifier).

What is the ICD-9-PCS equivalent of 2W3FX3Z?

Under the General Equivalence Mappings, Immobilization of Left Hand using Brace crosswalks to ICD-9-PCS 93.59. The mapping is approximate, so confirm it fits the documentation.