B348ZZ3Ultrasonography of Bilateral Internal Carotid Arteries, Intravascular
- Billable / Specific Code
B348ZZ3 is a billable ICD-10-PCS procedure code for Ultrasonography of Bilateral Internal Carotid Arteries, Intravascular. It is valid on HIPAA claims for fiscal year 2026 (October 1, 2025 through September 30, 2026). The root operation Ultrasonography involves real time display of images of anatomy or flow information developed from the capture of reflected and attenuated high frequency sound waves.
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 | 3 | Upper Arteries |
| 3 | Type | 4 | Ultrasonography |
| 4 | BodyPart | 8 | Internal Carotid Arteries, Bilateral |
| 5 | Contrast | Z | None |
| 6 | Qualifier | Z | None |
| 7 | Qualifier | 3 | Intravascular |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for B348ZZ3 under the General Equivalence Mappings.
Similar Procedure Codes
Questions About B348ZZ3
Is B348ZZ3 a billable code?
Yes. B348ZZ3 is a complete seven-character ICD-10-PCS code, specific enough to report Ultrasonography of Bilateral Internal Carotid Arteries, Intravascular on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in B348ZZ3 mean?
B348ZZ3 breaks down character by character: the 1st character B is the Section (Imaging); the 2nd character 3 is the Body System (Upper Arteries); the 3rd character 4 is the Type (Ultrasonography); the 4th character 8 is the BodyPart (Internal Carotid Arteries, Bilateral); the 5th character Z is the Contrast (None); the 6th character Z is the Qualifier (None); the 7th character 3 is the Qualifier (Intravascular).
What is the ICD-9-PCS equivalent of B348ZZ3?
Under the General Equivalence Mappings, Ultrasonography of Bilateral Internal Carotid Arteries, Intravascular crosswalks to ICD-9-PCS 21. The mapping is approximate, so confirm it fits the documentation.
