ClickCease

Other Sexual Disorders

ICD-10 code F66 covers various psychological and behavioral sexual disorders related to sexual orientation and development, but these codes are excluded from ICD-11 as of 2022, reflecting updated clinical perspectives and human rights considerations.

How ICD-10 F66 codes show up in behavioral health documentation

ICD-10 code family F66 is labeled “Other sexual disorders” and includes several codes related to psychosexual development, sexual maturation, sexual relationship concerns, and unspecified psychosexual development concerns [source:1]. In behavioral health documentation, these codes require careful wording because the clinical focus should be the client’s distress, impairment, presenting concern, goals, and treatment needs—not pathologizing sexual orientation or identity.

For clinicians in the United States, diagnosis selection remains the provider’s responsibility. AutoNotes can help create structured, editable documentation drafts, but it does not assign diagnoses or replace clinical judgment. If an F66 code appears in a record, referral, superbill, or historical chart, the note should clearly support the clinical rationale and avoid language that treats identity itself as a disorder.

The ICD system is used internationally to classify diseases and health conditions for reporting, research, and health data comparison [source:5]. In the U.S., ICD-10-CM is the clinical modification used for diagnosis coding in healthcare settings [source:3]. That coding context matters, but a progress note still needs to read like a clinical record: what brought the client to care, what was assessed, what interventions were provided, how the client responded, and what happens next.

The F66 code family and what each code describes

The F66 category includes five ICD-10 codes. Clinicians may encounter them in older records, payer documentation, referral paperwork, or legacy electronic health record fields. The presence of a code in a system does not mean it is clinically appropriate for every case.

  • F66.0 Sexual maturation disorder: Related to distress or uncertainty about sexual maturation or orientation during development [source:1].
  • F66.1 Egodystonic sexual orientation: Historically used when a person’s sexual orientation was experienced as unwanted or in conflict with the person’s self-concept [source:1].
  • F66.2 Sexual relationship disorder: Related to concerns in a sexual relationship connected to sexual orientation or psychosexual development [source:1].
  • F66.8 Other psychosexual development disorders: Used for other specified psychosexual development concerns that do not fit the previous codes [source:1].

A fifth code, F66.9 Psychosexual development disorder, unspecified, is used when the documentation does not specify the type of psychosexual development concern [source:1]. Unspecified codes can be appropriate in limited circumstances, but they often require clear support in the clinical narrative, especially if more specific information is available after assessment.

These codes should be handled with care. Research and policy work related to ICD-11 raised concerns about classifying distress related to sexual orientation as a mental disorder, and ICD-11 removed the F66 categories [source:2]. For current documentation, that history reinforces a practical point: describe the client’s actual symptoms, distress, functional impact, relational concerns, safety issues, and treatment goals. Do not document sexual orientation or identity as the clinical problem.

Why ICD-11 removed these categories, and why clinicians may still see them

ICD-11 went into effect internationally on January 1, 2022, and the F66 “psychological and behavioural disorders associated with sexual development and orientation” categories from ICD-10 were not retained [source:2]. The change reflected updated evidence, clinical practice concerns, and human rights considerations related to sexual orientation and gender diversity [source:2].

Clinicians in the U.S. may still encounter ICD-10-CM codes because U.S. healthcare billing and reporting systems continue to rely on ICD-10-CM for diagnosis coding. ICD-10-CM was adopted for covered healthcare transactions in 2015, and national implementation of a new coding system requires major updates to payers, health IT systems, datasets, and reporting workflows [source:4].

This creates a documentation challenge. A clinician might see an F66 code in a past diagnosis list, but current clinical practice may call for a different assessment focus. For example, a client may present with anxiety related to family rejection, religious conflict, relationship stress, trauma history, minority stress, or depressive symptoms. The note should document the clinically assessed condition and the client’s treatment needs, not simply carry forward an outdated label.

Documentation should focus on distress, impairment, and treatment need

Strong documentation starts with the client’s presenting concern. If sexual development, sexual relationships, identity-related stress, or internal conflict is part of the session, the note should capture what the client reported and how it affects functioning.

Useful clinical details may include:

  • Client’s own words about the concern, when clinically relevant
  • Onset, duration, intensity, and frequency of distress
  • Functional impact at home, work, school, relationships, or community settings
  • Current symptoms such as anxiety, depressed mood, shame, avoidance, conflict, or sleep disruption

Risk and safety documentation may also be needed. If the client reports suicidal ideation, self-harm urges, coercion, abuse, exploitation, intimate partner violence, or unsafe sexual situations, the note should reflect assessment, protective factors, safety planning, mandated reporting considerations when applicable, and follow-up steps.

Use neutral, clinically precise language. For instance, instead of writing “client has abnormal sexual concerns,” a stronger note might state: “Client reported increased anxiety and sleep disturbance after conflict with family regarding sexual orientation. Client identified fear of rejection as a primary trigger and denied current suicidal ideation.” That wording identifies symptoms, context, and safety status without treating orientation as pathology.

SOAP and DAP note examples for F66-related documentation contexts

Clinicians often need a practical way to translate sensitive session content into a progress note. The structure depends on the practice setting, payer expectations, and clinician preference, but the clinical elements are similar.

SOAP note documentation example

Subjective: Client reported feeling “confused and ashamed” after recent relationship conflict and family pressure related to sexual identity. Client described increased rumination, reduced appetite, and difficulty concentrating at work over the past two weeks.

