A chart that says “depression NOS” may still show F32.9 because an older code mapping or copied diagnosis survived the introduction of F32.A. In current U.S. ICD-10-CM, depression NOS and major depression NOS have different reference entries, so the first check is the provider’s actual diagnosis wording. A mismatch calls for record review, not an automatic code replacement.
This walkthrough is for coders, billers and documentation staff reconciling a diagnosis label with a code. It does not diagnose depression, select treatment or assign a final code to an encounter. The examples are constructed illustrations, not patient records or claims that we audited.
What the current wording distinction means
“NOS” means not otherwise specified, but the words before it still matter. Depression NOS leaves the depressive diagnosis unspecified; major depression NOS explicitly names major depression. Treating those phrases as interchangeable can add specificity that the provider did not document or remove specificity that the provider did document.
The official FY2027 Index and Tabular List separate these entries. Start with the complete diagnosis in the Alphabetic Index, then verify the Tabular List and all applicable instructions. The reference table below shows the distinction; it is not a substitute for reviewing the full encounter.
Swipe horizontally to compare the full table on a small screen.
| Documented phrase | Reference entry | What still needs checking |
|---|---|---|
| Depression NOS / depressive disorder NOS | F32.A — Depression, unspecified | Whether the diagnosis is current and reportable, and whether more specific provider documentation exists. |
| Major depression NOS | F32.9 — Major depressive disorder, single episode, unspecified | The complete diagnosis, episode information and any documented severity or remission detail. |
| Recurrent MDD, unspecified | F33.9 — Major depressive disorder, recurrent, unspecified | Whether recurrence is actually established in provider documentation; repeated visits alone do not establish it. |
Why depression NOS can still appear as F32.9
The historical route explains why this mismatch deserves a closer look. In the FY2021 Tabular List, F32.9 included depression NOS and depressive disorder NOS alongside major depression NOS. F32.A was introduced in FY2022, effective 1 October 2021, separating unspecified depression from that major-depression entry.
That change did not make every existing F32.9 entry incorrect. A legacy encounter must be assessed under its applicable release, while current documentation may genuinely establish major depression. The useful question is whether the code reflects the right wording for the right encounter and code year.
An EHR mapping may retain the older association
A diagnosis picker can display a familiar phrase while sending a different code downstream. One possible explanation is an older terminology-to-code association that was never revised, but that needs system evidence. Ask the coding or informatics lead to inspect the selected term, its stored code and the release used by the mapping.
Test a suspected mapping issue through the organization’s authorized workflow using synthetic records. Compare the diagnosis picker, saved assessment, problem list and claim export rather than assuming they all carry the same value. A screenshot of the displayed phrase is useful context, but it does not show every transformation between the note and the claim.
A copied problem list can hide the origin
An old entry may be carried into later visits without a fresh description of what it means. Its date, original author and diagnostic wording matter when staff are deciding whether it reflects the current encounter. A carried-forward label should be reconciled with current documentation under the organization’s record and reporting policies.
For example, a historical list may say depression NOS while a current assessment clearly establishes recurrent major depressive disorder. In that situation, changing the code merely because the historical label is shorter would introduce a different error. Conversely, a code attached to an old list does not establish a current major-depression diagnosis by itself.
A four-line documentation check
Read the four pieces together before deciding what needs escalation. The purpose is to distinguish a wording issue, a release issue and a genuine documentation conflict. None of these checks gives permission to infer a diagnosis from symptoms or to rebill from this article.
- Current diagnosis: locate the provider’s complete diagnostic statement, including modifiers, rather than relying on a truncated display label.
- Code and source: identify the stored or submitted code and whether it originated in the assessment, diagnosis picker, copied list or another system.
- Applicable release: establish the release for the encounter, using outpatient service dates or inpatient discharge dates as applicable.
- Record agreement: determine whether provider statements are consistent, incomplete or conflicting, then use the appropriate coding/CDI review process.
Four examples that lead to different reviews
These brief examples intentionally leave out patient details and clinical findings. They illustrate which documentation question changes the review, rather than providing a code assignment for a real chart. Any actual query must use the relevant facts from the actual record.
Swipe horizontally to compare the full table on a small screen.
| Illustrative fragment | Review implication | Next check |
|---|---|---|
| “Depression NOS” in the current assessment; F32.9 shown | For FY2027, the unspecified-depression reference entry differs from the displayed code. | Check for established MDD elsewhere, an outdated mapping or conflicting documentation. |
| “Major depression NOS”; F32.9 shown | The diagnosis phrase and reference entry may align. | Verify the full record and any more specific episode, severity or remission information. |
| Old “depression NOS” list; current “MDD, recurrent, unspecified” | The current diagnosis adds recurrence; the old list cannot resolve the encounter alone. | Reconcile the record and verify the documented recurrent-MDD entry. |
| “Depression” in one current statement; “major depressive disorder” in another | Potential ambiguity or conflict cannot be resolved by choosing the shorter phrase. | Use a record-specific clarification process if review does not resolve the discrepancy. |
The first example is a review flag because F32.9 carries a major-depression description. It is not proof of incorrect billing: a fuller diagnosis elsewhere may explain the selection. A defensible review records what was checked and what documentation supports the eventual decision.
When F32.9 may still be appropriate
F32.9 remains a current code; the introduction of F32.A did not retire it. Its inclusion term includes major depression NOS, and its description identifies single-episode major depressive disorder with unspecified detail. Do not strip away a documented major-depression diagnosis simply to make the code match a shorter display label.
A repeated prescription, several visits or an old episode does not let this page decide that the disorder is recurrent. Equally, a PHQ-9 score alone does not establish the provider’s diagnosis, episode pattern or reportable code. Code assignment follows the diagnostic statement and applicable rules, not a conversion of a screening number into a diagnosis.
The Official Guidelines for Coding and Reporting base diagnosis code assignment on provider documentation and direct clarification when medical-record documentation conflicts. They also distinguish uncertain outpatient diagnoses from certain qualifying inpatient discharge diagnoses. Confirm the setting before applying a rule about a diagnosis described as possible, probable or suspected.
See the wording before reviewing the code
Keep the phrase comparison visible while you trace the record. The word “major” carries information that “depression NOS” does not, and recurrence adds another distinction. The illustration below keeps those two NOS phrases separate without treating either one as a complete coding decision.

