Skip to main content
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-01",
    "valid_end_date": "2099-12-31",
    "invalid_reason": null,
    "synonyms": [
      "Primary hypertension",
      "Idiopathic hypertension",
      "High blood pressure",
      "HTN - Hypertension"
    ],
    "mappings": [
      {
        "target_concept_id": 435216,
        "target_concept_name": "Essential hypertension",
        "target_concept_code": "I10",
        "target_vocabulary_id": "ICD10CM",
        "relationship_id": "Maps to",
        "mapping_type": "equivalent"
      }
    ]
  },
  "meta": {
    "request_id": "req_concept_code_123",
    "timestamp": "2024-12-22T10:00:00Z",
    "vocab_release": "2025.2"
  }
}

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-01",
    "valid_end_date": "2099-12-31",
    "invalid_reason": null,
    "synonyms": [
      "Primary hypertension",
      "Idiopathic hypertension",
      "High blood pressure",
      "HTN - Hypertension"
    ],
    "mappings": [
      {
        "target_concept_id": 435216,
        "target_concept_name": "Essential hypertension",
        "target_concept_code": "I10",
        "target_vocabulary_id": "ICD10CM",
        "relationship_id": "Maps to",
        "mapping_type": "equivalent"
      }
    ]
  },
  "meta": {
    "request_id": "req_concept_code_123",
    "timestamp": "2024-12-22T10:00:00Z",
    "vocab_release": "2025.2"
  }
}

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.
I