> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omophub.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Search Suggest

> Get intelligent search suggestions and alternative query recommendations based on user intent, medical context, and search patterns.

## Overview

This endpoint provides intelligent search suggestions and query recommendations to help users refine their medical terminology searches. It analyzes user queries, medical context, and search patterns to suggest alternative search terms, related concepts, and improved query formulations.

## Query Parameters

<ParamField query="query" type="string" required>
  Original search query for which suggestions are needed
</ParamField>

<ParamField query="vocabulary_ids" type="string">
  Target vocabularies for suggestions (comma-separated)

  <br />

  **Examples**: `SNOMED`, `ICD10CM,LOINC`, `RXNORM,NDC`
</ParamField>

<ParamField query="domain_ids" type="string">
  Filter suggestions to specific domains (comma-separated)

  <br />

  **Examples**: `Condition,Procedure`, `Drug,Device`
</ParamField>

<ParamField query="concept_class_ids" type="string">
  Filter to specific concept classes (comma-separated)
</ParamField>

<ParamField query="suggestion_types" type="string" default="all">
  Types of suggestions to include (comma-separated)

  <br />

  **Options**: `spelling`, `synonym`, `related`, `broader`, `narrower`, `alternative`, `trending`, `popular`, `all`
</ParamField>

<ParamField query="medical_context" type="string">
  Medical specialty context for relevant suggestions

  <br />

  **Examples**: `cardiology`, `oncology`, `pediatrics`, `emergency_medicine`
</ParamField>

<ParamField query="user_context" type="string">
  User type for suggestion personalization

  <br />

  **Options**: `physician`, `nurse`, `pharmacist`, `researcher`, `patient`, `student`
</ParamField>

<ParamField query="search_intent" type="string">
  Detected or specified search intent

  <br />

  **Options**: `diagnostic`, `therapeutic`, `procedural`, `research`, `educational`, `administrative`
</ParamField>

<ParamField query="include_corrections" type="boolean" default="true">
  Include spelling corrections and typo fixes
</ParamField>

<ParamField query="include_alternatives" type="boolean" default="true">
  Include alternative phrasings and synonyms
</ParamField>

<ParamField query="include_related" type="boolean" default="true">
  Include conceptually related terms
</ParamField>

<ParamField query="include_hierarchical" type="boolean" default="true">
  Include broader and narrower concepts
</ParamField>

<ParamField query="include_trending" type="boolean" default="false">
  Include trending medical terms
</ParamField>

<ParamField query="include_popular" type="boolean" default="true">
  Include popular search terms
</ParamField>

<ParamField query="include_explanations" type="boolean" default="false">
  Include explanations for why suggestions are relevant
</ParamField>

<ParamField query="personalization" type="boolean" default="false">
  Enable personalized suggestions based on user history
</ParamField>

<ParamField query="cultural_context" type="string">
  Cultural or regional context for suggestions

  <br />

  **Examples**: `US`, `UK`, `international`, `multicultural`
</ParamField>

<ParamField query="language" type="string" default="en">
  Language for suggestions (ISO 639-1 code)
</ParamField>

<ParamField query="complexity_level" type="string" default="balanced">
  Preferred complexity level for suggestions

  <br />

  **Options**: `simple`, `intermediate`, `advanced`, `technical`, `balanced`
</ParamField>

<ParamField query="patient_facing" type="boolean" default="false">
  Whether suggestions should be patient-appropriate
</ParamField>

<ParamField query="standard_concept" type="string">
  Filter by standard concept status: `S`, `N`, `C`
</ParamField>

<ParamField query="include_invalid" type="boolean" default="true">
  Include suggestions for invalid/deprecated concepts
</ParamField>

<ParamField query="page" type="integer" default="1">
  Page number (1-based indexing)
</ParamField>

<ParamField query="page_size" type="integer" default="20">
  Number of suggestions to return per page (max 100)
