Question 1

Is T19 a billable ICD-10 code?

Accepted Answer

No, T19 is not a billable code. It is a category code that requires additional specificity. You must select a more specific code from the subcategories for billing purposes.

Question 2

What does ICD-10 code T19 mean?

Accepted Answer

ICD-10-CM code T19 represents Foreign body in genitourinary tract. This code is part of the International Classification of Diseases, 10th Revision, Clinical Modification used for medical coding and billing in the United States.

Question 3

When was ICD-10 code T19 introduced?

Accepted Answer

Code T19 has been part of ICD-10-CM since 2016, when the coding system was mandated for use in the United States. This code was included in the original US implementation.

Question 4

What is the parent category for ICD-10 code T19?

Accepted Answer

The parent category for T19 is section:T15-T19 (Effects of foreign body entering through natural orifice (T15-T19)). This hierarchical classification helps organize related diagnoses for more accurate coding.

Question 5

What conditions should be coded separately from T19?

Accepted Answer

Code T19 has Type 2 Excludes including: complications due to implanted mesh (T83.7-); mechanical complications of contraceptive device (intrauterine) (vaginal) (T83.3-); presence of contraceptive device (intrauterine) (vaginal) (Z97.5). These conditions are not included in T19 but can be coded together if the patient has both conditions.

Question 6

Does T19 require a 7th character extension?

Accepted Answer

Yes, T19 requires a 7th character to specify the encounter type. Available extensions include: A (initial encounter), D (subsequent encounter), S (sequela). Use "X" as a placeholder to fill empty positions before the 7th character (e.g., T19XXA for initial encounter). The extension indicates whether this is an initial visit, follow-up, or treatment for a late effect.

T192026

Excludes29Not included here

Use Additional Code2Add code for detail

Notes2Additional information

7th Character Extensions3Encounter type specifiers