F52.0 is the ICD-10-CM code commonly used for HSDD documentation
F52.0 refers to Hypoactive Sexual Desire Disorder in ICD-10-CM coding resources and sits within the F52 category for sexual dysfunction not due to a substance or known physiological condition [source:1]. For behavioral health clinicians, the code may appear in documentation related to individual therapy, couples work, sex therapy, psychiatric assessment, or care coordination with medical providers.
This guide is focused on documentation support. It does not assign a diagnosis, determine medical necessity, or replace clinical judgment. The clinician remains responsible for assessing the client, selecting any applicable diagnosis, confirming payer or organizational requirements, and finalizing the clinical record.
In practice, F52.0 documentation often needs to show more than “low desire.” A clear note usually describes the client’s reported concern, distress or interpersonal impact, relevant clinical context, interventions used during the session, and how treatment is connected to the client’s goals.
How F52.0 fits within sexual dysfunction documentation
The ICD-10-CM F52 code family covers sexual dysfunctions that are not attributed to a substance or known physiological condition [source:1]. That distinction matters for documentation. If the clinical picture includes medication effects, endocrine concerns, pain conditions, neurological issues, pregnancy or postpartum factors, substance use, or another medical contributor, the record may need to reflect referral, consultation, or additional assessment rather than assuming F52.0 is the best fit.
Clinicians may encounter low sexual desire in several documentation contexts:
- A client reports distress about reduced sexual interest within a long-term relationship.
- A couple presents with conflict related to mismatched desire, avoidance, or shame.
- A client describes low desire alongside depression, anxiety, trauma symptoms, grief, or high stress.
- A psychiatric or therapy note includes medication, health, or relationship factors that may affect sexual functioning.
The note should make the clinical reasoning visible without over-documenting sensitive details. Use client-centered language, avoid assumptions about what “normal” desire should look like, and document the concern in relation to distress, functioning, values, relational impact, and treatment goals.
Clinical details that support an HSDD-related note
Progress notes for sexual desire concerns should be specific enough to support continuity of care while respecting the client’s privacy. A useful note identifies what was assessed, what the client reported, what the clinician did, and what changed or needs follow-up.
Presenting concern and symptom pattern
Document the client’s own description of the concern. For example: “Client reported reduced sexual interest over the past year and stated this has contributed to avoidance of intimacy and increased conflict with partner.” That is more useful than a vague phrase such as “sexual problems discussed.”
When clinically relevant, include whether the concern appears lifelong or acquired, generalized or situational, persistent or episodic. If the client reports that desire changes only in specific relational contexts, under high stress, after medication changes, or during depressive episodes, document that context.
Distress, impairment, and relationship impact
Low desire alone may not be clinically significant for every client. Documentation should describe whether the client experiences distress, conflict, avoidance, shame, reduced self-esteem, relationship strain, or other functional impact. Use neutral language. For example: “Client reported distress related to desire discrepancy and described withdrawing from affectionate contact due to fear that it may lead to sexual expectations.”
Relevant biopsychosocial factors
Sexual desire concerns may intersect with mental health, relationship dynamics, trauma history, cultural or religious beliefs, body image, pain, medications, substance use, hormonal concerns, sleep, chronic illness, and life-stage changes. The note does not need to include every detail from the client’s sexual history. It should include factors that directly inform assessment, treatment planning, referral decisions, or risk considerations.
What to document during assessment and intake
During intake or assessment, clinicians often need a fuller record than they would include in a routine progress note. The assessment should show how the concern was evaluated and what information remains incomplete.
Consider documenting these areas when clinically appropriate:
- Client report: onset, duration, frequency, context, distress level, and client goals.
- Mental health context: mood symptoms, anxiety, trauma symptoms, grief, stress, body image, or self-worth concerns.
- Relationship context: communication patterns, conflict, consent, safety, intimacy expectations, and partner response.
- Medical coordination: medications, pain, hormonal concerns, chronic illness, substance use, or referral needs.
Assessment documentation should also reflect the clinician’s limits. A therapist may document that medical contributors were discussed and that the client was encouraged to consult a primary care provider, gynecologist, urologist, psychiatrist, or other qualified medical professional when indicated. This is especially relevant when symptoms may relate to medication side effects, endocrine changes, pain, or another medical factor.
Progress note language for F52.0-related sessions
A strong progress note connects the client’s concern to the session content and treatment plan. It does not need explicit sexual detail unless that information is clinically necessary. The goal is to create a record that another treating professional could understand without exposing more private information than needed.
SOAP note example
Subjective: Client reported ongoing low sexual desire and stated that the issue has contributed to tension with spouse. Client described feeling “pressured and guilty” when intimacy is discussed and reported avoiding conversations about sex due to fear of conflict.
Objective: Client was engaged and reflective during session. Affect appeared constricted when discussing relationship concerns. No acute safety concerns were reported during this session.
Assessment: Client continues to experience distress related to reduced sexual desire and relationship conflict. Session themes suggest anxiety, avoidance, and negative self-appraisal may be maintaining distress. Clinician used supportive reflection and cognitive restructuring to identify beliefs related to obligation, rejection, and self-worth.
Plan: Continue therapy focused on communication skills, reduction of avoidance, and values-based intimacy goals. Client will practice a planned conversation with spouse using agreed-upon boundaries. Clinician will revisit possible medical consultation if client reports continued concerns about medication, pain, or hormonal factors.
DAP note example
Data: Client discussed reduced sexual interest and reported that partner has interpreted this as rejection. Client identified increased stress, fatigue, and resentment related to household responsibilities as possible contributing factors. Clinician provided psychoeducation on desire variability and facilitated exploration of nonsexual intimacy and communication patterns.
Assessment: Client demonstrated insight into relational and emotional contributors to avoidance. Distress remains present, especially around guilt and perceived partner disappointment. Client was able to identify one specific boundary and one request to communicate before next session.
Plan: Continue work on communication, emotional regulation, and treatment goal related to increased comfort discussing intimacy. Assign brief reflection on situations where client feels connected versus pressured. Review progress and barriers next session.
Related ICD-10-CM codes may appear in the same documentation area
F52.0 is only one code within a broader sexual dysfunction category. Related codes may be relevant in some clinical records, depending on the clinician’s assessment and the client’s presentation. The following examples are for documentation context, not diagnosis assignment:
- F52.1: Sexual aversion disorder [source:1]
- F52.21: Male erectile disorder [source:1]
- F52.22: Female sexual arousal disorder [source:1]
- F52.31/F52.32: Female orgasmic disorder and male orgasmic disorder [source:1]
If multiple sexual functioning concerns are discussed, the note should distinguish the client’s primary complaint from secondary concerns. For example, a client may report low desire because of pain, performance anxiety, relationship conflict, medication changes, or fear of disappointing a partner. Clear documentation helps preserve that clinical nuance.
Treatment planning considerations for low sexual desire concerns
Treatment planning should connect the client’s stated goals with measurable clinical focus areas. Avoid goals that imply a required level of sexual activity. A more client-centered plan might focus on reducing distress, improving communication, increasing insight into desire patterns, addressing avoidance, or supporting informed medical consultation.
Examples of treatment plan targets include:
- Client will identify emotional, relational, and situational factors that affect sexual desire.
- Client will practice communication skills for discussing intimacy, boundaries, and expectations.
- Client will use coping strategies to reduce shame, anxiety, or avoidance linked to intimacy concerns.
- Client will coordinate with a medical provider if symptoms may be related to medication, pain, hormones, or health changes.
Interventions may include psychoeducation, CBT, emotion-focused interventions, mindfulness, sensate-focus-informed work, couples communication exercises, trauma-informed therapy, or referral for medical evaluation. The selected approach should match the clinician’s scope, training, client consent, and treatment goals.
Common documentation mistakes to avoid
HSDD-related documentation can become too vague or too detailed. Both create problems. Vague notes make it hard to show treatment focus. Overly explicit notes may expose sensitive information that is not needed for continuity of care.
Watch for these issues:
- Using labels without support: Document the client’s reported distress, impairment, and clinical context rather than relying only on the code name.
- Ignoring possible contributors: Note relevant mental health, relationship, medication, substance, medical, or trauma-related factors when they affect treatment.
- Overstating certainty: Use appropriate clinical language when assessment is ongoing or referral is needed.
- Skipping the plan: Include the next clinical step, such as communication practice, symptom tracking, treatment plan review, or medical coordination.
Good documentation is careful, not excessive. It gives enough information to support care while keeping the client’s dignity and privacy at the center of the record.
How AutoNotes supports clinician-controlled HSDD documentation
AutoNotes helps behavioral health professionals create structured, editable progress note drafts from session details. For sessions involving HSDD or other sexual functioning concerns, that structure can help clinicians organize sensitive material into a clear note format: presenting concern, interventions, client response, assessment, and plan.
AutoNotes does not choose diagnoses for clinicians. Diagnosis selection, clinical interpretation, editing, and final approval remain the provider’s responsibility. The platform is designed to give clinicians a faster starting point while keeping the final record under clinician control.
For HSDD-related documentation, clinicians can use AutoNotes to draft SOAP, DAP, intake, assessment, treatment plan, or progress note formats. This can be especially helpful after a full day of sessions when the clinician needs to capture nuanced information without spending unnecessary time rebuilding the note from scratch.
If you want a faster way to create structured, editable therapy note drafts, start your free trial and see how AutoNotes fits your documentation workflow.