</ParamField>

<ParamField query="relevance_threshold" type="number" default="0.6">
  Minimum relevance score for suggestions (0.0-1.0)
</ParamField>

<ParamField query="vocab_release" type="string">
  Specific vocabulary release version (defaults to latest)
</ParamField>

## Response

<ResponseField name="success" type="boolean">
  Indicates if the request was successful
</ResponseField>

<ResponseField name="data" type="object">
  <Expandable title="Search Suggestions">
    <ResponseField name="query" type="string">
      Original search query
    </ResponseField>

    <ResponseField name="query_analysis" type="object">
      <Expandable title="Query Analysis">
        <ResponseField name="detected_intent" type="string">
          Automatically detected search intent
        </ResponseField>

        <ResponseField name="confidence" type="number">
          Confidence in intent detection (0.0-1.0)
        </ResponseField>

        <ResponseField name="query_quality" type="string">
          Assessment of query quality (Excellent, Good, Fair, Poor)
        </ResponseField>

        <ResponseField name="medical_concepts" type="array">
          Medical concepts identified in the query
        </ResponseField>

        <ResponseField name="potential_issues" type="array">
          Potential issues with the query
        </ResponseField>

        <ResponseField name="improvement_opportunities" type="array">
          Ways the query could be improved
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="suggestions" type="object">
      <Expandable title="Suggestion Categories">
        <ResponseField name="spelling_corrections" type="array">
          Spelling and typo corrections

          <Expandable title="Spelling Correction">
            <ResponseField name="original" type="string">
              Original potentially misspelled term
            </ResponseField>

            <ResponseField name="correction" type="string">
              Suggested correction
            </ResponseField>

            <ResponseField name="confidence" type="number">
              Confidence in the correction (0.0-1.0)
            </ResponseField>

            <ResponseField name="correction_type" type="string">
              Type of correction (typo, spelling, grammar)
            </ResponseField>

            <ResponseField name="explanation" type="string">
              Explanation of the correction (if include\_explanations=true)
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="synonyms" type="array">
          Synonym suggestions

          <Expandable title="Synonym Suggestion">
            <ResponseField name="original_term" type="string">
              Original term from query
            </ResponseField>

            <ResponseField name="synonym" type="string">
              Suggested synonym
            </ResponseField>

            <ResponseField name="relevance_score" type="number">
              Relevance score (0.0-1.0)
            </ResponseField>

            <ResponseField name="concept_id" type="integer">
              Associated concept ID (if applicable)
            </ResponseField>

            <ResponseField name="vocabulary_id" type="string">
              Source vocabulary
            </ResponseField>

            <ResponseField name="usage_context" type="string">
              Typical usage context
            </ResponseField>

            <ResponseField name="formality_level" type="string">
              Level of formality (Technical, Clinical, Lay)
            </ResponseField>

            <ResponseField name="explanation" type="string">
              Why this synonym is relevant (if include\_explanations=true)
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="related_concepts" type="array">
          Conceptually related suggestions

          <Expandable title="Related Concept Suggestion">
            <ResponseField name="suggested_term" type="string">
              Suggested related term
            </ResponseField>

            <ResponseField name="relationship_type" type="string">
              Type of relationship (associated, causes, treats, etc.)
            </ResponseField>

            <ResponseField name="relevance_score" type="number">
              Relevance score (0.0-1.0)
            </ResponseField>

            <ResponseField name="concept_id" type="integer">
              Concept ID
            </ResponseField>

            <ResponseField name="vocabulary_id" type="string">
              Source vocabulary
            </ResponseField>

            <ResponseField name="domain_id" type="string">
              Domain classification
            </ResponseField>

            <ResponseField name="clinical_context" type="string">
              Clinical context or use case
            </ResponseField>

            <ResponseField name="explanation" type="string">
              Relationship explanation (if include\_explanations=true)
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="broader_concepts" type="array">
          More general concept suggestions

          <Expandable title="Broader Concept Suggestion">
            <ResponseField name="suggested_term" type="string">
              Suggested broader term
            </ResponseField>

            <ResponseField name="hierarchy_level" type="integer">
              Levels up in hierarchy
            </ResponseField>

            <ResponseField name="relevance_score" type="number">
              Relevance score (0.0-1.0)
            </ResponseField>

            <ResponseField name="concept_id" type="integer">
              Concept ID
            </ResponseField>

            <ResponseField name="vocabulary_id" type="string">
              Source vocabulary
            </ResponseField>

            <ResponseField name="generalization_type" type="string">
              Type of generalization (category, class, system)
            </ResponseField>

            <ResponseField name="use_case" type="string">
              When to use this broader term
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="narrower_concepts" type="array">
          More specific concept suggestions

          <Expandable title="Narrower Concept Suggestion">
            <ResponseField name="suggested_term" type="string">
              Suggested narrower term
            </ResponseField>

            <ResponseField name="hierarchy_level" type="integer">
              Levels down in hierarchy
            </ResponseField>

            <ResponseField name="relevance_score" type="number">
              Relevance score (0.0-1.0)
            </ResponseField>

            <ResponseField name="concept_id" type="integer">
              Concept ID
            </ResponseField>

            <ResponseField name="vocabulary_id" type="string">
              Source vocabulary
            </ResponseField>

            <ResponseField name="specialization_type" type="string">
              Type of specialization (subtype, specific case, variant)
            </ResponseField>

            <ResponseField name="clinical_specificity" type="string">
              Level of clinical specificity
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="alternative_phrasings" type="array">
          Alternative ways to phrase the query

          <Expandable title="Alternative Phrasing">
            <ResponseField name="alternative_query" type="string">
              Alternative query phrasing
            </ResponseField>

            <ResponseField name="phrasing_type" type="string">
              Type of alternative (formal, informal, technical, lay)
            </ResponseField>

            <ResponseField name="appropriateness_score" type="number">
              Appropriateness score (0.0-1.0)
            </ResponseField>

            <ResponseField name="target_audience" type="string">
              Intended audience for this phrasing
            </ResponseField>

            <ResponseField name="expected_results" type="integer">
              Expected number of search results
            </ResponseField>

            <ResponseField name="advantages" type="array">
              Advantages of this phrasing
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="trending_suggestions" type="array">
          Trending medical terms related to the query

          <Expandable title="Trending Suggestion">
            <ResponseField name="suggested_term" type="string">
              Trending term
            </ResponseField>

            <ResponseField name="trend_score" type="number">
              Trend strength score (0.0-1.0)
            </ResponseField>

            <ResponseField name="trend_context" type="string">
              Context for the trend (research, clinical, news)
            </ResponseField>

            <ResponseField name="relevance_to_query" type="number">
              Relevance to original query (0.0-1.0)
            </ResponseField>

            <ResponseField name="trend_duration" type="string">
              How long it's been trending
            </ResponseField>

            <ResponseField name="specialty_focus" type="array">
              Medical specialties driving the trend
            </ResponseField>
          </Expandable>
        </ResponseField>

        <ResponseField name="popular_suggestions" type="array">
          Popular search terms related to the query

          <Expandable title="Popular Suggestion">
            <ResponseField name="suggested_term" type="string">
              Popular term
            </ResponseField>

            <ResponseField name="popularity_score" type="number">
              Popularity score (0.0-1.0)
            </ResponseField>

            <ResponseField name="search_volume" type="string">
              Relative search volume (High, Medium, Low)
            </ResponseField>

            <ResponseField name="user_base" type="string">
              Primary user base for this term
            </ResponseField>

            <ResponseField name="seasonal_pattern" type="string">
              Seasonal usage pattern (if applicable)
            </ResponseField>

            <ResponseField name="stability" type="string">
              Stability of popularity (Stable, Growing, Declining)
            </ResponseField>
          </Expandable>
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="contextual_recommendations" type="object">
      <Expandable title="Contextual Recommendations">
        <ResponseField name="search_strategy" type="string">
          Recommended search strategy
        </ResponseField>

        <ResponseField name="vocabulary_recommendations" type="array">
          Recommended vocabularies for this query
        </ResponseField>

        <ResponseField name="domain_focus" type="array">
          Recommended domains to focus on
        </ResponseField>

        <ResponseField name="filter_suggestions" type="array">
          Suggested filters to apply
        </ResponseField>

        <ResponseField name="search_tips" type="array">
          General search tips for this type of query
        </ResponseField>
      </Expandable>
    </ResponseField>

    <ResponseField name="personalization_insights" type="object">
      Personalized recommendations (if personalization=true)

      <Expandable title="Personalization Insights">
        <ResponseField name="user_patterns" type="array">
          Detected user search patterns
        </ResponseField>

        <ResponseField name="preferred_vocabularies" type="array">
          User's preferred vocabularies
        </ResponseField>

        <ResponseField name="common_domains" type="array">
          User's commonly searched domains
        </ResponseField>

        <ResponseField name="suggested_specialties" type="array">
          Suggested medical specialties based on history
        </ResponseField>

        <ResponseField name="learning_opportunities" type="array">
          Suggested learning opportunities
        </ResponseField>
      </Expandable>
    </ResponseField>
  </Expandable>
