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

# Get Concept by Code

## 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

<ParamField path="vocabulary_id" type="string" required>
  The vocabulary identifier (e.g., "SNOMED", "ICD10CM", "LOINC")
</ParamField>

<ParamField path="concept_code" type="string" required>
  The vocabulary-specific code (e.g., "59621000" for SNOMED, "I10" for ICD10CM)
</ParamField>

<RequestExample>
  ```bash cURL theme={null}
  curl -X GET "https://api.omophub.com/v1/concepts/by-code/SNOMED/59621000" \
    -H "Authorization: Bearer YOUR_API_KEY"
  ```

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

  response = requests.get(
      "https://api.omophub.com/v1/concepts/by-code/SNOMED/59621000",
      headers={"Authorization": "Bearer YOUR_API_KEY"}
  )
  concept = response.json()
  ```

  ```javascript JavaScript theme={null}
  const response = await fetch('https://api.omophub.com/v1/concepts/by-code/SNOMED/59621000', {
    headers: {
      'Authorization': 'Bearer YOUR_API_KEY'
    }
  });
  const concept = await response.json();
  ```

  ```bash cURL (ICD10CM) theme={null}
  curl -X GET "https://api.omophub.com/v1/concepts/by-code/ICD10CM/I10" \
    -H "Authorization: Bearer YOUR_API_KEY"
  ```

  ```python Python (ICD10CM) theme={null}
  import requests

  response = requests.get(
      "https://api.omophub.com/v1/concepts/by-code/ICD10CM/I10",
      headers={"Authorization": "Bearer YOUR_API_KEY"}
  )
  icd_concept = response.json()
  ```
</RequestExample>

<ResponseExample>
  ```json Response theme={null}
  {
    "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"
    }
  }
  ```

  ```json Response (with details) theme={null}
  {
    "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,
      "synonyms": [
        "Primary hypertension",
        "Idiopathic hypertension",
        "High blood pressure"
      ],
      "relationships": {
        "parents": [
          {
            "concept_id": 316866,
            "concept_name": "Hypertensive disorder",
            "relationship_id": "Is a"
          }
        ],
        "children": [
          {
            "concept_id": 4124681,
            "concept_name": "Accelerated hypertension",
            "relationship_id": "Subsumes"
          }
        ]
      }
    },
    "meta": {
      "request_id": "req_concept_code_123",
      "timestamp": "2024-12-22T10:00:00Z",
      "vocab_release": "2025.2"
    }
  }
  ```
</ResponseExample>

## Response Fields

| Field               | Type    | Description                                                             |
| ------------------- | ------- | ----------------------------------------------------------------------- |
| `concept_id`        | integer | Unique concept identifier                                               |
| `concept_name`      | string  | Human-readable concept name                                             |
| `concept_code`      | string  | Vocabulary-specific code                                                |
| `vocabulary_id`     | string  | Source vocabulary identifier                                            |
| `domain_id`         | string  | Clinical domain (Condition, Drug, etc.)                                 |
| `concept_class_id`  | string  | Concept classification within vocabulary                                |
| `standard_concept`  | string  | "S" (Standard), "C" (Classification), or null                           |
| `valid_start_date`  | string  | ISO 8601 timestamp when concept became valid                            |
| `valid_end_date`    | string  | ISO 8601 timestamp when concept expires                                 |
| `invalid_reason`    | string  | Reason for deprecation, or null if valid                                |
| `is_valid`          | boolean | Whether concept is currently valid (not expired)                        |
| `is_standard`       | boolean | Whether concept is a standard concept                                   |
| `is_classification` | boolean | Whether concept is a classification concept                             |
| `synonyms`          | array   | List of synonym names (only when `include_synonyms=true`)               |
| `relationships`     | object  | Parent and child relationships (only when `include_relationships=true`) |

## Query Parameters

<ParamField query="vocab_release" type="string">
  Specific vocabulary release to use (e.g., "2025.2"). Uses latest if not specified.
</ParamField>

<ParamField query="include_synonyms" type="boolean" default="false">
  Include concept synonyms in the response
</ParamField>

<ParamField query="include_relationships" type="boolean" default="false">
  Include concept relationships and mappings
</ParamField>

<ParamField query="include_hierarchy" type="boolean" default="false">
  Include concept hierarchy information
</ParamField>

<ParamField query="include_invalid" type="boolean" default="true">
  Include concepts with invalid\_reason set (deprecated/updated concepts).
  Set to false to only return valid concepts.
</ParamField>

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