BF26ZZZComputerized Tomography (CT Scan) of Liver and Spleen
- Billable / Specific Code
BF26ZZZ is a billable ICD-10-PCS procedure code for Computerized Tomography (CT Scan) of Liver and Spleen. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Computerized Tomography (CT Scan) involves computer reformatted digital display of multiplanar images developed from the capture of multiple exposures of external ionizing radiation.
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 | 2 | Computerized Tomography (CT Scan) |
| 4 | BodyPart | 6 | Liver and Spleen |
| 5 | Contrast | Z | None |
| 6 | Qualifier | Z | None |
| 7 | Qualifier | Z | None |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for BF26ZZZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About BF26ZZZ
Is BF26ZZZ a billable code?
Yes. BF26ZZZ is a complete seven-character ICD-10-PCS code, specific enough to report Computerized Tomography (CT Scan) of Liver and Spleen on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in BF26ZZZ mean?
BF26ZZZ 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 2 is the Type (Computerized Tomography (CT Scan)); the 4th character 6 is the BodyPart (Liver and Spleen); 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 BF26ZZZ?
Under the General Equivalence Mappings, Computerized Tomography (CT Scan) of Liver and Spleen crosswalks to ICD-9-PCS 88.01. The mapping is approximate, so confirm it fits the documentation.