</ResponseField>

<ResponseField name="meta" type="object">
  <Expandable title="Metadata">
    <ResponseField name="request_id" type="string">
      Unique identifier for the request
    </ResponseField>

    <ResponseField name="timestamp" type="string">
      Request timestamp
    </ResponseField>

    <ResponseField name="suggestion_engine_version" type="string">
      Suggestion engine version
    </ResponseField>

    <ResponseField name="total_suggestions" type="integer">
      Total number of suggestions returned
    </ResponseField>

    <ResponseField name="processing_time_ms" type="integer">
      Time taken to generate suggestions
    </ResponseField>

    <ResponseField name="personalization_applied" type="boolean">
      Whether personalization was used
    </ResponseField>

    <ResponseField name="context_factors" type="array">
      Contextual factors influencing suggestions
    </ResponseField>

    <ResponseField name="vocab_release" type="string">
      Vocabulary release version used
    </ResponseField>
  </Expandable>
</ResponseField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X GET "https://api.omophub.com/v1/search/suggest?query=hart%20atack&vocabulary_ids=SNOMED,ICD10CM&suggestion_types=spelling,synonym,related&medical_context=cardiology&include_explanations=true" \
    -H "Authorization: Bearer YOUR_API_KEY" \
    -H "Content-Type: application/json"
  ```

  ```javascript JavaScript theme={null}
  const response = await fetch('https://api.omophub.com/v1/search/suggest?query=diabetis&user_context=physician&include_corrections=true&include_alternatives=true&include_related=true&include_hierarchical=true', {
    method: 'GET',
    headers: {
      'Authorization': 'Bearer YOUR_API_KEY',
      'Content-Type': 'application/json'
    }
  });

  const data = await response.json();
  ```

  ```python Python theme={null}
  import requests

  headers = {
      'Authorization': 'Bearer YOUR_API_KEY',
      'Content-Type': 'application/json'
  }

  params = {
      'query': 'chest pain breathing problems',
      'vocabulary_ids': 'SNOMED,ICD10CM',
      'domain_ids': 'Condition,Procedure',
      'suggestion_types': 'spelling,synonym,related,broader,narrower',
      'medical_context': 'emergency_medicine',
      'user_context': 'physician',
      'search_intent': 'diagnostic',
      'include_corrections': 'true',
      'include_alternatives': 'true',
      'include_related': 'true',
      'include_hierarchical': 'true',
      'include_trending': 'true',
      'include_explanations': 'true',
      'complexity_level': 'advanced',
      'page_size': 30,
      'relevance_threshold': 0.7
  }

  response = requests.get(
      'https://api.omophub.com/v1/search/suggest',
      headers=headers,
      params=params
  )

  data = response.json()
  ```
</RequestExample>

<ResponseExample>
  ```json Response theme={null}
  {
    "success": true,
    "data": {
      "query": "hart atack",
      "query_analysis": {
        "detected_intent": "diagnostic",
        "confidence": 0.89,
        "query_quality": "Poor",
        "medical_concepts": [
          {
            "concept": "heart attack",
            "confidence": 0.85,
            "issues": ["spelling error in 'hart'", "spelling error in 'atack'"]
          }
        ],
        "potential_issues": [
          "Multiple spelling errors detected",
          "Informal terminology used",
          "Could be more specific"
        ],
        "improvement_opportunities": [
          "Use correct spelling: 'heart attack'",
          "Consider medical terminology: 'myocardial infarction'",
          "Specify type: 'acute myocardial infarction'"
        ]
      },
      "suggestions": {
        "spelling_corrections": [
          {
            "original": "hart",
            "correction": "heart",
            "confidence": 0.95,
            "correction_type": "spelling",
            "explanation": "Common misspelling of 'heart' in medical queries"
          },
          {
            "original": "atack",
            "correction": "attack", 
            "confidence": 0.92,
            "correction_type": "spelling",
            "explanation": "Missing 't' in 'attack' - common typo"
          }
        ],
        "synonyms": [
          {
            "original_term": "heart attack",
            "synonym": "myocardial infarction",
            "relevance_score": 0.98,
            "concept_id": 22298006,
            "vocabulary_id": "SNOMED",
            "usage_context": "Clinical documentation",
            "formality_level": "Technical",
            "explanation": "Standard medical terminology for heart attack, preferred in clinical settings"
          },
          {
            "original_term": "heart attack",
            "synonym": "MI",
            "relevance_score": 0.92,
            "concept_id": 22298006,
            "vocabulary_id": "SNOMED",
            "usage_context": "Clinical abbreviation",
            "formality_level": "Clinical",
            "explanation": "Common clinical abbreviation for myocardial infarction"
          },
          {
            "original_term": "heart attack",
            "synonym": "acute coronary syndrome",
            "relevance_score": 0.85,
            "concept_id": 394659003,
            "vocabulary_id": "SNOMED",
            "usage_context": "Emergency medicine",
            "formality_level": "Clinical",
            "explanation": "Broader clinical term encompassing heart attacks and related conditions"
          }
        ],
        "related_concepts": [
          {
            "suggested_term": "angina pectoris",
            "relationship_type": "related_condition",
            "relevance_score": 0.87,
            "concept_id": 194828000,
            "vocabulary_id": "SNOMED",
            "domain_id": "Condition",
            "clinical_context": "Precursor or related chest pain condition",
            "explanation": "Related cardiac condition that can precede or mimic heart attack"
          },
          {
            "suggested_term": "coronary artery disease",
            "relationship_type": "underlying_cause",
            "relevance_score": 0.82,
            "concept_id": 53741008,
            "vocabulary_id": "SNOMED", 
            "domain_id": "Condition",
            "clinical_context": "Underlying pathology leading to heart attack",
            "explanation": "Primary underlying condition that causes most heart attacks"
          },
          {
            "suggested_term": "cardiac arrest",
            "relationship_type": "potential_complication",
            "relevance_score": 0.79,
            "concept_id": 410429000,
            "vocabulary_id": "SNOMED",
            "domain_id": "Condition",
            "clinical_context": "Serious complication of heart attack",
            "explanation": "Potential life-threatening complication of myocardial infarction"
          }
        ],
        "broader_concepts": [
          {
            "suggested_term": "cardiovascular disease",
            "hierarchy_level": 2,
            "relevance_score": 0.76,
            "concept_id": 49601007,
            "vocabulary_id": "SNOMED",
            "generalization_type": "system",
            "use_case": "For broader cardiovascular condition searches"
          },
          {
            "suggested_term": "heart disease",
            "hierarchy_level": 1,
            "relevance_score": 0.81,
            "concept_id": 56265001,
            "vocabulary_id": "SNOMED",
            "generalization_type": "category",
            "use_case": "For general cardiac condition searches"
          }
        ],
        "narrower_concepts": [
          {
            "suggested_term": "ST elevation myocardial infarction",
            "hierarchy_level": 1,
            "relevance_score": 0.89,
            "concept_id": 401314000,
            "vocabulary_id": "SNOMED",
            "specialization_type": "subtype",
            "clinical_specificity": "High - specific type based on ECG findings"
          },
          {
            "suggested_term": "non-ST elevation myocardial infarction",
            "hierarchy_level": 1,
            "relevance_score": 0.87,
            "concept_id": 401303003,
            "vocabulary_id": "SNOMED",
            "specialization_type": "subtype",
            "clinical_specificity": "High - specific type based on ECG findings"
          },
          {
            "suggested_term": "acute anterior myocardial infarction",
            "hierarchy_level": 1,
            "relevance_score": 0.84,
            "concept_id": 54329005,
            "vocabulary_id": "SNOMED",
            "specialization_type": "anatomical_location",
            "clinical_specificity": "Very High - location-specific type"
          }
        ],
        "alternative_phrasings": [
          {
            "alternative_query": "heart attack",
            "phrasing_type": "corrected_lay",
            "appropriateness_score": 0.95,
            "target_audience": "General public, patients",
            "expected_results": 234,
            "advantages": [
              "Correct spelling",
              "Widely understood",
              "Patient-friendly"
            ]
          },
          {
            "alternative_query": "myocardial infarction",
            "phrasing_type": "medical_technical",
            "appropriateness_score": 0.92,
            "target_audience": "Healthcare professionals",
            "expected_results": 187,
            "advantages": [
              "Precise medical terminology",
              "Preferred in clinical documentation",
              "Standardized term"
            ]
          },
          {
            "alternative_query": "acute MI",
            "phrasing_type": "clinical_abbreviation",
            "appropriateness_score": 0.87,
            "target_audience": "Clinical staff",
            "expected_results": 156,
            "advantages": [
              "Efficient clinical communication",
              "Commonly used abbreviation",
              "Time-saving"
            ]
          }
        ],
        "trending_suggestions": [
          {
            "suggested_term": "troponin elevation",
            "trend_score": 0.78,
            "trend_context": "diagnostic_biomarker",
            "relevance_to_query": 0.82,
            "trend_duration": "6 months",
            "specialty_focus": [
              "emergency_medicine",
              "cardiology"
            ]
          }
        ],
        "popular_suggestions": [
          {
            "suggested_term": "chest pain",
            "popularity_score": 0.94,
            "search_volume": "High",
            "user_base": "Healthcare professionals and patients",
            "seasonal_pattern": "Stable year-round",
            "stability": "Stable"
          },
          {
            "suggested_term": "cardiac symptoms",
            "popularity_score": 0.86,
            "search_volume": "Medium",
            "user_base": "Healthcare professionals",
            "seasonal_pattern": "None",
            "stability": "Stable"
          }
        ]
      },
      "contextual_recommendations": {
        "search_strategy": "Start with corrected spelling, then explore specific types if needed",
        "vocabulary_recommendations": [
          {
            "vocabulary": "SNOMED",
            "reason": "Comprehensive cardiac terminology",
            "priority": "High"
          },
          {
            "vocabulary": "ICD10CM",
            "reason": "Administrative coding and billing",
            "priority": "Medium"
          }
        ],
        "domain_focus": [
          "Condition",
          "Observation"
        ],
        "filter_suggestions": [
          {
            "filter": "domain=Condition",
            "reason": "Focus on diagnostic conditions"
          },
          {
            "filter": "specialty=cardiology",
            "reason": "Cardiac-specific context"
          }
        ],
        "search_tips": [
          "Use correct spelling for better results",
          "Try both lay terms and medical terminology",
          "Consider specific types (STEMI, NSTEMI) for detailed information",
          "Include related symptoms (chest pain, shortness of breath) for broader context"
        ]
      },
      "personalization_insights": null
    },
    "meta": {
      "request_id": "req_search_suggest_123",
      "timestamp": "2024-01-15T10:30:00Z",
      "suggestion_engine_version": "v3.1.0",
      "total_suggestions": 45,
      "processing_time_ms": 178,
      "personalization_applied": false,
      "context_factors": [
        "medical_context: cardiology",
        "spelling_errors_detected",
        "intent: diagnostic",
        "formality: mixed"
      ],
      "vocab_release": "2024.2"
    }
  }
  ```
</ResponseExample>

## Usage Examples

### Spelling Correction Suggestions

Get suggestions for queries with spelling errors:

```bash theme={null}
curl -X GET "https://api.omophub.com/v1/search/suggest?query=pnemonia&suggestion_types=spelling,synonym&include_corrections=true" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

