Guide

Guide | Reference

27  How to Use Prototypes

This chapter explains when prototypes help and when they mislead. Most useful for handoffs, communication, and billing.

Purpose. Provide practical rules for when and how to apply prototype labels. Keep prototypes optional, communication-focused, and DSM-compatible.

27.1 When to Use Prototypes

• When a recognizable pattern improves communication with clinicians, patients, or systems.
• When a label improves documentation clarity or billing alignment.
• When the pattern aligns with observed domains and time-course.

27.2 When Not to Use Prototypes

• When evidence is unclear or competing explanations dominate.
• When a label would reduce nuance or increase stigma.
• When acute rule-out conditions are unresolved.

27.3 How to Assign a Prototype (short workflow)

• Start with Atlas entry to confirm phenomenology.
• Rate relevant domains (0-4) and course.
• Apply the prototype tag only if it adds value.
• Record uncertainty or provisional status if needed.

27.4 Comorbidity and Overlap

• Overlap is expected; multiple prototypes can be used sparingly.
• Prefer domain ratings to convey complexity; use prototypes for shorthand only.

Documentation Output. Prototype tag(s) + confidence (high/medium/provisional). Linked domains and key specifiers.