6A550Z1Pheresis of Leukocytes, Single

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

6A550Z1 is a billable ICD-10-PCS procedure code for Pheresis of Leukocytes, Single. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Pheresis involves extracorporeal separation of blood products.

Code Identity

ICD-10-PCS Code
6A550Z1
Billable Status
Yes — Valid for Submission
Code Describes
Pheresis of Leukocytes, Single
Parent Code
Short Description
Pheresis of Leukocytes, Single

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
1Section6Extracorporeal or Systemic Therapies
2Body SystemAPhysiological Systems
3Operation5Pheresis
4BodySystem5Circulatory
5Duration0Single
6QualifierZNo Qualifier
7Qualifier1Leukocytes

Convert to ICD-9-PCS

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

99.72
Approximate match.

Similar Procedure Codes

Questions About 6A550Z1

Is 6A550Z1 a billable code?

Yes. 6A550Z1 is a complete seven-character ICD-10-PCS code, specific enough to report Pheresis of Leukocytes, Single on inpatient claims from October 1, 2025 through September 30, 2026.

What do the characters in 6A550Z1 mean?

6A550Z1 breaks down character by character: the 1st character 6 is the Section (Extracorporeal or Systemic Therapies); the 2nd character A is the Body System (Physiological Systems); the 3rd character 5 is the Operation (Pheresis); the 4th character 5 is the BodySystem (Circulatory); the 5th character 0 is the Duration (Single); the 6th character Z is the Qualifier (No Qualifier); the 7th character 1 is the Qualifier (Leukocytes).

What is the ICD-9-PCS equivalent of 6A550Z1?

Under the General Equivalence Mappings, Pheresis of Leukocytes, Single crosswalks to ICD-9-PCS 99.72. The mapping is approximate, so confirm it fits the documentation.