### Comprehensive Query Suggestions

Get comprehensive suggestions for query improvement:

```bash theme={null}
curl -X GET "https://api.omophub.com/v1/search/suggest?query=diabetes&suggestion_types=all&medical_context=endocrinology&user_context=physician&include_explanations=true" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

### Alternative Phrasing Suggestions

Get alternative ways to phrase a medical query:

```bash theme={null}
curl -X GET "https://api.omophub.com/v1/search/suggest?query=high%20blood%20pressure&suggestion_types=alternative,synonym&complexity_level=technical&patient_facing=false" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

### Hierarchical Concept Suggestions

Get broader and narrower concept suggestions:

```bash theme={null}
curl -X GET "https://api.omophub.com/v1/search/suggest?query=pneumonia&suggestion_types=broader,narrower&include_hierarchical=true&vocabulary_ids=SNOMED" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

### Patient-Friendly Suggestions

Get patient-appropriate suggestions:

```bash theme={null}
curl -X GET "https://api.omophub.com/v1/search/suggest?query=myocardial%20infarction&user_context=patient&patient_facing=true&complexity_level=simple&include_alternatives=true" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

### Trending and Popular Suggestions

Get trending and popular related terms:

```bash theme={null}
curl -X GET "https://api.omophub.com/v1/search/suggest?query=covid&suggestion_types=trending,popular,related&include_trending=true&include_popular=true" \
  -H "Authorization: Bearer YOUR_API_KEY"
```

