Blog Details

F31.3 ICD-10 Diagnosis Code: Documentation and Reimbursement Guide

The International Classification of Diseases, Tenth Revision, Clinical Modification (ICD-10-CM) replaced ICD-9 in October 2015 across the United States. Since then, the specificity demanded of mental health diagnoses has grown considerably. A coder who once typed a broad bipolar diagnosis code now has to reflect the current episode type, its severity, and whether psychotic features are present. F31.3 is the gateway into that granularity for depressive episodes at the mild-to-moderate end of the spectrum.

ICD-10 Chapter	Code block	Episode type	Psychotic features
Chapter 5 — Mental & Behavioral Disorders	F31 — Bipolar disorder	Current depressive (mild or moderate)	Absent (see F31.5 if present)

The ICD-10 code hierarchy for bipolar disorder

To code accurately, practitioners and coders alike need to understand the parent-child relationships within the F31 block. The hierarchy is not arbitrary — it mirrors the DSM-5’s own episode-based framework and helps payers understand the clinical picture without reading the full note.

F31 hierarchy — depressive episodes

• F31.3 — Current depressive episode, mild or moderate (parent code, non-billable)
• F31.30 — Unspecified severity (use only when documentation does not specify)
• F31.31 — Current episode depressed, mild (preferred when severity documented as mild)
• F31.32 — Current episode depressed, moderate (preferred when documented as moderate)
• F31.4 — Current depressive episode, severe, without psychotic features
• F31.5 — Current depressive episode, severe, with psychotic features

Key coding note

Note that F31.3 itself is a header code — most payers require a fifth-character subcode. Submitting F31.3 alone on a claim will frequently trigger an edit or denial. Always drill down to F31.30, F31.31, or F31.32 based on the clinician’s documented severity assessment.

Clinical criteria a provider must document

The foundation of clean coding is complete clinical documentation. For F31.3x codes, the record must support three interlocking things: the bipolar disorder diagnosis itself, the fact that the current episode is depressive (not manic, hypomanic, or mixed), and that severity falls within the mild-to-moderate range.

Confirming the bipolar disorder diagnosis

Bipolar disorder requires a lifetime history of at least one manic or hypomanic episode. The clinical note should acknowledge this history — either through the patient’s own prior documented episodes or through a family history combined with pharmacological response if episodes pre-date the current practice’s records. An isolated depressive episode without any manic or hypomanic history would point toward a unipolar depressive code (F32.x or F33.x), not an F31.x code.

Defining the current episode as depressive

The note should explicitly state that the patient is currently in a depressive phase. Clinical indicators the provider should document include persistent low mood or anhedonia lasting at least two weeks, neurovegetative symptoms (changes in sleep, appetite, psychomotor activity, energy), and cognitive symptoms such as difficulty concentrating or recurrent thoughts of death. The DSM-5 threshold of five or more criteria within a two-week window applies, and a well-structured clinical note will address these criteria individually rather than relying on a checkbox only.

Severity: mild versus moderate

This is where many notes fall short. Severity determination is not just a word the clinician types — it should be backed by a validated rating instrument or a narrative that maps symptom count and functional impact to the DSM-5 severity specifiers. A patient meeting exactly five criteria with minimal functional impairment is at the mild end. A patient meeting six or seven criteria with significant but not incapacitating functional decline sits in the moderate range. Documenting the PHQ-9 score, the MADRS, or a clinical severity specifier statement (“the patient meets criteria for a moderate depressive episode based on seven DSM-5 criteria with notable impairment in occupational function”) gives coders and auditors the evidence they need.

Minimum documentation checklist for F31.31 / F31.32

• Confirmation of prior manic or hypomanic episode history
• Current episode explicitly described as depressive
• Duration of episode (minimum 2 weeks)
• Symptom inventory with count (at least 5 DSM-5 criteria)
• Validated rating scale score or severity narrative
• Functional impact assessment (work, social, daily activities)
• Absence of psychotic features explicitly noted
• Ruling out substance-induced or medical etiology

Billing and reimbursement considerations

