ICD-10 Code F31.9: Bipolar Disorder, Unspecified

Key Takeaways

ICD-10 Code F31.9 classifies bipolar disorder, unspecified, under the Mood [affective] disorders block (F30-F39).

Use F31.9 only when the episode type or severity cannot be determined from available documentation.

Extended use of F31.9 without progression to a more specific code may invite payer audit scrutiny.

Pabau’s psychiatry EMR and claims management tools support accurate F31.9 documentation and billing workflows.

Coders regularly encounter bipolar disorder documentation that falls short of the specificity a more granular ICD-10-CM code requires. ICD-10 Code F31.9 exists for exactly this situation: when a clinician has established a bipolar disorder diagnosis but has not yet documented the current episode type or its severity. Getting the code selection right matters because payers increasingly scrutinize unspecified codes, and sustained use without clinical justification can trigger claim reviews. This article covers the clinical definition, correct usage criteria, documentation requirements, related codes, and billing guidance for ICD-10 Code F31.9.

The World Health Organization’s ICD-10 classification places bipolar disorder within Chapter V (Mental, Behavioral and Neurodevelopmental Disorders), block F30-F39, alongside other mood and affective disorders. Clinicians working in mental health EHR environments need to understand both the code’s appropriate use and its documentation thresholds to avoid claim denials.

ICD-10 Code F31.9: Clinical Definition and Code Structure

F31.9 is the final code within the F31 bipolar disorder category. The official clinical description is “Bipolar disorder, unspecified,” with manic depression listed as an inclusion term. This means any documentation that uses the term “manic depression” without further qualification maps to F31.9 in ICD-10-CM.

The F31 category covers a spectrum of bipolar presentations. The CMS ICD-10-CM tabular list confirms F31.9 as a valid, billable ICD-10-CM code for the 2026 fiscal year. It sits at the end of the F31.x hierarchy, serving as the catch-all when subcategory detail is unavailable.

Clinicians using psychiatry EMR software should configure their clinical note templates to capture the four elements that distinguish one F31 subcategory from another: current episode polarity, episode severity, presence or absence of psychotic features, and whether the pattern fits Bipolar I versus Bipolar II.

When to Use F31.9 and When to Choose a More Specific Code

The ICD-10-CM coding guidelines establish a clear principle: assign the code that offers the highest degree of specificity supported by the documentation. F31.9 is appropriate in two scenarios.

• Initial diagnostic encounter: A patient presents with symptoms consistent with bipolar spectrum disorder but the clinical picture has not yet clarified sufficiently to establish episode type or polarity.
• Documentation gap: The treating clinician has documented “bipolar disorder” without specifying the current episode state, and querying the provider is not practicable before coding.

The AHA Coding Clinic (First Quarter 2020, p. 23) provides an instructive example: when documentation states “bipolar disorder and mild major depressive disorder, recurrent,” coders should assign only F31.9 rather than attempting to split the diagnosis across two codes. The bipolar disorder subsumes the depressive component in that clinical context.

F31.9 is not appropriate as a long-term code when the clinical picture has clarified. Once a clinician documents a specific episode type, severity, or Bipolar II pattern, the more specific code must be used. Sustained use of F31.9 across multiple encounters without any progression to a more granular code may attract payer scrutiny, particularly under Medicare and commercial payer audit programs. This is a best-practice consideration rather than an explicit regulatory prohibition, but it reflects the ICD-10-CM guideline requiring maximum specificity.

For context on adjacent unspecified codes used in behavioral health, see this reference on anxiety ICD-10 code usage, which follows similar specificity logic under the F40-F48 block.

Documentation Requirements for F31.9

Supporting documentation for F31.9 must establish two things: that bipolar disorder is the diagnosis, and that the clinician could not yet specify the episode type. Vague language like “mood disorder, possible bipolar” does not support F31.9 because it introduces diagnostic uncertainty about whether bipolar disorder exists at all.

According to AAPC Codify, appropriate documentation elements for F31.9 include:

• Confirmed diagnosis of bipolar disorder in the provider’s own words (not “rule out” or “possible”)
• Reference to a history of manic or hypomanic episodes, even if the current episode state is unspecified
• Clinical rationale for why a more specific F31.x code cannot be assigned at this encounter
• DSM-5 diagnostic criteria checklist or equivalent clinical reasoning when coding for initial episodes

For telehealth and remote monitoring encounters, documentation standards are identical to in-person visits. The platform used does not change the coding requirement. Clinicians should ensure their session notes contain the same diagnostic specificity they would include in office visit records. A structured psychiatric evaluation template can standardize this process across your team and reduce the risk of documentation gaps at billing time.

HIPAA-compliant documentation practices require that mental health records support the billed diagnosis. Using HIPAA-compliant clinical software with structured note templates helps practices maintain defensible records if a payer requests supporting documentation for F31.9 claims.

F31.9 vs. F31.81 and Other Related Codes

The most common miscoding error involves using F31.9 when F31.81 (Bipolar II disorder) is the correct choice. These are not interchangeable.