## Suggestion Types

### Spelling Corrections

* **Purpose**: Fix typos and spelling errors
* **Confidence**: High for obvious corrections
* **Use Case**: Improve query accuracy
* **Examples**: "hart" → "heart", "diabetis" → "diabetes"

### Synonyms

* **Purpose**: Alternative terms with same meaning
* **Formality Levels**: Technical, Clinical, Lay
* **Use Case**: Find standard terminology
* **Examples**: "heart attack" → "myocardial infarction"

### Related Concepts

* **Relationships**: Associated, causes, treats, complicates
* **Clinical Context**: Related conditions and procedures
* **Use Case**: Explore connected medical concepts
* **Examples**: "diabetes" → "insulin", "hyperglycemia"

### Broader Concepts

* **Hierarchy**: Move up concept hierarchies
* **Generalization**: Category, system, class level
* **Use Case**: Widen search scope
* **Examples**: "pneumonia" → "lung disease" → "respiratory condition"

### Narrower Concepts

* **Specialization**: Subtypes, variants, specific cases
* **Clinical Specificity**: Increase diagnostic precision
* **Use Case**: Get more specific results
* **Examples**: "diabetes" → "type 2 diabetes" → "insulin-resistant diabetes"

### Alternative Phrasings

* **Formality**: Formal, informal, technical, lay
* **Target Audience**: Professionals, patients, researchers
* **Use Case**: Reach different audiences
* **Examples**: "MI" vs "heart attack" vs "myocardial infarction"

