This feature is coming soon and is not yet available in the current API version.
Overview
This endpoint will provide intelligent autocomplete functionality for medical terminology searches. It will offer real-time suggestions as users type, helping them find the correct medical terms quickly and accurately. The system will understand medical context, abbreviations, and common spelling patterns to provide relevant suggestions.Query Parameters
Partial search query for autocompletion (minimum 2 characters)
Target vocabularies for suggestions (comma-separated)
Examples:
Examples:
SNOMED
, ICD10CM,LOINC
, RXNORM,NDC
Filter suggestions to specific domains (comma-separated)
Examples:
Examples:
Condition,Procedure
, Drug,Device
Filter to specific concept classes (comma-separated)
Types of suggestions to include (comma-separated)
Options:
Options:
exact
, fuzzy
, semantic
, phonetic
, abbreviation
, all
Autocomplete completion strategy
Options:
Options:
prefix
, substring
, fuzzy
, semantic
, balanced
Medical specialty context for suggestions
Examples:
Examples:
cardiology
, oncology
, pediatrics
, emergency_medicine
User type for suggestion personalization
Options:
Options:
physician
, nurse
, pharmacist
, researcher
, patient
, student
, psychiatrist
Include synonyms in suggestions
Include medical abbreviations and acronyms
Include brief definitions with suggestions
Include usage frequency information
Boost recently searched terms
Boost commonly used medical terms
Enable personalized suggestions based on user history
Minimum usage frequency for suggestions (integer count). This maps to the normalized frequency_score (0.0-1.0) in responses. Higher frequency counts result in higher frequency_scores through logarithmic normalization.
Tolerance for fuzzy matching (0.0-1.0)
Language for suggestions (ISO 639-1 code)
Regional variant for terminology preferences
Examples:
Examples:
US
, UK
, AU
, CA
Filter by standard concept status:
S
, N
, C
Include invalid/deprecated concepts
Maximum number of suggestions to return (max 50)
Maximum response time in milliseconds (for real-time UX)
Note: 100ms applies only to highly optimized self-hosted stacks. Benchmark p50/p95 latency under realistic load. Third-party providers often exceed 500ms so adjust expectations accordingly.
Note: 100ms applies only to highly optimized self-hosted stacks. Benchmark p50/p95 latency under realistic load. Third-party providers often exceed 500ms so adjust expectations accordingly.
Specific vocabulary release version (defaults to latest)
Response
Indicates if the request was successful
Usage Examples
Basic Autocomplete
Get basic suggestions for a partial query:Medical Specialty Context
Get suggestions tailored to a medical specialty:Multi-Type Suggestions
Include different types of suggestions:Real-Time Autocomplete
Optimize for real-time user experience:Personalized Suggestions
Get personalized suggestions based on user context:Domain-Specific Autocomplete
Focus suggestions on specific medical domains:Completion Modes
Prefix Mode
- Description: Matches terms that start with the query
- Best For: Traditional autocomplete behavior
- Performance: Fastest
- Example: “diab” → “diabetes”, “diabetic”
Substring Mode
- Description: Matches terms containing the query anywhere
- Best For: Finding terms when users know partial words
- Performance: Fast
- Example: “card” → “myocardial”, “pericardium”
Fuzzy Mode
- Description: Tolerates typos and spelling variations
- Best For: Handling user input errors
- Performance: Moderate
- Example: “diabetis” → “diabetes”, “diabetic”
Semantic Mode
- Description: Finds conceptually related terms
- Best For: Discovering related medical concepts
- Performance: Slower
- Example: “heart attack” → “myocardial infarction”, “coronary syndrome”
Balanced Mode
- Description: Combines multiple strategies with weighting
- Best For: General-purpose autocomplete
- Performance: Moderate
- Example: Uses all approaches with intelligent scoring
Suggestion Types
Exact Suggestions
- Description: Direct prefix or substring matches
- Confidence: High
- Use Case: User knows the beginning of the term
- Examples: “diab” → “diabetes”, “diabetic”
Fuzzy Suggestions
- Description: Matches with spelling tolerance
- Confidence: Medium to High
- Use Case: User has typos or spelling variations
- Examples: “pnemonia” → “pneumonia”
Semantic Suggestions
- Description: Conceptually related terms
- Confidence: Medium
- Use Case: Discovery and exploration
- Examples: “chest pain” → “angina”, “myocardial infarction”
Phonetic Suggestions
- Description: Matches based on pronunciation
- Confidence: Medium
- Use Case: Voice input or pronunciation-based search
- Examples: “noomonia” → “pneumonia”
Abbreviation Suggestions
- Description: Medical abbreviations and acronyms
- Confidence: High
- Use Case: Professional medical communication
- Examples: “MI” → “myocardial infarction”, “DM” → “diabetes mellitus”
User Context Optimization
Physician Context
- Priority: Standard medical terminology
- Include: Technical terms, abbreviations
- Exclude: Lay terms, simplified language
- Example: Prefer “myocardial infarction” over “heart attack”
Nurse Context
- Priority: Clinical terms with patient care focus
- Include: Nursing-specific terminology, care procedures
- Exclude: Highly technical research terms
- Example: Include “medication administration”, “patient assessment”
Pharmacist Context
- Priority: Drug-related terminology
- Include: Medication names, drug interactions, dosages
- Exclude: Surgical procedures, diagnostic terms
- Example: Emphasize drug names, pharmaceutical terminology
Researcher Context
- Priority: Technical and research terminology
- Include: Research methods, statistical terms, technical concepts
- Exclude: Patient-facing language
- Example: Include “biomarkers”, “clinical endpoints”
Patient Context
- Priority: Patient-friendly terminology
- Include: Lay terms, simplified explanations
- Exclude: Complex medical jargon
- Example: Prefer “heart attack” over “myocardial infarction”
Student Context
- Priority: Educational terminology with explanations
- Include: Basic concepts with definitions
- Exclude: Highly specialized terms
- Example: Include terms with educational definitions
Performance Features
Real-Time Optimization
- Target Response Time: <100ms for optimal UX
- Caching Strategy: Aggressive caching of popular queries
- Index Optimization: Pre-computed suggestions for common prefixes
- Load Balancing: Distributed processing for high traffic
Intelligent Caching
- Query Pattern Cache: Common medical term prefixes
- User-Specific Cache: Personalized suggestion cache
- Frequency-Based Cache: Cache popular medical terms
- Context-Aware Cache: Specialty-specific suggestion cache
Progressive Enhancement
- Minimum Query Length: 2 characters for performance
- Graduated Complexity: Simple suggestions first, complex later
- Quality Thresholds: Filter low-quality suggestions
- Response Size Limits: Optimal payload size for speed
Related Endpoints
- Basic Search - Execute full search with completed term
- Fuzzy Search - Handle typos in completed searches
- Semantic Search - Meaning-based search
- Search Suggest - Alternative query suggestions