Mental health parity legislation has improved reimbursement coverage for bipolar disorder management significantly over the past decade, but coding specificity remains the lever that providers must pull correctly. The F31.3 code group is generally covered under both commercial insurance and Medicare/Medicaid when documentation supports medical necessity — but what “support” looks like varies by payer.

Place of service and code pairing

F31.31 or F31.32 will appear most often alongside outpatient evaluation and management codes (99202–99215), psychiatric diagnostic evaluation codes (90791, 90792), and psychotherapy add-on codes (90833, 90836, 90838). For inpatient settings, the code pairs with 99221–99223 for admissions and 99231–99233 for subsequent visits. Partial hospitalization and intensive outpatient programs use H0035 (or program-specific HCPCS codes) alongside the diagnosis. Ensuring the procedure code’s typical setting aligns with the diagnosis severity is a soft audit trigger — a mild F31.31 episode driving an inpatient admission, for instance, should have clear medical necessity language in the record.

Prior authorization language

Prior authorization requests for medication management or therapy involving F31.3x diagnoses should mirror the language in the clinical note. Payers look for severity language that matches the subcode selected. If F31.32 (moderate) is coded, the auth request should describe moderate functional impairment, treatment history, and the rationale for the specific intervention requested. Inconsistency between the claim code and the auth language is a red flag that can delay authorization or trigger retrospective review.

Medicare and Medicaid specifics

Under Medicare, mental health services for bipolar disorder are covered under Part B with a standard 20% coinsurance after the deductible. The Improving Medicare Post-Acute Care Transformation (IMPACT) Act and subsequent value-based care initiatives have increased scrutiny of mental health coding accuracy. Medicaid coverage varies by state, but most state plans follow CMS guidance that requires a specific ICD-10 code at the claim level — F31.3 alone (non-billable) will reject in virtually every Medicaid managed care system.

Pro tip: For practices submitting to multiple payers, maintain a code-pairing reference sheet that maps F31.31 and F31.32 to the CPT codes most commonly used in your practice setting. This reduces coder variability and speeds up claim submission.

Common coding errors and how to avoid them

Even experienced coders make predictable mistakes with the F31.3x family. Recognizing these patterns ahead of time is the most cost-effective form of compliance work available to a billing team.

Error 1 — Using the non-billable parent code

Submitting F31.3 without a fifth character is the most common issue. Many EHR problem-list dropdowns populate with the parent code because it appears first alphabetically or by frequency. Build hard stops in your EHR or clearinghouse that flag F31.3 without a subcode extension before the claim goes out the door.

Error 2 — Choosing F31.30 when severity is documented

The “unspecified” subcode F31.30 should only be used when the clinician genuinely has not specified mild versus moderate. If the note says “moderate depressive episode” and the coder defaults to F31.30 out of habit, the claim is technically inaccurate. It also undersells the clinical picture for payers that tier reimbursement or authorization requirements by severity.

Error 3 — Confusing F31.3x with F32.x (major depressive disorder)

A patient being seen for a depressive episode with a prior history of bipolar disorder must always be coded in the F31.x series, not F32.x. F32 (major depressive disorder, single episode) and F33 (recurrent depressive disorder) are not appropriate when bipolar disorder is the underlying diagnosis, even if the current presentation is purely depressive. Using F32 when F31 is correct misrepresents the diagnosis, can affect the patient’s treatment record, and may cause formulary issues if the payer flags antidepressant monotherapy as inappropriate for what should be coded as bipolar disorder.

Error 4 — Missing the “absence of psychotic features” note

F31.3x specifically excludes psychotic features. If a provider does not document the absence of psychosis, a coder cannot assume it. In an audit, this gap can cause a claim to be reclassified upward to F31.5 (with psychotic features) or, worse, flagged for insufficient documentation. A single sentence in the mental status exam — “no evidence of hallucinations, delusions, or thought disorder” — closes this gap cleanly.

Compliance risk: Patterns of upcoding from F31.31 to F31.32 without corresponding documentation can trigger payer audits and OIG scrutiny. Severity codes should always trail the documentation — never lead it.