### Trending Suggestions

* **Temporal**: Currently popular or emerging
* **Context**: Research, clinical practice, news
* **Use Case**: Discover emerging topics
* **Examples**: New treatments, recent outbreaks, research terms

### Popular Suggestions

* **Usage**: Commonly searched terms
* **Stability**: Stable, growing, or declining popularity
* **Use Case**: Find common related searches
* **Examples**: High-volume search terms

## Search Intent Detection

### Diagnostic Intent

* **Characteristics**: Symptom descriptions, condition names
* **Suggestions**: Differential diagnoses, related symptoms
* **Context**: Clinical assessment, patient evaluation
* **Examples**: "chest pain" → diagnostic conditions

### Therapeutic Intent

* **Characteristics**: Treatment queries, medication searches
* **Suggestions**: Treatment options, drug alternatives
* **Context**: Treatment planning, medication selection
* **Examples**: "diabetes treatment" → therapeutic options

### Procedural Intent

* **Characteristics**: Procedure names, intervention queries
* **Suggestions**: Related procedures, alternatives
* **Context**: Procedure selection, surgical planning
* **Examples**: "cardiac catheterization" → related procedures

### Research Intent

* **Characteristics**: Technical terms, study-related queries
* **Suggestions**: Research terminology, methodological terms
* **Context**: Academic research, literature review
* **Examples**: "biomarkers" → research concepts

