Accurate coding for thrombocytopenia is essential for clinical communication, patient safety, and correct reimbursement. Thrombocytopenia reflects a low platelet count that increases bleeding risk and can signify a broad range of hematologic, infectious, drug-related, or systemic disease processes. Using the correct ICD-10-CM code affects claim acceptance, case mix, risk adjustment, and clinical registries.
This guide explains what the ICD-10 code for thrombocytopenia is, clinical scenarios that justify use of Thrombocytopenia, unspecified, when to select a more specific code, and practical documentation and billing strategies to reduce denials and improve revenue cycle performance. It is written for coders, clinical documentation improvement specialists, and revenue cycle managers who need actionable guidance.
The ICD-10-CM Code for Thrombocytopenia, unspecified is D69.6.
Thrombocytopenia is a hematologic condition defined by a platelet count below the laboratory reference range, often associated with bleeding, petechiae, purpura, or risk of hemorrhage. Thrombocytopenia, unspecified is the classification used when a clinician documents thrombocytopenia but does not specify a cause, subtype, or whether it is primary or secondary. D69.6 captures cases where the low platelet count is recognized and documented but lacking sufficient clinical detail to assign a more specific diagnosis such as immune thrombocytopenic purpura, drug-induced thrombocytopenia, or thrombocytopenia secondary to another disorder.
Use of Thrombocytopenia, unspecified should reflect the documented clinical assessment, laboratory confirmation of low platelets, and the absence of more specific etiologic information in the medical record.
Use Thrombocytopenia, unspecified when a patient presents with a newly identified low platelet count and the clinician documents thrombocytopenia but has not yet determined or documented a cause. Examples include ED encounters where platelet count is low, symptomatic bleeding evaluation has begun, and no definitive diagnosis is recorded.
When a laboratory result triggers notification and the clinician documents “thrombocytopenia” in the chart without specifying severity, etiology, or whether it is immune, drug-related, or secondary, code Thrombocytopenia, unspecified. This is appropriate for interim documentation before additional diagnostic workup is completed.
Use Thrombocytopenia, unspecified for routine follow-up visits where the provider documents ongoing thrombocytopenia and orders serial platelet counts or monitoring but does not add new diagnostic specificity. This supports medical necessity for monitoring while reflecting the current documentation.
For encounters addressing minor bleeding, petechiae, or bruising where the provider attributes symptoms to a documented low platelet count but cannot or does not record an identified cause, Thrombocytopenia, unspecified is appropriate for coding a low-complexity visit.
Do not use Thrombocytopenia, unspecified if the clinician documents a specific diagnosis such as immune thrombocytopenic purpura, drug-induced thrombocytopenia, or thrombocytopenia due to bone marrow failure. Instead, assign the code corresponding to the documented subtype (for example, Immune thrombocytopenic purpura).
If thrombocytopenia is explicitly linked to another condition (for example, chemotherapy-induced thrombocytopenia, aplastic anemia, liver disease, or disseminated intravascular coagulation) code the underlying condition or the designated secondary thrombocytopenia code rather than Thrombocytopenia, unspecified.
When documentation includes severity descriptors, treatment intent, or causal testing results that point to a defined diagnosis—such as documented platelet count thresholds tied to specific management—or a confirmed cause after testing, select the more specific code reflecting that information instead of D69.6.
Avoid Thrombocytopenia, unspecified if the thrombocytopenia is coded as a complication or adverse effect tied to a specific procedure, medication, or external cause that should be captured with the appropriate external cause or adverse effect codes and a specific thrombocytopenia code.
| Condition | Code | When It Is Used | When It Is Not Used |
|---|---|---|---|
| Thrombocytopenia, unspecified | D69.6 | Documented thrombocytopenia without a specific cause, initial or follow-up visits where clinician records "thrombocytopenia" only | When a specific subtype, secondary cause, or etiology is documented (use a more specific D69 code or underlying disease code) |
| Immune thrombocytopenic purpura | D69.3 | When clinician documents immune-mediated platelet destruction, e.g., ITP diagnosis confirmed by clinical assessment and testing | Not used when documentation lacks immune etiology or when thrombocytopenia is drug-induced, secondary to infection, or unspecified |
| Secondary thrombocytopenia | D69.5 | When thrombocytopenia is explicitly attributed to another condition (e.g., chemotherapy, bone marrow disorder, liver disease) and documented as secondary | Not used when no secondary cause is identified or when primary/immune thrombocytopenia is documented |
| Allergic purpura (Henoch-Schönlein purpura) | D69.0 | When purpura is due to allergic or immune complex-mediated vasculitis documented by the clinician | Not used for isolated thrombocytopenia without allergic purpura features or when another specific platelet disorder is documented |
Include the actual platelet count, date/time of draw, and whether counts are trending up or down. Objective lab values justify medical necessity and support the use of Thrombocytopenia, unspecified when etiology is not yet established.
Document the reason for visits or orders (e.g., monitoring, transfusion consideration, bleeding evaluation) and planned workup. Clear clinical intent links services to the diagnosis and reduces denials for lack of medical necessity.
When a provider suspects a cause but lacks confirmation, document the suspected etiology (for example, “suspected drug-induced thrombocytopenia pending review”). This helps clinical documentation improvement teams determine whether a more specific code can be reported or if D69.6 remains appropriate until confirmation.
Ensure thrombocytopenia appears on the active problem list with dates and resolution status when applicable. Consistent problem-list maintenance supports accurate coding across settings and clinicians.
Integrate coding validation and claim scrubbing tools to flag ambiguous documentation and prompt clinicians for specificity before submission. CombineHealth.ai's AI-powered platform and CombineHealth.ai's intelligent platform provide automated claim scrubbing and coding validation to catch errors pre-submission and reduce denials.
Coding for thrombocytopenia has direct impact on revenue cycle outcomes:
Accurate ICD-10 coding is critical for healthcare revenue cycle performance. CombineHealth.ai's AI-powered platform helps RCM teams ensure coding accuracy, reduce denials, and optimize reimbursement through intelligent denial management and claim validation. CombineHealth.ai's intelligent platform provides automated claim scrubbing and coding validation to catch errors before submission, reducing denials and improving first-pass acceptance rates.
Q1: What is the ICD-10 code for thrombocytopenia?
The ICD-10-CM code for thrombocytopenia is D69.6. This code applies when a clinician documents thrombocytopenia but does not specify an etiology, subtype, or secondary cause; lab-confirmed low platelets should be recorded in the chart.
Q2: When should I use Thrombocytopenia, unspecified vs related codes?
Use Thrombocytopenia, unspecified when documentation contains only the term thrombocytopenia without cause. Select immune thrombocytopenic purpura, secondary thrombocytopenia, or other specific D69 codes when the provider documents an immune cause, drug or disease-related cause, or other defined subtype.
Q3: What documentation is required when coding for thrombocytopenia?
Document the platelet count and date/time, clinical signs or symptoms, suspected or confirmed etiology if known, treatment decisions (monitoring, transfusion, medication changes), and follow-up plans. Clear linkage between the diagnosis and billed services strengthens medical necessity.
Q4: What are common denial reasons when coding for thrombocytopenia?
Common denials stem from non-specific documentation, missing lab values, incorrect code selection when a specific cause is documented, and lack of medical necessity linkage for procedures or testing. See our guide on denial management for strategies to reduce denials and improve appeals.