F31.9 vs. F31.81: F31.81 requires documented evidence of at least one hypomanic episode and at least one major depressive episode, with no history of full manic episodes. If the clinician’s notes establish this pattern, F31.81 must be used. F31.9 cannot serve as a placeholder for Bipolar II simply because the clinician did not write “Bipolar II” explicitly; coders must look at the clinical picture documented.

F31.9 vs. F31.0: F31.0 (Bipolar disorder, current episode hypomanic) applies when the current episode is clearly hypomanic. If the patient is in a hypomanic state at the encounter, the episode type is specified and F31.9 is incorrect.

F31.9 vs. F32/F33: Bipolar disorder with a current depressive episode maps to F31.3x, F31.4, or F31.5, depending on severity. If the provider documents only a depressive episode without a bipolar history, codes F32 (single episode) or F33 (recurrent) may be more appropriate. Careful review of prior encounter history is necessary. For a broader view of mood disorder coding logic, this ICD-10 code reference illustrates how unspecified codes function across different diagnostic categories.

Streamline Bipolar Disorder Documentation and Billing

Pabau's psychiatry EMR helps behavioral health teams capture the episode specificity ICD-10-CM requires, reducing claim denials and audit risk for F31.x codes.

Book a demo

Billing and Reimbursement Guidance for Bipolar Disorder Coding

F31.9 is a billable ICD-10-CM code and pairs with standard behavioral health CPT codes. The most commonly used CPT codes alongside F31.9 include:

• 90837 (Psychotherapy, 60 minutes) for individual therapy encounters
• 90834 (Psychotherapy, 45 minutes) for standard individual sessions
• 90792 (Psychiatric diagnostic evaluation with medical services) for initial assessments
• 99213 / 99214 (Office/outpatient E&M) when medication management is the primary service

Payer policies on unspecified codes vary. Some commercial payers accept F31.9 without additional documentation for a limited number of encounters before requiring specificity. Medicare does not maintain a blanket restriction on unspecified diagnosis codes, but local coverage determinations for behavioral health services may impose additional requirements depending on the MAC jurisdiction.

Practices billing F31.9 should use claims management software capable of flagging encounters where an unspecified code persists beyond a configured number of visits. This allows billing teams to prompt provider queries before claims are submitted, reducing the risk of prospective denials. The CDC/NCHS ICD-10-CM web tool provides the official code descriptions and tabular list notes that support medical necessity documentation for payer requests.

Insurance reimbursement rates for F31.9 follow the standard behavioral health fee schedules applicable to the paired CPT code, not the diagnosis code itself. The diagnosis supports medical necessity; the procedure code drives reimbursement. Using digital intake forms that capture a structured symptom history at the first visit makes it easier for clinicians to document the episode specificity that supports a more granular F31.x code on subsequent encounters.

Transitioning from F31.9 to More Specific Bipolar Disorder Codes

The goal of using F31.9 is temporary clarity, not permanent convenience. As a patient’s clinical picture develops across encounters, the documentation should reflect growing specificity, and the code selection should follow.

Three clinical triggers should prompt a coder or provider to revisit the F31.9 assignment:

1. A documented manic or hypomanic episode: Once the nature of the elevated-mood episode is established, codes F31.0 through F31.2x become available.
2. Confirmed depressive episode polarity: Bipolar disorder with a current depressive episode maps to F31.3x through F31.5, depending on severity.
3. Ruling out Bipolar I in favor of Bipolar II: When clinical history confirms hypomanic-only elevation with no full mania, F31.81 replaces F31.9.

Behavioral health practices benefit from a structured review workflow. Setting a clinical milestone (for example, after the third encounter or after a mood charting period of four to six weeks) to review whether the diagnosis can be specified further reduces the audit risk associated with sustained unspecified coding. A therapy practice management platform with encounter-level flags can automate this review trigger.

Ethically, clinicians should resist the temptation to use F31.9 indefinitely simply to avoid documentation effort. The DSM-5 criteria for bipolar disorder subtypes are well-defined, and sustained unspecified coding when the clinical picture has clarified may misrepresent the patient’s actual diagnosis in insurance and health records systems.

Expert Picks

Need a structured psychiatric assessment framework? Psychiatric Evaluation Template provides a step-by-step guide for documenting the clinical detail that supports specific F31.x code selection.

Managing a mental health practice workflow? Mental Health EMR covers how Pabau’s documentation tools help behavioral health teams maintain code-ready clinical records.

Looking for AI-assisted documentation? Pabau Scribe helps clinicians generate structured clinical notes that capture the episode specificity ICD-10-CM coding requires.

Conclusion

F31.9 serves a legitimate function in behavioral health coding, but it is a transitional code, not a default. Practices that use it correctly, with documented clinical justification and a clear plan for specificity upgrades, minimize denial risk and demonstrate coding integrity under payer review.

Pabau’s psychiatry EMR software gives behavioral health teams the structured documentation tools, automated claims flags, and digital intake workflows needed to keep F31.9 usage defensible and transition to more specific codes as the clinical picture develops. Book a demo to see how Pabau supports accurate bipolar disorder coding from first encounter through ongoing care.

Frequently Asked Questions