Secondary keywords and related diagnostic considerations

Medical coders and clinical documentation improvement (CDI) specialists working with F31.3x records will frequently encounter adjacent terms and codes that need to be addressed carefully in the same encounter.

Bipolar II disorder and hypomanic history

Patients with bipolar II disorder — characterized by hypomania rather than full mania — will also receive F31.3x codes when currently depressed. The F31 block accommodates both bipolar I and bipolar II, and the subcode selection is driven by the current episode, not the type designation. Documentation should still reference the nature of the hypomanic history to establish the bipolar diagnosis, even when the patient is in a purely depressive phase.

Cyclothymia and related mood disorder codes

Cyclothymia (F34.0) involves chronic mood instability that does not meet the full criteria for bipolar episodes. Providers sometimes confuse a cycling presentation of cyclothymia with a moderate bipolar depressive episode. The distinction lies in whether the depressive periods meet full DSM-5 criteria for a major depressive episode — if they do, and there is a manic or hypomanic history, F31.3x is appropriate. If the mood disturbance is subthreshold throughout, F34.0 is the more accurate landing point.

Anxiety comorbidities and additional coding

Bipolar disorder frequently co-occurs with anxiety disorders. ICD-10-CM guidelines allow — and in many cases require — coding of comorbid conditions that receive treatment or affect management during the encounter. If a patient with F31.32 also has a clinically addressed panic disorder (F41.0) or generalized anxiety disorder (F41.1), both codes should appear on the claim in the appropriate sequencing order, with the reason for the visit listed first.

Substance use disorder overlap

Alcohol use disorder and stimulant use disorder commonly co-occur with bipolar disorder. When both conditions are active and addressed during the encounter, the relevant substance use disorder code (F10.x–F19.x) should accompany the F31.3x code. However, coders must take care not to code F31.3x if the depressive episode is substance-induced — in that case, a substance-induced mood disorder code (within the F10–F19 range) would more accurately describe the presentation.

Practical compliance and auditing strategies

Proactive compliance work around F31.3x codes protects both the practice and the patient record. The following strategies are drawn from CDI best practices and OIG work-plan guidance on behavioral health coding.

Conduct quarterly internal code audits

Pull a random sample of claims filed with F31.30, F31.31, and F31.32 each quarter. For each claim, verify that the supporting documentation actually contains a severity assessment, that the episode type matches the clinical note, and that the procedure codes billed are appropriate for the setting and complexity described. A 10-claim sample per provider per quarter is usually sufficient to identify systematic issues before they become patterns large enough to attract external scrutiny.

Educate providers on documentation specificity

Clinicians did not go to medical school to learn ICD-10 granularity, and expecting them to self-police code-level documentation without training is unrealistic. Brief, targeted education sessions — fifteen minutes at a staff meeting, a laminated one-page reference card near workstations, or a smart-text phrase in the EHR — can dramatically reduce documentation gaps for severity specifiers and psychosis exclusion language.

Leverage CDI technology for real-time prompting

Modern clinical documentation improvement tools integrated with EHR platforms can query providers at the point of note completion: “You have documented a bipolar disorder diagnosis with a depressive episode. Please specify severity (mild/moderate/severe) and confirm the presence or absence of psychotic features.” These nudges take seconds and prevent hours of retrospective query work later.

Stay current with annual ICD-10-CM updates

The F31 code block has seen incremental revisions since ICD-10’s US launch. New codes, revised inclusion and exclusion notes, and changes to coding guidelines are published each October by CMS and the National Center for Health Statistics. A dedicated coding compliance calendar that flags October 1 updates — and includes time for training before the effective date — is a minimal investment relative to the cost of coding with outdated references.

Accurate use of F31.31 and F31.32 is not simply a billing exercise — it is a clinical act. The code that appears on the claim becomes part of the patient’s longitudinal record, shapes insurer perception of severity, and can influence future coverage decisions. When documentation supports the code and the code faithfully represents the clinical picture, providers, coders, and — most importantly — patients all benefit.