Skip to main content

​
Overview

Retrieve concept information using the vocabulary-specific code instead of the universal concept ID. This is useful when working with source data that contains original codes.

​
Path Parameters

​
vocabulary_id
string
required
The vocabulary identifier (e.g., “SNOMED”, “ICD10CM”, “LOINC”)
​
concept_code
string
required
The vocabulary-specific code (e.g., “59621000” for SNOMED, “I10” for ICD10CM)
curl -X GET "https://api.omophub.com/v1/concepts/by-code/SNOMED/59621000" \
  -H "Authorization: Bearer YOUR_API_KEY"

{
  "success": true,
  "data": {
    "concept_id": 320128,
    "concept_name": "Essential hypertension",
    "concept_code": "59621000",
    "vocabulary_id": "SNOMED",
    "domain_id": "Condition",
    "concept_class_id": "Clinical Finding",
    "standard_concept": "S",
    "valid_start_date": "1970-01-01T00:00:00.000Z",
    "valid_end_date": "2099-12-31T00:00:00.000Z",
    "invalid_reason": null,
    "is_valid": true,
    "is_standard": true,
    "is_classification": false
  },
  "meta": {
    "request_id": "req_concept_code_123",
    "timestamp": "2024-12-22T10:00:00Z",
    "vocab_release": "2025.2"
  }
}

​
Response Fields

FieldTypeDescription
concept_idintegerUnique concept identifier
concept_namestringHuman-readable concept name
concept_codestringVocabulary-specific code
vocabulary_idstringSource vocabulary identifier
domain_idstringClinical domain (Condition, Drug, etc.)
concept_class_idstringConcept classification within vocabulary
standard_conceptstring”S” (Standard), “C” (Classification), or null
valid_start_datestringISO 8601 timestamp when concept became valid
valid_end_datestringISO 8601 timestamp when concept expires
invalid_reasonstringReason for deprecation, or null if valid
is_validbooleanWhether concept is currently valid (not expired)
is_standardbooleanWhether concept is a standard concept
is_classificationbooleanWhether concept is a classification concept
synonymsarrayList of synonym names (only when include_synonyms=true)
relationshipsobjectParent and child relationships (only when include_relationships=true)

​
Query Parameters

​
vocab_release
string
Specific vocabulary release to use (e.g., “2025.2”). Uses latest if not specified.
​
include_synonyms
boolean
default:"false"
Include concept synonyms in the response
​
include_relationships
boolean
default:"false"
Include concept relationships and mappings
​
include_hierarchy
boolean
default:"false"
Include concept hierarchy information

​
Common Use Cases

​
1. Source Data Processing

Convert source system codes to standardized concepts during ETL processes.

​
2. Legacy System Integration

Map existing codes from legacy healthcare systems.

​
3. Claims Processing

Look up diagnosis and procedure codes from insurance claims.

​
4. Clinical Documentation

Validate codes entered by healthcare providers.