Objective: Client appeared tearful at times, maintained appropriate eye contact, and was engaged throughout session. Speech was normal in rate and tone. No psychotic symptoms observed. Client denied current suicidal or homicidal ideation.

Assessment: Client presents with anxiety symptoms and relational distress connected to family rejection and internal conflict. Symptoms appear to be affecting work focus and sleep. Clinician continued assessment of mood, anxiety, supports, coping skills, and safety.

Plan: Continue weekly therapy. Practice grounding exercise before family contact. Explore values, support system, and boundaries in next session. Client agreed to contact crisis support or emergency services if safety concerns emerge.

DAP note documentation example

Data: Client discussed distress about sexual relationship concerns and fear of partner rejection. Client reported avoiding conversations with partner, increased muscle tension, and difficulty sleeping. Clinician provided validation, psychoeducation on anxiety responses, and guided client through identifying communication goals.

Assessment: Client showed insight into avoidance pattern and identified fear of abandonment as a key trigger. No acute safety concerns reported. Symptoms remain moderate and appear linked to relationship stress and self-criticism.

Plan: Client will draft talking points for partner conversation and practice paced breathing before discussion. Next session will review outcome, coping response, and treatment goal progress.

Treatment planning considerations for sensitive sexual health concerns

Treatment planning should connect the client’s stated goals with measurable clinical targets. For F66-related documentation contexts, the treatment plan may focus on anxiety reduction, mood stabilization, relationship communication, identity integration, trauma recovery, boundary setting, or coping with stigma and rejection.

Examples of treatment plan goals include:

  • Reduce anxiety symptoms related to relationship or family conflict from daily to three times per week over 90 days.
  • Increase use of coping skills before and after difficult conversations, as reported in session.
  • Identify three affirming supports and create a plan for safe contact during periods of distress.
  • Improve communication with partner by practicing one planned conversation strategy between sessions.

Interventions should be documented in a way that shows the clinician’s work. Depending on scope of practice and modality, this may include CBT techniques, acceptance and commitment therapy exercises, emotion regulation skills, psychoeducation, trauma-informed grounding, motivational interviewing, safety planning, couples work, or referral coordination.

The plan should also show continuity. If the client’s distress changes, update the treatment plan. If the diagnosis changes after assessment, document the clinical basis for that change. If an F66 code appears in historical records but is not clinically appropriate for current care, the clinician may need to clarify the active diagnosis list according to practice policy and payer requirements.

Common documentation mistakes to avoid

Because F66 codes carry historical and ethical complexity, small wording choices matter. Notes should be clinically useful, respectful, and tied to assessed symptoms.

  • Do not treat orientation or identity as the problem. Document distress, symptoms, impairment, relational conflict, trauma, stigma, or safety concerns instead.
  • Do not copy forward old codes without review. Historical diagnoses may not reflect the current clinical picture.
  • Do not use vague phrases such as “sexual issues.” State the clinically relevant concern in neutral language.
  • Do not let the code carry the note. The narrative should support medical necessity, treatment focus, and progress.

Documentation also needs to separate client report from clinician assessment. “Client reported fear that family will reject them” is different from “family rejection is causing the disorder.” Clear attribution helps protect accuracy and keeps the note grounded in what was assessed during the session.

How AutoNotes supports clinician-controlled documentation

AutoNotes helps behavioral health professionals create structured, editable progress note drafts from session details. For sensitive topics such as sexual development, identity-related stress, relationship concerns, or sexual health discussions, structure can help clinicians avoid vague wording and make sure key elements are covered.

AutoNotes does not choose the diagnosis for the clinician. Instead, it supports the documentation workflow around the clinician’s assessment. A therapist can enter clinically relevant session details, select a note format such as SOAP or DAP, and review a draft that organizes interventions, client response, progress toward goals, and plan details.

Compared with writing every note from a blank page, AI-assisted drafts can give clinicians a faster starting point. Compared with generic AI writing tools, AutoNotes is built around behavioral health documentation needs, including progress notes, intake documentation, assessments, treatment plans, and service-specific templates. The clinician still reviews, edits, and finalizes the note before it becomes part of the record.

For F66-related documentation contexts, that review step is essential. Clinicians can refine language, remove assumptions, add risk assessment details, clarify treatment goals, and make sure the note reflects current clinical judgment.

Build clearer progress notes without giving up clinical control

F66 codes may still appear in ICD-10-CM workflows, but documentation should be current, respectful, and clinically specific. Focus on the client’s symptoms, distress, functional impact, safety, interventions, response, and plan. Diagnosis selection belongs to the clinician, and the note should support the clinician’s reasoning.

AutoNotes gives therapists, counselors, social workers, psychologists, psychiatrists, and other behavioral health professionals a structured way to draft notes faster while keeping final review in their hands. If documentation is taking over evenings or creating inconsistent records, start your free trial and see how editable AI-assisted note drafts can fit into your clinical workflow.

Finish notes in
minutes, not hours.

AutoNotes makes documentation fast, easy, and stress-free — so you can focus on what matters, your clients.

No credit card required

See the Magic in Action

Auto-generate notes in seconds

SOAP Note Snippet

Ready to Spend Less Time on Documentation?

Generate progress notes, treatment plans, intake assessments, and more in seconds with AI built for behavioral health clinicians.