BN19ZZZFluoroscopy of Bilateral Temporomandibular Joints
- Billable / Specific Code
BN19ZZZ is a billable ICD-10-PCS procedure code for Fluoroscopy of Bilateral Temporomandibular Joints. 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
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 | N | Skull and Facial Bones |
| 3 | Type | 1 | Fluoroscopy |
| 4 | BodyPart | 9 | Temporomandibular Joints, Bilateral |
| 5 | Contrast | Z | None |
| 6 | Qualifier | Z | None |
| 7 | Qualifier | Z | None |
Convert to ICD-9-PCS
Closest ICD-9-PCS equivalents for BN19ZZZ under the General Equivalence Mappings.
Similar Procedure Codes
Questions About BN19ZZZ
Is BN19ZZZ a billable code?
Yes. BN19ZZZ is a complete seven-character ICD-10-PCS code, specific enough to report Fluoroscopy of Bilateral Temporomandibular Joints on inpatient claims from October 1, 2025 through September 30, 2026.
What do the characters in BN19ZZZ mean?
BN19ZZZ breaks down character by character: the 1st character B is the Section (Imaging); the 2nd character N is the Body System (Skull and Facial Bones); the 3rd character 1 is the Type (Fluoroscopy); the 4th character 9 is the BodyPart (Temporomandibular Joints, Bilateral); 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 BN19ZZZ?
Under the General Equivalence Mappings, Fluoroscopy of Bilateral Temporomandibular Joints crosswalks to ICD-9-PCS 87.16. The mapping is approximate, so confirm it fits the documentation.
