Slot: Concept Status (concept_status)
Status of this variable's coverage in the target health-data vocabulary (existing / proposed / gap). Makes the vocabulary gap explicit rather than silent. Required.
Tier: core
Why this slot matters
A downstream system must know whether to expect a concept id. The explicit existing/proposed/gap status makes vocabulary gaps visible and countable rather than silently null — which is what drives vocabulary-extension requests for environmental variables.
In plain terms
A simple status flag saying whether the health-data catalogue already has a code for this measurement, has one in the works, or has nothing yet. It turns a silent gap into an explicit, reportable fact.
URI: envar:slot/concept_status
Applicable Classes
| Name |
Description |
Modifies Slot |
| VariableIdentity |
The identity and semantics of an environmental exposure variable — what physi... |
yes |
Properties
Type and Range
Cardinality and Requirements
Examples
Annotations
| property |
value |
| tier |
core |
| justification |
A downstream system must know whether to expect a concept id. The explicit existing/proposed/gap status makes vocabulary gaps visible and countable rather than silently null — which is what drives vocabulary-extension requests for environmental variables. |
| explanation |
A simple status flag saying whether the health-data catalogue already has a code for this measurement, has one in the works, or has nothing yet. It turns a silent gap into an explicit, reportable fact. |
| covered_by |
None |
Schema Source
Mappings
| Mapping Type |
Mapped Value |
| self |
envar:concept_status |
| native |
envar:concept_status |
LinkML Source
name: concept_status
annotations:
tier:
tag: tier
value: core
justification:
tag: justification
value: A downstream system must know whether to expect a concept id. The explicit
existing/proposed/gap status makes vocabulary gaps visible and countable rather
than silently null — which is what drives vocabulary-extension requests for
environmental variables.
explanation:
tag: explanation
value: A simple status flag saying whether the health-data catalogue already has
a code for this measurement, has one in the works, or has nothing yet. It turns
a silent gap into an explicit, reportable fact.
covered_by:
tag: covered_by
annotations:
omop_gaia:
tag: omop_gaia
annotations:
extent:
tag: extent
value: absent
status:
tag: status
value: asserted
where:
tag: where
value: no column
note:
tag: note
value: GAIA fills a placeholder exposure_concept_id but carries no existing/proposed/gap
status flag saying whether a real OMOP concept exists — an EnVar-novel
slot.
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 has no concept binding and so no coverage-status flag.
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 has no concept binding and so no coverage-status flag.
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 carries no existing/proposed/gap coverage status for a target
vocabulary.
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: A gap-status flag against a target vocabulary is instance/target
bookkeeping, outside CODATA's conceptual-alignment layer.
description: Status of this variable's coverage in the target health-data vocabulary
(`existing` / `proposed` / `gap`). Makes the vocabulary gap explicit rather than
silent. Required.
title: Concept Status
examples:
- value: gap
description: no OMOP concept exists yet for daily Tmax
from_schema: https://w3id.org/linkml/microschemas/envar
rank: 1000
domain_of:
- VariableIdentity
range: ConceptStatusEnum