Skip to content

Slot: Target Concept Vocabulary (target_concept_vocabulary)

The downstream health-data vocabulary that target_concept_id and concept_status refer to, e.g. omop (OHDSI Standardised Vocabulary), bdc (BioData Catalyst). Names the vocabulary so the schema privileges no single health-data layer.

Tier: recommended

Why this slot matters

target_concept_id and concept_status are meaningless without knowing which vocabulary they refer to; naming it explicitly keeps the record portable across health-data layers (OMOP, BDC, ...) instead of silently assuming one.

In plain terms

Health databases each keep their own catalogue of codes for the things they record. This slot says which catalogue the record's health-data code (and its status) comes from — for example the OMOP catalogue used by many hospital research databases.

URI: envar:slot/target_concept_vocabulary

Applicable Classes

Name Description Modifies Slot
VariableIdentity The identity and semantics of an environmental exposure variable — what physi... no

Properties

Type and Range

Property Value
Range String
Domain Of VariableIdentity

Cardinality and Requirements

Property Value

Examples

Value
omop

See Also

Identifier and Mapping Information

Annotations

property value
tier recommended
justification target_concept_id and concept_status are meaningless without knowing which vocabulary they refer to; naming it explicitly keeps the record portable across health-data layers (OMOP, BDC, ...) instead of silently assuming one.
explanation Health databases each keep their own catalogue of codes for the things they record. This slot says which catalogue the record's health-data code (and its status) comes from — for example the OMOP catalogue used by many hospital research databases.
covered_by None

Schema Source

Mappings

Mapping Type Mapped Value
self envar:target_concept_vocabulary
native envar:target_concept_vocabulary

LinkML Source

name: target_concept_vocabulary
annotations:
  tier:
    tag: tier
    value: recommended
  justification:
    tag: justification
    value: '`target_concept_id` and `concept_status` are meaningless without knowing
      which vocabulary they refer to; naming it explicitly keeps the record portable
      across health-data layers (OMOP, BDC, ...) instead of silently assuming one.'
  explanation:
    tag: explanation
    value: Health databases each keep their own catalogue of codes for the things
      they record. This slot says which catalogue the record's health-data code (and
      its status) comes from — for example the OMOP catalogue used by many hospital
      research databases.
  covered_by:
    tag: covered_by
    annotations:
      omop_gaia:
        tag: omop_gaia
        annotations:
          extent:
            tag: extent
            value: full
          status:
            tag: status
            value: verified
          where:
            tag: where
            value: external_exposure.exposure_concept_id + exposure_type_concept_id
              (32885) + unit_concept_id (8653) — OMOP vocabulary is the implicit target
          evidence:
            tag: evidence
            value: EnVar/examples/heat/COMPARISON.md §D (Exposure concept / variable
              identity — ✅ for GAIA)
          note:
            tag: note
            value: The OMOP CDM is the target vocabulary itself; the concept slots
              land the value against OHDSI concept ids.
      degauss:
        tag: degauss
        annotations:
          extent:
            tag: extent
            value: absent
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: no column
          note:
            tag: note
            value: DeGAUSS emits a bare `tmax` value with no target-vocabulary binding.
      amadeus:
        tag: amadeus
        annotations:
          extent:
            tag: extent
            value: absent
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: no column
          note:
            tag: note
            value: Amadeus carries no target-vocabulary binding; the variable is implicit
              in the `tmmx` column name.
      cher:
        tag: cher
        annotations:
          extent:
            tag: extent
            value: absent
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: no column
          note:
            tag: note
            value: C-HER's controlled vocabs (DCMI Type, IANA media types) describe
              resource type/format, not a downstream health-data target vocabulary
              for the variable.
      codata:
        tag: codata
        annotations:
          extent:
            tag: extent
            value: out_of_layer
          status:
            tag: status
            value: asserted
          where:
            tag: where
            value: no column
          note:
            tag: note
            value: Binding to a downstream health-data layer is an instance/target
              concern; CODATA aligns concepts across standards but names no single
              target vocabulary.
description: The downstream health-data vocabulary that `target_concept_id` and `concept_status`
  refer to, e.g. `omop` (OHDSI Standardised Vocabulary), `bdc` (BioData Catalyst).
  Names the vocabulary so the schema privileges no single health-data layer.
title: Target Concept Vocabulary
examples:
- value: omop
  description: OHDSI Standardised Vocabulary (OMOP CDM)
from_schema: https://w3id.org/linkml/microschemas/envar
see_also:
- https://athena.ohdsi.org/
- https://biodatacatalyst.nhlbi.nih.gov/
rank: 1000
domain_of:
- VariableIdentity
range: string