F88 vs F89
F89 — Unspecified disorder of psychological development
Distinguish the residual 'other' category for developmental disorders (F88, a genuine but atypically-patterned developmental disorder that does not fit F80-F84) from the residual 'unspecified' category (F89, used when a developmental disorder is present but the available information does not support any further specification), reinforcing the same 'other versus unspecified' reasoning pattern used across the rest of this application's other block-level residual pairs.
This is just for your own thinking. It is never submitted, sent, or stored anywhere — it disappears the moment you leave or reload this page.
Show overlap — what both share
Both are residual categories used when a developmental disorder does not cleanly fit F80-F84, and both can be reached for as a default when a vignette does not obviously match a specific named category.
Show decisive evidence
- F88 is used when a developmental disorder is present with a genuine, identifiable pattern of features that nonetheless does not fit any of the named F80-F84 categories.
- F89 is used when a developmental disorder is present, but the information actually available is not sufficient to identify even an atypical specific pattern.
- A vignette with enough clinical detail to describe a specific, if unusual, developmental pattern that still does not match F80-F84 favours F88.
- A vignette confirming a developmental disorder is present but genuinely lacking the detail needed to characterise its pattern at all favours F89.
What weakens F88: The presence of enough detail to describe an atypical but identifiable pattern weakens F89 in favour of F88; a genuine absence of that detail, not merely a vignette that requires closer reading, weakens F88 in favour of F89.
Show duration / course
Both require a developmental (not acquired) onset consistent with the F80-F89 block generally; neither is defined by a distinct duration or course requirement of its own beyond that shared developmental-onset framing.
Show exclusions / context
F89 should never be used as a shortcut for a vignette that is simply effortful to work through when the detail needed to specify a pattern is actually present — the same reasoning already captured in this application's existing 'unspecified as default' misconception, reused here.
Show information still needed
Whether the vignette provides enough detail to describe a specific, even if atypical, developmental pattern (F88), or whether that detail is genuinely unavailable (F89).
Show the common trap
Reaching for the unspecified code (F89) because a vignette's atypical pattern does not immediately map onto a familiar named category, rather than checking whether the detail given is actually sufficient to describe that atypical pattern under F88.
Mini challenge — practise this distinction
Apply the discriminating evidence above to a fresh case before checking the full feedback.