Skip to main content

Overview

This lightweight endpoint quickly determines whether a concept has any relationships to other concepts. This is useful for UI components, validation logic, or filtering concepts that are isolated vs. connected in the terminology network.

Path Parameters

conceptId
integer
required
The unique OMOP concept ID to check for relationships

Query Parameters

relationship_types
string
Comma-separated list of relationship types to check (e.g., “Maps to”, “Is a”)
vocabulary_ids
string
Comma-separated list of vocabulary IDs to limit relationship check
include_reverse
boolean
default:"true"
Include reverse relationships (concepts that relate to this concept)
include_invalid
boolean
default:"true"
Include relationships to invalid/deprecated concepts
vocab_release
string
Specific vocabulary release version (e.g., “2024.1”)

Response

success
boolean
required
Indicates whether the request was successful
data
object
required
Response data containing relationship check results
meta
object
required
Response metadata and API information

Usage Examples

Simple Relationship Check

Check if a concept has any relationships:

Check for Standard Mappings

Check if concept has “Maps to” relationships:

Check Cross-Vocabulary Relations

Check relationships to specific vocabularies:

Batch Checking in Applications

Use in loops or batch processing to filter connected concepts:
TypeScript

Important Notes

  • Performance optimized - Much faster than fetching full relationship data
  • Filtering support - All the same filters as the full relations endpoint
  • UI integration - Perfect for showing relationship icons or badges
  • Batch processing - Ideal for filtering large concept lists
  • Standard mappings - The has_standard_mappings flag is useful for data quality checks