Trace where the mismatch started
When a discrepancy appears, work back from the exported code to the stored diagnosis and then to the provider’s assessment. That sequence helps separate a system mapping from a documentation disagreement. It also prevents a display-label correction from being mistaken for a correction to the underlying clinical record.
An informatics review and a provider clarification address different problems. A mapping defect needs system investigation; a genuine diagnostic disagreement needs the appropriate documentation process. Both may be involved, but neither should be assumed from this illustration.

Use Record Clarity to identify the next check
Choose the documented phrase, displayed code, applicable release and record state. Record Clarity returns a documentation review summary, with conflicts and unverified releases taking priority over a phrase comparison. It uses no patient text and gives no final code, payer approval or reimbursement conclusion.
Documentation before the claim
Record Clarity
Find the next check when a note and a code do not match.
Educational reference only. This check does not diagnose, assign a final code, validate a claim, or establish coverage. Use the full record, applicable code year and qualified coding review. Do not enter patient information.
Depression NOS and major depression NOS have different reference entries. A copied label, a conflicting assessment or the wrong code year needs review before any correction.
Choose all four inputs to see the next documentation check.
Method and limits
Reference entries were checked in the official FY2027 Index and Tabular List on 7 October 2026. Branches prioritize record conflicts and unverified code years. Matching labels are not proof that a diagnosis is reportable. No symptom scores, patient text, browser storage, analytics or external API requests are used.
For a mismatch result, retrieve the full diagnosis and investigate the code source before escalating. For an aligned result, continue the usual review of specificity, reportability and applicable instructions. The optional A4 sheet is a compact handoff checklist, not a coding authorization or part of a patient chart.
What a provider clarification can ask
If clarification is needed, state the actual documentation issue neutrally. Identify the relevant record statements and their sources, then ask the provider to clarify the diagnosis using independent clinical judgment. An open wording approach can ask which diagnosis is established for the encounter, with any episode or other detail the provider can determine.
For a conflict, an illustrative question is: “The assessment and problem list use different diagnosis wording. Based on your clinical evaluation and the relevant record information, please clarify the diagnosis for this encounter, or indicate if it cannot be determined.” This is an educational wording example; the actual record indicators, sources and organizational policy must be supplied through the authorized query workflow.
The 2026 AHIMA/ACDIS query guidance is the current professional reference for developing that process. Avoid asking for major depression simply to fit a code or payment outcome. A generic prompt cannot certify that a record-specific query meets the organization’s requirements.

What this page cannot decide
A code description does not establish a patient’s severity, the appropriate treatment or whether an insurer will cover a service. This page also does not determine risk adjustment, medical necessity or the validity of a denial. Those decisions need the relevant record, setting, payer requirements and qualified professional review.
Keep other diagnoses outside this narrow comparison rather than forcing them into one of its entries. Bipolar diagnoses, PMDD and other specified depressive presentations require their own complete lookup and review. If the wording does not fit the limited phrases here, stop the comparison and use the appropriate diagnostic entry.
Frequently asked questions
Is depression NOS the same code as major depression NOS?
No. The FY2027 reference entry for depression NOS is F32.A, while major depression NOS is an inclusion term at F32.9. Those reference entries do not replace review of the complete diagnosis and encounter.
When did F32.A take effect?
F32.A was introduced for FY2022, effective 1 October 2021. Do not apply it retrospectively to an encounter governed by a release in which it did not exist. Verify the release applicable to the service or discharge date.
Can a coder change F32.9 to F32.A without a query?
This page cannot authorize that change. A qualified coder must review the complete documentation, applicable release and organizational correction policy. Conflicting or unresolved diagnostic documentation may need provider clarification; a blog comparison alone is insufficient.
Does depressive disorder NOS have the F32.A reference entry?
Yes. The FY2027 Tabular List includes depressive disorder NOS at F32.A. More specific or conflicting provider documentation still needs review before assigning a code to the encounter.
What if the note says depression and the problem list says MDD?
Review the origin, timing and current relevance of both statements. Do not automatically treat either the shorter label or the copied list as the controlling diagnosis. Use the organization’s clarification process when the record remains ambiguous or conflicting.
Does a PHQ-9 score by itself pick the code?
No. A screening score alone does not supply the provider’s diagnosis or establish episode and severity documentation for coding. Review the diagnostic statement and applicable guidelines rather than selecting a code from the number.
The wording check to keep
Before changing a depression code, establish what the provider documented, which release applies and whether the record agrees. F32.A helps distinguish unspecified depression from major depression, but it does not resolve an incomplete or contradictory chart. Use the mismatch to guide review, then leave the final coding decision with the qualified reviewer.