### Educational Intent

* **Characteristics**: Learning-focused queries
* **Suggestions**: Educational resources, explanatory terms
* **Context**: Medical education, patient education
* **Examples**: "anatomy" → educational concepts

### Administrative Intent

* **Characteristics**: Coding, billing, documentation queries
* **Suggestions**: Administrative codes, documentation terms
* **Context**: Medical coding, billing processes
* **Examples**: "ICD codes" → administrative terminology

## Personalization Features

### User Pattern Analysis

* **Search History**: Commonly searched terms and domains
* **Vocabulary Preferences**: Preferred medical vocabularies
* **Specialty Focus**: Medical specialties of interest
* **Complexity Level**: Preferred terminology complexity

### Personalized Suggestions

* **Relevant Terms**: Terms matching user's interests
* **Vocabulary Bias**: Suggestions from preferred vocabularies
* **Specialty Context**: Specialty-specific recommendations
* **Learning Path**: Educational progression suggestions

### Privacy Considerations

* **Opt-in**: Personalization requires explicit consent
* **Data Security**: Secure storage of user patterns
* **Anonymization**: Personal data anonymization
* **User Control**: Users can disable personalization

## Cultural and Regional Context

### Regional Terminology

* **US Medical Terms**: American medical terminology preferences
* **UK Medical Terms**: British medical terminology variations
* **International**: WHO and international standard terms
* **Multicultural**: Inclusive terminology for diverse populations

### Cultural Sensitivity

* **Inclusive Language**: Culturally appropriate medical terms
* **Accessibility**: Terms accessible to diverse populations
* **Local Practices**: Regional medical practice variations
* **Language Variants**: Regional language preferences

## Related Endpoints

* [Search Autocomplete](/api-reference/search/search-autocomplete) - Real-time query completion
* [Basic Search](/api-reference/search/basic-search) - Execute suggested searches
* [Semantic Search](/api-reference/search/semantic-search) - Meaning-based search
* [Fuzzy Search](/api-reference/search/fuzzy-search) - Typo-tolerant search